Nonstop Database

HiRDB Version 9

Messages

3020-6-458-40(E)

Contents

Notices

Preface

1. Overview of Messages

1.1 Message output formats

1.2 Descriptive notation

2. Messages

2.1 KFPA messages

2.2 KFPC messages

2.3 KFPD messages

2.4 KFPH messages

2.5 KFPI messages

2.6 KFPJ messages

2.7 KFPK messages

2.8 KFPL messages

2.9 KFPM messages

2.10 KFPN messages

2.11 KFPO messages

2.12 KFPR messages

2.13 KFPS messages

2.14 KFPT messages

2.15 KFPU messages

2.16 KFPX messages

2.17 KFPY messages

2.18 KFPZ messages

3. ABORT Codes

3.1 ABORT Codes

4. Error Detail Codes

4.1 Detail codes for RPC-related errors

4.2 Detail codes for system-related errors

4.3 System call return codes

4.4 Communication error codes

5. HiRDB File System Error Codes

5.1 Error codes returned from HiRDB file system access requests

6. Lock Control Errors

6.1 Resource types, resource names, and resource information for lock control errors

7. Messages Related to Sort Processing

7.1 Messages related to sort processing (Windows edition)

7.1.1 Message format

7.1.2 Messages

7.2 Messages related to sort processing (UNIX edition)

7.2.1 Message format

7.2.2 Messages

8. SQLSTATE

8.1 SQLSTATE

8.1.1 When the PDSTANDARDSQLSTATE client environment variable is set to YES or the pd_standard_sqlstate system common definition is set to Y

8.1.2 When the PDSTANDARDSQLSTATE client environment variable is set to NO or the pd_standard_sqlstate system common definition is set to N

Index

[Trademarks]

All Rights Reserved. Copyright (C) 2011, 2014, Hitachi, Ltd.

Notices

Relevant program products

List of program products:
For the Red Hat Enterprise Linux AS 4 (AMD64 & Intel EM64T), Red Hat Enterprise Linux ES 4 (AMD64 & Intel EM64T), and Linux 5 (AMD/Intel 64) operating systems:

P-9W62-3592 HiRDB Server Version 9 09-04
P-9W62-1D92 HiRDB/Run Time Version 9 (64) 09-04
P-9W62-1E92 HiRDB/Developer's Kit Version 9 (64) 09-04
P-9S62-1B92 HiRDB/Run Time Version 9 09-04
P-9S62-1C92 HiRDB/Developer's Kit Version 9 09-04
P-F9W62-11925 HiRDB Non Recover Front End Server Version 9 09-00
P-F9W62-11926 HiRDB Advanced High Availability Version 9 09-00

For the Red Hat Enterprise Linux 6 (64-bit x86_64) operating system:

P-9W62-4592 HiRDB Server Version 9 09-04
P-9W62-2D92 HiRDB/Run Time Version 9 (64) 09-04
P-9W62-2E92 HiRDB/Developer's Kit Version 9 (64) 09-04
P-9S62-2B92 HiRDB/Run Time Version 9 09-04
P-9S62-2C92 HiRDB/Developer's Kit Version 9 09-04
P-F9W62-11925 HiRDB Non Recover Front End Server Version 9 09-00
P-F9W62-11926 HiRDB Advanced High Availability Version 9 09-00

For the Windows Server 2003 x64 Editions, Windows Server 2008 R2, Windows Server 2008 (x64), Windows Server 2012, Windows XP x64 Edition, Windows Vista Ultimate (x64), Windows Vista Business (x64), Windows Vista Enterprise (x64), Windows 7 Professional (x64), Windows 7 Enterprise (x64), Windows 7 Ultimate (x64), Windows 8 Pro (x64), and Windows 8 Enterprise (x64) operating systems:

P-2962-9197 HiRDB Server Version 9 09-04

For the Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows Server 2012, Windows 7, and Windows 8 operating systems:

P-2662-1197 HiRDB/Run Time Version 9 09-04

For the Windows XP x64 Edition, Windows Server 2003 x64 Editions, Windows Vista (x64), Windows Server 2008 (x64), Windows Server 2012, Windows 7 (x64), Windows 8 Pro (x64), and Windows 8 Enterprise (x64) operating systems:

P-2962-1197 HiRDB/Run Time Version 9 (64) 09-04

This edition of the manual is released for the preceding program products, which have been developed under a quality management system that has been certified to comply with ISO9001 and TickIT. This manual can be used for products other than the products shown above. For details, see the Release Notes.

Trademarks

ActiveX is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.
AIX is a trademark of International Business Machines Corporation in the United States, other countries, or both.
AIX 5L is a trademark of International Business Machines Corporation in the United States, other countries, or both.
AMD, AMD Opteron, and combinations thereof, are trademarks of Advanced Micro Devices, Inc.
CORBA is a registered trademark of Object Management Group, Inc. in the United States.
DataStage, MetaBroker, MetaStage and QualityStage are trademarks of International Business Machines Corporation in the United States, other countries, or both.
DB2 is a trademark of International Business Machines Corporation in the United States, other countries, or both.
HACMP is a trademark of International Business Machines Corporation in the United States, other countries, or both.
HP-UX is a product name of Hewlett-Packard Development Company, L.P. in the U.S. and other countries.
IBM is a trademark of International Business Machines Corporation in the United States, other countries, or both.
Itanium is a trademark of Intel Corporation in the United States and other countries.
Linux(R) is the registered trademark of Linus Torvalds in the U.S. and other countries.
Microsoft and Visual Studio are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
Microsoft Access is a registered trademark of Microsoft Corporation in the U.S. and other countries.
Microsoft Office and Excel are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
Motif is a registered trademark of the Open Software Foundation, Inc.
Microsoft and MS-DOS are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
ODBC is Microsoft's strategic interface for accessing databases.
OLE is the name of a software product developed by Microsoft Corporation and the acronym for Object Linking and Embedding.
Oracle and Java are registered trademarks of Oracle and/or its affiliates.
OS/390 is a trademark of International Business Machines Corporation in the United States, other countries, or both.
PowerHA is a trademark of International Business Machines Corporation in the United States, other countries, or both.
Red Hat is a trademark or a registered trademark of Red Hat Inc. in the United States and other countries.
UNIFY2000 is a product name of Unify Corp.
UNIX is a registered trademark of The Open Group in the United States and other countries.
VERITAS is a trademark or registered trademark of Symantec Corporation in the U.S. and other countries.
Visual Basic is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.
Visual C++ is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.
Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.
Windows NT is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.
Windows Server is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.
Windows Vista is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.
X/Open is a registered trademark of The Open Group in the U.K. and other countries.
X Window System is a trademark of X Consortium, Inc.
Other product and company names mentioned in this document may be the trademarks of their respective owners. Throughout this document Hitachi has attempted to distinguish trademarks from descriptive terms by writing the name with the capitalization used by the manufacturer, or by writing the name with initial capital letters. Hitachi cannot attest to the accuracy of this information. Use of a trademark in this document should not be regarded as affecting the validity of the trademark.

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.

Issued

Mar. 2014: 3020-6-458-40(E)

Copyright

All Rights Reserved. Copyright (C) 2011, 2014, Hitachi, Ltd.

Preface

This manual describes the messages issued by the HiRDB Version 9 Nonstop Database program products.

Intended readers

This manual is intended for users of HiRDB Version 9 (hereafter referred to as HiRDB).

Readers of this manual must have the following:

For Windows systems, a basic knowledge of managing Windows

For UNIX Systems, a basic knowledge of managing UNIX or Linux

A basic knowledge of SQL

Organization of this manual

This manual is organized into the following chapters:

1. Overview of Messages

Chapter 1 provides an overview of the message output formats and the notations used in this manual to explain the messages.

2. Messages

Chapter 2 explains each message and the action to be taken when each message is output.

3. ABORT Codes

Chapter 3 explains the causes of ABORT codes (abnormal termination cause codes) and the actions to be taken in response to each ABORT code.

4. Error Detail Codes

Chapter 4 explains RPC-related errors, detailed codes about system-related errors, system call return codes, and communication error codes.

5. HiRDB File System Error Codes

Chapter 5 explains the error codes and the information about locked resources that are displayed by HiRDB.

6. Lock Control Errors

Chapter 6 explains resource types, resource names, and resource information output for lock control errors.

7. Messages Related to Sort Processing

Chapter 7 explains messages related to sort processing.

8. SQLSTATE

Chapter 7 explains messages related to SQLSTATE.

Related publications

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

HiRDB (for UNIX)

HiRDB Version 9 Description (3000-6-451(E)), for UNIX systems

HiRDB Version 9 Installation and Design Guide (3000-6-452(E)), for UNIX systems

HiRDB Version 9 System Definition (3000-6-453(E)), for UNIX systems

HiRDB Version 9 System Operation Guide (3000-6-454(E)), for UNIX systems

HiRDB Version 9 Command Reference (3000-6-455(E)), for UNIX systems

HiRDB Version 9 Staticizer Option Description and User's Guide (3000-6-463), for UNIX systems#

HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide (3000-6-464(E)), for UNIX systems

HiRDB Version 9 Batch Job Accelerator (3020-6-468)#

HiRDB Version 9 Memory Database Installation and Operation Guide (3020-6-469), for UNIX systems#

HiRDB (for Windows)

HiRDB Version 9 Description (3020-6-451(E)), for Windows systems

HiRDB Version 9 Installation and Design Guide (3020-6-452(E)), for Windows systems

HiRDB Version 9 System Definition (3020-6-453(E)), for Windows systems

HiRDB Version 9 System Operation Guide (3020-6-454(E)), for Windows systems

HiRDB Version 9 Command Reference (3020-6-455(E)), for Windows systems

HiRDB Version 8 Batch Job Accelerator (3020-6-368)#

HiRDB (for both Windows and UNIX)

HiRDB Version 9 UAP Development Guide (3020-6-456(E))

HiRDB Version 9 SQL Reference (3020-6-457(E))

HiRDB Version 9 XDM/RD E2 Connection Facility (3020-6-465)#

HiRDB Version 9 XML Extension (3020-6-480)#

HiRDB Version 9 Text Search Plug-in (3020-6-481)#

HiRDB Version 8 Security Guide (3020-6-359)#

HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide (3020-6-360(E))

HiRDB Datareplicator Extension Version 8 (3020-6-361)#

HiRDB Dataextractor Version 8 Description, User's Guide and Operator's Guide (3020-6-362(E))

In references to HiRDB Version 9 manuals, this manual omits the phrases for UNIX systems and for Windows systems. Refer to either the UNIX or Windows HiRDB manual, whichever is appropriate for your platform.

Others

EasyMT (3000-3-573)#

EasyMT (3000-3-578)#

Hitachi HA Toolkit (3000-9-115)#

VOS3 XDM/RD E2 Description (6190-6-637)#

VOS3 XDM E2 Programmer's Guide (XDM/RD E2) (6190-6-638)#

VOS3 XDM E2 Messages (XDM/RD E2) (6190-6-643)#

VOS3 XDM/RD E2 SQL Reference (6190-6-656)#

VOS1 RDB1 E2 User's Guide (6150-6-561)#

VOSK SQL/K (650-3-241)#

#: This manual has been published in Japanese only; it is not available in English.

Organization of HiRDB manuals

The HiRDB manuals are organized as shown below. For the most efficient use of these manuals, it is suggested that they be read in the order they are shown, going from left to right.

Conventions: Abbreviations

Unless otherwise required, this manual uses the following abbreviations for product and other names:

Full name or meaning
Abbreviation

HiRDB Server Version 9
HiRDB/Single Server
HiRDB or HiRDB Server

HiRDB/Parallel Server

HiRDB/Developer's Kit Version 9
HiRDB/Developer's Kit
HiRDB Client

HiRDB/Developer's Kit Version 9(64)

HiRDB/Run Time Version 9
HiRDB/Run Time

HiRDB/Run Time Version 9(64)

HiRDB Accelerator Version 8
HiRDB Accelerator

HiRDB Accelerator Version 9

HiRDB Adapter for XML - Standard Edition
HiRDB Adapter for XML

HiRDB Adapter for XML - Enterprise Edition

HiRDB Advanced High Availability Version 9
HiRDB Advanced High Availability

HiRDB Control Manager
HiRDB CM

HiRDB Control Manager Agent
HiRDB CM Agent

HiRDB Dataextractor Version 8
HiRDB Dataextractor

HiRDB Datareplicator Version 8
HiRDB Datareplicator

HiRDB Disaster Recovery Light Edition Version 9
HiRDB Disaster Recovery Light Edition

HiRDB Non Recover Front End Server Version 9
HiRDB Non Recover FES

HiRDB Staticizer Option Version 9
HiRDB Staticizer Option

HiRDB Text Search Plug-in Version 9
HiRDB Text Search Plug-in

HiRDB XML Extension Version 9
HiRDB XML Extension

Single server
SDS

System manager
MGR

Front-end server
FES

Dictionary server
DS

Back-end server
BES

Microsoft(R) ActiveX(R)
ActiveX

DNCWARE ClusterPerfect (Linux Edition)
ClusterPerfect

DataStage(R)
DataStage

DB2 Universal Database for OS/390 Version 6
DB2

JP1/Magnetic Tape Access
EasyMT

EasyMT

JP1/Automatic Job Management System 2 - Scenario Operation
JP1/AJS2-SO

JP1/Automatic Job Management System 3
JP1/AJS3

JP1/Automatic Job Management System 2

JP1/Cm2/Extensible SNMP Agent
JP1/ESA

JP1/Cm2/Extensible SNMP Agent for Mib Runtime

JP1/Integrated Management - Manager
JP1/Integrated Management or JP1/IM

JP1/Integrated Management - View

JP1/NETM/Audit - Manager
JP1/NETM/Audit

JP1/NETM/DM
JP1/NETM/DM

JP1/NETM/DM Manager

JP1/Cm2/Network Node Manager
JP1/NNM

JP1/Performance Management
JP1/PFM

JP1/Performance Management - Agent Option for HiRDB
JP1/PFM-Agent for HiRDB

JP1/Performance Management - Agent Option for Platform
JP1/PFM-Agent for Platform

JP1/Performance Management/SNMP System Observer
JP1/SSO

JP1/VERITAS NetBackup BS V4.5 Agent for HiRDB License
JP1/VERITAS NetBackup Agent for HiRDB License

JP1/VERITAS NetBackup V4.5 Agent for HiRDB License

JP1/VERITAS NetBackup 5 Agent for HiRDB License

LifeKeeper for Linux V7 Update1
LifeKeeper

MetaBroker(R)
MetaBroker

MetaStage(R)
MetaStage

Microsoft(R) Office Excel
Microsoft Excel or Excel

JP1/Magnetic Tape Library
MTguide

JP1/VERITAS NetBackup BS v4.5
NetBackup

JP1/VERITAS NetBackup v4.5

PowerHA for AIX, V5.5
PowerHA

PowerHA SystemMirror V6.1

QualityStage(TM)
QualityStage

OpenTP1/Server Base Enterprise Option
TP1/EE

Hitachi TrueCopy
TrueCopy

Hitachi TrueCopy Asynchronous

Hitachi TrueCopy basic

Hitachi TrueCopy Software

TrueCopy

TrueCopy Asynchronous

TrueCopy remote replicator

Hitachi Universal Replicator Software
Universal Replicator

Universal Replicator

Microsoft(R) Visual C++(R)
Visual C++ or C++ language

Oracle WebLogic Server
WebLogic Server

Virtual-storage Operating System 3/Forefront System Product
VOS3/FS
VOS3

Virtual-storage Operating System 3/Leading System Product
VOS3/LS

Virtual-storage Operating System 3/Unific System Product
VOS3/US

VOS3 Database Connection Server
DB Connection Server

Extensible Data Manager/Base Extended Version 2
XDM Basic Program XDM/BASE E2
XDM/BASE E2

XDM/Data Communication and Control Manager 3
XDM Data Communication Management System XDM/DCCM3
XDM/DCCM3

XDM/Relational Database
Relational Database System XDM/RD
XDM/RD
XDM/RD

XDM/Relational Database Extended Version 2
Relational Database System XDM/RD E2
XDM/RD E2

HP-UX 11i V2 (IPF)
HP-UX or HP-UX (IPF)

HP-UX 11i V3 (IPF)

AIX 5L V5.2
AIX 5L
AIX

AIX 5L V5.3

AIX V6.1
AIX V6.1

AIX V7.1
AIX V7.1

Linux(R)
Linux

Red Hat Enterprise Linux(R) AS 4(AMD64 & Intel EM64T)
Linux AS 4
Linux

Red Hat Enterprise Linux(R) AS 4(x86)

Red Hat Enterprise Linux(R) ES 4(AMD64 & Intel EM64T)
Linux ES 4

Red Hat Enterprise Linux(R) ES 4(x86)

Red Hat Enterprise Linux(R) 5 Advanced Platform (x86)
Linux 5

Red Hat Enterprise Linux(R) 5 (x86)

Red Hat Enterprise Linux(R) 5 Advanced Platform (AMD/Intel 64)

Red Hat Enterprise Linux(R) 5 (AMD/Intel 64)

Red Hat Enterprise Linux(R) 6 (32-bit x86)
Linux 6

Red Hat Enterprise Linux(R) 6 (64-bit x86_64)

Red Hat Enterprise Linux(R) AS 4(AMD64 & Intel EM64T)
Linux (EM64T)

Red Hat Enterprise Linux(R) ES 4(AMD64 & Intel EM64T)

Red Hat Enterprise Linux(R) 5 Advanced Platform (AMD/Intel 64)

Red Hat Enterprise Linux(R) 5 (AMD/Intel 64)

Red Hat Enterprise Linux(R) 6 (64-bit x86_64)

Red Hat Enterprise Linux(R) 5 Advanced Platform (x86)
Linux 5 (x86)
Linux 5

Red Hat Enterprise Linux(R) 5 (x86)

Red Hat Enterprise Linux(R) 5 Advanced Platform (AMD/Intel 64)
Linux 5 (AMD/Intel 64)

Red Hat Enterprise Linux(R) 5 (AMD/Intel 64)

Red Hat Enterprise Linux(R) 6 (32-bit x86)
Linux 6 (32-bit x86)
Linux 6

Red Hat Enterprise Linux(R) 6 (64-bit x86_64)
Linux 6 (64-bit x86_64)

turbolinux 7 Server for AP8000
Linux for AP8000

Microsoft(R) Windows NT(R) Workstation Operating System Version 4.0
Windows NT

Microsoft(R) Windows NT(R) Server Network Operating System Version 4.0

Microsoft(R) Windows Server(R) 2003, Standard Edition
Windows Server 2003 Standard Edition
Windows Server 2003

Microsoft(R) Windows Server(R) 2003, Enterprise Edition
Windows Server 2003 Enterprise Edition

Microsoft(R) Windows Server(R) 2003, Standard x64 Edition
Windows Server 2003 Standard x64 Edition

Microsoft(R) Windows Server(R) 2003, Enterprise x64 Edition
Windows Server 2003 Enterprise x64 Edition

Microsoft(R) Windows Server(R) 2003 R2, Standard Edition
Windows Server 2003 R2

Microsoft(R) Windows Server(R) 2003 R2, Enterprise Edition

Microsoft(R) Windows Server(R) 2003 R2, Standard x64 Edition

Microsoft(R) Windows Server(R) 2003 R2, Enterprise x64 Edition

Microsoft(R) Windows Server(R) 2003 R2, Standard x64 Edition
Windows Server 2003 R2 x64 Editions

Microsoft(R) Windows Server(R) 2003 R2, Enterprise x64 Edition

Microsoft(R) Windows Server(R) 2008 Standard
Windows Server 2008 Standard
Windows Server 2008

Microsoft(R) Windows Server(R) 2008 Enterprise
Windows Server 2008 Enterprise

Microsoft(R) Windows Server(R) 2008 R2 Standard (x64)
Windows Server 2008 R2

Microsoft(R) Windows Server(R) 2008 R2 Enterprise (x64)

Microsoft(R) Windows Server(R) 2008 R2 Datacenter (x64)

Microsoft(R) Windows Server(R) 2008 Standard (x64)
Windows Server 2008 (x64)

Microsoft(R) Windows Server(R) 2008 Enterprise (x64)

Microsoft(R) Windows Server(R) 2012 Standard
Windows Server 2012

Microsoft(R) Windows Server(R) 2012 Datacenter

Microsoft(R) Windows Server(R) 2003, Standard x64 Edition
Windows Server 2003 x64 Editions
Windows (x64)

Microsoft(R) Windows Server(R) 2003, Enterprise x64 Edition

Microsoft(R) Windows Server(R) 2003 R2, Standard x64 Edition

Microsoft(R) Windows Server(R) 2003 R2, Enterprise x64 Edition

Microsoft(R) Windows(R) XP Professional x64 Edition
Windows XP x64 Edition

Microsoft(R) Windows Server(R) 2003, Enterprise x64 Edition
Windows Server 2003 (IPF)
Windows(IPF)

Microsoft(R) Windows(R) XP Professional x64 Edition
Windows XP x64 Edition
Windows XP

Microsoft(R) Windows(R) XP Professional Operating System
Windows XP Professional

Microsoft(R) Windows(R) XP Home Edition Operating System
Windows XP Home Edition

Microsoft(R) Windows Vista(R) Home Basic
Windows Vista Home Basic
Windows Vista

Microsoft(R) Windows Vista(R) Home Premium
Windows Vista Home Premium

Microsoft(R) Windows Vista(R) Ultimate
Windows Vista Ultimate

Microsoft(R) Windows Vista(R) Business
Windows Vista Business

Microsoft(R) Windows Vista(R) Enterprise
Windows Vista Enterprise

Microsoft(R) Windows Vista(R) Home Basic (x64)
Windows Vista (x64)

Microsoft(R) Windows Vista(R) Home Premium (x64)

Microsoft(R) Windows Vista(R) Ultimate (x64)

Microsoft(R) Windows Vista(R) Business (x64)

Microsoft(R) Windows Vista(R) Enterprise (x64)

Microsoft(R) Windows Vista(R) Ultimate (x64)
Windows Vista Ultimate (x64)

Microsoft(R) Windows Vista(R) Business (x64)
Windows Vista Business (x64)

Microsoft(R) Windows Vista(R) Enterprise (x64)
Windows Vista Enterprise (x64)

Microsoft(R) Windows(R) 7 Home Premium
Windows 7 Home Premium
Windows 7

Microsoft(R) Windows(R) 7 Professional
Windows 7 Professional

Microsoft(R) Windows(R) 7 Enterprise
Windows 7 Enterprise

Microsoft(R) Windows(R) 7 Ultimate
Windows 7 Ultimate

Microsoft(R) Windows(R) 7 Home Premium (x64)
Windows 7 (x64)

Microsoft(R) Windows(R) 7 Professional (x64)

Microsoft(R) Windows(R) 7 Enterprise (x64)

Microsoft(R) Windows(R) 7 Ultimate (x64)

Microsoft(R) Windows(R) 7 Professional (x64)
Windows 7 Professional (x64)

Microsoft(R) Windows(R) 7 Enterprise (x64)
Windows 7 Enterprise (x64)

Microsoft(R) Windows(R) 7 Ultimate (x64)
Windows 7 Ultimate (x64)

Microsoft(R) Windows(R) 8 (Core Edition)
Windows 8 (Core Edition)
Windows 8

Microsoft(R) Windows(R) 8 Pro
Windows 8 Pro

Microsoft(R) Windows(R) 8 Enterprise
Windows 8 Enterprise

Microsoft(R) Windows(R) 8 (Core Edition) (x64)
Windows 8 (Core Edition) (x64)

Microsoft(R) Windows(R) 8 Pro (x64)
Windows 8 Pro (x64)

Microsoft(R) Windows(R) 8 Enterprise (x64)
Windows 8 Enterprise (x64)

Windows Server 2003, Windows Server 2008, and Windows Server 2012 are often referred to collectively as Windows Server. Windows XP, Windows Server, Windows Vista, Windows 7, and Windows 8 are often referred to collectively as Windows.

The hosts file means the hosts file stipulated by TCP/IP (including the /etc/hosts file in UNIX). As a rule, a reference to the hosts file means the %windir%\system32\drivers\etc\hosts file.

This manual also uses the following abbreviations:

Abbreviation | Full name or meaning
ACK | Acknowledgement
ADM | Adaptable Data Manager
ADO | ActiveX Data Objects
ADT | Abstract Data Type
AP | Application Program
API | Application Programming Interface
ASN.1 | Abstract Syntax Notation One
BES | Back End Server
BLOB | Binary Large Object
BMP | Basic Multilingual Plane
BOM | Byte Order Mark
CD-ROM | Compact Disc - Read Only Memory
CLOB | Character Large Object
CMT | Cassette Magnetic Tape
COBOL | Common Business Oriented Language
CORBA | Common ORB Architecture
CPU | Central Processing Unit
CSV | Comma Separated Values
DAO | Data Access Object
DAT | Digital Audio Tape
DB | Database
DBMS | Database Management System
DDL | Data Definition Language
DIC | Dictionary Server
DLT | Digital Linear Tape
DML | Data Manipulate Language
DNS | Domain Name System
DOM | Document Object Model
DS | Dictionary Server
DTD | Document Type Definition
DTP | Distributed Transaction Processing
DWH | Data Warehouse
EUC | Extended UNIX Code
EX | Exclusive
FAT | File Allocation Table
FD | Floppy Disk
FES | Front End Server
FQDN | Fully Qualified Domain Name
FTP | File Transfer Protocol
GUI | Graphical User Interface
HD | Hard Disk
HDP | Hitachi Dynamic Provisioning
HTML | Hyper Text Markup Language
ID | Identification number
IP | Internet Protocol
IPF | Itanium(R) Processor Family
JAR | Java Archive File
Java VM | Java Virtual Machine
JDBC | Java Database Connectivity
JDK | Java Developer's Kit
JFS | Journaled File System
JFS2 | Enhanced Journaled File System
JIS | Japanese Industrial Standard code
JP1 | Job Management Partner 1
JRE | Java Runtime Environment
JTA | Java Transaction API
JTS | Java Transaction Service
KEIS | Kanji processing Extended Information System
LAN | Local Area Network
LIP | Loop Initialization Process
LOB | Large Object
LRU | Least Recently Used
LTO | Linear Tape-Open
LU | Logical Unit
LVM | Logical Volume Manager
MGR | System Manager
MIB | Management Information Base
MRCF | Multiple RAID Coupling Feature
MSCS | Microsoft Cluster Server
MSFC | Microsoft Failover Cluster
NAFO | Network Adapter Fail Over
NAPT | Network Address Port Translation
NAT | Network Address Translation
NIC | Network Interface Card
NIS | Network Information Service
NTFS | New Technology File System
ODBC | Open Database Connectivity
OLE | Object Linking and Embedding
OLTP | On-Line Transaction Processing
OOCOBOL | Object Oriented COBOL
ORB | Object Request Broker
OS | Operating System
OTS | Object Transaction Service
PC | Personal Computer
PIC | Plug-in Code
PNM | Public Network Management
POSIX | Portable Operating System Interface for UNIX
PP | Program Product
PR | Protected Retrieve
PU | Protected Update
RAID | Redundant Arrays of Inexpensive Disk
RD | Relational Database
RDB | Relational Database
RDO | Remote Data Objects
RiSe | Real time SAN replication
RM | Resource Manager
RMM | Resource Manager Monitor
RPC | Remote Procedure Call
SAX | Simple API for XML
SDS | Single Database Server
SGML | Standard Generalized Markup Language
SJIS | Shift JIS
SNMP | Simple Network Management Protocol
SNTP | Simple Network Time Protocol
SR | Shared Retrieve
SU | Shared Update
TCP/IP | Transmission Control Protocol / Internet Protocol
TM | Transaction Manager
UAP | User Application Program
UOC | User Own Coding
VOS3 | Virtual-storage Operating System 3
WS | Workstation
WWW | World Wide Web
XDM/BASE E2 | Extensible Data Manager / Base Extended Version 2
XDM/DS | Extensible Data Manager / Data Spreader
XDM/RD E2 | Extensible Data Manager / Relational Database Extended Version 2
XDM/XT | Extensible Data Manager / Data Extract
XDS | Extended Data Server
XML | Extensible Markup Language

Log representations

In Windows

The application log that is displayed by Windows Event Viewer is referred to as the event log. The following procedure is used to view the event log.

To view the event log:

1. Choose Start, Programs, Administrative Tools (Common), and then Event Viewer.

2. Choose Log, and then Application.

The application log is displayed. Messages with HiRDBSingleServer or HiRDBParallelServer displayed in the Source column were issued by HiRDB.

If you specified a setup identifier when you installed HiRDB, the specified setup identifier follows HiRDBSingleServer or HiRDBParallelServer.

In UNIX

The OS log is referred to generically as syslogfile. syslogfile is the log output destination specified in /etc/syslog.conf. Typically, the following files are specified as syslogfile.

OS | File
HP-UX | /var/adm/syslog/syslog.log
Solaris | /var/adm/messages or /var/log/syslog
AIX | /var/adm/ras/syslog
Linux | /var/log/messages

Conventions: Fonts and symbols

The following table explains the text formatting conventions used in this manual:

Text formatting
Convention

Bold
Bold characters indicate text in 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.

Italic
Italic characters 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)

Italic characters are also used for emphasis. For example:

Do not delete the configuration file.

Monospace
Monospace characters indicate 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.

The following table explains the symbols used in this manual:

Symbol
Convention

|
In syntax explanations, a vertical bar separates multiple items, and has the meaning of OR. For example:
A|B|C means A, or B, or C.

{ }
In syntax explanations, curly brackets indicate that only one of the enclosed items is to be selected. For example:
{A|B|C} means only one of A, or B, or C.

[ ]
In syntax explanations, square brackets indicate that the enclosed item or items are optional. For example:
[A] means that you can specify A or nothing.
[B|C] means that you can specify B, or C, or nothing.

...
In coding, an ellipsis (...) indicates that one or more lines of coding have been omitted.
In syntax explanations, an ellipsis indicates that the immediately preceding item can be repeated as many times as necessary. For example:
A, B, B, ... means that, after you specify A, B, you can specify B as many times as necessary.

()
Parentheses indicate the range of items to which the vertical bar (|) or ellipsis (...) is applicable.

{{ }}
A double pair of curly brackets encloses multiple items, all of which you can specify multiple times as a unit.
Example: {{pdbuffer -a option-name}}
This example indicates that you can specify the above multiple times as follows:
pdbuffer -a option-name
pdbuffer -a option-name

~
A swung dash precedes the attributes of a user-specified value.

<< >>
A double pair of angle brackets encloses the default value assumed by the system when the specification is omitted.

< >
A single pair of angle brackets encloses the syntax element notation for a user-specified value.

(( ))
A double pair of parentheses encloses the permitted range of values that can be specified.

Round up the result to the next integer.
Example: The result of 34 3 will be 12.

Discard digits following the decimal point.
Example: The result of 34 3 will be 11.

MAX
Select the largest value as the result.
Example: The result of MAX(3 6, 4 + 7) will be18.

MIN
Select the smallest value as the result.
Example: The result of MIN(3 6, 4 + 7) will be 11.

Conventions: KB, MB, GB, and TB

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.

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.

Path name representations

The backslash (\) is used as the delimiter in path names. Readers who are using a UNIX edition of HiRDB must replace the backslash with a forward slash (/). When the path names in the Windows and UNIX editions differ, both path names are given.

The HiRDB directory path is represented as %PDDIR%. However, when the path names in the Windows and UNIX editions differ, the directory path in the UNIX edition is represented as $PDDIR, as shown in the following example:

In Windows: %PDDIR%\CLIENT\UTL\

In UNIX: $PDDIR/client/lib/

%windir% refers to a Windows installation directory path.

Notes on Windows path names

In this manual, the Windows terms directory and folder are both referred to as directory.

Include the drive name when you specify an absolute path name.

Example: C:\win32app\hitachi\hirdb_s\spool\tmp

When you specify in a command argument, control statements file, or HiRDB system definition file a path name that includes a space or a parenthesis, you must enclose the entire path name in double quotation marks (").

Example: pdinit -d "C:\Program Files(x86)\hitachi\hirdb_s\conf\mkinit"

However, double quotation marks are not necessary when you use the set command in a batch file or at the command prompt to set an environment variable or when you specify the installation directory. If you do use double quotation marks in such a case, the enclosing double quotation marks become part of the value assigned to the environment variable.

Example: set PDCLTPATH=C:\Program Files\hitachi\hirdb_s\spool

HiRDB cannot use files on a networked drive, so you must install HiRDB and configure the HiRDB environment on a local drive. Files used by utilities, such as utility input and output files, must also be on the local drive.

Do not use short path names (for example, do not use path names such as C:\PROGRA~1).

Important notes on this manual

The following facilities are explained, but they are not supported:

Distributed database facility

Server mode system switchover facility#

User server hot standby#

Rapid system switchover facility#

Standby-less system switchover (1:1) facility

Standby-less system switchover (effects distributed) facility

HiRDB External Data Access facility

Inner replica facility

Updatable online reorganization

Sun Java System Directory Server linkage facility

Simple setup tool

Extended syslog facility

Rapid batch facility

Memory database facility

Linkage with JP1/NETM/Audit

The following products and option program products are explained, but they are not supported:

HiRDB CM

HiRDB Disaster Recovery Light Edition

uCosminexus Grid Processing Server

HiRDB Text Search Plug-in

HiRDB XML Extension

TP1/Server Base

JP1/PFM-Agent Option for HiRDB

JP1/VERITAS NetBackup Agent for HiRDB License

XDM/RD

HiRDB SQL Tuning Advisor

COBOL2002

#: Supported in the UNIX edition. Not supported in the Windows edition.

1. Overview of Messages

This chapter explains the message output formats and the notations used in this manual to explain the messages.

Organization of this chapter

1.1 Message output formats

1.2 Descriptive notation

1.1 Message output formats

Organization of this section

(1) Messages output to standard error output or standard output

(2) Messages output to the standard output by the pdcat command

(3) Messages output to an event log (in UNIX, syslogfile)

(1) Messages output to standard error output or standard output

The following subsections describe the format of messages output by the HiRDB system.

(a) Output format of HiRDB messages

AAAAA hh:mm:ss BBBB CCCCCCCC KFPA00000-E XX....XX

or

KFPA00000-E xx....xx

AAAAA: Process ID (for AIX and HP-UX (IPF) editions, this is a 10-digit decimal number; for all other editions, this is a 5-digit decimal number)

hh:mm:ss: time (in hours:minutes:seconds format) (8-digit decimal number)

BBBB: Unit identifier (4 alphanumeric characters)

CCCCCCCC: Name of the server that requested that the message be output (8 alphanumeric characters)

KFPA00000-E: Message ID (11 alphanumeric characters)

xx....xx: Message text (maximum of 243 characters)

Note that the unit identifier and the name of the server that requested that the message be output may not appear.

(b) Output format of pre-processor messages

pdcpp: filename, line-number: error-number: text

pdcpp:

Identifier of a message output by the C language preprocessor; for COBOL, the identifier is pdcbl.

filename:

Name of the UAP source file resulting in the error

line-number:

Line number in the UAP source file resulting in the error

error-number:

Message ID

text:

Message text

(2) Messages output to the standard output by the pdcat command

This type of message includes supplemental information, in addition to a message ID and message text. Whether or not the supplemental information is to be omitted is specified with the pdcat command's option flag. When this option flag is not specified, the additional information, message ID, and message text are all output.

Following is the format of a message with supplemental information that is output to the standard output:

AAAAAAA BB....BB CCCCCCC DDDD yyyy/mm/dd hh:mm:ss
EEEEEEEE FFFF GGGGGGGG HHH KFPA00000-E xx...xx

Additional information:

AAAAAAA:

Message serial number (7 decimal digits)

BB....BB:

Process ID (for AIX and HP-UX (IPF) editions, this is a 10-digit decimal number; for all other editions, this is a 5-digit decimal number)

CCCCCCC:

Serial number of the message within the process (server) (7 decimal digits)

DDDD:

HiRDB identifier (4 alphanumeric characters)

yyyy/mm/dd:

Date (10 decimal digits in the format year/month/date)

hh:mm:ss:

Time (8 decimal digits in the format hour:minute:second)

EEEEEEEE:

Request source host name (first 8 characters)

FFFF:

Unit identifier (4 alphanumeric characters)

GGGGGGGG:

Name of the server requesting the message output (8 alphanumeric characters)

HHH:

Internal information used by the system (3 alphanumeric characters)

Fixed part of message:

KFPA00000-E:

Message ID (11 decimal digits)

xx...xx:

Message text (up to 223 characters)

Some messages do not contain the request source unit identifier or request source server name.

(3) Messages output to an event log (in UNIX, syslogfile)

Messages that are output to an event log (in UNIX, syslogfile) include optional information in addition to a message ID and message text. Following is the format of messages issued by the HiRDB system:

mmm dd hh:mm:ss AA...AA HiRDB[nn....nn]: KFPA00000-E BBBB CCCC xx...xx (DD....DD)

Supplemental information:

mmm:

Month (3 alphabetic characters)

dd:

Date (2 decimal digits)

hh:mm:ss:

Time (8 decimal digits in the format hour:minute:second)

AA...AA:

Standard host name of the message output request source (up to 63 alphanumeric characters)

nn....nn:

Process ID (for AIX and HP-UX (IPF) editions, this is a 10-digit decimal number; for all other editions, this is a 5-digit decimal number)

KFPA00000-E:

Message ID (11 alphanumeric characters)

BBBB:

HiRDB identifier (4 alphanumeric characters)

CCCC:

HiRDB unit identifier (4 alphanumeric characters)

xx...xx:

Message text*

DD....DD:

Process ID of the message output request source*

* The message text and the process ID of the source that requested that the message be output must total no more than 233 characters (including spaces between characters). Text exceeding 233 characters is discarded.

Some messages do not contain a HiRDB identifier, HiRDB unit identifier, or process ID of the message output request source; in such cases, this supplemental information either is displayed as spaces or is omitted altogether (i.e., only the message text is displayed).

1.2 Descriptive notation

Organization of this section

(1) Format

(2) Message ID codes

(3) Explanation of message text

(4) Notes on messages

(1) Format

This manual explains messages in the following format:

KFPX₁ n₁ n₂ n₃ n₄ n₅ -I Y TYPEx

message-text

Explanation of the message:
S: Action taken by HiRDB once the message has been issued.
P: Action that should be taken by the programmer.
O: Action that should be taken by the operator.

Action

Action that should be taken by the HiRDB administrator.

Note

The phrase Contact the customer support center in a message explanation means that the system administrator needs to contact a Hitachi customer service representative.

(2) Message ID codes

The following explains the codes used in the message ID:

KFP: Code indicating that the message was issued by the HiRDB system.

X₁: Code identifying the message management source:

A: Message concerning an SQL statement (this message is also output following the execution of a utility or command)

C: Windows-specific message

D: Dictionary manager message

H: Database-related message

I: HiRDB file system message

J: JDBC drive message

K: Utility-related message (statistics analysis utility or database condition analysis utility)

L: Utility-related message (database load utility or database reorganization utility)

M: MIB-related message

N: Utility-related message (optimization or JP1/NETM/Audit Log Output)

O: OS library message

R: Utility-related message (database recovery utility)

S: System manager message

T: Updatable online reorganization messages

U: Utility-related message (any utility)

X: Utility-related message (environment definition)

Y: Plug-in related message

Z: Client message

n₁ to n₅: Message number

i: Message severity code:

E: Error message (indicates that the error disabled a function)

W: Warning message (indicates a warning concerning resource utilization status, etc., or indicates that a command specification error was detected but processing continued using the default value)

I: Information message (indicates an operating status that does not apply to E or W)

Q: Response request message (indicates that the system is waiting for the user's response to the displayed message)

Y: Message output destination

If a message has multiple output destinations, all the destinations to which output may be directed are shown, separated by the plus sign (+). L denotes output to the standard output device when the pdcat command or the real-time output function is used.

KFPJ messages are collected into getMessage(), which is an SQLException object of JDBC driver.

A: SQLCA (SQL communication area)#1

D: Message dialog

E: Standard error output#6

J: JP1 event database#2

L: Message log file and event log (in UNIX, syslogfile)#3, #4, #5

P: XDS message log file

R: Error log file and client error log file#7

S: Standard output#6

#1

The output destination of KFPA messages output when a utility or a command is executed is E or L.

#2

This is output when the system is linked to JP1.

#3

In the following situations, either no message is output or the message is output to the event log in the host where the message output source unit is located (in UNIX, to syslogfile). The message might also be output to the standard error output of the host where the message output source unit is located.

When an error occurs on a single server or on a unit with a system manager

After abnormal termination and before restart of the message log server

When a standby system is used

When HiRDB is starting

#4

Messages output by operation commands or utilities are output only to the event log (syslogfile in UNIX) of the host where the message output source unit is located, and are not output to the message log file.

#5

Messages output by XDS are output to the following output destinations, instead of the message log file:

syslogfile

XDS message log file

However, note that while XDS is starting, messages might not be output to syslogfile or the XDS message log file.

#6

Messages output by XDS are output to the following output destinations, instead of standard error output or standard output:

XDS log file

XDS message log file

However, note that while XDS is starting, messages might not be output to the XDS message log file.

#7

Messages output by XDS that include KFPZ in their message ID are output to the following output destinations, instead of the error log file and the client error log file:

XDS log file

syslogfile

XDS message log file

However, note that while XDS is starting, messages might not be output to syslogfile or the XDS message log file.

TYPEx:

Message KFPJ can include two types of messages sharing the same message ID: Type 2 JDBC driver messages and Type 4 JDBC driver messages. If a message contains both Type 2 and Type 4 messages, both messages are listed. When two types of messages exist, and only when two types exist, the messages are represented as follows so that they can be distinguished:

TYPE2: Indicates a Type 2 JDBC driver message.

TYPE4: Indicates a Type 4 JDBC driver message.

In a Type 4 JDBC driver message, the message text can be followed by the name of the class that generated the message, and the name of the method by which the message was generated, in the following format:

KFPxn₁n₂n₃n₄n₅-i message-text [aa....aa.bb....bb]

aa....aa: Name of the class that generated the message

bb....bb: Name of the method by which the message was output

(3) Explanation of message text

The message text explains the message or event, as well as embedded characters.

The following notations are used in message text:

{ }: Only one of the text items enclosed in braces is displayed; the text items are delimited by the vertical bar (|).

Example: {authorization-identifier|password}

[ ]: A text item enclosed in square brackets may not be displayed.

(4) Notes on messages

Relationships between message IDs and SQLCODE codes
The following table shows the relationships between message IDs and the SQLCODE codes in the SQL Communications Area (SQLCA) used by the UAP:

Message ID | SQLCODE
KFPA11nnn | -nnn
KFPA19nnn | -1nnn
KFPA12nnn | +nnn

Notes on the UNIX edition
For the following return code, the HiRDB system does not output a message; only the error code is returned to SQLCODE:

SQLCODE=-849

The SQLCODE description is set at the message ID location.

About query numbers
The term query number is used in the message descriptions.
A query number is a number assigned to each query specification, or subquery, appearing in an SQL statement, and serves to identify each query by number in the SQL statement. Within a subquery, the query number will be 2 or greater. Parts of the statement that are not contained in a query specification, or subquery, will have a query number of 1.

2. Messages

This chapter identifies messages that are generated by the system, explains their meanings, and shows action to be taken by a user.

Organization of this chapter

2.1 KFPA messages

2.2 KFPC messages

2.3 KFPD messages

2.4 KFPH messages

2.5 KFPI messages

2.6 KFPJ messages

2.7 KFPK messages

2.8 KFPL messages

2.9 KFPM messages

2.10 KFPN messages

2.11 KFPO messages

2.12 KFPR messages

2.13 KFPS messages

2.14 KFPT messages

2.15 KFPU messages

2.16 KFPX messages

2.17 KFPY messages

2.18 KFPZ messages

2.1 KFPA messages

KFPA11101-E A

More than 255 nested operations, or implementation restriction exists

The operation contains more than 255 nesting levels, or an SQL statement cannot be executed due to restrictions on the system processing.

S: Ignores this SQL statement.

P: Take one of the following actions:

Reduce the nesting levels to no more than 255 and re-execute. There are cases in which the nesting levels in the SQL that specifies a named derived table are 255 or less. In such cases, decrease the number of nesting levels in the SQL or in the query that derives the named derived table.

Either simplify the SQL statement (by reducing the number of tables or columns, etc.) or reduce the number of table indexes the applicable SQL statement references, and then re-execute.

If a large number of SQL statements that create work tables are being executed in a transaction, revise the SQL statements so that the number of work tables created is 255 or less, and then re-execute the SQL statements. For a description of how to estimate the number of work tables that are created, see the manual HiRDB Version 9 Installation and Design Guide.

KFPA11102-E A

More than aa....aa bytes in character string literal

One of the following values exceeds the maximum specifiable number (aa....aa):

Number of bytes specified for a character string literal

Number of bytes in the result of a concatenation operation between character string literals

Number of bytes in the result of a scalar function (HEX) for which a literal is specified in its argument

Number of bytes in the result of a character string literal after it is converted into the conversion target (for assignment or comparison)

The following maximum specifiable numbers apply:

When specified in the SQLSTATE value: 5

When specified in the CREATE TABLE or ALTER TABLE boundary values and storage conditions: 255

All other cases: 32000

aa....aa:

{ 5|255|32000 }

S: Ignores this SQL statement.

P: Reduce the length of the character string literal to no more than aa....aa bytes and re-execute.

KFPA11103-E A

Invalid floating point numeric literal aa....aa

The format of a specified floating-point numeric literal is invalid.

aa....aa: Invalid floating-point numeric literal

S: Ignores this SQL statement.

P: Correct the floating-point numeric literal and re-execute.

KFPA11104-E A

Invalid part "aa....aa" in SQL

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

The SQL statement is followed by a superfluous character string.

A syntactically invalid character or keyword is specified.

The first keyword in the SQL statement is invalid.

A name does not begin with an alphabetic character.

There is a name of zero length.

aa....aa: Invalid part of the SQL statement

If the SQL statement contains a syntactically invalid character, the character is displayed with its hexadecimal representation enclosed in parentheses.

S: Ignores this SQL statement.

P: Correct the error and re-execute.

KFPA11105-E A

Invalid token "bb....bb" after token "aa....aa"

Syntactically, "bb....bb" cannot follow "aa....aa" in an SQL statement.

aa....aa: Last characters satisfying the syntax rules

bb....bb: Syntactically invalid characters

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute. Possible errors are as follows:

The specification contains a syntax error.

The order of clauses is invalid.

KFPA111106-E A

Incomplete SQL

An SQL statement is not complete.

S: Ignores this SQL statement.

P: Complete the SQL statement and re-execute.

If you specified Y for pd_sql_simple_comment_use in the system definition and this is a simple comment, check whether the linefeed code that ends the simple comment is missing. If it is missing, add the linefeed code, and then retry the operation.

KFPA11107-E A

More than 30 characters in identifier "aa....aa"

The name is longer than 30 characters. Another possibility is that an invalid keyword is specified.

aa....aa: The first 30 characters of the name.

S: Ignores this SQL statement.

P: If the name is longer than 30 characters, revise it so that it is 30 characters or less, and then re-execute. Revise any authorization identifier to 8 characters or less. If a keyword is specified incorrectly, revise the SQL statement, and re-execute it.

KFPA11112-E A

Invalid argument of set function "aa....aa"

One of the following errors exists in an argument of the set function "aa....aa":

No column was specified in the argument.

A FLAT specification was specified for an argument in a set function other than MAX or MIN.

A column other than a repetition column was specified for the FLAT specification in the set function MAX or MIN.

A set function with FLAT specified in an argument was specified in a GROUP BY clause query in which a value expression other than a column was specified.

aa....aa: Set function:

{ AVG |COUNT |COUNT_FLOAT |MAX |MIN |SUM }

S: Ignores this SQL statement.

P: Specify the argument correctly in the set function and re-execute.

KFPA11113-E A

aa....aa function "bb....bb" is specified in argument of set function, query-no=ccc

Set function "bb....bb" is specified as an argument of a set function.

aa....aa: Specified function

Set

bb....bb: Set function:

{ AVG |COUNT |COUNT_FLOAT |MAX |MIN |SUM }

ccc: Query number

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11114-E A

Invalid specification in predicate "aa....aa", query-no=bbb

There is an error in the specification of a NULL, LIKE, XLIKE, SIMILAR, BETWEEN, Boolean predicate, or XMLEXISTS predicate.

A literal, USER value function, CURRENT_DATE value function, CURRENT_TIME value function, CURRENT_TIMESTAMP value function, ? parameter, or embedded variable was specified in a LIKE predicate, in a value expression in an XLIKE predicate, or in the row-value-constructor-1 of a BETWEEN predicate.

A CURRENT_DATE value function, CURRENT_TIME value function, CURRENT_TIMESTAMP value function, ? parameter, or embedded variable was specified in a value expression in a SIMILAR predicate.

A row value constructor was specified in the value expression of a NULL, LIKE, XLIKE, SIMILAR, or Boolean predicate.

An XMLEXISTS predicate was specified somewhere other than in a WHERE clause. Note that the XMLEXISTS predicate cannot be specified in a subquery of a WHERE clause.

aa....aa: Predicate whose operand is invalid:

{NULL|LIKE|XLIKE|SIMILAR|BETWEEN|BOOL|XMLEXISTS}

bbb: Number of the query that specified the predicate

S: Ignores this SQL statement. Alternatively, rolls back if the SQL statement is a definition SQL.

P: Correct the SQL statement as follows and re-execute:

KFPA11116-E A

Invalid search condition in "HAVING" clause, query-no=aaa

Structured repetition predicate was specified in the search condition in a HAVING clause

aaa: Number of the query that specified the predicate

S: Ignores this SQL statement.

P: Correct the search condition in the HAVING clause and re-execute.

KFPA11117-E A

Number of aa....aa not equal to number of bb....bb

The number of aa....aa does not match the number of bb....bb.

aa....aa

{insert-values|update-values-specified-by-subquery|left-side-row-value-constructor-elements|derived-column-list}

bb....bb

{insert-columns|update-columns|right-side-row-value-constructor-elements|derived-columns}

S: Ignores this SQL statement. Rollback occurs in the case of a definition SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11118-E A

Invalid use of update table in update value

The following error occurred in the use of a table subject to updating:

When the table to be updated is specified in the FROM clause of a subquery specified in the SET or ADD clause of the UPDATE statement, and the columns of the table to be updated are referenced externally, value expressions with the following attributes cannot be specified in the selection expression of the subquery:
BLOB
BINARY with a maximum length of 32,001 bytes or larger
Repetition column
Abstract data type

When the UPDATE statement uses a cursor, a subquery that specifies the table to be updated in the FROM clause cannot be specified in the SET clause.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11119-E A

Column "aa....aa" in bb....bb clause must be either group column or within set function, query-no=(ccc,ddd)

In a query specifying a GROUP BY clause or a set function, the column specification in the SELECT, HAVING, or ORDER BY clause must satisfy either of the following conditions:

The column specification must be a grouping column.

The column specification must be specified in the argument of a set function.

If a value expression other than a column specification is specified in the GROUP BY clause, a grouping column cannot be referenced from a scalar subquery specified in the query's selection expression.

aa....aa: Name of the column whose specification is invalid

bb....bb: Name of the clause specifying "aa....aa"

{SELECT|HAVING|ORDER BY|subquery in SELECT}

ccc: Number of the innermost query specifying the column

ddd: Number of the query specifying the clause

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11120-E A

Cannot specify "aa....aa" function in "bb....bb" query-no=(ccc,ddd)

A set function, SQL/XML set function, or window function is specified at an invalid location.

aa....aa: {set|SQL/XML set|window|only window}

bb....bb: Name of the clause or statement in which a set function or window function is specified

{"WHERE" clause|"SET" clause|"ADD"clause

|"ON" clause|"GROUP BY" clause|"IF" statement

|"WHILE" statement|"SET" statement

|"RETURN" statement|"VALUES" clause

|"CALL" statement|"WRITE LINE" statement

|"HAVING" clause|insert statement|subquery|derived table|select list

| select list with set function|value expression|set operation

|select list with group by clause|select list with having clause}

ccc: Query number in which a set function, SQL/XML set function, or window function is specified

ddd: Query number in which the clause or statement is specified

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11121-E A

Duplicate update items or insert columns

In an INSERT statement, a column to be inserted cannot be specified more than once.
In an UPDATE statement, a column or attribute cannot be specified more than once as a column to be updated or as an update attribute. An element in a repetition column cannot be specified more than once.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11122-E A

More than 255 value expressions in "GROUP BY" clause

More than 255 value expressions were specified in the GROUP BY clause.

S: Ignores this SQL statement.

P: Reduce the number of value expressions in the GROUP BY clause to no more than 255 and re-execute.

KFPA11123-E A

Duplicate columns "aa....aa" in "bb....bb" clause

The same column cannot be specified more than once in the GROUP BY, ORDER BY, or FOR UPDATE clause, or in a derived column list.

aa....aa: Name of the column specified more than once, or the sort item specification number

bb....bb: Name of the clause specifying "aa....aa"

{GROUP BY|ORDER BY|FOR UPDATE OF|derived column list}

S: Ignores this SQL statement.

P: If the specified column name is invalid, correct the column name and re-execute. If the specified column name is correct, delete the invalid specification and re-execute.

KFPA11124-E A

More than 255 columns in "ORDER BY" clause

More than 255 columns were specified in the ORDER BY clause.

S: Ignores this SQL statement.

P: Reduce the number of columns in the ORDER BY clause to no more than 255 and re-execute.

KFPA11125-E A

Invalid integer aa....aa in "ORDER BY" clause

The following error was detected in the sort item specification number specified in the ORDER BY clause:

The sort item specification number exceeds the number of derived columns.

aa....aa: The erroneous sort item specification number

S: Ignores this SQL statement.

P: For the sort item specification number, specify the number indicating the location of the derived column in the SELECT clause of the selection expression, and then re-execute.

KFPA11126-E A

"ROW" can not be specified in "ORDER BY" clause using sort item number

A sort item specification number cannot be specified in the ORDER BY clause of an SQL statement specifying ROW.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11127-E A

Keyword "DISTINCT" already specified in query specification, query-no=aaa

DISTINCT cannot be specified more than once in one query specification.

aaa: Number of the query specifying DISTINCT more than one time.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11128-E A

Invalid use of keyword "NULL", query-no=aaa

One of the following errors was detected in the usage of NULL:

NULL was specified as a value other than the NULL predicate in a search condition

NULL was specified in the SELECT clause

NULL was specified as the object of an arithmetic operation or concatenation operation

NULL was specified as the argument of a scalar function

aaa: Number of the query that specified NULL.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11129-E A

More than aa....aa bb....bb

The number of bb....bb specified in an SQL statement exceeds the maximum number aa....aa.

aa....aa: Permitted maximum value:

{ 16 |64 |65 |128 |255 |1023 |30000 }

bb....bb: Specification exceeding the permitted maximum:

{tables | select columns

| update columns

| columns in "INTO" clause

| variables or parameters

| columns in "FOR UPDATE OF" clause

| values in "VALUES" clause

| view columns

| "WITH" query columns

| "java.sql.ResultSet[]" in EXTERNAL NAME clause

| attributes in type definition

| data types

| arguments in function invocation

| multi-value columns in column name list of ARRAY predicate

| SQL variables and SQL parameters

| row value constructor elements

| derived columns

| correlation names

| arguments in XMLQUERY function

| arguments in XMLEXISTS predicate

| SQL parameters in C routine}

S: Ignores this SQL statement.

P: Reduce the number of bb....bb to no more than aa....aa and re-execute.

KFPA11131-E A

Invalid precision or scale in scalar function "DECIMAL"

Invalid precision or scale was specified in the DECIMAL scalar function.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11132-E A

Invalid use of aa....aa dd....dd "bb....bb", query-no=ccc

One of the following was used incorrectly:

A column, SQL variable, or SQL parameter of the aa....aa type

An attribute of the aa....aa type

A function invocation of the aa....aa type, used as a data type for a function return value

SQL/XML set function, or SQL/XML scalar function

aa....aa: Incorrectly used data type

{ BLOB |BINARY |abstract |BOOLEAN |XML }

bb....bb: Name of the incorrectly used column, SQL variable, SQL parameter, attribute, or function

ccc: Number of the innermost query that specified an incorrectly used column, SQL variable, SQL parameter, attribute, or function

dd....dd: Type of the incorrectly used name

{ column, SQL variable or SQL parameter | attribute | function invocation | set function }

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Correct the SQL statement and re-execute.

KFPA11133-E A

Invalid specification of update value for aa....aa column or attribute

When updating or inserting an abstract data type column or attribute, neither an embedded variable nor the ? parameter can be specified as the insertion value or update value.

aa....aa: Invalid data type (abstract)

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Correct the SQL statement and re-execute.

KFPA11134-E A

Invalid use of long data cc....cc "aa....aa", query-no=bbb

One of the following items was used incorrectly:

A column of long data, an SQL variable, or an SQL parameter

An attribute of long data

A function invocation with a long data data type for its function return value

Long data refers to any of the following data types:

CHAR, VARCHAR, MCHAR, MVARCHAR, or BINARY with a definition length of 256 bytes or greater

NCHAR or NVARCHAR with a definition length of 128 characters or greater

aa....aa: Name of the incorrectly used column, SQL variable, SQL parameter, attribute, or function

bbb: Number of the innermost query that specified an incorrectly used column, SQL variable, SQL parameter, attribute, or function

cc....cc: Type of the incorrectly used name

{ column, SQL variable or SQL parameter
|attribute|function invocation }

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11136-E A

Invalid use of ? parameter in aa....aa statement

The ? parameter is used in a procedure definition, in a procedure body in a type definition, in a function definition, or in a function body in a type definition modification.

aa....aa: CREATE PROCEDURE, PROCEDURE definition in CREATE TYPE, CREATE FUNCTION, FUNCTION definition in CREATE TYPE

S: Ignores this SQL statement

P: Correct the SQL statement and re-execute.

KFPA11137-E A

More than 255 aa....aa in bb....bb

The number of items in bb....bb, which was specified in the descriptor displayed for cc....cc, exceeds the maximum number aa....aa.

aa....aa: { 255 | 30000 }

bb....bb: { value expressions| row value expressions }

cc....cc: { "IN" predicate | scalar function "VALUE"| case abbreviation "COALESCE"}

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11138-E A

Invalid use of derived table

The correlation name for the derived table was not specified. The correlation name for the derived table can be omitted only when the outermost query is specified in the following format:

SELECT COUNT(*) FROM derived-table

SELECT COUNT_FLOAT(*) FROM derived-table

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11139-E A

More than 30000 elements in multi-value specification

The number of elements in a repetition value expression is greater than the maximum allowable value (30000). Repetition value expression refers to ARRAY[element-value, ....].

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Reduce the number of element values, and then rerun the program.

KFPA11140-E A

Invalid national character string literal

Specified national character string literal contains a syntax error.

S: Ignores this SQL statement.

P: Correct the national character string literal in the SQL statement and re-execute.

KFPA11141-E A

More than aa....aa characters in national character string literal

One of the following numbers is greater than the maximum specifiable number (aa....aa):

Number of characters specified in a national character string literal

Number of characters in the result of a concatenation operation between national character string literals

The following maximum specifiable numbers apply:

Number when specified in the CREATE TABLE or ALTER TABLE boundary values and storage conditions: 127

All other cases: 16,000

aa....aa: 16000 or 127

S: Ignores this SQL statement.

P: Correct the national character string literal so that its length does not exceed aa....aa characters, then re-execute.

KFPA11142-E A

Invalid identifier in XDS

One of the following errors was detected in an identifier being used in the memory database:

Single- and double-byte characters are mixed together.

Double-byte space characters are specified.

S: Ignores this SQL statement.

P: Correct the identifier and re-execute.

KFPA11144-E A

Invalid aa....aa string literal

There is a syntax error in the hexadecimal character string literal specification.

aa....aa:{usage of hex|hex}

For usage of hex:

The hexadecimal character string literal is specified in the following locations:

COMMENT statement

Plug-in option

For hex:

The hexadecimal character length specified in the hexadecimal character string literal is not a multiple of 2.

A character other than 0-9, a-f, or A-F was specified in the hexadecimal character string literal.

S: Ignores this SQL statement.

P:

When aa....aa is usage of hex:

Use a character string literal instead of a hexadecimal character string literal.

When aa....aa is hex:

Take one of the following actions, and then re-execute:

In the hexadecimal character string literal, specify a hexadecimal character length that is a multiple of 2.

Delete any characters other than 0-9, a-f, or A-F that are specified in the hexadecimal character string literal.

KFPA11145-E A

More than 64000 bytes in hex string literal

The hexadecimal character length specified in the hexadecimal character string literal is more than 64,000 characters.

S: Ignores this SQL statement.

P: Reduce the hexadecimal character length of the hexadecimal character literal to a maximum of 64,000 characters.

KFPA11146-E A

More than 255 compound(BEGIN) statements and FOR statement nested

There are more than 255 nesting levels in the compound statement and FOR statement.

S: Ignores this SQL statement.

P: Reduce the nesting level count of the compound statement and FOR statement to 255 or less and re-execute.

KFPA11148-E A

Invalid use of holdable cursor

The specified holdable cursor is invalid for one of the following reasons:

A holdable cursor cannot be specified for a single-line retrieval.

A holdable cursor cannot be specified in a search specifying columns of the abstract data type provided by a plug-in.

A holdable cursor cannot be specified in a search specifying a function call provided by a plug-in.

A holdable cursor cannot be specified in a search of a named derived table specified in a function call provided by a plug-in.

A holdable cursor cannot be specified in a search using a list.

A holdable cursor cannot be specified in a search of a transaction-specific temporary table (a temporary table that specifies ON COMMIT DELETE ROWS).

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute. For details about plug-in support for holdable cursors, check the values in the PLUGIN_HOLDABLE column in the dictionary table SQL_PLUGINS. For details about the dictionary table SQL_PLUGINS, see the HiRDB Version 9 UAP Development Guide.

KFPA11149-E A

Invalid use of keyword "ROW"

One of the following errors was detected in the usage of ROW:

ROW cannot be specified in a query specifying the GROUP BY clause, HAVING clause, or a set function.

ROW cannot be specified in a subquery (including derived tables in the FROM clause).

ROW cannot be specified in a query using UNION.

ROW cannot be specified in a view definition query or in a WITH clause.

ROW cannot be specified in a derived table of a FOR statement cursor specification.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11154-E A

Invalid use of SQL parameter or SQL variable "aa....aa"

An identifier was specified in a location where only a value specification is allowed in an SQL statement other than CREATE PROCEDURE, CREATE TRIGGER, CREATE FUNCTION, or CREATE TYPE.
Note that you cannot specify an SQL parameter or SQL variable in an SQL statement other than CREATE PROCEDURE, CREATE TRIGGER, CREATE FUNCTION, or CREATE TYPE. The only identifiers that can be specified as a value specification are SQL parameters and SQL variables.

aa....aa: Name of the specified SQL variable or SQL parameter

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11155-E A

Invalid use of "aa....aa" clause

A FOR UPDATE OF or FOR READ ONLY clause cannot be specified in any location other than a cursor declaration or a dynamic SELECT statement. A FOR READ ONLY clause cannot be specified in a single-row SELECT statement. In addition, you cannot specify the lock option and FOR UPDATE with NOWAIT specified at the same time.

aa....aa: Name of the invalid clause:

{"FOR UPDATE OF" clause|"FOR READ ONLY" clause|"FOR UPDATE" clause with "NOWAIT"}

S: Ignores this SQL statement.

P: Correct the SQL statement or update option and re-execute.

KFPA11156-E A

Invalid query for "UPDATE" or "DELETE" statement with cursor

None of the following can be specified in a query that updates or deletes data using a cursor, or in a query that specifies the FOR UPDATE clause:

Joining tables

FROM clause derived table

Grouping

Set function

Set operation

Duplicate elimination

Specification, in the FROM clause of a subquery, of a table specified in a FROM clause of the outermost query specification

Read-only viewed table

WITHOUT LOCK NOWAIT

Query name specified in a FROM clause of the outermost query specification in the query expression body that specified a WITH clause

Result set returned from a procedure

Window function

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11157-E A

Invalid use of "UPDATE" or "DELETE" statement with cursor

One of the following errors occurred in the UPDATE or DELETE statement using a cursor:

The UPDATE or DELETE statement using a statically declared cursor cannot be preprocessed by the PREPARE statement.

The UPDATE or DELETE statement using a cursor that can be preprocessed cannot be statically executed.

The cursor is incorrectly declared or is not assigned.

S: Ignores this SQL statement.

P: Take one of the following actions:

If the SQL statement is executed dynamically, revise the SQL statement to an UPDATE or DELETE statement that uses a preprocessable cursor, and re-execute.

If the SQL statement is executed statically, revise the SQL statement to an UPDATE or DELETE statement that uses a statically declared cursor, and re-execute.

Revise the cursor declaration or assignment and re-execute.

KFPA11158-E S

Invalid SQL statement for pddef utility

The specified SQL statement cannot be executed by the database definition utility (pddef).

S: Ignores this SQL statement.

P: Specify an SQL statement that can be executed by the database definition utility and re-execute.

KFPA11159-E A

Unable to specify aa....aa in bb....bb SQL

An ASSIGN LIST statement, DROP LIST statement, or a search using a list cannot be embedded directly in the host program for execution. Also, GET DIAGNOSTICS cannot be dynamically executed.

aa....aa:

{ ASSIGN LIST|DROP LIST|
 query using LIST|GET DIAGNOSTICS }

bb....bb: {dynamic|static}

S: Ignores this SQL statement.

P: Take one of the following actions:

Specify the ASSIGN LIST statement or DROP LIST statement in the PREPARE statement or EXECUTE IMMEDIATE statement.

In a PREPARE statement, specify a search that uses a list.

Do not specify GET DIAGNOSTICS in a PREPARE statement or an EXECUTE IMMEDIATE statement.

KFPA11161-E A

Zero divisor specified

Zero was specified as the divisor.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11162-E A

Ending label name must be the same name as beginning label name, beginning-label=aa....aa, ending-label=bb....bb

The beginning label does not match the ending label.

aa....aa: Specified beginning label

bb....bb: Specified ending label

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11163-E A

Invalid search condition in IF statement or WHILE statement

The following error was detected in the search condition specified in the IF or WHILE statement:

A subquery is specified.

A structured repetition predicate was specified.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11164-E A

Missing cursor name after "where current of"

The cursor name or extended cursor name is missing in an UPDATE or DELETE statement that uses a cursor.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11165-E A

Invalid value "aa....aa" of cc....cc "bb....bb"

The following error exists in the SQL statement:

There is an error in the value or identifier of the specified compile option.

aa....aa: Specified compile option, or the value or identifier of the option

If the option is longer than 30 characters, and then the first 30 characters are displayed. Also, the option becomes ******** if the option value is a null character string.

bb....bb: Invalid compile option or other option

{ISOLATION|OPTIMIZE LEVEL|ADD OPTIMIZE LEVEL|SUBSTR LENGTH|COLLATING_SEQUENCE|TRAILING_SPACE|NULLABLE_SCHEMA|TABLE|USING_BES|USER|PASSWD}

cc....cc: Error location:

{compile option|OPTIONS}

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11167-E A

More than 255 WHEN clauses in CASE expression, query_no=aaa

More than 255 WHEN clauses were specified in one CASE expression or in an outermost CASE expression that included nested CASE expressions.

aaa: Number of the query that specified a CASE expression

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11168-E A

Invalid search condition in CASE expression, query_no=aaa

The search condition in a CASE expression contains the following error:

A structured repetition predicate was specified.

aaa: Number of the query that specified a CASE expression

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11169-E A

Unable to specify joined table in view definition, "WITH" query or query expression body with "WITH" clause

A joined table cannot be specified in a view-definition-derived query expression, a derived query expression in a WITH clause, or in a query expression body for a query expression containing a WITH clause specification.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11170-E A

Unable to specify aa....aa in environment using bb....bb character code set

While Unicode (UTF-8) or the Chinese character encoding GB18030 (CHINESE-GB18030) were being used, one of the following errors was detected:

A national character literal was used.

A column with the national character data type was defined.

While one-byte character codes were being used, one of the following errors was detected:

A national character or mixed character string literal was used.

A column with the national character or mixed character data type was defined.

While a character encoding other than SJIS was being used, the following error was detected:

An EBCDIK character set specification was used.

While a character encoding other than Unicode (UTF-8) was being used, the following error was detected:

A UTF16 character set specification was used.

aa....aa: {national character|mixed character|national character or mixed character|character set "EBCDIK"|character set "UTF16"}

bb....bb: {chinese|ujis|utf-8|lang-c|chinese-gb18030|sjis}

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11171-E A

Duplicate value expressions in "GROUP BY" clause

Only one value expression of the same type can be specified in the GROUP BY clause.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11172-E A

Unable to specify outer reference "aa....aa"."bb....bb" in query with grouping by expression, query-no=ccc

If a value expression other than the column specification is used in the GROUP BY clause contained in a subquery, a column that makes an external reference cannot be specified in the WHERE clause or ON clause for the same subquery.

aa....aa: Table identifier or correlation name

bb....bb: Name of column that makes an external reference

ccc: Number of the query specifying a column that makes an external reference

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11173-E A

Invalid value expression in "GROUP BY" clause, query-no=aaa

One of the following errors was detected in the GROUP BY clause:

A value expression other than a column specification is specified in a view definition or in the GROUP BY clause of a derived query expression containing a WITH clause.

A value expression other than a column specification is specified in the GROUP BY clause of a subquery contained in a WHERE clause for a query specification in which a value expression other than a column specification is specified in the GROUP BY clause.

A ? parameter or embedded variable was specified in the value expression in the GROUP BY clause.

A component specification is specified in a value expression in a GROUP BY clause.

A subquery is specified in a value expression in a GROUP BY clause.

aaa: Number of the query specifying an invalid GROUP BY clause

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11174-E A

RETURN statement not specified in function definition

The RETURN statement is not specified in the function definition.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11175-E A

Unable to specify component specification in derived table

Component specifications are not allowed in a derived table.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11176-E A

Specify only routine control statement except FOR statement in function definition

Only routine control SQL statements other than the FOR statement are allowed in a function definition.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11177-E A

Invalid use of "AS" clause or ? parameter or embedded variable for argument in aa....aa

One of the following errors occurred in the specification of an AS data-type clause, ? parameter, or embedded variable:

Either a ? parameter or embedded variable was specified in an argument without specifying AS data-type.

The specified data type cannot be specified in AS data-type.
Function invocation:
A non-predefined data type was specified.
Scalar function (LENGTH, SUBSTR, or POSITION):
A data type other than BLOB or BINARY was specified.
XML constructor function:
A data type other than BINARY was specified.
XMLSERIALIZE function:
A data type other than VARCHAR or BINARY was specified.
XMLPARSE function:
A data type other than the following was specified in AS data-type:
Character string data type (CHAR, VARCHAR)
Mixed character string data type (MCHAR, MVARCHAR)
BINARY type

AS data-type was specified in an argument other than a ? parameter or an embedded variable.

A unary operation using a ? parameter or an embedded variable was specified for an argument.

If aa....aa is an assignment statement, one of the following errors occurred in the specification of the assignment value:

A ? parameter or embedded variable was specified in the assignment value without specifying AS data-type.

A data type other than BLOB or BINARY was specified in AS data-type.

aa....aa: Statement containing the syntax error

{function invocation

|scalar function "LENGTH"

|scalar function "SUBSTR"

|scalar function "POSITION"

|assignment statement

|XML constructor

|XMLSERIALIZE

|XMLPARSE }

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11179-E A

Unable to specify aa....aa in search condition of ARRAY predicate, query-no=bbb

The following specifications are not allowed in a search condition in a structured repetition predicate:

A structured repetition predicate

An XMLEXISTS predicate

A subquery

A column other than those specified in ARRAY(repetition-column [, repetition-column]....).

One of the following specifications made in a predicate comparison condition:

System-defined scalar function, function invocation, and predicate that includes IS_USER_CONTAINED_IN_HDS_GROUP.

Predicate that does not include a column specification

aa....aa:

{ ARRAY predicate |XMLEXISTS predicate |subquery
|except columns in column name list of ARRAY predicate
|function invocation |predicate without column }

bbb: Number of the query specifying a predicate

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Correct the SQL statement and re-execute.

KFPA11180-E A

Subscript specified for single-value column, SQL variable, or SQL parameter "aa....aa", query-no=bbb

Subscripts cannot be specified in a non-repetition column, an SQL variable, or the SQL parameter "aa....aa".

aa....aa: Item for which an incorrect subscript was specified

bbb: Number of the innermost query specifying "aa....aa".

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Correct the SQL statement and re-execute.

KFPA11181-E A

Invalid use of multi-value column "aa....aa" without subscript, query-no=bbb

A repetition column that omitted subscripts is specified at an invalid location.

aa....aa: Column name of the column from which subscripts are omitted

bbb: Number of the innermost query specifying "aa....aa".

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Correct the SQL statement and re-execute.

KFPA11182-E A

Invalid use of multi-value column "aa....aa" with subscript, query-no=bbb

A repetition column with a subscript specification is specified at an invalid location.

aa....aa: Column name of the repetition column with a subscript specification

bbb: Number of the innermost query specifying "aa....aa".

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Correct the SQL statement and re-execute.

KFPA11183-E A

Invalid use of multi-value column "aa....aa", query-no=bbb

A repetition column is specified at an invalid location.

aa....aa: Name of the incorrectly specified column. However, if this incorrectly specified column is a column of a named derived table that was derived from a set function that has a repetition column as an argument, the column name of the base table of the applicable named derived table is displayed.

bbb: Number of the innermost query specifying "aa....aa".

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Correct the SQL statement and re-execute.

KFPA11184-E A

Subscript of multi-value column "aa....aa" exceeds maximum number of elements, query-no=bbb

The subscript specified in a repetition column exceeds the maximum number of elements.

aa....aa: Column name of the repetition column

bbb: Number of the innermost query specifying "aa....aa".

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Correct the SQL statement and re-execute.

KFPA11185-E A

Invalid specification of update or insert value for column "aa....aa"

The insert or update value contains one of the following errors:

Insert value:

A non-NULL simple structure value is specified for a repetition column that omitted subscripts.

A repetition structure value is specified for a column in a simple structure.

Update value in a SET clause:

A non-NULL simple structure value is specified for a repetition column that omitted subscripts.

A repetition structure value is specified in a component specification, a column of a simple structure, or a repetition column with a subscript specification.

Update value in ADD clause:

A simple structure value is specified.

A subquery is specified for the element value of a repetition column.

aa....aa: The column name with an insert or update value specification error, or the column name in a component specification

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Correct the SQL statement and re-execute.

KFPA11186-E A

Invalid subscript for multi-value column "aa....aa", query-no=bbb

The subscript specified for a repetition column contains an error.

aa....aa: Column name of the repetition column

bbb: Number of the innermost query specifying "aa....aa".

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Correct the SQL statement and re-execute.

KFPA11187-E A

DISTINCT specified for multi-value column, query-no=aaa

DISTINCT cannot be specified for a repetition column.

aaa: Number of the innermost query specifying a repetition column

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Correct the SQL statement and re-execute.

KFPA11188-E A

Invalid query with FLAT specification

The following error occurred in a query with FLAT specified in the FROM clause:

A column other than the column specified by FLAT is specified.

The number of columns specified in FLAT exceeds 16.

Not all of the indexes included for the columns specified in FLAT are defined. Another possibility is that, for queries that include an RDAREA name specification, the number of partitions of the indexes included for all columns specified in FLAT is different from the number of partitions of the table.

The columns specified in FLAT do not include any repetition columns.

A viewed table or query is specified in the FROM clause.

FLAT is specified in the SELECT clause of INSERT SELECT, a view definition, the WITH clause, a FROM clause derived table, or a subquery.

The following items are specified:
FOR READ ONLY
FOR UPDATE clause
LIMIT clause
GROUP BY clause that specifies a value expression other than a column specification
Component specification
Set function containing a FLAT specification
Function call
Subquery
Set operation
Table join
Column that specifies a subscript

The following item is specified in a search condition:
Structured repetition predicate

S: Ignores this SQL statement.

P: Take one of the following actions:

Correct the SQL statement and re-execute.

If an RDAREA name is specified, make sure that the number of partitions of the defined index is equal to the number of partitions of the table, and then re-execute the SQL statement.

KFPA11189-E A

Invalid subscript for multi-value column "aa....aa"

The maximum number of elements in the repetition column "aa....aa" specified in the CREATE TABLE or ALTER TABLE statement is invalid.

aa....aa: Column name of the repetition column

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11191-E A

Subquery specified in ASSIGN LIST statement

A subquery (excluding subqueries in an IN predicate without a NOT specification that do not make an external reference) is specified in an ASSIGN LIST statement.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11192-E A

Two or more selection items specified in scalar subquery, query-no=aaa

More than one retrieval item is specified in a scalar subquery.

aaa: Number of the subquery in which more than one retrieval item is specified

However, if a set operation is specified in a subquery, this becomes the number of the first specified query specification among the query specifications of the set operation.

S: Ignores this SQL statement.

P: Correct the SQL statement so that only one retrieval item is specified and re-execute.

KFPA11194-E A

Unable to specify qualified column name in ORDER BY clause in query using set operation

A qualified column name has been specified in the ORDER BY clause of a query using a set operation.

S: Ignores this SQL statement.

P: Correct the SQL statement as follows and re-execute:

If AS column-name is specified in the SELECT clause specified in the first query, specify the column name specified in AS column-name.

If there is no AS column-name specification, delete the table specification.

Specify a sort item specification number.

If no sorting is to be performed, delete the ORDER BY clause.

KFPA11195-E A

Derived tables for SET operation must have same number of columns

The number of derived columns does not match the number specified for a set operation.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11196-E A

Precision exceeds ddd in aa....aa, result data type decimal, column-no=bbbbb, query-no=ccc

The data type of the execution result of the scalar function VALUE, the result of a CASE expression, the execution result of a set operation, or the result of a function invocation, is the DECIMAL data type. Or, the resulting precision exceeded ddd.

aa....aa: SQL statement containing the error

{ scalar function |SET operation |CASE expression
|function invocation }

bbbbb: The column number indicating which element in the derived table exceeded ddd in precision (the value 0 indicates a scalar function, a CASE expression, or a function invocation)

ccc: Number of the query specifying the error-causing scalar function, CASE expression, set operation, or function invocation

ddd: Maximum precision

The maximum precision is determined by the following conditions:

Value of system common definition pd_sql_dec_op_maxprec | Precision of the operands | Maximum precision
29 or omitted | All 29 digits or fewer | 29
Includes operands with 30 digits or more | 38
38 | Any | 38

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P:

Correct the decimal data specified in the VALUE scalar function, the CASE expression, or the set operation, and then re-execute.

For a function invocation, correct the data type in the RETURNS clause in the function definition, and then re-execute.

KFPA11197-E A

Inconvertible data type in SET operation, column-no=aaaaa, query-no=bbb

A set operation was specified, but the data type of the corresponding column cannot be converted. If the data type of the corresponding column is a character string data type, conversion is not possible when the character sets are different. However, if the second and subsequent corresponding columns in the set operation are the following value expression, conversion is performed based on the character set of the first corresponding column in the set operation:

Character string literal

aaaaa: Number of the column of the derived table resulting in the error

bbb: Number of the query resulting in an error

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11198-E A

Invalid specification of SET clause in UPDATE statement

One of the following error corrections must be made to the UPDATE statement:

If only one update target item is specified as the assignment target for the SET clause, omit the parentheses enclosing the update target's name.

If multiple update target items are specified as the assignment targets for the SET clause, enclose all the update target names in parentheses. In this case, specify a subquery for the assignment source.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11201-E A

Invalid item specification, authorization identifier aa....aa, table identifier aa....aa, table identifier, correlation name, query name, statement label or routine identifier "bb....bb", query-no=ccc

In the SQL statement, the table specification that qualifies a column name is not a valid name. Or, a qualifier of the SQL parameter or the SQL variable is not a valid name specified in the SQL statement.
The invalid qualifier is aa....aa.bb....bb or "bb....bb".

aa....aa: Authorization identifier specified in the table specification

bb....bb: Table identifier, correlation name, query name, statement label name, or routine name

ccc: Number of the innermost query specifying the invalid qualifier

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Correct the SQL statement and re-execute.

KFPA11202-E A

Column, SQL variable, or SQL parameter "aa....aa" not found in any tables, query names, statement label, or routines, query-no=bbb

Column "aa....aa" cannot be found in any table of the SQL statement or query, or in a query name. Or, the SQL variable or SQL parameter "aa....aa" is not declared in the routine.

aa....aa: SQL variable, SQL parameter, or column name that could not be found in the SQL statement

bbb: Number of the query specifying the column, SQL variable, or SQL parameter.

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Correct the SQL statement, and then re-execute.

KFPA11203-E A

Column "aa....aa" ambiguous, query-no=bbb

Because column "aa....aa" was found in more than one table in this query or in more than one query name, the table or query name column corresponding to column "aa....aa" cannot be determined.

aa....aa: Name of the column that was found more than once in the query

bbb: Number of the query specifying the column

S: Ignores this SQL statement.

P: Modify the column name with the correct table name, correlation name, or query name, and then re-execute.

KFPA11204-E A

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

aa....aa bb....bb."cc....cc" was not found in the HiRDB system.
In a data manipulation SQL statement that includes a WITH clause, if aa....aa is Table, table bb....bb."cc....cc" was not found in the HiRDB system, or query name cc....cc was not found in the WITH clause.

aa....aa: {Table|Index|Trigger|Sequence}

bb....bb: Authorization identifier

cc....cc:

When aa....aa is Table: Table identifier, query name

When aa....aa is Index: Index identifier

When aa....aa is Trigger: Trigger identifier

When aa....aa is Sequence: Sequence generator identifier

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11205-E A

Column "aa....aa" not found in table bb....bb."cc....cc"

Column aa....aa was not found in table bb....bb."cc....cc", in the correlation name of a derived table of the FROM clause, or in query name "cc....cc" in a query of the WITH clause.

aa....aa: Column name

bb....bb: Authorization identifier

cc....cc: Table identifier (for a derived table, the correlation name) or query name

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

If the column indicated in aa....aa is a reserved column, reserved columns cannot be specified in this SQL statement. Modify the SQL statement so that it does not specify a reserved column, and then retry the operation.

KFPA11206-E A

Invalid aa....aa type

One of the following errors was detected in the table specification:

DROP TABLE cannot be used to delete a viewed table definition.

DROP VIEW cannot be used to delete a base table definition.

aa....aa: Table

S: Ignores this SQL statement.

P: When executing DROP TABLE, specify a base table, and when executing DROP VIEW, specify a viewed table, and then retry the operation.

KFPA11207-E A

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

No cc....cc is defined for table aa....aa."bb....bb".

aa....aa: Authorization identifier

bb....bb: Table identifier

cc....cc:

{ CLUSTER KEY |PRIMARY KEY |PRIMARY CLUSTER KEY }

S: Ignores this SQL statement.

P: Delete this SQL statement.

KFPA11208-E A

Sort column "aa....aa" must be selected column

Column "aa....aa" specified in the ORDER BY clause is not specified in the SELECT clause of the outermost query.

aa....aa: Name of the sort column

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11209-E A

Column cannot be updated

An attempt was made to update a column that cannot be updated. The following columns cannot be updated:

Column specifying a storage condition

Column specifying a cluster key

Column of a table with the WITHOUT ROLLBACK specification that specifies the index

S: Invalidates this transaction.

P: Correct the SQL statement and re-execute.

KFPA11210-E A

"NOT NULL" constraint violation

An attempt was made to set the NULL value in a column where the NULL value cannot be set, or in an argument passed to a Java stored procedure.

A NULL value cannot be set in a column that has the NOT NULL constraint.

A NULL value cannot be set in a table column or ROW that has the FIX attribute.

A NULL value cannot be set in a cluster key or for configuring a primary key.

If a Java stored procedure is defined where a NULL value data type cannot be set as the argument for a Java method specified as an external routine, a NULL value cannot be set for the argument used when the Java stored procedure is called.

S: Ignores this SQL statement.

P: Set a value other than the NULL value in the column that cannot accept NULL values or in the argument of the Java stored procedure, and then re-execute. Or, redefine the Java stored procedure by changing the argument of the Java method to a data type that can be set to a NULL value, and re-execute.

KFPA11211-E A

Duplicate identifier "aa....aa" in "FROM" clause, query-no=bbb

Name "aa....aa" is duplicated in the FROM clause. The same correlation name cannot be used for more than one table. Or, the correlation name cannot be the same as the table identifier or query name.

aa....aa: Name

bbb: Number of the query specifying a duplicate name

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Correct the SQL statement and re-execute.

KFPA11212-E A

"NULL" predicate cannot be specified in column "aa....aa" with "NOT NULL", query-no=bbb

The NULL predicate was specified for a column for which the null value cannot be specified:

A NULL predicate cannot be specified for a column that has the NOT NULL constraint.

A NULL predicate cannot be specified for a column or ROW that has the FIX attribute.

A NULL predicate cannot be specified for a column configured as a cluster key.

aa....aa: Name of the column for which the invalid NULL predicate was specified

bbb: Number of the innermost query specifying the invalid column

S: Ignores this SQL statement.

P: Correct the search condition and re-execute.

KFPA11213-E A

"ROW" specification ambiguous

Because there is more than one applicable table in a query specifying ROW, the table corresponding to the ROW specification cannot be determined.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11214-E A

Unable to specify "ROW",due to aa....aa

Cannot specify ROW due to reason aa....aa.

aa....aa: The reason ROW cannot be specified

non-"FIX" attribute table: The table does not have the FIX attribute.

column character set specification: There is no character set specification column in the table.

endian mismatch: The endian of the client and server do not match.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

In the case of an endian mismatch between client and server, see the following table regarding the compatibility of the endian of various clients and servers:

Client | Server
HP-UX | Solaris | AIX | Linux | Windows
HP-UX | Y | Y | Y | N | N
Solaris | Y | Y | Y | N | N
AIX | Y | Y | Y | N | N
Linux | N | N | N | Y | Y
Windows | N | N | N | Y | Y

Legend:

Y: Endian does match.

N: Endian does not match.

KFPA11215-E A

Invalid update VALUE for "ROW" specification

When specifying ROW and inserting or updating data, specify an embedded variable, ? parameter, SQL variable, or SQL parameter was specified as the update value.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11216-E A

"ROW" cannot be specified for inner table

ROW cannot be specified for an inner table specified for an outer join of a joined table.

S: Ignores this SQL statement; executes a rollback in the case of a definition SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11217-E A

Invalid use of aa....aa

There is an error in the specification of SQLCODE, SQLCOUNT, SQLCODE_OF_LAST_CONDITION, or SQLERRM_OF_LAST_CONDITION.
These values can only be used in a condition in an IF or WHILE statement, in an assignment value in an assignment (SET) statement, in a return value in a RETURN statement, or in a value expression in a WRITE LINE statement.

aa....aa: { SQLCODE | SQLCOUNT

| SQLCODE_OF_LAST_CONDITION

| SQLERRM_OF_LAST_CONDITION }

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11218-E A

Duplicate column "aa....aa" in derived table

A duplicate column, "aa....aa", is present in the derived table of the FROM clause.

aa....aa: Duplicate column name

S: Ignores this SQL statement. However, if this SQL statement is a definition SQL statement, it is rolled back.

P: Correct the SQL statement and re-execute.

KFPA11220-E A

Sort column "aa....aa" found more than once in derived table

Column "aa....aa" specified in the ORDER BY clause was detected more than once in the table derived as the result of a query.

aa....aa: Column name specified in the ORDER BY clause

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11223-E A

Invalid type, aa....aa must be specified

An invalid data type is specified.
If aa....aa is abstract data, a subtype cannot be defined by specifying a plug-in-provided data type in the under clause.

aa....aa: Type of the data type that needs to be specified

abstract data: Abstract data type

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11224-E A

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

The user-defined type "bb....bb" or "cc....cc" of the type aa....aa is not in the HiRDB system.

aa....aa: Data type

{Data |Index}

bb....bb: Authorization identifier (owner of the type)

cc....cc: Data type identifier or index type identifier

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11227-E A

Column "aa....aa" in "ON" condition not found in any tables, query-no=bbb

The column name "aa....aa" specified in the ON condition is not found in any of the following tables:

Table joined in a joined table containing the ON condition

Table that can make an external reference

aa....aa: Column name

bbb: Query number

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11228-E A

Attribute "aa....aa" not found in data type "bb....bb"."cc....cc"

The attribute "aa....aa" is not in the data type "bb....bb"."cc....cc".

aa....aa: Attribute name

bb....bb: Authorization identifier (owner of the user-defined type)

cc....cc: Data type identifier

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFP11231-E A

SQL variable "aa....aa" already defined

The specified SQL variable "aa....aa" is already defined.

aa....aa: SQL variable

S: Ignores this SQL statement and executes rollback.

P: Correct the SQL statement and re-execute.

KFPA11232-E A

Cursor "aa....aa" already defined

The specified cursor is already defined.

aa....aa: Cursor name

S: Ignores this SQL statement and executes rollback.

P: Correct the SQL statement and re-execute.

KFPA11233-E A

DECLARE CURSOR statement missing for cursor "aa....aa"

The specified cursor "aa....aa" is not declared as a cursor.

aa....aa: Cursor name

S: Ignores this SQL statement and executes rollback.

P: Correct the SQL statement and re-execute.

KFPA11234-E A

Invalid statement label "aa....aa" in LEAVE statement

One of the following errors was found in statement label "aa....aa" of the LEAVE statement.

The statement label specified in the LEAVE statement was not found.

The statement label specified in the LEAVE statement is not a statement label of a compound statement that includes that LEAVE statement, or a statement label of a WHILE statement.

A LEAVE statement that omits the label name is not included in the compound statement or WHILE statement.

A LEAVE statement to exit handler operation was specified while the handler was running.

A FOR statement loop variable name, which cannot be specified.

aa....aa: Statement label (******** when the label name is omitted)

S: Ignores this SQL statement and executes rollback.

P: Correct the SQL statement and re-execute.

KFPA11235-E A

Number of call parameters not equal to number of SQL parameters

The number of arguments specified in the CALL statement does not match the number of SQL parameters of the procedure to be called.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11236-E A

Invalid use of SQL parameter or column "aa....aa", due to in/out parameter mode or qualification by old row value correlation

One of the following usage errors was found in SQL parameter "aa....aa" that the SQL parameter or old correlation name qualified:

An input parameter or column qualified by an old correlation name was specified in a FETCH statement, in the INTO clause of a single-row SELECT statement, or in the assignment target of an assignment statement.

An argument definition of a routine subject to the CALL statement specifies an input parameter or column qualified by the old correlation name in the OUT or INOUT argument.

An output parameter was specified in a location other than the FETCH statement, the INTO clause in a single-row SELECT statement, the assignment target in an assignment statement, or the value expression in a WRITE LINE statement.

An output parameter was specified in the IN argument of the argument definition for a routine that is subject to the CALL statement.

aa....aa: SQL parameter

S: Ignores this SQL statement and executes rollback.

P: Correct the SQL statement and re-execute.

KFPA11237-E A

Unable to specified column "aa....aa", query-no=bbb

Column "aa....aa" is specified in a specification-disabled location.
A specification-disabled location is either of the following:

Pattern character string or escape character in the LIKE predicate

Pattern character string or escape character in the SIMILAR predicate

The right-hand value of the IN predicate

aa....aa: Column that was specified incorrectly

bbb: Number of the query incorrectly specifying the column

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P:

Correct the SQL statement and re-execute.

If the same column name as the SQL variable or SQL parameter exists in the SQL statements table, qualify the SQL variable or SQL parameter with a statement label and procedure name.

KFPA11238-E A

Invalid parameter mode of argument in call statement for SQL parameter definition of procedure

The argument specification (IN, OUT, INOUT) specified in the CALL statement does not match the SQL parameter specification (IN, OUT, INOUT) of the procedure to be called.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11240-E A

Duplicate statement label or loop variable "aa....aa" appeared in the scope of statement label or loop variable

The same statement label or loop variable is specified more than once in statement labels or loop variables contained in a compound statement or in a WHILE or FOR statement.

aa....aa: Statement label name or loop variable name

S: Ignores this SQL statement and executes rollback.

P: Correct the SQL statement and re-execute.

KFPA11241-E A

Invalid table specification, as qualiifier, authorization identifier aa....aa, table identifier or correlation name or query name "bb....bb", query-no=ccc

The specified column name or table specification that qualifies * or ROW is not the valid name specified in the SQL statement.
The invalid qualifier is aa....aa.bb....bb or "bb....bb".

aa....aa: Authorization identifier specified in the table specification

bb....bb: Table identifier, correlation name, or query name

ccc: Number of the innermost query specifying the invalid qualifier

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Correct the SQL statement and re-execute.

KFPA11242-E A

Column "aa....aa" not found in any tables or query names, query-no=bbb

Column "aa....aa" cannot be found in any SQL statement, table with a query specification, or query name.

aa....aa: Name of the column that is not in the SQL statement, query specification table, or query name

bbb: Number of the query specifying a column name not listed in the table

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Correct the SQL statement and re-execute.

KFPA11243-E A

Table aa....aa."bb....bb" with multi-value column in joined table

The following tables cannot be specified in a joined table:

Tables containing a repetition column

Tables derived from a table containing a repetition column

aa....aa: Authorization identifier for a table containing a repetition column, or for a table derived from a table containing a repetition column

bb....bb: Table identifier for a table containing a repetition column, or for a table derived from a table containing a repetition column

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Correct the SQL statement and re-execute.

KFPA11245-E A

Invalid part "aa....aa" in EXTERNAL NAME

One of the following errors was found in the external routine name:

In the case of an external Java stored routine:

An extraneous character string was detected at the end.

A letter or keyword that is syntactically invalid was detected.

A JAR file name or class name does not begin with an alphabetic character.

A JAR file name exceeds 255 bytes.

A class name, including the package name, exceeds 255 bytes.

A method name exceeds 255 bytes.

In the case of an external C stored routine:

An extraneous character string was detected at the end.

A letter that is syntactically invalid was detected.

An external function identifier begins with a number.

aa....aa: Area with an invalid external routine name. If a character that is syntactically invalid was detected, that character and its hexadecimal representation will be shown in parentheses.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11246-E A

Incomplete EXTERNAL NAME

The external routine name is incomplete.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11247-E A

Invalid Java method argument "aa....aa" in EXTERNAL NAME

One of the following errors was found in the Java method argument of the external routine name:

Another data type was specified following the java.sql.ResultSet type.

The java.sql.ResultSet type was not specified as an array.

A multi-dimensional array was specified for the java.sql.ResultSet type.

The byte type was not specified for an array.

A multi-dimensional array was specified for the byte type.

A multi-dimensional array was specified for a data type that is not the byte type.

The java.sql.ResultSet type was specified in CREATE FUNCTION.

aa....aa: Argument of the Java method containing the error

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11248-E A

Invalid Java method return data type "aa....aa" in EXTERNAL NAME

One of the following errors was found in the Java method return portion of the external routine name:

The java.sql.ResultSet type was specified.

An array was specified for a data type that is not the byte type.

The byte type was not specified for an array

A multi-dimensional array was specified for the byte type.

aa....aa: Java method return portion containing the error

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11249-E A

Invalid specification of style in PARAMETER STYLE

One of the following errors was detected in the parameter style:

JAVA was specified for the LANGUAGE clause, but a parameter style other than JAVA was specified for the PARAMETER STYLE clause.

SQL was specified for the LANGUAGE clause.

C was specified for the LANGUAGE clause, but a parameter style other than RDSQL was specified for the PARAMETER STYLE clause.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11250-E A

Invalid number of DYNAMIC RESULT SETS

One of the following errors has occurred:

The number of result sets specified in the DYNAMIC RESULT SETS clause was a negative value or exceeded the maximum value.

The number of result sets specified in the DYNAMIC RESULT SETS clause was smaller than the number of result sets specified in the Java signature with external routine specification.

A cursor that specifies WITH RETURN was declared in an SQL procedure, and 0 was specified in the DYNAMIC RESULT SETS clause, or the DYNAMIC RESULT SETS clause was not specified.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11251-E A

Invalid item specification, authorization identifier aa....aa, statement label or routine identifier or loop variable "bb....bb", query-no=ccc

The qualifier specification for the SQL parameter or an SQL variable is invalid in SQL statements, or a column is specified in an incorrect location.
The invalid qualifier is aa....aa.bb....bb or "bb....bb".

aa....aa: The authorization identifier specified in the item specification

bb....bb: Statement label name, routine name, loop variable name, or table identifier

ccc: Number of the innermost query specifying an invalid qualifier

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Correct the SQL statement and re-execute.

KFPA11252-E A

SQL variable or SQL parameter "aa....aa" not found in any statement label or routines, query-no=bbb

Either the SQL variable or the SQL parameter "aa....aa" is not declared in the routine, or a column name is specified in an incorrect location.

aa....aa: The SQL variable, SQL parameter, or column name that is not in the routine

bbb: Number of the innermost query specifying an SQL variable, SQL parameter, or column name not found in the routine

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Correct the SQL statement and re-execute.

KFPA11254-E A

Invalid specification aa....aa-th argument in CALL statement, reason=parameter mode "bb....bb"

One of the following errors was found in the aa....aath argument of the CALL statement.

The argument is a value expression, but a parameter mode other than IN was specified.

The argument is a value expression, but the call procedure was a parameter mode other than IN.

aa....aa: Argument number containing the error

bb....bb: Parameter mode of the CALL statement argument, or parameter mode of the calling procedure

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11255-E A

SQL variable "aa....aa" not found in statement label or loop variable "bb....bb"

SQL variable "aa....aa" is not in statement label or loop variable "bb....bb".

aa....aa: SQL variable that does not exist

bb....bb: Statement label name or loop variable name

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Correct the SQL statement and re-execute.

KFPA11256-E A

SQL parameter "aa....aa" not found in routine bb....bb."cc....cc"

SQL parameter "aa....aa" is not in routine bb....bb."cc....cc".

aa....aa: SQL parameter that does not exist

bb....bb: Authorization identifier

cc....cc: Routine name

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Correct the SQL statement and re-execute.

KFPA11259-E A

Unable to specify invocation of aa....aa "bb....bb"."cc....cc" in definition of dd....dd with same name

When bb....bb is the authorization identifier of a routine being defined:

You cannot specify a call to a routine inside a routine definition when the routine being called and the routine being defined match in the following respects:

When aa....aa is function:

If the name of a called function specified in the body of function is qualified with an authorization identifier, when the called function and the function being defined share the same authorization identifier, routine identifier, and number of arguments

If the name of a called function specified in the body of function is not qualified with an authorization identifier, when the called function and the function being defined share the same routine identifier and number of arguments

When aa....aa is procedure:

If a procedure name in a call statement in the body of function is qualified with an authorization identifier, when the called procedure and the procedure being defined share the same authorization identifier and routine identifier

If a procedure name in a call statement in the body of function is not qualified with an authorization identifier, when the called procedure and the procedure being defined share the same routine identifier

When bb....bb is PUBLIC:

You cannot specify a call to a routine inside a public routine definition when the routine being called and the routine being defined match in the following respects:

When aa....aa is function:

If the name of a called function specified in the body of function is qualified with PUBLIC, when the called function and the public function being defined share the same routine identifier and number of arguments

If the name of a called function specified in the body of function is not qualified with an authorization identifier, when the called function and the public function being defined share the same routine identifier and number of arguments

When aa....aa is procedure:

If a procedure name in a call statement in the body of function is qualified with PUBLIC, when the called procedure and the public routine being defined share the same authorization identifier and routine identifier

If a procedure name in a call statement in the body of function is not qualified with an authorization identifier, when the called procedure and the public routine being defined share the same routine identifier

aa....aa: {function|procedure}

bb....bb: {authorization identifier|PUBLIC}

cc....cc: Routine identifier

dd....dd:

{ function |procedure }

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11260-E A

Attribute "aa....aa" not defined in abstract data bb....bb "cc....cc"

"aa....aa" is not defined as an attribute of "cc....cc", which is a column of the abstract data type, an SQL variable, an SQL parameter, or an attribute.

aa....aa: Name of the undefined attribute

bb....bb:

{ column, SQL variable or SQL parameter |attribute }

cc....cc: Name of the column, SQL variable, SQL parameter, or attribute for which "aa....aa" is specified as an attribute

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11262-E A

aa....aa "bb....bb" not defined as abstract data

The column bb....bb, the SQL variable, the SQL parameter, or the attribute that is a qualifier in a component specification is not defined as an abstract data type.

aa....aa:

{ column, SQL variable or SQL parameter |attribute }

bb....bb: Name of the column, SQL variable, SQL parameter, or attribute

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11263-E A

Unable to access attribute "aa....aa" because of encapsulation level bb....bb

When bb....bb is PRIVATE:

Because the encapsulation level for the attribute "aa....aa" is PRIVATE, this attribute can be accessed only in the CREATE TYPE statement that defines it.

When bb....bb is PROTECTED:

Because the encapsulation level for the attribute "aa....aa" is PROTECTED, this attribute can be accessed only in the CREATE TYPE statement that defines it, or in a subtype CREATE TYPE statement.

aa....aa: Name of the attribute

bb....bb: Encapsulation level

{ PRIVATE |PROTECTED }

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11266-E A

Unable to specify component specification in argument of set function

Component specifications cannot be specified in an argument in a set function.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11267-E A

Unable to specify component specification in "SELECT" clause in INSERT statement

Component specifications cannot be specified in the SELECT clause of an INSERT statement (except for a SELECT clause in a subquery).

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11273-E A

Invalid use of WRITE specification

One of the following errors was found in the usage of the WRITE specification:

Duplicate locking cannot be specified for a query in which a WRITE specification is specified.

A WRITE specification cannot be used as a sort key.

When a BLOB column is specified for the output BLOB value of a WRITE specification, the same column cannot be specified by itself in the selection expression or in the output BLOB value of another WRITE specification.

When the output BLOB value of a WRITE specification is not a column, FOR READ ONLY cannot be specified for the query.

A WRITE specification cannot be specified in a routine.

A set operation cannot be specified for a query in which a WRITE specification is specified.

A WRITE specification cannot be specified in the selection expression of a query specification of an INSERT statement.

A WRITE specification cannot be specified in the selection expression of a subquery (including the derived table of a FROM clause).

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11274-E A

Invalid use of GET_JAVA_STORED_ROUTINE_SOURCE specification

One of the following errors was detected in the use of a GET_JAVA_STORED_ROUTINE_SOURCE specification:

Duplicate locking cannot be specified in a query in which a GET_JAVA_STORED_ROUTINE_SOURCE specification is specified.

A GET_JAVA_STORED_ROUTINE_SOURCE specification cannot be specified as a sort key.

When a GET_JAVA_STORED_ROUTINE_SOURCE specification is specified, FOR READ ONLY cannot be specified in the query.

A set operation cannot be specified for a query in which a GET_JAVA_STORED_ROUTINE_SOURCE specification is specified.

A GET_JAVA_STORED_ROUTINE_SOURCE specification cannot be specified for the selection expression of a query specification of an INSERT statement.

A GET_JAVA_STORED_ROUTINE_SOURCE specification cannot be specified for a selection expression inside a subquery (including the derived table of a FROM clause).

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11276-E A

Unable to specify outer reference column of abstract data type

An abstract data type column that makes an external reference cannot be specified.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11277-E A

Unable to specify outer reference column of BLOB data type in argument of function invocation

BLOB columns that make an external reference cannot be specified in an argument for a user-defined function.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11280-E A

PLUGIN not installed for abstract data type "aa....aa"."bb....bb"

A plug-in for the abstract data type "aa....aa"."bb....bb" is not installed.

aa....aa: Authorization identifier

bb....bb: Name of the abstract data type

S: Ignores this SQL statement.

P: Ask the HiRDB administrator to install the required plug-in.

Action

Install the required plug-in.

KFPA11281-E A

PLUGIN "aa....aa" not installed

The plug-in "aa....aa" is not installed.

aa....aa: Name of the plug-in

S: Ignores this SQL statement.

P: Ask the HiRDB administrator to install the required plug-in.

Action

Install the required plug-in.

KFPA11282-E A

Receiving function for inter-function value passing can be specified only in "SELECT" or "SET" clause

The receiving function for inter-function value passing can be specified only in an update value in the SELECT or SET clause (it cannot be specified in a routine control statement).

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11283-E A

Sending function for inter-function value passing can be specified only in "WHERE" clause or "ON" condition in query specification without view or "WITH" clause

The sending function for inter-function value passing can be specified only in a WHERE clause or an ON search condition (it cannot be specified in the routine control statement). However, if you specify the sending function for inter-function value passing in the ON search conditions of a joined table specifying an outer join, you cannot specify a column of the outer table in the first argument.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11284-E A

Sending function for inter-function value passing cannot be specified in "OR" condition

The sending function for inter-function value passing can be specified in the OR condition only when the index can be used (when specified following a NOT condition, an OR condition is converted into an AND condition and an AND condition is converted into an OR condition).
The index can be used when all of the following conditions are met:

A plug-in index is defined in the first argument of the sending function for inter-function value passing.

The first argument of the sending function for inter-function value passing is a column specification in a base table that does not make an external reference.

Arguments including the following expressions are not specified in arguments other than the first argument of the sending function for inter-function value passing:

Column specifications other than those that make an external reference

Component specification in a column

A predicate including IS FALSE, IS UNKNOWN, or NOT was not specified in the sending function for inter-function value passing.

No sending function for inter-function value passing was specified in CAST.

When the FROM clause specifies more than one table, the table column that differs from the first argument of the sending function for inter-function value passing was not specified in the search conditions of the OR operand.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11285-E A

Function for inter-function value passing cannot be specified in "CASE" expression or scalar function "VALUE"

The receiving or sending function for inter-function value passing cannot be specified in a CASE expression or the scalar function VALUE.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11286-E A

Receiving function for inter-function value passing without sending function

The receiving function for inter-function value passing cannot be specified unless there is a corresponding sending function for inter-function value passing in the same query specification. For details about the corresponding send function for passing inter-function values, see the plug-in manual. If a table is being searched via a list, the cause is that the receive function for passing inter-function values does not correspond to the inter-function values collected from the list.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute. For a table search via a list, the plug-in version is old, which may cause the receive function for passing inter-function values not to correspond to the inter-function values collected from the list. In this case, contact the HiRDB administrator.

Action

For a table search via a list, obtain the plug-in version, and refer to the manual that corresponds to that version. Check that the receive function for passing inter-function values corresponds to the inter-function values collected from the list, and upgrade the plug-in version if necessary.

KFPA11287-E A

Invalid specification of first argument in receiving function for inter-function value passing

The first argument in the receiving function for inter-function value passing is invalid. The first argument must satisfy the following conditions:

Its data type must be an abstract data type.

It must be specified in a column specification, an SQL parameter, or an SQL variable.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11288-E A

Unable to specify receiving function for inter-function value passing except in set function in query with grouping or set function

In a query specifying a GROUP BY clause, a HAVING clause, or a set function, a receiving function for inter-function value passing cannot be specified in locations other than an argument for a set function.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11289-E A

More than one sending function for inter-function value passing with same first arguments

Two or more receiving functions for inter-function value passing with identical first arguments cannot be specified.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11291-E A

No available index for ARRAY predicate

An index for the evaluation of a structured repetition predicate is missing.
For queries that include an RDAREA name specification, the structured repetition predicate cannot be evaluated because the number of partitions of the index for the structured repetition predicate is different from the number of partitions of the table.

S: Ignores this SQL statement.

P: Take one of the following actions:

Correct the SQL statement, or revise the index definition, and then retry the operation.

When an RDAREA name is specified, make sure that the number of partitions of the defined index is equal to the number of partitions of the table, and then re-execute the SQL statement.

KFPA11292-E A

Unable to specify ARRAY predicate in operand of boolean operator "NOT"

A structured repetition predicate cannot be negated by using the NOT operator.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11294-E A

Unable to specify ARRAY predicate with columns of aa....aa of outer join in bb....bb, query-no=ccc

A structured repetition predicate cannot be specified for the following columns:

Column in an outer table in an ON search condition of a query specification that includes an outer join

Column in an inner table in a WHERE clause of a query specification that includes an outer join

aa....aa: Table type:

inner table: Inner table

outer table: Outer table

bb....bb: Condition type:

ON condition: In an ON search condition

WHERE clause: In a WHERE clause

ccc: Query number in which the predicate is specified

S: Ignores the SQL statement and continues processing. Rollback occurs in the case of a definition SQL statement.

P: Correct the SQL statement as explained below and re-execute:

When specifying a structured repetition predicate for a column of an outer table of a joined table in a query specification that includes an outer join, specify the predicate in a WHERE clause.

When specifying a structured repetition predicate for a column of an inner table of a joined table in a query specification that includes an outer join, specify the predicate in an ON search condition.

KFPA11295-E A

Unable to aa....aa rebalancing table bb....bb."cc....cc" with unique constraint

When table bb....bb."cc....cc" is being rebalanced and an index with UNIQUE specified is being defined for the table, aa....aa cannot be executed for that table.

aa....aa:

{ INSERT INTO|UPDATE }

bb....bb: Authorization identifier

cc....cc: Table identifier

S: Ignores this SQL statement.

P: Re-execute the SQL statement after the rebalancing has finished.

KFPA11296-E A

Unable to aa....aa shared table without LOCK TABLE IN EXCLUSIVE MODE

Without executing the LOCK statement with the IN EXCLUSIVE MODE specification, the following SQL statements cannot be executed for a shared table:

INSERT statement

UPDATE statement accompanying index updates

UPDATE statement specifying DEFAULT in the update value for a TIMESTAMP column with the USING BES specification defined in the DEFAULT clause

DELETE statement

aa....aa: {INSERT | UPDATE | DELETE}

S: Ignores this SQL statement.

P: Execute the LOCK statement with the IN EXCLUSIVE MODE specification on the table corresponding to the INSERT, UPDATE, or DELETE statement, and re-execute the SQL statement.

KFPA11299-E A

Duplicate LIST name "aa....aa" in ASSIGN LIST statement

List name "aa....aa" is already specified in the ASSIGN LIST statement. The same name cannot be specified more than once in an ASSIGN LIST statement.

aa....aa: Duplicated list name

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11301-E A

Inconvertible data type of input variable aa....aa

The data type of input variable aaaaa cannot be converted. Or, the input variable has an inconvertible structure (a simple structure or a repetition structure).

aa....aa: Sequence number of input variable

S: Ignores this SQL statement.

P: Change the input variable into a convertible data type with the correct structure, and then re-execute.

KFPA11302-E A

Input data too large for column or assignment target aa....aa

One of the following errors was detected:

The input data is outside the range of values permitted for the data type of the column.

The number of elements in the input data is greater than the maximum number of elements for a repetition column.

In a call-out of a user-defined function or system-defined scalar function, the input arguments exceed the range of values permitted for the data type of the parameter.

The argument of the input variable for the scalar function VALUE exceeds the range of values permitted for the data type.

aa....aa: One of the following characters:

Sequential number of the in variable variable
When independently specifying an input variable or when independently specifying an input variable in an argument for the scalar function VALUE

One-byte space
In all other cases

S: Ignores this SQL statement.

P: If the input data is invalid, correct it and re-execute.

KFPA11303-E A

Inconvertible data type of output variable aaaaa

The data type of output variable aaaaa cannot be converted. Or, the output variable has an inconvertible structure (a simple structure or a repetition structure).

aaaaa: Sequence number of the output variable

S: Ignores this SQL statement.

P: Change the output variable into a convertible data type with the correct structure, and then re-execute.

KFPA11304-E A

Output data too large for variable aa....aa

The data length to be output exceeds the value permitted for the variable attribute.

aa....aa: Sequential number of the invalid output variable

S: Ignores this SQL statement.

P: Change the attribute of the variable and re-execute.

KFPA11305-E A

Indicator must be specified for null value in variable aa....aa

Because no indicator variable was specified, null-value output data cannot be returned.

aa....aa: Sequential number of the invalid output variable

S: Terminates processing.

P: Specify an indicator variable and re-execute the UAP.

KFPA11306-E A

Invalid data aa....aa variable bbbbb

An error was detected in the following data (data to be set to national character string data type might have a length that is an odd number of bytes, or there might be data that cannot be converted into the target character set).

When aa....aa is in input:
Data in the bbbbbth input variable

When aa....aa is to output:
Data to be set in the bbbbbth output variable
Data to be set in the bbbbbth SQL parameter whose parameter mode is OUT or INOUT in an external routine
Data to be set in the bbbbbth SQL parameter (if bbbbb is *****) in an external routine

aa....aa: Variable type:

{ in input |to output }

bbbbb: One of the following:

Serial number of an input variable or output variable

Serial number of an SQL parameter whose parameter mode is OUT or INOUT.
***** is displayed for the return value of a function.

S: Ignores this SQL statement.

P: Correct the data and re-execute the SQL.

KFPA11307-E A

No RDAREA for specified divided Key VALUEs

The RDAREA for storing the specified values was not specified in the table definition.

S: Ignores this SQL statement.

P: Modify the specification so that the specified values satisfy the storage condition. Or, re-evaluate the specified storage condition.

KFPA11308-E A

Unexpected request, SQLNAME or TYPE option necessary in PREPARE

The DESCRIBE statement or the DESCRIBE TYPE statement cannot be executed for the following reasons:

In the PREPARE statement, the receipt (Column Name Descriptor Area (SQLCNDA)) of either a column name or an attribute name is specified in either the DESCRIBE or DESCRIBE TYPE statement without the specification of the WITH SQLNAME OPTION.

In the PREPARE statement, the receipt (Type Name Descriptor Area (SQLTNDA)) of a data type name of a user-defined type is specified in the DESCRIBE statement without the specification of the WITH TYPE OPTION.

In the PREPARE statement, the DESCRIBE TYPE statement is specified without the specification of the WITH ALL TYPE OPTION.

S: Ignores this SQL statement.

P:

In the PREPARE statement, specify the WITH SQLNAME OPTION and re-execute. Or, re-execute without specifying the Column Name Descriptor Area (SQLCNDA) in either the DESCRIBE or DESCRIBE TYPE statement.

In the PREPARE statement, specify the WITH TYPE OPTION and re-execute. Or, re-execute without specifying the Type Name Descriptor Area (SQLTNDA) in either the DESCRIBE or DESCRIBE TYPE statement.

In the PREPARE statement, specify the WITH ALL TYPE OPTION and re-execute. Or, re-execute without specifying the Type Name Descriptor Area in the DESCRIBE TYPE statement.

KFPA11310-E A

Invalid number of variables

The value of either SQLN or SQLD specified in the SQL descriptor area is invalid.

S: Ignores this SQL statement.

P: Correct the value specified for either SQLN or SQLD to satisfy the conditions 0 SQLD 30,000 and SQLD SQLN 30,000 and re-execute.

KFPA11311-E A

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

Embedded variable aa....aa or parameter variable declaration is invalid. Or, the maximum number of elements, the data type, or the length of the aa....aath variable specified in the SQL descriptor area is invalid.

aa....aa: Sequence number of variable#

#

When specifying an embedded variable or ? parameter as an argument of a CALL statement, the sequence number output in aa....aa might be different from the order of the variables specified in the CALL statement. This is to keep the sequence numbers separate for variables whose input/output mode is IN and variables whose input/output mode is OUT.

bb....bb: Additional information

Any of the following information:

(input) cc....cc (argument):

The cc....ccth input argument of the CALL statement or CALL COMMAND statement is incorrect.

(output) cc....cc (argument):

The cc....ccth output argument of the CALL statement or CALL COMMAND statement is incorrect.

(into):

aa....aa is the sequence number of the variable specified in into.

(using):

aa....aa is the sequence number of the variable specified in using.

S: Ignores this SQL statement.

P: Correct the embedded variable or parameter variable declaration and re-execute. Or, correct the maximum number of elements, the data type, or the length of the aa....aa variable specified in the SQL descriptor area and re-execute. In addition, if UTF-8 or CHINESE-GB18030 is used as the character encoding, specify a data type other than national character string data for the embedded variable, and then retry the operation.

KFPA11312-E A

Sum of aa....aa variable length exceeds 2GB

The total length of variable aa....aa exceeds 2 GB.

aa....aa: Variable resulting in the error:

INPUT: Input variable

OUTPUT: Output variable

S: Ignores this SQL statement.

P: Correct what is specified in the SQL descriptor area so that the total length of the input and output variables is less than 2 GB, and then re-execute the SQL statement. For details about how to calculate the total length of the input and output variables, see Outbound message length (when executing other SQL code) and Inbound message length (when executing other SQL code) under Estimating the memory size of a client library in the HiRDB Version 9 UAP Development Guide.

KFPA11313-E A

Number of variables not equal to number of parameters

One of the following errors occurred:

The number of embedded variables specified in the DECLARE CURSOR statement is not the same as the number of embedded variables specified in the OPEN statement.

The number of ? parameters in the SQL code that is pre-processed in a PREPARE statement or EXECUTE IMMEDIATE statement is not the same as the number of embedded variables that give values to those ? parameters, or the number specified for SQLD in the SQL descriptor area.

A ? parameter, rather than an embedded variable, was specified in that SQL code that is not pre-processed in a PREPARE statement or EXECUTE IMMEDIATE statement, or a mixture of embedded variables and ? parameters was specified.

S: Ignores this SQL statement.

P: Depending on the error, take one of the following actions:

Correct the SQL statement so that the number of embedded variables specified in the DECLARE CURSOR statement is the same as the number of embedded variables in the OPEN statement, and then retry the operation.

Correct the SQL statement or program so that the number of ? parameters in the SQL code that is pre-processed in a PREPARE statement or EXECUTE IMMEDIATE statement is the same as the number of embedded variables that give values to those ? parameters or number specified for SQLD in the SQL descriptor area, and then retry the operation.

Change the ? parameters to embedded variables in the SQL code that is not pre-processed in a PREPARE statement or EXECUTE IMMEDIATE statement, and then retry the operation.

KFPA11314-E A

Invalid data type name specified in DESCRIBE TYPE

A data type name (owner name and data type identifier) not associated with the SQL statement preprocessed by the PREPARE statement was specified in the DESCRIBE TYPE statement. Only data type names of the user-defined type can be specified in selection item in the SQL statement preprocessed by the PREPARE statement.

S: Ignores this SQL statement.

P: Correct the specified data type name specification and re-execute.

KFPA11315-E A

Unable to use multi value columns on this client library or application

An attempt was made to reference or update a repetition column by using a version of a client library that does not support repetition columns.

S: Continues processing.

P: When not using a repetition column, revise the UAP so that the value 1 is explicitly assigned to the SQLXDIM of the SQL descriptor area. When using a repetition column, use a version of a client library that supports repetition columns, and then re-execute the preprocessing and execution steps.

KFPA11316-E R+A

Invalid number of elements of array variable

The size specified for an array is 0, a negative value, or is greater than the maximum value.

S: Ignores this SQL statement.

P: Correct the program so that the dynamic size value specified in the FETCH or INSERT statement that uses the array is a value less than the maximum value, and re-execute.

KFPA11317-E E+L+P

An error occurred during XDS start or termination processing in XDS. information = aaa

An error occurred during XDS start or termination processing.

aaa: Maintenance information

S: Terminates abnormally.

O: If an error message was output immediately prior to this error message, then refer to that message to eliminate the cause of the error. If no error message was output prior to this message, save the contents of this message and any core file that was output. Then contact the HiRDB administrator.

Action

Contact the customer support center.

KFPA11318-E E+L+P

XDS aborted because an error occurred in XDS. information = aa....aa

An error was detected in XDS, therefore XDS was stopped.

aa....aa: Maintenance information

S: Terminates abnormally.

O: If an error message was output immediately prior to this error message, then refer to that message to eliminate the cause of the error. If no error message was output prior to this message, save the contents of this message and any core file that was output. Then contact the HiRDB administrator.

Action

Contact the customer support center.

KFPA11321-E A

Sequence generator limit exceeded, sequence generator=aa....aa."bb....bb"

The sequence generator aa....aa."bb....bb", which was specified as NO CYCLE, exceeded the maximum value or fell below the minimum value.

aa....aa: Authorization identifier

bb....bb: Sequence generator identifier

S: Ignores this SQL statement.

P: After deleting the sequence generator once, define the sequence generator again.

KFPA11326-E A

Length, precision, or number of elements of input variable "aa....aa" conflicts with SQLDA

The data in input variable "aa....aa" contradicts the specification in an embedded variable, parameter variable declaration, or SQL Data Area:

If the input variable is variable-length data, its length either exceeds the maximum value or is 0 or less.

If the input variable is decimal data, either the data format is invalid or the precision is invalid.

If the input variable is a repetition column, either the number of elements is greater than the maximum allowable number or is less than or equal to 0.

aa....aa: Sequence number of input variable

S: Ignores this SQL statement.

P: Correct the input data, variable declaration, or specification in the SQL Data Area and re-execute.

KFPA11329-E A

Invalid SQL for query in "aa....aa"

One of the following errors has occurred:

An SQL statement using the cursor is invalid for the query specified in the cursor declaration.

For a query specified by a cursor allocation, an SQL statement using the cursor is incorrect.

A query specifying a table can be executed only by the UPDATE or DELETE statement for the table.

aa....aa: {DECLARE CURSOR|ALLOCATE CURSOR}

S: Ignores this SQL statement.

P: Correct the SQL statement, recompile the module, then execute it.

KFPA11330-E A

CURSOR not opened or not positioned on any ROW

One of the following errors was detected:

The cursor has not been opened.

Row retrieval was not executed.
The row cannot be updated or deleted using the cursor.

S: Ignores this SQL statement.

P: Define the cursor, open it, modify the UAP so that the row can be updated or deleted, then re-execute.

KFPA11331-E A

Specified table different from that in cursor specification

The table specified in the cursor specification is not the same as the table specified in this SQL statement. Therefore, the UPDATE or DELETE statement cannot be executed using the cursor.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11332-E A

Fetch of all ROWs completed, or an error occurred during fetch

Because row fetch was completed or an error occurred during row fetch processing, the cursor specified in the UPDATE or DELETE statement cannot be executed.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11340-E A

Invalid address for variable aaaaa in SQLDATA or SQLIND

The value specified in SQLDATA or SQLIND in the SQL descriptor area is invalid or has not been set. Another possibility is that an address for an embedded variable or indicator variable in the SQL statement is incorrect.

aaaaa: Sequence number of variable

S: Ignores this SQL statement.

P: Set the variable correctly and re-execute.

KFPA11342-E A

Insufficient data area in client, size=aa....aa

Retrieval result cannot be transferred to the client, because the output buffer is too small.

aa....aa: Length (in bytes) of the data area requested by the client

The size of the data area includes the length of the SQL descriptor area.

S: Ignores this SQL statement.

P:

Check the type of embedded variable that receives the retrieval result to make sure that it correctly corresponds to the data type of the column.

If the SQL descriptor area is used directly, check if the value of SQLLEN is set correctly based on the data type of the corresponding column.

If an indicator variable is used, check if the length of the receive area is correct.

If a Column Name Descriptor Area (SQLCNDA) or Type Name Descriptor Area (SQLTNDA) is used, check that the length of the receive area is correct.

KFPA11343-E A

Invalid condition number in "GET DIAGNOSTICS" statement

The following values cannot be specified as a condition number:

Value smaller than zero

Value greater than the number of errors in the diagnostic area

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11351-E A

Unable to specify column or value expression for update value of ADD clause in UPDATE statement with cursor

The following items cannot be specified as an update value in the ADD clause of the UPDATE statement using a cursor:

Columns

Scalar operations

Component specifications

Function invocations

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Correct the SQL statement and re-execute.

KFPA11355-E A

Unable to FETCH from LIST using arrays

A FETCH that uses an array cannot be used for a search via a list.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11356-E A

File "aa....aa" bb....bb error occurred in processing for WRITE specification, code=cc....cc

An error occurred during a file operation for the processing of a WRITE specification.

aa....aa: Name of the file in which the error occurred:

If the file name consists of no more than 126 bytes, the entire file name is displayed; if it exceeds 126 bytes, the excess is truncated, and 2 bytes of periods (..) are displayed following the first 126 bytes.

bb....bb: Operation in which the error occurred:

OPEN: Error occurred in open system call in BLOB data file

CLOSE: Error occurred in close system call in BLOB data file

WRITE: Error occurred in write system call in BLOB data file

cc....cc: Detail codes for system-related errors

-20000: Output file exists.

Other than the above: see 4.2 Detail codes for system-related errors.

S: Ignores this SQL statement.

P:

When cc....cc is -20000:

Overwriting denied (a value of 2 or 6) was specified in the file output options. Check for an error in the file output options, eliminate the cause of the error, and then re-execute the SQL statement.

Other than above:

Eliminate the cause of the error and re-execute the SQL statement.

KFPA11358-E A

RDAREA aa....aa freezed

RDAREA aa....aa is in frozen update status.

aa....aa: Name of the RDAREA

S: Ignores this SQL statement.

Action

To handle a frozen area:

Check to be sure your work flow did not incorrectly issue a request to update an RDAREA in frozen update status.

Use the pddbfrz -d command to release the frozen update status of the RDAREA, and re-execute. In such cases, perform maintenance on the RDAREA, and then back up the entire RDAREA.

KFPA11359-E A

Unable to delete row in delete prohibition period

The process cannot delete a row in the falsification prevented table during the deletion prevented period.

S:

Deleting using the cursor:
The process continues without deleting the row indicated by the cursor.

In all other cases:
The process ignores this SQL statement and rolls back.

P: Correct the deletion conditions and re-execute.

KFPA11360-E A

Invalid format specification in scalar function "aa....aa", pos=bbb, query-no=ccc, format="dd....dd"

The format specified by the scalar function "aa....aa" is invalid.

aa....aa: Name of the scalar function that specified the invalid format:

{VARCHAR_FORMAT|DATE|TIME|TIMESTAMP_FORMAT}

bbb: Location where the error was detected (byte bbb)

ccc: Query number

dd....dd: Invalid format:

"dd....dd" displays a hash mark (#) at byte 100 when the format exceeds 100 bytes.

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Check the available format elements, correct the format, and re-execute.

KFPA11361-E A

Character representation unmatch specified format in scalar function "aa....aa", pos=bbb, query-no=ccc, format="dd....dd"

The character string representation in scalar function "aa....aa" does not match the specified format.

aa....aa: Scalar function specifying a value expression that does not match the format

{DATE|TIME|TIMESTAMP_FORMAT}

bbb: Location of character string representation that does not match the specified format (byte bbb of the format)

ccc: Query number

dd....dd:

Specified format:

"dd....dd" displays a hash mark (#) at byte 100 when the format exceeds 100 bytes. Also, when the query specifies a value expression not using a literal and specifies the format using a literal, the following character strings indicate format elements other than the character strings and the delimiting characters:

Year: YYYY

Month: MM

Abbreviations for month: MON, Mon, mon#

Name of a month: MONTH, Month, month#

Day: DD

Hour: HH

Minute: MI

Second: SS

Fractional second: NN....N (the specified number of digits)

#: Follows the upper case or lower case convention described in the format (in the first or second character).

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Either make the specified format and the character string match or correct the format and re-execute.

KFPA11362-E A

No format element aa....aa in format specification in scalar function "bb....bb", query-no=ccc

The format specified by scalar function "bb....bb" does not contain the required format element aa....aa.

aa....aa: The missing format element:

{DD|HH|MI|MM, MON or MONTH|SS|YYYY}

bb....bb: Scalar function:

{DATE|TIME|TIMESTAMP_FORMAT}

ccc: Query number

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Check the correlation between the scalar function and the required format elements, add the required format elements, and re-execute.

KFPA11364-E A

Invalid LOCATOR specified, pos=aaaaa

An invalid locator was specified.

aaaaa: Sequence number of the embedded variable or ? parameter

S: Performs one of the following processing functions:

For the FREE LOCATOR statement
Invalidates all valid locators.

For all else
Ignores this SQL statement.

P: Correct the SQL statement to specify a valid locator, and re-execute.

KFPA11366-E A

Indicator must be specified for null value assigned to LOCATOR in variable aa....aa

The data value assigned to the locator is a null value, and there is no indicator variable.

aa....aa: Sequence number of the embedded variable or ? parameter

S: Ignores this SQL statement.

P: Specify an indicator variable in the locator, and re-execute the UAP.

KFPA11367-E A

Unable to update non null valued column with "UPDATE ONLY FROM NULL"

Because the value stored in the column with UPDATE ONLY FROM NULL specified is not a null value, this column cannot be updated.

S: Ignores this SQL statement.

P: Correct the UAP so that it does not update a column that contains a non-null value that is specified with UPDATE ONLY FROM NULL, and re-execute.

KFPA11381-E A

Overflow in converting floating point numeric, type=aa....aa

Overflow occurred during conversion of data to floating-point data.

aa....aa: Error cause:

{INPUT|OUTPUT}

S: Ignores this SQL statement.

P: Change the data type so that overflow does not occur.

KFPA11382-E A

Invalid use of "CURRENT OF" clause

CURRENT OF cursor-name or extended cursor name was specified during batch retrieval.

S: Ignores this SQL statement.

P: Correct the SQL statement so that CURRENT OF cursor-name or an extended cursor name is not specified. Or, correct the environment definition so that batch retrieval is not executed.

KFPA11385-E E+L+P

A timeout was detected during command sending or receiving processing in XDS. wait time = aa....aa

After data was sent to request command processing, a timeout was detected before the message was received.

aa....aa: Timeout time (unit: minutes)

S: Terminates processing.

O: If you can specify the cutoff time for command processing, change the cutoff time and re-execute. If this message is displayed repeatedly, contact the HiRDB administrator.

Action

If this message is output repeatedly, contact the customer support center.

KFPA11401-E A

Inconvertible data type in "aa....aa" predicate, query-no=bbb

The data types specified in the operands on both sides of predicate aa....aa are not valid for comparison or conversion. Even if the operands on both sides of predicate aa....aa are character string data types, they cannot be compared or converted if they are coded in different character sets. However, the following value expressions can be converted to the character set of the comparison target, and then, compared:

Character string literals

Embedded variables

? parameters

aa....aa: Predicate specifying the invalid data types:

{COMPARISON|IN|LIKE|BETWEEN|XLIKE|SIMILAR}

bbb: Number of the query specifying the predicate

S: Ignores this SQL statement.

P: Correct the predicate and re-execute.

KFPA11402-E A

Argument of "AVG" or "SUM" must be numeric, query-no=aaa

The argument of a set function (AVG or SUM) is not numeric data.

aaa: Number of the query specifying a set function

S: Ignores this SQL statement.

P: Correct the set function and re-execute.

KFPA11403-E A

Unable to specify "aa....aa"."bb....bb" in SET function "cc....cc", query-no=ddd

If arguments of a set function specify values other than columns, they must not include rows that make an external reference.

aa....aa: Table identifier or correlation name

bb....bb: Name of column that makes an external reference

cc....cc: Name of the set function

ddd: Query number

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11404-E A

Input data too long for column or assignment target aa....aa

One of the following errors was detected:

A column of the input data is longer than the defined column.

The assignment value data in the SET statement is longer than the assignment destination.

In a call-out of a user-defined function or system-defined scalar function, the argument is too long for the parameter.

An argument is longer than the data in the result of the scalar function VALUE.

The default value specified in the DEFAULT clause of the SQL variable declaration is too long for the SQL variable.

The input data is too long for the AS data type specification.

aa....aa: One of the following characters:

Sequential number of the in variable variable
When independently specifying an input variable or when independently specifying an input variable in an argument for the scalar function VALUE

One-byte space
In all other cases

S: Ignores this SQL statement.

P: Correct the input data and re-execute.

KFPA11405-E A

Numeric literal out of range

Specified numeric literal is outside the following permitted value range:

Integer literal:

-2,147,483,648 to 2,147,483,647

Decimal literal#:

10³⁸ to (10³⁹ - 1)

Floating point numeric literal:

4.9 10⁻³²⁴ to 1.7 10³⁰⁸

Integer literal specified for a labeled duration:

YEAR(S): -9,998 to +9,998

MONTH(S): -119,987 to +119,987

DAY(S): -3,652,058 to +3,652,058

HOUR(S): -23 to +23

MINUTE(S): -1,439 to +1,439

SECOND(S): -86,399 to +86,399

Integer literal specified as the row count in the LIMIT clause: -1 to +2,147,483,647

Integer literal specified as the offset in the LIMIT clause: 0 to +2,147,483,647

#: The maximum number of specifiable digits is 38 (including the number of leading zeros).

S: Ignores this SQL statement.

P: Correct the specification of the numeric literal and re-execute.

KFPA11406-E A

Arithmetic operation cannot be specified for string, binary, timestamp, abstract, or Boolean data, query-no=aaa

Arithmetic operations cannot be specified for national character string data, large object data (BLOB), binary data (BINARY), timestamp data, abstract data, or Boolean data (BOOLEAN).
In addition, if character string data or mixed character string data is specified, the following restrictions apply:

Arithmetic operations cannot be specified for the following value expressions if they result in character string data:

USER value function

SQLERRM_OF_LAST_CONDITION

When specifying arithmetic operations involving character string data or mixed character string data in the following locations, only character string literals or mixed character string literals can be specified:

Selection expression

Argument of a set function

Argument of a user-defined function (including system-defined scalar functions)

GROUP BY clause

Value expression in a VALUES clause for a partitioning column

Value expression in the VALUES clause of an INSERT statement, or in the SET clause of the UPDATE statement, referenced by a new values correlation name

Value expression in the SET clause of the UPDATE statement referenced by an old values correlation name

aaa: Number of the query specifying character string data, national character string data, mixed character string data, large object data, binary data, timestamp data, abstract data, or Boolean data.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11407-E A

aa....aa predicate can be specified for string data only, query-no=bbb

The LIKE, XLIKE, or SIMILAR predicate cannot be specified in any of the following data types:

Numeric data

Date data

Date interval data

Time data

Time interval data

Timestamp data

Large object data

Binary data (however, binary data with a maximum length of 32,000 bytes can be specified in a LIKE or SIMILAR predicate)

aa....aa: error-containing predicate {LIKE |XLIKE |SIMILAR}

bbb: The query number in which an invalid LIKE, XLIKE, or SIMILAR predicate is specified

S: Ignores this SQL statement.

P: Revise the LIKE, XLIKE, or SIMILAR predicate, and re-execute.

KFPA11408-E A

Inconvertible data type for update or insert value

The data type of the specified update or insertion value cannot be converted.
When an insertion or update is performed on a character string data type, the insert or update value must use the same character set as the target of the insertion or update. However, if an embedded variable, ? parameter, or character string literal is specified as the update value, it is automatically converted to the character set of the update target.
When an insertion or update is performed on an abstract data type, the insert or update value must be the same abstract data type as the target of the insertion or update, or a subtype of the target of the insertion or update.

S: Ignores this SQL statement.

P: Correct the update or insert value and re-execute.

KFPA11409-E A

Unable to specify character string data of more than 4,036 bytes in aa....aa in XDS

Character type data of 4,037 bytes or more was specified in an invalid location of the memory database allocation table in SQL.

aa....aa:

"COMPARISON" predicate

"SELECT" clause

"ORDER BY" clause

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11410-E A

Invalid numeric literal aa....aa

Specified numeric literal contains a syntax error.

aa....aa: Erroneous numeric literal

S: Ignores this SQL statement.

P: Correct the numeric literal and re-execute.

KFPA11411-E A

Inconvertible data type in concatenation operation, query-no=aaa

The data types specified in the operands on both sides of a concatenation operation are not valid for comparison or conversion. Even if the operands on both sides of the concatenation operation are character string data types, conversion is not possible when the character sets are different. However, the following value expression can be converted to the character set of the other operand:

Character string literal

aaa: Number of the query specifying a nonconvertible data type in a data type of a concatenation operation

S: Ignores this SQL statement.

P: Correct the specification of the concatenation operation and re-execute.

KFPA11412-E A

Concatenation operation can be specified for string data except large object, query-no=aaa

The following data types cannot be specified for concatenation operations:

Date data

Year-to-day data

Time data

Hour-to-second data

Timestamp data

Large object data (BLOB)

Abstract data

Logical data (BOOLEAN)

However, the concatenation operation of large object data (BLOB) cannot be specified in the update value of the UPDATE statement.

aaa: Number of the query specifying an invalid data type

S: Ignores this SQL statement.

P: Correct the specification of the concatenation operation and re-execute.

KFPA11413-E A

Invalid operation specified in date/time arithmetic operation, query-no=aaa

A data type not permitted for a date or time operation was used in an arithmetic operation (such as date data plus date data or year-to-day data minus integer data). Or, a monomial operation is used for date data, time data, or labeled duration.

aaa: Number of the query specifying an invalid date or time operation

S: Ignores this SQL statement.

P: Correct the specification of the arithmetic operation and re-execute.

KFPA11414-E A

Invalid use of labeled duration, query-no=aaa

A labeled duration can be specified only for an addition or subtraction operation on date or time data.

aaa: Query number specifying the invalid labeled duration

S: Ignores this SQL statement.

P: Correct the specification of the labeled duration and re-execute.

KFPA11415-E A

aa....aa can be specified for integer or smallint data only, query-no=bbb

Only INTEGER or SMALLINT data types can be specified for aa....aa.

aa....aa: The value expression or predicate that caused an error

{Labeled duration|Row count in "LIMIT" clause}

bbb: Query number

S: Ignores this SQL statement.

P: For a labeled duration, correct the specified value expression and re-execute. For LIMIT, correct the specified row count or offset, and re-execute.

KFPA11416-E A

Invalid character representation for data type aa....aa

One of the following errors was detected in the character string representation that the data type aa....aa indicates:

A character other than a numeral or hyphen (-) was used in the character string representation of the date data.

Three or more hyphens (-) were used in the character string representation of the date data or the time data.

The character string representation of the date data or the time data does not meet one of the following conditions:
0001 year 9999
01 month 12
01 day last day of month

A character other than a numeral or colon (:) was used in the character string representation of the timestamp data.

Three or more colons (:) were used in the character string representation of the timestamp data.

The character string representation of the time data or the timestamp data does not meet one of the following conditions:
00 hour 23
00 minute 59
00 second 59

A character other than a numeral, hyphen (-), colon (:), space, or period (.) was used in the character string representation of the timestamp data.

Two or more spaces or periods (.) were used in the character string representation of the timestamp data.

The character string representation of the timestamp data does not meet the following condition:
000000 fractional second 999999

A digit count other than 0, 2, 4, or 6 was specified for the fractional second precision in the character string representation of the timestamp data.

A character other than a sign (+ or -) or a numeral was used in the character representation of the integer.

A character other than a sign (+ or -), a decimal point (.) or a numeral was used in the decimal character representation.

No decimal was used in the decimal character representation.

A character other than a sign (+ or -), a numeral, E, or e was used in the floating-point character string representation.

Neither E nor e was used in the floating-point character string representation.

aa....aa: Data in which an invalid character string representation is specified

{TIME|DATE|TIMESTAMP|INTEGER|DECIMAL|FLOAT}

S: Ignores this SQL statement.

P: Correct the data with character string representation and re-execute.

KFPA11417-E A

Value specifications cannot be specified for both operands of compare operation or left-hand side operand in predicate "IN", query-no=aaa

A ? parameter cannot be specified in both operands of a comparison predicate. Another possibility is that a value (literal, USER, CURRENT_DATE, CURRENT_TIME, CURRENT_TIMESTAMP, ? parameter) cannot be specified in both operands of a comparison predicate or in the left operand of the IN predicate.

aaa: Number of the query specifying the comparison predicate or the IN predicate

S: Ignores this SQL statement.

P: Correct the specification of the comparison predicate or the IN predicate and re-execute.

KFPA11418-E A

Parameter cannot be specified in "SELECT" clause, query-no=aaa

The ? parameter or embedded variable cannot be specified in the SELECT clause.

aaa: Number of the query in which the ? parameter or embedded variable is specified

S: Ignores this SQL statement.

P: Correct the SELECT clause and re-execute.

KFPA11419-E A

Parameters cannot be specified for both operands of arithmetic operation or concatenation operation, query-no=aaa

The ? parameter cannot be specified in both operands of an arithmetic or concatenation operation.

aaa: Number of the query specifying the arithmetic operation or concatenation operation

S: Ignores this SQL statement.

P: Correct the specification of the arithmetic or concatenation operation and re-execute.

KFPA11420-E A

Result string of aa....aa too long or result type invalid, query-no=bbb

One of the following errors was detected:

The character string length of the result of value expression aa....aa exceeded one of the following maximums:
CHAR, VARCHAR, MCHAR, or MVARCHAR: 32,000 bytes
NCHAR or NVARCHAR: 16,000 characters
BINARY: 32,000 bytes

Because the character string length of the result of value expression aa....aa exceeded one of the following maximums, this result cannot be specified in the value expression of a HEX scalar function.
CHAR, VARCHAR, MCHAR, and MVARCHAR: 16,000 bytes
NCHAR and NVARCHAR: 8,000 characters
BINARY: 16,000 bytes

The result of the value expression aa....aa cannot be specified in a value expression in the scalar function HEX because it is one of the following data types:
BOOLEAN
BLOB

Because the value expression result of aa....aa is one of the following data types, the result cannot be specified in the value expression of a predicate or set function. However, the BOOLEAN type can be specified in a Boolean predicate.
BOOLEAN
BLOB
BINARY 32,001 bytes or larger

Because the data type of the value expression result of aa....aa is BLOB or is BINARY and is 32,001 bytes or larger, the result cannot be specified in a CALL statement, function call, or system definition scalar function argument.

aa....aa: Name of operation

{ concatenation |scalar function "SUBSTR"
|scalar function "HEX" |scalar function "UPPER"
|scalar function "LOWER" |scalar function "VALUE"
|scalar function "IS_USER_CONTAINED_IN HDS_GROUP"
|scalar function "BIT_AND_TEST"
|scalar function "TRIM"
|simple CASE |searched CASE |case abbreviation
|cast specification | scalar subquery }

bbb: Query number specifying aa....aa

S: Ignores this SQL statement; executes rollback in the case of a definition SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11421-E A

Invalid operation specified for arithmetic operation or concatenation operation, query-no=aaa

A concatenation operation was specified in an arithmetic operation. Or, an arithmetic operation was specified in a concatenation operation.

aaa: Number of the query specifying the invalid concatenation operation or arithmetic operation

S: Ignores this SQL statement.

P: Correct the concatenation or arithmetic operation and re-execute.

KFPA11422-E A

Variable or parameter cannot be specified for concatenation operation or date/time arithmetic operation, query-no=aaa

An embedded variable or ? parameter cannot be specified for the following operations:

Concatenation operation

Date or time operation

aaa: Number of the query specifying an embedded variable or the ? parameter

S: Ignores this SQL statement.

P: Correct the concatenation operation or time operation specifying the embedded variable or ? parameter and re-execute.

KFPA11424-E A

Invalid aa....aa in bb....bb predicate

The value expression aa....aa specified in the LIKE, XLIKE, or SIMILAR predicate contains an error.

aa....aa: Invalid SQL statement specification:

{PATTERN |ESCAPE CHARACTER}

PATTERN:

If bb....bb is either LIKE or XLIKE, the character following the escape character in the pattern character string cannot be an underscore (_), percent sign (%), or an escape character.

If bb....bb is SIMILAR, the pattern character string is specified incorrectly. For a description of conditions in which pattern character strings can be invalid, see the section on the SIMILAR predicate in the manual HiRDB Version 9 SQL Reference.

ESCAPE CHARACTER:

The length of the escape character is not one character.

bb....bb: Predicate containing an error

{LIKE |XLIKE |SIMILAR}

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Correct the SQL statement and re-execute.

KFPA11425-E A

Invalid data type for operand aaa in scalar function "bb....bb", query-no=ccc

The data type of the value expression or type expression specified at aaa is invalid in scalar function bb....bb. If bb....bb is TRIM and aaa is 1, the TRIM character might be two or more characters.

aaa: Number assigned to the invalid value expression

bb....bb: Name of the scalar function:

{ ABS |CHARACTER |DATE |DAY |DAYS |DECIMAL
|DIGITS |FLOAT |HEX |HOUR |INTEGER |LENGTH
|LOWER |MINUTE |MOD |MONTH |SECOND |SUBSTR
|TIME |TIMESTAMP |UPPER |VALUE |YEAR
|VARCHAR_FORMAT |TIMESTAMP_FORMAT
|IS_USER_CONTAINED_IN_HDS_GROUP|BIT_AND_TEST
| MICROSECOND | POSITION | TRIM }

ccc: Query number

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11426-E A

Operand aaa incompatible with first operand in bb....bb, query-no=ccc

The data types of the first value expression and the aaath value expression of a scalar function (VALUE, BIT_AND_TEST, POSITION, TRIM) or a CASE abbreviation (NULLIF, COALESCE) are not compatible. Even when the first value expression and the aaath value expression are character string data types, the data types might not be compatible if the character sets are different. However, if either the first value expression or the aaath value expression are one the following value expressions, it is converted to the character set of the corresponding value expression:

Scalar function VALUE, CASE abbreviation COALESCE:
If the aaath value expression is a character string literal, it is converted to the character set of the first value expression.

Scalar function POSITION:
If the first value expression is a character string literal, it is converted to the character set of the second value expression.

Scalar function BIT_AND_TEST, CASE abbreviation NULLIF:
If the first value expression is a character string literal, it is converted to the character set of the second value expression. Conversely, if the second value expression is a character string literal, it is converted to the character set of the first value expression.

Scalar function TRIM:
If the first value expression (the TRIM character) is a character string literal, it is converted to the character set of the second value expression (the TRIM source).

aaa: Number assigned to the value expression whose data type is not compatible with the data type of the first value expression

bb....bb: Erroneous function or expression:

{scalar function "VALUE"|scalar function "BIT_AND_TEST"
|scalar function "POSITION"
|scalar function "TRIM"
|case abbreviation "NULLIF"|case abbreviation "COALESCE"}

ccc: Query number

S: Ignores this SQL statement; executes rollback in the case of a definition SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11427-E A

Operand a out of range in scalar function "bb....bb", query-no=ccc

Value expression a in scalar function "bb....bb" does not satisfy the following conditions:

Scalar function SUBSTR

1 value-expression-2 length of value-expression-1

0 value-expression-3 length of value-expression-1 - value-expression-2 + 1

Note that 0 cannot be specified if a literal is specified in a.

Scalar function POSITION

1 value-expression-3 length-of-value-expression-2

a: Number assigned to the value expression:

{2|3}

bb....bb: Scalar function name {SUBSTR|POSITION}

ccc: Query number

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11428-E A

Variable or parameter cannot be specified in aa....aa, query-no=bbb

One of the following errors was detected in a scalar function (VALUE, HEX, or BIT_AND_TEST), in an embedded variable stored in the CASE expression, or the ? parameter.

An embedded variable or ? parameter was specified in the first operand of the scalar function (VALUE).

An embedded variable or ? parameter was specified as the value expression of the scalar function (HEX).

An embedded variable or the ? parameter was specified in both operands of the scalar operation (BIT_AND_TEST).

An embedded variable or ? parameter was specified in the first operand of the CASE abbreviation (COALESCE).

An embedded variable or ? parameter was specified in both operands of the CASE abbreviation (NULLIF).

An embedded variable or ? parameter was specified in the first WHEN clause of the simple CASE expression.

An embedded variable or ? parameter was specified in the THEN or ELSE clause of the simple CASE expression or searched CASE expression.

An embedded variable or ? parameter was specified in the CASE clause of the simple CASE expression.

aa....aa: Erroneous function or expression:

{ scalar function "VALUE" |scalar function "HEX"
|case abbreviation "COALESCE"
|case abbreviation "NULLIF"
|simple CASE |searched CASE
|scalar function "BIT_AND_TEST" }

bbb: Query number

S: Ignores this SQL statement; executes rollback in the case of a definition SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11430-E A

Invalid data type specified in select list

A data type of a selection expression is invalid.
Invalid data type:

BOOLEAN

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11431-E A

aa....aa error occurred, code=bbbb

An error occurred during execution of an internal system function.

aa....aa: Name of the internal function resulting in the error

bbbb: Detail error code

S: Ignores this SQL statement.

P: Contact the HiRDB administrator.

Action

Contact the customer support center.

KFPA11440-E A

Inconvertible data type in assignment statement

The data types of the assignment destination and assignment value in the SET statement are not convertible.
For the character string data type, the source and the destination of an assignment must use the same character set. However, if the assignment value is a character string literal, it is automatically converted to the character set of the assignment target, even if the character sets are different.
For an abstract data type, either the source and the destination of an assignment must have the same abstract data type, or the abstract data type for the source must be a subtype of that target.

S: Ignores this SQL statement and executes rollback.

P: Correct the SQL statement and re-execute.

KFPA11441-E A

Invalid use of data type in "SELECT" clause, select-list-no=aaaaa, query-no=bbb

When the literal, operation, component specification, or function invocation result specified in a selection expression is one of the following data types, you cannot query a table derived by specifying the FOR READ ONLY clause, duplicate elimination, or a set operation:

BLOB

BINARY (larger than 32,000 bytes)

Abstract data type

BOOLEAN

In the selection expression of the derived table of a FROM clause, the following data type operators cannot be specified in the operational result.

BLOB

BINARY with a maximum length of 32,001 bytes or more

aaaaa: The number in the selection expression with an invalid data type or data length

bbb: Query number

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11442-E A

Invalid use of BLOB in scalar function "LENGTH", query-no=aa

Usage of the LENGTH scalar function with a BLOB data column specified is incorrect. The LENGTH scalar function with a BLOB data column specified can be specified only in a selection expression or update value as a single-unit LENGTH function.

aa: Number of the query specifying an invalid LENGTH function

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Correct the SQL statement and re-execute.

KFPA11443-E A

Inconvertible data type of target specification "aa....aa" in FETCH or SELECT statement

The target specification for the FETCH statement or the single-row SELECT statement is not a convertible data type.
For a character string data type, one of the following conditions must be satisfied (except in the case of an embedded variable):

The FETCH statement and the target specification for the FETCH statement must use the same character set.

The single-row SELECT statement and the target specification for the single-row SELECT statement must use the same character set.

For an abstract data type, one of the following conditions must be satisfied:

The FETCH statement and the target specification for the FETCH statement must be of the same abstract data type.

The single-row SELECT statement and the target specification for the single-row SELECT statement must be of the same abstract data type.

The abstract data type of the FETCH statement must be a subtype of the abstract data type of the target specification for the FETCH statement.

The abstract data type of the single-row SELECT statement must be a subtype of the abstract data type of the target specification for the single-row SELECT statement.

aa....aa: Name of the target

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11444-E A

Invalid data type for operand aaa in bb....bb, query-no=ccc

The data type or format specified in a CASE expression is invalid for the following reason:

The result of the value expression is the BLOB type, BINARY type of 32,001 bytes or larger, abstract data type, or BOOLEAN type.

This error was detected in the following value expression:

Value expression aaa in the CASE abbreviation

Value expression in CASE aaa, WHEN aaa, or THEN aaa, or ELSE aaa of the simple CASE expression

Value expression in THEN aaa or ELSE aaa of the searched CASE expression

aaa: Number of the operand containing the erroneous value expression or the number of the erroneous value expression

bb....bb: Erroneous CASE expression or the operand of the erroneous CASE expression:

{ case abbreviation "COALESCE"
|case abbreviation "NULLIF"
|"CASE" in simple CASE |"WHEN" in simple CASE
|"THEN" in simple CASE |"ELSE" in simple CASE
|"THEN" in searched CASE |"ELSE" in searched CASE }

ccc: Query number

S: Ignores this SQL statement; executes rollback in the case of a definition SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11445-E A

Variables or parameters cannot be specified in argument of set function "aa....aa", query-no=bbb

An embedded variable, SQL parameter, or ? parameter cannot be specified in the argument of a set function.

aa....aa: Name of the set function specifying an embedded variable or ? parameter in its argument

bbb: Query number

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11446-E A

CASE operand is incompatible with WHEN operand aaa in simple CASE, query-no=bbb

The data type of a CASE value expression in a simple CASE expression is not compatible with the data type of the aaath WHEN value expression. Even if the CASE value expression in a simple CASE expression and the aaath WHEN value expression are character string data types, the data types might not be compatible if the character set are different. However, if the WHEN value expression is the following, it is converted to the character set of the CASE expression:

Character string literal

aaa: Number of value expression in WHEN that does not match the data type of the value expression in CASE

bbb: Query number

S: Ignores this SQL statement; executes rollback in the case of a definition SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11447-E A

THEN operand aaa is incompatible with THEN or ELSE operand bbb in simple CASE or searched CASE, query-no=ccc

The data type of the value expression in THEN aaa does not match the data type of the value expression in THEN bbb or ELSE bbb in a simple CASE expression or searched CASE expression.

aaa: Number of the value expression to become the basis for checking data type compatibility

bbb: Number of the value expression whose data type does not match the data type of value expression aaa

ccc: Query number

S: Ignores this SQL statement; executes rollback in the case of a definition SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11448-E A

At least one THEN operand in simple CASE or searched CASE must be value expression, query-no=aaa

NULL was specified in all THEN operands. In a simple CASE expression or searched CASE expression, a value expression must be specified in at least one THEN operand.

aaa: Query number

S: Ignores this SQL statement; executes rollback in the case of a definition SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11449-E A

Cardinality violation in single row select

The result of a single-row SELECT statement is two or more rows.

S: Ignores this SQL statement.

P: Either specify a query whose selection result becomes one row or less or use the cursor for selection.

KFPA11450-E A

Cardinality violation at aaa-th subquery.Two or more rows found

The result of a subquery of one of the following types consists of at least two rows:

Scalar subquery specified with a comparison predicate or the SET clause of an UPDATE statement

Row subquery

aaa: Position from the beginning of the subquery that resulted in the base error. However, when a set operation is specified in a subquery, this is the number of the first specified query in the set operation query specification. Also, if the cause of the error is the contents of the viewed table definition, this is the number of the query that specified the viewed table.

S: Ignores this SQL statement.

P: Correct the SQL statement so that the subquery result is one row or less and re-execute.

KFPA11451-E A

aa....aa constraint "bb....bb" violation at cc....cc

There is a violation of a referential constraint or a check constraint.

aa....aa: Type of constraint

{Referential|Check}

bb....bb: Name of the constraint involved in the constraint violation

cc....cc: SQL statement involved in the constraint violation

{INSERT | UPDATE | DELETE}

aa....aa: Referential (referential constraint violation)

For a primary key update of a referenced table, the value of the primary key configuration column before update and the value of the row that holds the equivalent foreign key configuration column are in the referencing table.

For a primary key deletion of a referenced table, the value of the primary key configuration column of the row to be deleted and the value of the row that holds the equivalent foreign key configuration column are in the referencing table.

For a foreign key insertion of a referencing table, the value of the primary key configuration column of the row to be inserted and the value of the row that holds the equivalent foreign key configuration column are not in the referencing table.

For a foreign key update of a referencing table, the value of the primary key configuration column after the update and the value of the row that holds the equivalent foreign key configuration column are not in the referencing table.

The same primary key has already been referenced within a table, and there are multiple definitions of referential constraints that include the ON UPDATE CASCADE specification in the specified referential constraint operation.

aa....aa: Check (check constraint violation)

The update value or the insert value does not satisfy the conditions defined for the check constraint.

The same primary key has already been referenced within a table, and there are multiple definitions of referential constraints that include the ON UPDATE CASCADE specification in the specified referential constraint operation.

S: Ignores this SQL statement. If this is a definition SQL statement, it is rolled back.

P:

aa....aa: Referential

If an UPDATE statement is for a referenced table, take one of the following actions:
Change the update conditions.
Delete from the referencing table the row that holds the foreign key value that is equivalent to the value of the primary key before update, or update the value of the foreign key of the referencing table to the value of another primary key in the referenced table.

If a DELETE statement is for a referenced table, take one of the following actions:
Change the deletion conditions.
Delete from the referencing table the row that holds the foreign key value that is equivalent to the value of the primary key to be deleted, or update the value of the foreign key of the referencing table to the value of another primary key in the referenced table.

If an INSERT statement is for a referenced table, take one of the following actions:
Change the value of the foreign key to be inserted to an appropriate value.
Add to the referenced table the row that holds the insert value of the foreign key of the referencing table as the primary key.

If an UPDATE statement is for a referenced table, take one of the following actions:
Change the update conditions.
Change the update value of the foreign key to an appropriate value.
Add to the referenced table the row that holds the update value of the foreign key of the referencing table as the primary key.

If an error occurs after taking the above actions, change the specification to one referential constraint that includes the ON UPDATE CASCADE specification in the referential constraint operation, which references the same primary key, and re-define the table.

aa....aa: Check

Correct the update or insertion value to satisfy the conditions of the check constraint definition.

If an error occurs even after taking the above action, change the specification to one referential constraint that includes the ON UPDATE CASCADE specification in the referential constraint operation, which references the same primary key, and re-define the table.

KFPA11453-E A

CAST error occurred, reason=aa....aa, query-no=bbb

The method of specifying CAST or the data content is invalid.

aa....aa: Error cause

COMBINATION:

An error occurred when combining the data type and data length of the value expression result with the data type and data length after conversion. This applies to the character set as well as the data type. For details about which data type conversions are possible, see the manual HiRDB Version 9 SQL Reference.

Examples: CAST(TIME-type AS INT)

CAST(MCHAR-type AS CHAR(1) CHARACTER SET EBCDIK)

FORMAT:

The format of a character string literal in the conversion source data is invalid.

(Example) CAST('ABC' AS INT)

VALUE:

A value in the conversion source data is invalid.

(Example) CAST('1999-99-99' AS DATE)

TRUNCATION:

Characters were truncated.

(Example) CAST(DATE-type AS CHAR(1))

OVERFLOW:

An overflow occurred.

(Example) CAST(99999 AS DEC(1,1))

INVALID CAST OPERAND:

An invalid specification exists in the conversion source.

(Example) CAST(BLOB-type AS data-type)

DATA TYPE:

A data type that cannot be used is specified as a conversion data type.

(Example) CAST(C1 AS BLOB)

bbb: Number of the query specifying CAST specification that caused the error.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11455-E A

Unable to specify aa....aa in view definition or in "WITH" query

If a CASE expression is specified in a selection expression in the outermost query of a view definition, or in a derived query expression for a query in a WITH clause, a repetition column cannot be specified in its search condition.

aa....aa: multi-value column in search condition of CASE expression

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11456-E A

Outer reference specified for column derived from set function with argument of operation

When a set function in which an operation is an argument is specified in either a selection expression for a view definition or a selection expression in a derived query expression for a query in a WITH clause, the applicable column cannot be specified in a subquery as an outer reference column.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11458-E A

Duplicate query name "aa....aa" in "WITH" clause

Query name "aa....aa" is duplicated in the WITH clause. The same query name cannot be specified more than once in the WITH clause.

aa....aa: Duplicated query name

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11459-E A

Duplicate column name "aa....aa" in derived table "bb....bb" in view definition or "WITH" query

The column name "aa....aa" in the query name "bb....bb" in the viewed table or the WITH clause is duplicated. A column name can be specified only once in a viewed table or in a query name in a WITH clause.

aa....aa: Duplicate column name

bb....bb: Name of the viewed table or the query name containing duplicate column names

S: Ignores this SQL statement.

P:

If a column name is specified, correct the column name to eliminate duplication.

If a column name is omitted, the column name in the query selection expression must be duplicated, resulting in duplicate column names in the viewed table or in the query in the WITH clause. In this case, explicitly specify a unique column name.

KFPA11460-E A

No name for derived column in view definition or "WITH" query

If a table derived by a view definition or a derived query expression in a WITH clause contains an unnamed column, a column name cannot be omitted from the name of the viewed table or the query name.

S: Ignores this SQL statement.

P: Specify a column name.

KFPA11461-E A

Unable to derive internal table for view or "WITH" query having long data column or abstract data column or multi-value column

A query to create an internal derived table cannot be specified for a named derived table specified in one of the following selection expressions:

BLOB

BINARY 32,001 bytes or larger

Abstract data type

Repetition column

The conditions for creating an internal derived table are as follows:

In a query for a named derived table, derived by specifying SELECT DISTINCT, the named derived table is included in a subquery or directly includes one of the following:

GROUP BY clause, HAVING clause, or set function

SELECT DISTINCT

Table join (including outer join and inner join)

A value expression other than a column specification is specified in the selection expression.

None of the columns of the named derived table specified in the FROM clause is specified singularly in the selection expression.

NEXT VALUE expression

A query for a named derived table, derived by specifying a GROUP BY clause, HAVING clause, or a set function, directly includes one of the following:

GROUP BY clause, HAVING clause, or set function

Table join (including outer join and inner join)

Window function

NEXT VALUE expression

One of the following is directly included in the query for a named derived table specified by a selection expression that is a value expression other than a column specification:

GROUP BY clause, HAVING clause, or set function

Window function

Joined table

A query on a named derived table derived by directly specifying a set function with DISTINCT contains one of the following:

GROUP BY clause, HAVING clause, or set function

SELECT DISTINCT

Window function

A query for a named derived table derived by specifying a table join (including outer join and inner join) directly includes a table join (including outer join and inner join), and one of the specified table joins specifies a joined table.

A query on a named derived table derived by directly specifying a scalar subquery as a selection expression contains one of the following:

SELECT DISTINCT

GROUP BY clause, HAVING clause, or set function

Table join (including outer join and inner join)

A value expression other than a column specification specified in a selection expression

A scalar subquery specified in a selection expression

The same column derived from a value expression containing a subquery, specified more than once in the selection expression for a named derived table

A column derived from a value expression containing a subquery, specified as an external reference column in the selection expression for a named derived table

A viewed table defined before HiRDB version 07-02

A query for a named derived table derived from a set operation, which satisfies one of the following conditions:

One of the operators of the set operation includes an internal derived table query, a query that specifies a derived table, or a query that specifies a subquery in a selection expression.

One of the operators of the set operation and the query for the named derived table satisfy one of the conditions of 1 through 6 above.

A query for a named derived table derived from a set operation that includes clauses other than UNION ALL, which directly includes one of the following:

GROUP BY clause, HAVING clause, or a set function

SELECT DISTINCT

Table join (including external or internal joins)

WHERE clause

Subquery

Value expression other than a column specification in a selection expression

In a selection expression, the columns of a named derived table specified in the FROM clause are not specified once each

NEXT VALUE expression

A query for a named derived table derived from a set operation that includes only UNION ALL, which directly includes one of the following:

GROUP BY clause, HAVING clause, or a set function

Window function

WHERE clause or subquery (however, a subquery, a set operation operator, or an INSERT statement query only)

Function call or system definition scalar function

Component specification

WRITE specification

GET_JAVA_STORED_ROUTINE_SOURCE specification

Sort specification with items not in the selection expression

Subquery for a named derived table derived from a set operation specified in the FROM clause

Subquery that specifies a derived table

Subquery specified in a value expression other than a column specification in the GROUP BY clause

A data type of an SQL variable specified in a selection expression or an SQL parameter that is one of the following:
BLOB type
BINARY type 32,001 bytes or larger
Abstract data type
BOOLEAN type

The query specification specified for the table-joining of named derived tables derived by a set operation consisting solely of UNION ALL specifies one of the following:

A named derived table in a table reference other than at the leftmost outer table for an outer join

The FROM clause specifying a named derived table, which specifies a comma join (that is, specifies a different table reference than the joined table for which a derived table is specified)

A subquery or a derived table

A query specification contained either in a subquery or in the operation term for a set operation

A set operation term that derives named derived tables and contains one of the following:
Table join
GROUP BY clause, HAVING clause, or a set function
SELECT DISTINCT
A value expression in a selection expression other than a column specification
A query that creates an inner derived table
A query specifying a derived table

A named derived table derived by specifying a set operation (in addition to a named derived table)

One of the following, in the table reference to a joined table specifying a named derived table:
A named derived table derived by specifying the joining of tables
A named derived table derived by specifying a GROUP BY clause, a HAVING clause, or a set function
A named derived table derived by specifying SELECT DISTINCT
A named derived table derived by specifying a value expression other than a column specification in a selection expression
A named derived table derived by specifying a query that creates an inner derived table
A named derived table derived by specifying a subquery

The total number of tables obtained by the following expression is greater than 65:
Total number of tables = a + b c + d
a: Total number of tables from which named derived tables are derived
b: Number of set operations from which named derived tables are derived + 1
c: Total number of tables specified on the right side of an outer join
d: If a query other than a query for which a named derived table is specified is also specified, the total number of tables specified in the query

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11463-E A

Unable to specify long, large object, abstract, or boolean data in "bb....bb" clause, query-no=aaa

A value expression with a result of abstract data, BOOLEAN data, BLOB data, or BINARY data with a maximum length of 32,001 bytes or larger cannot be specified in a GROUP BY clause value expression or an ORDER BY clause sort key.

aaa: Query number

bb....bb:

{GROUP BY|ORDER BY}

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11465-E A

Data type must be BOOLEAN in "BOOLEAN" predicate, query-no=aaa

A non-BOOLEAN data type cannot be specified in a logical predicate.

aaa: Query number for the logical predicate specifying an invalid data type

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11467-E A

Unable to specify aa....aa in view definition or in "WITH" query

The following items cannot be specified in a view definition, or in a query specification in a WITH clause:

WRITE specification

GET_JAVA_STORED_ROUTINE_SOURCE specification

XML constructor function

SQL/XML scalar function

SQL/XML predicate

SQL/XML set function

aa....aa:

{ WRITE specification

| GET_JAVA_STORED_ROUTINE_SOURCE specification

| XML constructor

| XMLQUERY

| XMLSERIALIZE

| XMLPARSE

| XMLAGG

| XMLEXISTS }

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11468-E A

Inconvertible data type in "RETURN" statement with "RETURNS" clause

The data types in the RETURN statement and the RETURNS clause are not convertible.
For a character string data type, the RETURNS clause and RETURN statement must use the same character set. However, if the value expression in the RETURN statement is a literal, the value expression is automatically converted to the character set of the RETURNS clause.
For an abstract data type, either the abstract data type for the RETURNS clause and the RETURN statement must be the same, or the abstract data type for the RETURN statement must be a subtype of that in the RETURNS clause.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11469-E A

Return data in "RETURN" statement too long for "RETURNS" clause

The length of the return value data in the RETURN statement is too long for the RETURNS clause.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11470-E A

Unable to specify aa....aa in column-name list of ARRAY predicate, query-no=bbb

The column specification for the structured repetition predicate contains one of the following errors:

The specified repetition columns do not belong to the same table or are not columns derived from the same table.

A repetition column is an outer reference column.

The same column is specified as a repetition column.

A non-repetition column, an SQL variable, or an SQL parameter is specified.

aa....aa:

{ columns in different tables |outer reference column
|same columns |single-value column,
 SQL variable or SQL parameter
|derived columns from different tables }

bbb: Number of the query specifying the predicate

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Correct the SQL statement and re-execute.

KFPA11471-E A

Unable to specify columns in different tables in OR condition includes ARRAY predicate

The following columns (excluding outer reference columns) cannot be specified in the search condition of the OR operand that includes a structured repetition predicate:

Columns from different tables

Columns derived from different tables

Different tables also includes tables that have the same base table but different correlation names.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11472-E A

Unable to specify both DISTINCT for selected row or distinct view and set operation in view definition or "WITH" query

The following items cannot be specified in a query specification that is the object of a set operation when a view definition is specified, or when a set operation (UNION ALL) is specified in a derived query expression for a query in a WITH clause:

SELECT DISTINCT

Viewed tables defined by specifying SELECT DISTINCT in the outermost query specification

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11473-E A

Unable to specify "aa....aa" in query for table derived from set operation

The following items cannot be specified in a query for a table that is derived by specifying a set operation (UNION ALL):

A GROUP BY clause, a HAVING clause, or a set operation

Joining of tables

Set operations

Subqueries specifying a joined table

Subqueries specifying a value expression other than a column specification in a GROUP BY clause

Queries specifying, in a sort key, a column that is not included in a column specification

Function invocations

Component specifications

aa....aa:

{ grouping or set function |join |set operation
|subquery with joined table
|subquery with grouping by expression
|sorting by unselected column
|function invocation |component specification }

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11474-E A

Unable to specify table derived from "bb....bb" in "aa....aa"

One of the following errors was detected:

A table derived by specifying a set operation (UNION ALL) cannot be specified in the FROM clause of the following types of query specification:

Query specification of an INSERT statement

Subquery

Derived query expression in a view definition

Derived query expression of a query that uses a WITH clause

A table derived by specifying a joined table cannot be specified in the FROM clause of the following types of query specification:

Derived query expression in a view definition

Derived query expression of a query that uses a WITH clause

A table derived by specifying a joined table for the query, which is the target of a set operation (UNION ALL), cannot be specified in the FROM clause of a query that specifies a subquery.

aa....aa:

{ subquery |INSERT statement |view definition
|"WITH" query |query in "FROM" clause
|query with subquery }

bb....bb:

{ set operation |joined table
|set operation with joined table }

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11475-E A

Invalid a-th operand in bb....bb

The ath operand in the bb....bb specification is invalid:

A value expression that is not allowed was specified.

A data type that is not allowed was specified.

a: Operand number containing the error

bb....bb: Name of the specification containing the error:

{ WRITE specification |WRITE LINE statement |GET_JAVA_STORED_ROUTINE_SOURCE }

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11476-E A

Error occurred during execution of system defined scalar function in aa....aa, query-no=bbb, detail="cc....cc"

An error occurred during execution of a system-defined scalar function.

aa....aa: Name of the clause or statement that specified the function:

{ "WHERE" clause |"SET" clause |"ADD" clause
|"SELECT" clause |"ON" condition |"GROUP BY" clause
|"HAVING" clause |"ORDER BY"clause |"IF" statement
|"WHILE" statement |"SET" statement |"RETURN" statement
|"VALUES" statement |"CALL" statement
|"WRITE LINE" statement |triggered action condition }

bbb: Query number that specified the clause or statement

cc....cc: Error detail message

S: Ignores this SQL statement.

P: Take action appropriate to the error detail message:

Error detail message (cc....cc)
Function name
Explanation
Action to be taken

Invalid value of 1st argument for function function-name
ADD_INTERNAL
DATETIME
DAYNAME
DAYOFWEEK
DAYOFYEAR
INTERVAL_DATETIMES
ISDIGITS
LAST_DAY
MONTHNAME
MONTHS_BETWEEN
NEXT_DAY
STRTONUM
YEARSBETWEEN
TRUNCYEAR
ROUNDMONTH
QUARTER
HALF
WEEK
WEEKOFMONTH
CENTURY
MIDNIGHTSECONDES
STRTONUM
Argument 1 value is invalid.
Modify the SQL by considering the following:

If a date, time, or date and time character string expression is specified for the argument, is the format correct?

If a numerical value character string expression is specified for the argument, is the format correct?

If the data type of the argument is variable-length character string, is the length appropriate?

For details about specifying this argument, see the description of the relevant scalar function in the manual HiRDB Version 9 SQL Reference.

Invalid value of 2nd argument for function function-name
DATETIME
INTERVAL_DATETIMES
LTRIM
MONTHS_BETWEEN
NEXT_DAY
NUMEDIT
REPLACE
REPLACE_LONG
ROUND
RTRIM
TRUNC
YEARSBETWEEN
INSERTSTR
INSERTSTR_LONG
LEFTSTR
RIGHTSTR
TRUNCYEAR
ROUNDMONTH
QUARTER
HALF
Argument 2 value is invalid.

Invalid value of 3rd argument for function function-name
REPLACE
REPLACE_LONG
ROUND
INSERTSTR
INSERTSTR_LONG
POSSTR
TRUNCYEAR
QUARTER
HALF
Argument 3 value is invalid.

Invalid value of 4th argument for function function-name
POSSTR
TRANSL
TRANSL_LONG
Argument 4 value is invalid.

Result data too long for returned data type in function function-name
REPLACE
REPLACE_LONG
INSERTSTR
INSERTSTR_LONG
TRANSL
TRANSL_LONG
Results length exceeded the maximum permissible length for the results data type.
Ensure that the results length does not exceed the maximum permissible length for the results data type.
For details about the length of the results data type, see the description of the relevant scalar function in the manual HiRDB Version 9 SQL Reference.

Domain error in function function-name
ACOS
ASIN
LN
LOG10
SQRT
Value outside the definition range of the function was passed.
Ensure that a value outside the definition range of the function is not passed.
For details about the definition range of the function, see the description of the relevant scalar function in the manual HiRDB Version 9 SQL Reference.

Division by zero in function function-name
POWER
Division by 0 occurred.
Ensure that division by 0 does not occur.
For details about conditions that cause this error, see the description of the relevant scalar function in the manual HiRDB Version 9 SQL Reference.

Overflow error in function function-name
ADD_INTERNAL
CEIL
COSH
DEGREES
EXP
FLOOR
GREATEST
LEAST
NEXT_DAY
NUMEDIT
POWER
ROUND
ROUNDMONTH
SINH
STRTONUM
TAN
TRUNCYEAR
Overflow occurred.
Ensure that the function results can be expressed in the results data type.

KFPA11477-E A

Data type of aa....aa-th argument in CALL statement inconvertible with parameter data type "bb....bb"

The data type of the aa....aath argument in the CALL statement and the data type bb....bb of the aa....aath parameter of the called procedure are not convertible data types.
Even when both have character string data types, conversion is not possible when the character sets are different. However, if the aa....aath argument of the CALL statement is one of the following value expressions, it is converted to the character set of the aa....aath parameter of the procedure being called:

Character string literal

Embedded variable

? parameter

aa....aa: Argument number of the inconvertible data type

bb....bb: Data type of the parameter to the procedure:

{INTEGER|SMALLINT|DECIMAL(m,n)|FLOAT|SMALLFLT

|CHARACTER(l)|CHARACTER(l) CHARACTER SET EBCDIK

|CHARACTER(l) CHARACTER SET UTF16

|VARCHAR(l)|VARCHAR(l) CHARACTER SET EBCDIK

|VARCHAR(l) CHARACTER SET UTF16

|NCHAR(l)

|NVARCHAR(l)|MCHAR(l)|MVARCHAR(l)|DATE

|TIME|TIMESTAMP(p)

|INTERVAL YEAR TO DAY

|INTERVAL HOUR TO SECOND

|BLOB(l)|BINARY(l)|ABSTRACT DATA TYPE}

m and n indicate the DECIMAL precision and scaling, respectively. l indicates the character string length. p indicates the precision in seconds.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11479-E A

Invalid concatenation operation for "aa....aa" in UPDATE statement

One of the following errors was detected when updating a BLOB string or BINARY string whose length is 32,001 bytes or more using a concatenation operation:

An item other than a column was specified in the first operation item of the concatenation operation.

An item other than the ? parameter, SQL variable, or SQL parameter was specified in the second operation item of the concatenation operation.

The column to be updated differs from the column in the first operation item of the concatenation operation.

A concatenation operation was specified for the result of the concatenation operation.

A BLOB column specified in the search condition of a check constraint or a BINARY column with a maximum length of 32,001 bytes or larger is specified as the column to be updated.

aa....aa: {BLOB|BINARY}

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Correct the SQL statement and re-execute.

KFPA11487-E A

Status of dynamic result set invalid

An object was returned as an invalid dynamic results set for the following reason:

The object returned as a dynamic results set from a method defined as a Java stored procedure is not the object for which a results set was determined by the query.

S: Invalidates the transaction.

P: Specify an object that performs a query as the object to be returned as a dynamic results set from the method defined as a Java stored procedure. (Use the SQL statement specified by JDBC's prepareStatement method as the SELECT statement.). Also execute a query of this object (execute JDBC's executeQuery method).

KFPA11488-E A

Duplicate dynamic result set

The object returned as a dynamic results set from a method defined as a Java stored procedure is specified by multiple parameters.

S: Invalidates the transaction.

P: Correct so that the object returned as a dynamic results set from the method defined as a Java stored procedure is not set by multiple parameters.

KFPA11489-E A

System function aa....aa error, code=bb....bb, in copying cc....cc file "dd....dd" to "ee....ee" for ff....ff

An error occurred in a system function during registration, re-registration, or deletion of a JAR file or C library file.

aa....aa: System function name

bb....bb: Detail codes for system-related errors

See 4.2 Detail codes for system-related errors.

cc....cc: File type

JAR: JAR file

CLIB: C library file

dd....dd: Name of file (only the first 80 characters if the name exceeds 80 characters)

ee....ee: Temporary file name

ff....ff: Type of file operation{ install | replace | remove }

S: Invalidates the transaction.

P: Remove the error cause and re-execute the transaction.

KFPA11490-E A

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

An attempt to register, re-register, or delete a JAR file or C library file failed.

aa....aa: Type of file operation { INSTALL | REPLACE | REMOVE }

bb....bb: File type

JAR: JAR file

CLIB: C library file

cc....cc: Name of file (only the first 80 characters if the name exceeds 80 characters)

dd....dd: Reason

transaction already begin:

The transaction has already started.

JAR file already installed:

The JAR file is already installed.

JAR file not found:

The JAR file cannot be found in the JAR file storage directory.

JAR file synchronization failed:

An error occurred in the pdjarsync command.

C library file already installed:

The C library file is already installed.

C library file not found:

The C library file cannot be found in the C library file storage directory.

C library file synchronization failed:

An error occurred in the pdclibsync command.

S: Invalidates the transaction.

P:

When dd....dd is transaction already begin:
Before registration, re-registration, or deletion, commit all transactions (perform a COMMIT or ROLLBACK).

When dd....dd is JAR file already installed:
If you want to overwrite the existing JAR file, execute REPLACE JAR.

When dd....dd is JAR file not found:
Correct the specified JAR file name and re-execute.

When dd....dd is JAR file synchronization failed:
Use the pdjarsync command to display a list of JAR files, and then check the contents. If necessary, re-execute registration, re-registration, or deletion with the pdjarsync command.

When dd....dd is C library file already installed:
If you want to overwrite the existing C library file, execute REPLACE CLIB.

When dd....dd is C library file not found:
Correct the specified C library file name and re-execute.

When dd....dd is C library file synchronization failed:
Use the pdclibsync command to display a list of C library files, and then check the contents. If necessary, re-execute registration, re-registration, or deletion with the pdclibsync command.

KFPA11491-E A

Error occurred on JavaVM, message=aa....aa

An error occurred in the Java Virtual Machine.

aa....aa: Error detail and type:

INIT

Error occurred during startup.

exception or error message

Error occurred at a time other than during startup. If the number of characters exceeds 208, a hash mark (#) is displayed as the 208th character.

******

Error occurred in the Java Virtual Machine.

S: Ignores this SQL statement.

P: Re-execute the Java stored procedure or Java stored function. If the same error occurs again, contact the HiRDB administrator.

O:

When aa....aa is INIT
Ensure that the following system definition operands are correct:
pd_java_option, pd_java_archive_directory, pd_java_classpath, pd_java_libpath, pd_java_stdout_file, pd_java_runtimepath

When aa....aa is exception or error message
Refer to the JDK documentation and take appropriate action.

When aa....aa is ******
Restart the HiRDB server.

KFPA11492-E A

Exception raised, in java method=cc....cc for ROUTINE aa....aa."bb....bb", message=dd....dd

An exception error occurred during execution of a Java method defined as a Java stored procedure or Java stored function.

aa....aa: Owner name

bb....bb: Name of Java stored procedure or Java stored function

cc....cc: Java method name (if the name exceeds 64 characters, a hash mark (#) is displayed as the 64th character)

dd....dd: One of the following (if the item exceeds 65 characters, a hash mark (#) is displayed as the 65th character):

Detailed message that is set for the exception error object caused by the Java method

Class name of the exception error object (this is displayed when no detailed message has been set)

S: Ignores this SQL statement.

P: Take one of the following actions:

Re-create the Java method by referring to the exception error message.

Eliminate the cause of the exception error by referring to standard output or standard error from the Java method, which is output to the file specified in the pd_java_stdout_file system definition operand.

O: Specify the pd_java_stdout_file operand to make it possible to obtain standard output or standard error from the Java method.

KFPA11493-E A

Unable to execute aa....aa for ROUTINE bb....bb."cc....cc", reason_code=dd, message=ee....ee

For reason dd, unable to execute the Java method or C function for a stored procedure or stored function defined as cc....cc and owned by bb....bb.

aa....aa: Implementation language of the external routine: {Java method|C function}

bb....bb: Owner name

cc....cc: Name of stored procedure or stored function

dd: Reason code

When aa....aa is Java method:

02: Specified method was not found.

03: Class loading failed.

04: Specified method caused a security violation exception.

05: JAR file I/O processing failed.

06: Specified JAR file was not found.

07: Specified class was not found.

08: Specified method has no static qualifier.

09: Return value type specified by EXTERNAL NAME in the definition of the Java stored procedure or Java stored function is different from the return value type of the Java method.

When aa....aa is C function:

02: Specified C function was not found.

05: I/O failure in the C library file for the external C stored routine.

06: C library file for the external C stored routine was not found.

ee....ee: Message (if it exceeds 109 characters, the first 108 characters are shown and a hash mark (#) is displayed in the 109th character)

When aa....aa is Java method:

Reason code | Message
02, 04, 08 | Method name
03, 07 | Class name
05, 06, 09 | JAR file name

When aa....aa is C function:

Reason code | Message
02 | C function name
05, 06 | C library file name

S: Ignores this SQL statement.

P: Take one of the following corrective actions:

Review and, if necessary, revise the specification of the external routine where the stored procedure or stored function is defined according to the tables below.

When aa....aa is Java method:

Reason code | Action
02, 04 | Check the specification of the method name.
03, 07 | Check the specification of the class name.
05, 06 | Check the specification of the JAR file name.
08 | Check the Java class source file to make sure that the method has a static qualifier.
09 | Make sure that the return value type matches the return value type of the Java method.

When aa....aa is C function:

Reason code | Action
02 | Check the external function identifier or C library file name.
05, 06 | Check the specification of the C library file name.

Make sure that the specified JAR file or C library file is registered correctly.

Make sure that the specified C function exists in the C library file that is specified when the stored procedure or stored function is defined.

KFPA11494-E A

Unable to use JAVA procedure or function

Java stored procedure or Java stored function cannot be used for the following reason:

The HiRDB being used is not a POSIX library version.

S: Ignores this SQL statement. The transaction is invalidated in the case of a definition SQL statement.

Action

To use Java stored procedures or Java stored functions, execute the pdsetup -l command.

KFPA11495-E A

Unable to execute SQL in function aa....aa."bb....bb" (cc....cc)

A database manipulation SQL statement is being executed from the aa....aa."bb....bb" function.

aa....aa: Owner name

bb....bb: Function name

cc....cc: Identifying name

S: Ignores this SQL statement.

P:

Correct so that the SQL statement is not executed from the aa....aa."bb....bb" function, and then re-execute.

If the function body is a Java method, correct so that the Java method does not manipulate the database, and then re-execute.

KFPA11497-E A

aa....aa in RDAREA name specification

One of the following errors occurred in the specified RDAREA name.

The specification contains a syntax error.

The same RDAREA name is specified more than once.

An RDAREA storing the table is not supported.

aa....aa: {Syntax error|Duplicate RDAREA names|Invalid RDAREA for table}

S: Ignores this SQL statement.

P: Correct the error and re-execute.

KFPA11500-E A

Unable to open holdable cursor

A holdable cursor cannot be opened for the following reason:

The maximum number of simultaneously open holdable cursors during non-runtime of the LOCK statement with UNTIL DISCONNECT specified that is specified in the pd_max_open_holdable_cursors operand of the server common definition, back-end server definition, dictionary server definition, or single server definition, was exceeded.

S: Ignores this SQL statement.

P: Correct the UAP or SQL and re-execute.

Action

Revise the maximum number of simultaneously open holdable cursors during non-runtime of a LOCK statement with UNTIL DISCONNECT specified that is specified in the pd_max_open_holdable_cursors operand of the server common definition, back-end server definition, dictionary server definition, or single server definition. If necessary, change the specified value and re-start HiRDB.

KFPA11501-E A

Cursor not opened

The cursor specified in the FETCH or CLOSE statement has not been opened.

S: Ignores this SQL statement.

P: Modify the UAP so that the cursor is opened before fetching a row and then is closed, then re-execute.

KFPA11502-E A

Cursor already opened

An attempt was made to open an already open cursor.

S: Ignores this SQL statement.

P: Modify the UAP so that the cursor is closed before reopening it, then re-execute.

KFPA11504-E A

Invalid data type specified in routine definition

One of the following errors was detected in a data type specification in the routine definition:

The data type of the parameter of the routine that specifies Java in the LANGUAGE clause is not convertible to the data type specified in the EXTERNAL NAME clause.

The data type of the RETURN clause of the routine that specifies Java in the LANGUAGE clause is not convertible to the data type specified in the EXTERNAL NAME clause.

The number of data types for the parameter of the routine that specifies Java in the LANGUAGE clause is different from the number of data types specified in the EXTERNAL NAME clause.

void is not specified as the returns type name in the EXTERNAL NAME clause of the procedure that specifies Java in the LANGUAGE clause.

BLOB type, BINARY type, or an abstract data type (including XML type) was specified in a parameter of the routine that specifies C in the LANGUAGE clause.

BLOB type, BINARY type, or an abstract data type (including XML type) was specified in the RETURNS clause of the routine that specifies C in the LANGUAGE clause.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11505-E A

aa....aa requested for query with opened cursor

Preprocessing or preprocessing invalidation was requested for a query while a cursor was open. Or, preprocessing or preprocessing invalidation was requested for a query open for reference by another cursor.

aa....aa: The SQL statement that requested execution

PREPARE: Preprocessing has been requested.

DEALLOCATE PREPARE: Preprocessing invalidation has been requested.

S: Ignores this SQL statement.

P: Revise the UAP so that the cursor is closed before preprocessing or preprocessing invalidation, and re-execute. Or, revise the UAP so that another cursor that is referencing is closed before preprocessing or preprocessing invalidation, and re-execute.

KFPA11506-E A

Invalid request for executing of query

A query for which preprocessing was executed with the PREPARE statement cannot be executed by the EXECUTE statement. Or, a query cannot be executed by the EXECUTE IMMEDIATE statement.

S: Ignores this SQL statement.

P: Modify the UAP so that the SQL statements are executed in the following order, then re-execute:

Cursor declaration or cursor assignment

OPEN statement

FETCH statement

CLOSE statement

KFPA11507-E A

aa....aa cursor for SQL except query

aa....aa: {Declare|Allocate}

aa....aa is Declare:

There is a cursor declaration (DECLARE CURSOR) for an SQL statement that is not a query.

aa....aa is Allocate:

There is a cursor assignment (ALLOCATE CURSOR) for an SQL statement that is not a query.

S: Ignores this SQL statement.

P:

aa....aa is Declare:

Revise the UAP to change the SQL statement that declares a cursor into a query, or delete the cursor declaration from the non-query SQL statement, and re-execute.

aa....aa is Allocate:

Revise the UAP to change the SQL statement that assigns a cursor into a query, or delete the cursor declaration from the non-query SQL statement, and re-execute.

KFPA11508-E A

Invalid use of "aa....aa" statement

An attempt was made to execute an SQL statement other than CALL or one row SELECT with an EXECUTE or EXECUTE IMMEDIATE statement that has an INTO clause.

aa....aa: {EXECUTE | EXECUTE IMMEDIATE}

S: Ignores this SQL statement.

P: Revise the usage of the EXECUTE or EXECUTE IMMEDIATE statement, and re-execute. If an SQL statement other than CALL or a one row SELECT statement is executed by the EXECUTE or EXECUTE IMMEDIATE statement, revise it into an EXECUTE or EXECUTE IMMEDIATE statement without INTO, and re-execute.

KFPA11511-E A

Unmatched RDAREA status or generation number between number "aa" of "bbbbb" RDAREA "cc....cc" and number "dd" of table RDAREA "ee....ee"

The statuses of RDAREA "cc....cc" for storing "bbbbb" and RDAREA "ee....ee" for storing tables do not match. Or, generation aa and generation "dd" do not match.

aa: Generation number of the RDAREA for user LOB or the RDAREA for index storage

bbbbb: Storage data type of the RDAREA:

{INDEX|LOB}

cc....cc: Name of the original RDAREA for the user LOB or the name of the original RDAREA for storing indexes

dd: Generation number of the RDAREA for storing tables

ee....ee: Name of the original RDAREA for storing tables

S: Ignores the transaction.

O: Contact the HiRDB administrator.

Actions

Perform one of the following actions to solve the problem:

If the generations of the RDAREA for storing tables and the RDAREA for user LOB, or the RDAREA for storing indexes, do not match during the current access:
Execute the pddbchg command and match up the generation numbers of the RDAREA for user LOB or the RDAREA for storing indexes and the RDAREA for storing tables.

If the replica RDAREA of the specified generation is not created in the applicable RDAREA:
Execute the pdmod command to create a replica RDAREA.

If the generation numbers of the RDAREA for storing tables and the RDAREA for user LOB do not match:
The statuses of the RDAREA for displaying tables and the RDAREA for user LOB do not match. Execute the pddbchg command and change the status of the RDAREA for storing tables and the RDAREA for user LOB to the current status or another status.

KFPA11512-E A

Invalid request for executing of SQL except query

A non-query SQL statement for which preprocessing was executed with the PREPARE statement cannot be executed by the OPEN, FETCH, or CLOSE statement.

S: Ignores this SQL statement.

P: Modify the UAP so that the SQL statement is executed with the EXECUTE statement, then re-execute. If the specified cursor is invalid, correct the cursor name and re-execute.

KFPA11513-E A

Unable to execute definition SQL due to aa....aa bb....bb. "cc....cc" using replicated RDAREA dd....dd

The following definition SQLs cannot be executed because the RDAREA for storing tables or indexes is using the inner replica function:

ALTER TABLE

CREATE INDEX

DROP INDEX

DROP SCHEMA

DROP TABLE

aa....aa: {TABLE|INDEX}

bb....bb: Authorization identifier

cc....cc: Table identifier when aa....aa is TABLE, or index identifier when aa....aa is INDEX

dd....dd: The RDAREA name

S: Ignores this SQL statement.

P: Cancel application of the inner replica function and re-execute.

KFPA11514-E A

Unable to execute "SET SESSION AUTHORIZATION" statement, due to aa....aa

The user cannot be changed for one of the following reasons:

Transaction has already started.

A holdable cursor is open.

A lock is applied using the LOCK statement with the UNTIL DISCONNECT specification.

This is not executed first in a transaction.

The statement is inside a stored procedure.

aa....aa: One of the following:

{ ACTIVE TRANSACTION |HOLDABLE CURSOR
|LOCK WITH UNTIL DISCONNECT
|DISTRIBUTED DATABASE ACCESS |NON-FIRST EXECUTION
|STORED PROCEDURE }

S: Ignores this SQL statement.

P: Correct the UAP and re-execute.

KFPA11528-E A

aa....aa bb....bb.cc....cc(dd....dd) not executable due to invalid SQL OBJECT

The SQL object is invalid; the routine bb....bb.cc....cc could not be executed.

aa....aa: Routine type

{ Procedure |Function }

bb....bb: Authorization identifier

cc....cc: Routine identifier

dd....dd: Special name

S: Ignores this SQL statement or invalidates the transaction.

P: Resolve the cause of the error that makes the SQL object invalid, redefine the procedure, and then retry the operation. The possible causes are:

Table, index, or definition changes

A change to the specification of the pd_rpl_func_control operand in the system common definition

Recovery of the data dictionary LOB RDAREA for object storage

KFPA11529-E A

aa....aa bb....bb.cc....cc invokable for specified arguments not found in system

The procedure specified in any of the following SQL statements was not found in the HiRDB system, or a callable routine did not exist:

DROP PROCEDURE

DROP FUNCTION

ALTER PROCEDURE

CALL statement

Function invocation (user-defined function, system-defined function)

The CALL statement or function invocations cannot call encapsulated routines.
A routine cannot be called if the number of arguments in the CALL statement and the function invocation does not match the number of parameters in the routine. A function cannot be called that has as a corresponding parameter a data type that is higher in priority than the data type of the argument.
For rules about determining the function to be called, see the manual HiRDB Version 9 SQL Reference.
For a CALL statement, a routine cannot be called if the data types of the arguments of the statement are incompatible with the data types of the parameters of the routine. Even if the argument and parameter are character string data types, the data types are incompatible if the character sets are different.

aa....aa: Routine type

{ Procedure |Function }

bb....bb: Authorization identifier

cc....cc: Routine identifier

S: Ignores this SQL statement or invalidates the transaction.

P:

Execution of a CALL statement or a function invocation (user-defined function):

Check that there are no errors in any of the specifications listed as follows:

Authorization identifier

Routine identifier

Number of arguments

Data types of arguments (including the character sets in the case of the character string data type)

If there are no errors, redefine the procedure by using CREATE PROCEDURE or CREATE FUNCTION, as appropriate, and then re-execute.

If there is an encapsulation level error in part of the routine definition, use CREATE TYPE to redefine the routine, and then re-execute.

Function invocation (system-defined function):

Check that the following specifications are correct:

Authorization identifier

Routine identifier

Argument count

Data types of arguments (including the character sets in the case of the character string data type)

During execution of DROP PROCEDURE:

Check that there are no errors in the specified authorization identifier or the routine identifier.

During execution of ALTER PROCEDURE:

Check that there are no errors in the specified authorization identifier or the routine identifier. If there are no errors, use CREATE PROCEDURE to redefine the procedure.

During execution of DROP FUNCTION:

Check that there are no errors in the specified values listed below. If there are no errors, no action is required.

Authorization identifier

Routine identifier

Number of arguments

Data types of arguments (including the character sets in the case of the character string data type)

KFPA11530-E A

SQL OBJECT not executable aa....aa, size=bb....bb

The specified SQL object cannot be executed because the transfer size of that SQL object exceeds 1 MB.

aa....aa: Reason the SQL object cannot be executed:

TRANSFER MAX SIZE: Transfer size of SQL object exceeds the maximum.

bb....bb: Transfer size that exceeds 1 MB

S: Invalidates the transaction.

P: Correct the SQL so that the SQL object transfer size is within 1 MB and re-execute.

KFPA11531-E A

SQL OBJECT CACHE currently full, server=aa....aa, info=bb....bb

The buffer for the SQL object is full; the SQL object cannot be executed.

aa....aa: Name of the server that has a buffer space shortage

bb....bb: Information about shortage resources

{ Numeric value, "SQL OBJECT MANAGEMENT", "ACTIVE LIST" }

S: Does not execute the SQL object, or invalidates the transaction.

P: Notify the HiRDB administrator to increase the value of pd_sql_object_cache_size. Or, based on shortage resources information, take the following actions:

If resources information is a numeric value:

Revise the SQL so that the SQL object length is less than the SQL object buffer size. (When calling a procedure or a function, re-create the procedure or the function to reduce its SQL object length.)

If resources information is "SQL OBJECT MANAGEMENT":

Reduce the number of UAPs that are concurrently executed. Alternatively, reduce the number of SQL statements, procedures, or functions that are executed per transaction.

If resources information is ACTIVE LIST:

Reduce the number of SQL statements, procedures, or functions that are executed per transaction. Or, increase the value of pd_max_access_tables.

Action

Estimate the required size for the SQL object buffer, and then increase the pd_sql_object_cache_size value for the affected server or system.

KFPA11537-E A

Unable to execute specified ROUTINE due to invalid SQL OBJECT

The specified routine does not contain the information necessary for delayed batch creation of a plug-in index. Therefore, the delayed batch creation of the plug-in index cannot be performed.

S: Invalidates the transaction.

P: If the delayed batch creation of a plug-in index is not required, specify PDPLGIXMK=NO in the client environment definition.

Action

If the delayed batch creation of a plug-in index is required, execute either ALTER ROUTINE or ALTER PROCEDURE on all routines that update the plug-in index.

KFPA11546-E A

Unable to assign LIST due to executing "pdmod"

List creation or retrieval cannot be executed because the RDAREA storing the base table from which the list to be created is being initialized by the database structure modification utility.

S: Ignores this SQL statement.

O: Re-execute after the processing by the database structure modification utility has finished.

KFPA11547-E A

Unable to define view from "SQL_USERS"

A viewed table cannot be defined using the SQL_USERS table of the dictionary table as a base.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11548-E A

Unable to execute aa....aa:no bb....bb privilege for cc....cc dd....dd.ee....ee

One of the following errors has occurred:

There is no dd....dd privilege for cc....cc dd....dd.ee....ee; SQL statement aa....aa could not be executed.

If the optimizing information collection utility (pdgetcst) is being used, the user does not have SELECT privilege for the table to be processed.

aa....aa: SQL statement to be executed

{SELECT|INSERT|UPDATE|DELETE|ASSIGN|DROP LIST|PREPARE/EXECUTE|PURGE TABLE|LOCK TABLE|CREATE VIEW}

bb....bb: Required access privilege

{SELECT|INSERT|UPDATE|DELETE|USAGE}

If the user attempted to execute LOCK TABLE with EXCLUSIVE specified and does not have DELETE, INSERT, or UPDATE privilege, UPDATE is displayed for bb....bb.

cc....cc: TABLE, or SEQUENCE

dd....dd: Authorization identifier

ee....ee:

When cc....cc is TABLE: Table identifier

When cc....cc is SEQUENCE: Sequence generator identifier

S: Ignores this SQL statement.

P: Acquire the required access privilege and re-execute.

O: If the optimizing information collection utility (pdgetcst) is being executed, make sure the user has the SELECT privilege for the table that is to be processed.

KFPA11549-E A

Invalid authorization identifier aa....aa

PUBLIC, MASTER, HiRDB, or ALL is specified as the authorization identifier. The following are examples of incorrect use of the authorization identifier:

An attempt was made to connect to the HiRDB server by specifying one of these character strings as the authorization identifier.

An attempt was made to create (or delete) a base table or viewed table identified by an authorization identifier consisting of one of these character strings.

An attempt was made to delete a table identified by an authorization identifier consisting of one of these character strings.

An attempt was made to update a table identified by an authorization identifier consisting of one of these character strings.

An attempt was made to create (or delete) a procedure of a function identified by an authorization identifier consisting of one of these character strings.

An attempt was made to re-create a procedure of a function identified by an authorization identifier consisting of one of these character strings.

An attempt was made to create (or delete) a data type or index type identified by an authorization identifier consisting of one of these character strings.

An attempt was made to update a data type or index type identified by an authorization identifier consisting of one of these character strings.

An attempt was made to search a table whose authorization identifier is HiRDB.

One of these character strings was specified as the user's authorization identifier to define a privilege (GRANT) or revoke a privilege (REVOKE).

aa....aa: PUBLIC, MASTER, HiRDB, or ALL

S: Ignores this SQL statement.

P: Correct the authorization identifier and re-execute.

KFPA11550-E A

Unable to access MASTER.aa....aa without DBA or Auditor privilege

Only users with DBA privileges or auditor privileges can access dictionary table aa....aa.

aa....aa: Table identifier of the dictionary table to be accessed

S: Ignores this SQL statement.

P: Check the table identifier of the dictionary to be accessed for an error. If there is an error, correct the error and re-execute. If there is no error, contact the HiRDB administrator and request DBA privileges or auditor privileges as necessary.

KFPA11551-E A

Unable to execute aa....aa due to lack of privilege for table bb....bb."cc....cc"

The SQL statement indicated by aa....aa cannot be executed because the executor is not the table owner.
Or, a privilege that has not been granted to the executor cannot be granted to other users.

aa....aa: SQL statement that cannot be executed:

grant table access privilege: Grant access privilege for a table.

revoke table access privilege: Revoke access privilege for a table.

bb....bb: Authorization identifier

cc....cc: Table identifier

S: Ignores this SQL statement.

Action

In the case of a GRANT or REVOKE statement, execute this SQL statement for a table the user owns. In addition, correct the SQL statement so that only the SELECT privilege is added to the read-only viewed table.

KFPA11552-E A

Unable to execute "aa....aa" due to lack of privilege

SQL statement aa....aa cannot be executed, because the user does not have the DBA privilege.
Or, the SQL statement displayed in "aa....aa" cannot be executed because the password of the DBA privilege holder is not registered in HiRDB.

aa....aa: SQL statement that cannot be executed:

GRANT DBA

GRANT CONNECT

GRANT RDAREA

GRANT SCHEMA

REVOKE DBA

REVOKE CONNECT

REVOKE RDAREA

REVOKE SCHEMA

S: Ignores this SQL statement.

P:

To execute this SQL statement, acquire the DBA privilege and re-execute.

Or, register the password of the DBA privilege holder in HiRDB and then execute this SQL statement.

KFPA11553-E A

Unable to execute function IS_USER_CONTAINED_IN_HDS_GROUP

The IS_USER_CONTAINED_IN_HDS_GROUP scalar function cannot be executed. Following are possible explanations for this error:

When specifying columns in a value expression, columns other than dictionary table columns cannot be specified.

Multiple table columns were specified in the value expression. When performing an OR operation for the predicate in which this scalar function is specified, you cannot specify multiple table columns in the OR operation. Here, an AND operation negated by NOT is also considered to be an OR operation.

This scalar function cannot be specified in a search that uses a list.

This scalar function cannot be specified in a selection expression or HAVING clause.

When specifying this scalar function as the ON search condition for a joined table with an outer join, columns of the outer table cannot be specified in the value expression.

When a joined table with an outer join is specified in a FROM clause and this scalar function is specified in a WHERE clause, columns of the inner table with an outer join cannot be specified.

The following cannot be specified when no dictionary table column is specified in the value expression:

Multiple tables in the FROM clause

ORDER BY

DISTINCT

GROUP BY

Set function

FOR UPDATE

FOR READ ONLY

More than one dictionary table was specified in the FROM clause.

S: Ignores this SQL statement.

P: Determine the reason for the error; if applicable, correct the SQL statement and re-execute.

KFPA11554-E A

Unable to grant privilege to yourself

The user cannot grant a privilege to himself/herself.

S: Ignores this SQL statement.

Action

Change the user's authorization identifier specified in the TO clause and re-execute.

KFPA11555-E A

Unable to revoke privilege from yourself

The user cannot revoke his/her own privilege.

S: Ignores this SQL statement.

Action

Change the user's authorization identifier specified in the FROM clause and re-execute.

KFPA11556-E A

Unable to execute aa....aa table access privilege bb....bb table owner

The list of authorization identifiers specified in the GRANT statement (privilege definition) or REVOKE statement (privilege revocation) contains the table owner's authorization identifier.

aa....aa: Erroneous SQL statement:

{ GRANT |REVOKE }

bb....bb: Erroneous specification in SQL statement:

{ TO |FROM }

S: Ignores this SQL statement.

Action

A table owner cannot grant a privilege to himself/herself or revoke his/her own privilege. Therefore, delete the table owner's authorization identifier from the TO or FROM clause and re-execute.

KFPA11558-E A

pdvrup command not executed

An attempt was made to upgrade the HiRDB version, but a UAP or utility could not be executed because the pdvrup command had not been executed.

S: Causes an error for this SQL statement.

O: Execute the pdvrup command.

KFPA11559-E A

Unable to grant privilege to unauthorized user aa....aa

The schema definition privilege cannot be granted to a user who does not have the CONNECT privilege.

aa....aa:

Authorization identifier of the user who does not have the CONNECT privilege

S: Ignores this SQL statement.

Action

Check if the specified authorization identifier aa....aa is correct. If it is not correct, correct it and re-execute the SQL statement.

If the authorization identifier is correct, grant CONNECT privileges to authorization identifier aa....aa and re-execute.

KFPA11560-E A

Invalid password for authorization identifier aa....aa

The specified password is not the correct password for authorization identifier aa....aa.
When using the Directory Server linkage facility, the specified password either differs from the password registered in the Directory Server, or the password has expired. If this message is output when accessing the table, either the password attribute in the user information on the Directory Server has been modified since the user previously connected to HiRDB, or the password has expired.

aa....aa: Authorization identifier for which an invalid password was specified

S: Ignores this SQL statement.

However, if a utility is being executed, processing is terminated.

P:

When this message is output during an attempt to connect to HiRDB, specify the correct password and re-execute.

In the Windows edition of HiRDB

When executing a utility with -u authorization-identifier specified, note the following point:

To enter a password as a response, there is no need to enclose the character string in backslashes (\). Enclosing it in backslashes is correct for the command line entry, but it is not necessary in the response format.

KFPA11561-E A

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

Specified authorization identifier aa....aa does not have the CONNECT privilege.

aa....aa: Authorization identifier without the CONNECT privilege

S: Ignores this SQL statement; however, if a utility is being executed, processing is terminated.

Action

Ask a user who has the DBA privilege to grant you the CONNECT privilege, and re-execute.

Also, when a utility in which -u authorization-identifier is specified is executed, also check the following:

If -u was omitted, as well as the PDUSER environment variable, the user ID entered at the time of logging in is assumed as the authorization identifier. Check this user ID for any error.

When an authorization identifier or password is entered in lower case letters to specify a utility or command option, it must be enclosed in double quotes. In this case, to ensure that the shell or other interpreter does not remove the quotes before passing the specified value to the utility, attach \ or '.

Examples

pddbst -u \"hitachi\" -p \"hitachi\"

pddbst -u '"hitachi"' -p '"hitachi"

KFPA11562-E A

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

The CONNECT privilege cannot be revoked due to aa....aa.

aa....aa:

DBA privilege: DBA privilege

schema: Schema

bb....bb: revoke

S: Ignores this SQL statement.

Action

Delete the DBA privilege or schema privilege and re-execute.

KFPA11563-E A

Unable to execute SQL before CONNECT

An SQL statement was executed before executing the CONNECT statement.

S: Terminates processing.

P: Check the program for an error in the SQL statement issuance order, correct the error, then re-execute.

If there is no error in the order in which SQL statements are issued, it is possible that the HiRDB server was disconnected during the execution of the SQL statement before the message was output. Determine whether an error message was returned during the execution of the SQL statement before the message was output.

KFPA11564-E A

Invalid authorization identifier aa....aa

Authorization identifier aa....aa contains a syntax error. Or, the length of the authorization identifier exceeds 8 characters.
If the specified authorization identifier contains a non-display character, aa....aa may not be displayed correctly.

aa....aa: Authorization identifier containing a syntactical error or authorization identifier that is longer than 8 characters

S: Ignores this SQL statement.

P:

Correct the authorization identifier and re-execute.

In the Windows edition of HiRDB

When executing a utility with a -u authorization-identifier specified, note the following point:

If -u was omitted as well as the PDUSER environment variable at the utility prompt, the user ID entered at the time of logging into Windows is assumed as the authorization identifier. Check this user ID for any error.

KFPA11565-E A

aa....aa bbbb call parameter cc....cc

When cc....cc is SQLIASDA or sqliasda:

When bbbb is OPEN or OPNR: In the OPEN statement of the query containing the input ? parameter, the embedded variable or SQL descriptor area that sets the input ? parameter was not specified.

When bbbb is AUX or AUXO: In the EXECUTE statement of the SQL containing the input ? parameter, the embedded variable or SQL descriptor area that sets the input ? parameter was not specified.

When bbbb is AUXI: In the EXECUTE IMMEDIATE statement of the SQL containing the input ? parameter, the embedded variable or SQL descriptor area that sets the input ? parameter was not specified.

When bbbb is OPN2, AUI2, AUI3 or CALL: ? parameters rather than embedded variables were specified in SQL that is not pre-processed in a PREPARE statement or EXECUTE IMMEDIATE statement.

When cc....cc is SQLIASDA2:

When bbbb is AUX or AUXI: In the EXECUTE statement or EXECUTE IMMEDIATE statement of the SQL containing the input ? parameter, the embedded variable or SQL descriptor area for receiving the output ? parameter was not specified.

When bbbb is CALL: ? parameters rather than embedded variables were specified in SQL that is not pre-processed in a PREPARE statement or EXECUTE IMMEDIATE statement.

aa....aa: Invalid

bbbb: Operation code (4 characters):

cc....cc: SQLIASDA, sqliasda, or SQLIASDA2

S: Ignores this request.

P: Perform the following action, and then re-execute the UAP:

When cc....cc is SQLIASDA or sqliasda:
Take one of the following actions depending on the value of the operation code (bbbb):

Operation code (bbbb) | Action
OPEN, OPNR, AUX, AUXI, or AUXO | Specify the embedded variable or SQL descriptor area name that sets the input ? parameter in the OPEN statement, EXECUTE statement or EXECUTE IMMEDIATE statement.
OPN2, AUI2, AUI3, or CALL | Specify an embedded variable rather than a ? parameter.
Other than the above | Contact the customer support center.

When cc....cc is SQLIASDA2:
Take one of the following actions depending on the value of the operation code (bbbb):

Operation code (bbbb) | Action
AUX or AUXI | Specify the embedded variable or SQL descriptor area name for receiving the output ? parameter or search results.
CALL | Specify an embedded variable rather than a ? parameter.
Other than the above | Contact the customer support center.

KFPA11569-E A

Directory server error occurred on aa....aa, func=bb....bb errno=cc....cc, dd....dd

During aa....aa processing, an error was returned from the HiRDB LDAP Option API used by the Directory Server linkage facility.

aa....aa: Name of process in which the error occurred

bb....bb: API name when the error occurred

cc....cc: Detailed error code

10: User is not registered.

11: Duplicate user names are registered on the Sun Java System Directory Server.

20: The role name is not registered.

21: Duplicate role names are registered on the Sun Java System Directory Server.

30: The specified user does not belong to the specified role.

40: There is no HiRDB LDAP Option environment definition file.

41: There are no access privileges to the HiRDB LDAP Option environment definition file.

42: Failed to open or close the HiRDB LDAP Option environment definition file (for details, see message KFPD00027-E).

43: Error occurred when reading the HiRDB LDAP Option environment definition file (for details, see message KFPD00027-E).

44: Operand required in the HiRDB LDAP Option environment definition was not specified.

50: There is no Runtime library in the specified path.

51: An error occurred when loading the Runtime library (for details, see message KFPD00027-E).

60: Insufficient memory.

90: The value (maximum wait time) of the NETWORKTIMELIMIT operand of the HiRDB LDAP Option environment definition was exceeded.

92: An unexpected error occurred.

99: Other error (for details, see message KFPD00027-E).

dd....dd: Role name

When bb....bb is p_f_dic_ismatchrulebyid, the role name for where the error occurred is output.
roleid=role-name

Blank in all other cases.

S: Ignores this SQL statement.

P: Take the following action according to the detailed error code. Also, see message KFPD00027-E.

Action

When the API name is ldp_xxxxxx, see the Sun Java System Directory Server documents, and take the action appropriate for the detailed error code.

For detailed error code 42, 43, 51, 60 or 99, follow the instructions in message KFPD00027-E.

Contact the customer support center when the detailed error code is 92.

KFPA11570-E A

More than 1600 authorization identifiers in "aa....aa" statement

More than 1600 authorization identifiers were specified in the GRANT statement (privilege definition) or REVOKE statement (privilege revocation) (maximum of 1600 authorization identifiers can be specified).

aa....aa: Invalid SQL statement:

{ GRANT |REVOKE }

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11571-E A

Password not specified for aa....aa

No password was specified for the authorization identifier to which DBA privilege is to be granted. Or, an attempt was made without specifying the correct password to change the password for the authorization identifier to which DBA privilege has been granted.

aa....aa: Authorization identifier for which no password was specified or that is to be changed

S: Ignores this SQL statement.

P: Specify the password and re-execute.

KFPA11572-E A

Duplicate access privilege "aaaaaa" in "bb....bb" statement

A duplicate access privilege was specified in the GRANT or REVOKE statement.

aaaaaa: Duplicate access privilege:

{ SELECT |UPDATE |INSERT |DELETE }

bb....bb: SQL statement to be executed:

{ GRANT |REVOKE }

S: Ignores this SQL statement.

P: Delete the duplicate access privilege and re-execute.

KFPA11573-E A

Privilege error

For the reasons given below, none of the following actions can be performed on another user: creating a schema, deleting a schema, re-creating a procedure, or re-creating a trigger SQL object.

The executing user does not have the DBA privilege.

The user who is to create a schema does not have the DBA or CONNECT privilege.

The password of the DBA privilege holder is not registered in HiRDB.

S: Ignores this SQL statement.

Action

Take one of the following actions:

Have a user with DBA privilege grant the DBA privilege, and re-execute the SQL statement.

Grant the DBA or CONNECT privilege to the user who will create a schema, and re-execute the SQL statement.

Register the password of the DBA privilege holder in HiRDB.

KFPA11574-E A

Duplicate RDAREA "aa....aa"

One of the following errors was detected:

The same RDAREA name is specified more than once in the primary key definition, cluster key definition, table storage RDAREA, LOB column storage RDAREA, or LOB attribute storage RDAREA in CREATE TABLE or ALTER TABLE.

The same RDAREA name is specified more than once in CREATE INDEX.

An attempt was made with ALTER TABLE to add the RDAREA in which this table is already stored.

aa....aa: Duplicate RDAREA name

S: Ignores this statement.

P: Delete or correct the duplicate RDAREA name and re-execute. Or, for ALTER TABLE, specify another RDAREA name and re-execute.

KFPA11576-E A

Unable to revoke RDAREA use privilege for "aa....aa" due to bb....bb cc....cc."dd....dd"

The RDAREA usage privilege cannot be revoked, because the specified RDAREA contains a table, index, or sequence generator.

aa....aa: RDAREA name

bb....bb:

table

index

sequence

cc....cc: Authorization identifier of the table, index, or sequence generator in the RDAREA

dd....dd: Table identifier, index identifier, or sequence generator identifier in the RDAREA

S: Ignores this SQL statement.

P: Delete the table, index, or sequence generator in the RDAREA, and then retry the operation.

KFPA11577-E A

Unable to revoke schema privilege due to table/routine/sequence existence

The schema definition privilege cannot be revoked because a table, routine, or sequence generator exists in the schema.

S: Ignores this SQL statement.

P: Delete the table, routine, sequence generator, or schema, and then retry the operation.

KFPA11578-E A

Unable to have two attributes(public,private) for RDAREA "aa....aa"

An attempt was made with GRANT RDAREA to change an RDAREA to be both a public and a private user RDAREA.

aa....aa: Name of the RDAREA resulting in the error

S: Ignores this SQL statement.

Action

To change a public user RDAREA to a private user RDAREA, execute REVOKE RDAREA RDAREA-name FROM PUBLIC and re-execute.

To change a private user RDAREA to a public user RDAREA, execute REVOKE RDAREA RDAREA-name FROM authorization-identifier and re-execute.

KFPA11579-E A

Unable to create aa....aa without schema privilege

The schema cannot be defined because the user does not have schema definition privileges.

aa....aa: Invalid SQL statement ( schema )

S: Ignores this SQL statement.

P: Ask a user with the DBA privilege to grant the schema definition privilege to this user, then re-execute.

KFPA11580-E A

Unable to drop aa....aa."bb....bb"

The routine aa....aa."bb....bb" defined in the create type statement, cannot be deleted by itself.

aa....aa: Authorization identifier

bb....bb: Routine identifier

S: Ignores this SQL statement.

P: If there is an error in the specification of the routine, correct the specification and re-execute. Or, execute the SQL that deletes the abstract data type definition that includes the specified routine.

KFPA11583-E A

Specified ROUTINE aa....aa."bb....bb" not available for index

A plug-in index cannot be applied to the routine aa....aa."bb....bb". Functions to which a plug-in index can be applied are those that are installed in a plug-in for which SCAN TYPE is specified in the operation qualifier for the plug-in IDL.

aa....aa: Authorization identifier

bb....bb: Routine identifier

S: Ignores this SQL statement.

P: Correct the specification of the applied function (FOR clause), and re-execute the index definition statement.

KFPA11584-E A

aa....aa "bb....bb" not available for index

The aa....aa "bb....bb" specified as an object of indexing does not match the index type.

aa....aa: Type of the target item

{ COLUMN }

bb....bb: Column or attribute name

S: Ignores this SQL statement.

P: Either change the target column specification or the specification for the index type to be used. Revise the SQL statement so that the target column and the index type are correctly associated, and then re-execute.

KFPA11585-E A

More than 16 RDAREAs in "aa....aa" RDAREA statement

More than 16 RDAREA names were specified in the GRANT RDAREA or REVOKE RDAREA statement (a maximum of 16 RDAREA names can be specified).

aa....aa: Invalid SQL statement:

{ GRANT |REVOKE }

S: Ignores this SQL statement.

Action

Correct the SQL statement and re-execute.

KFPA11590-E A

Number of specified authorization identifiers not equal to number of password in "GRANT" statement

The number of authorization identifiers specified in the GRANT statement does not match the number of passwords.

S: Ignores this SQL statement.

Action

Correct the SQL statement and re-execute.

KFPA11591-E A

Unable to specify "NULL" for "FIX" table

NULL cannot be specified in the column definition for a table for which FIX is specified.

S: Ignores this SQL statement.

Action

Either delete the FIX specification or delete the NULL specification from the column definition, then re-execute.

KFPA11592-E A

Unable to specify "NULL" for cluster key column or primary key column

NULL cannot be specified in the column definition for a column for which the single-column or multicolumn uniqueness constraint is specified.

S: Ignores this SQL statement.

Action

Delete the column for which NULL was specified from the single-column or multicolumn uniqueness constraint definition or delete the NULL specification from the column definition, then re-execute.

KFPA11595-E A

Duplicate parameter name "aa....aa"

Duplicate parameter names are specified in CREATE PROCEDURE, CREATE FUNCTION, or CREATE TYPE.

aa....aa: Duplicated parameter name

S: Invalidates this transaction.

P: Change the parameter name and re-execute.

KFPA11596-E A

No RDAREA for routine definition

A data dictionary LOB RDAREA is not defined; therefore, the following SQL statements cannot be executed:

ALTER PROCEDURE

ALTER ROUTINE

ALTER TRIGGER

CALL statement

CREATE FUNCTION

CREATE PROCEDURE

CREATE TRIGGER

CREATE TYPE

DROP FUNCTION

DROP PROCEDURE

Function invocation

S: Ignores this SQL statement.

P: Allocate a data dictionary LOB RDAREA with the database initialization utility (pdinit) or the database structure modification utility (pdmod) and re-execute the SQL.

KFPA11597-E A

Unable to alter table for "aa....aa" column

In ALTER TABLE, columns for which data type aa....aa is specified cannot be deleted.

aa....aa:

BLOB

abstract data (abstract data type)

S: Ignores this SQL statement.

P: To modify the definition of the table, delete the table with DROP TABLE, then create a new table with CREATE TABLE.

KFPA11599-E A

Specified RDAREA not for "LOB"

The specified RDAREA is not user LOB RDAREA.

S: Ignores this SQL statement.

P: Specify a user LOB RDAREA and re-execute.

KFPA11600-E A

Routine aa....aa."bb....bb" already specified for another index

Another plug-in index is already applied to the routine aa....aa."bb....bb".

aa....aa: Authorization identifier

bb....bb: Routine identifier

S: Ignores this SQL statement.

P: Either change the specification for the applied function or specify the target function, delete the defined index, and then re-execute.

KFPA11601-E A

Duplicate aa....aa bb....bb."cc....cc"

One of the following errors occurred:

When bb....bb is something other than ********:

The table identifier, index identifier, routine identifier, trigger identifier, constraint name, data type identifier, or sequence generator specified in one of the following SQL statements is already defined:

ALTER TABLE

ALTER INDEX

CREATE FUNCTION

CREATE INDEX

CREATE PROCEDURE

CREATE PUBLIC FUNCTION

CREATE PUBLIC PROCEDURE

CREATE PUBLIC VIEW

CREATE SEQUENCE

CREATE TABLE

CREATE TRIGGER

CREATE TYPE

CREATE VIEW

When bb....bb is ********:

The same routine identifier as the routine identifier specified in one of the following SQL statements is already defined by a public procedure:

CREATE PROCEDURE

CREATE TYPE

The same routine identifier as the routine identifier specified in the following SQL statement is already defined by a procedure:

CREATE PUBLIC PROCEDURE

aa....aa: SQL statement that was executed

{constraint|datatype|index|routine|sequence|table|trigger}

bb....bb: Authorization identifier, or ********

cc....cc: Table identifier, index identifier, routine identifier, trigger identifier, constraint name, data type identifier, or sequence generator identifier

S: Ignores this SQL statement.

P: Change the table identifier, index identifier, routine identifier, trigger identifier, constraint name, data type identifier, or sequence generator identifier, and then retry the operation.

KFPA11602-E A

Over 30000 columns in table

The total number of columns for a table exceeded the maximum (30,000).

S: Ignores this SQL statement.

P: If there is an error in the specified SQL statement, correct the error and re-execute. Alternatively, redesign the table so that the number of columns does not exceed 30,000.

KFPA11603-E A

Duplicate key value detected in unique index while creating index

An attempt was made to create an index with UNIQUE specified, but a duplicate column value was found in the table data.

S: Disables this transaction.

P: Correct the duplicate column value in the table and re-create the index with UNIQUE specified. Or, delete the UNIQUE specification, if possible, and create the index by the batch method.

KFPA11604-E A

Invalid length, precision or scale in column definition, column= aa....aa "bb....bb" cc....cc

The data type length, precision, or scaling factor specified in one of the following locations contains an error:

In a column, SQL parameter, SQL variable, or attribute definition

In a function specification in DROP FUNCTION

In the RETURNS clause of CREATE FUNCTION

In the AS clause in an argument in a function invocation

The AS clause of a CAST specification

CURRENT_TIMESTAMP value function

AS clause for the ? parameter or embedded variable

In the AS clause in a substructure specification in CREATE INDEX

In the AS clause in an argument in an XML constructor function

In the AS clause in an argument in an SQL/XML scalar function

Details of the errors in the data type length, precision, or scaling factor are as follows:

If the data type is DECIMAL:

The condition 1 precision 38, 0 scaling-factor 38 is not met.

The condition precision scaling-factor is not met.

If the data type is CHAR, MCHAR:

The condition 1 data-type-length 30,000 is not met.

If the data type is CHAR and the character set name is UTF16 in the character set specification:

The condition 1 data-type-length 30,000 is not met.

The data length is not a multiple of 2.

If the data type is VARCHAR, MVARCHAR:

The condition 1 data-type-length 32,000 is not met.

If the data type is VARCHAR and the character set name is UTF16 in the character set specification:

The condition 1 data-type-length 32,000 is not met.

The data length is not a multiple of 2.

If the data type is NCHAR:

The condition 1 data-type-length 15,000 is not met.

If the data type is NVARCHAR:

The condition 1 data-type-length 16,000 is not met.

If the data type is BLOB:

The condition 1 data-type-length 2,147,483,647 is not met.

If G is specified as the data length unit, the condition 1 specified length 2 is not met.

If M is specified as the data length unit, the condition 1 specified length 2,048 is not met.

If K is specified as the data length unit, the condition 1 specified length 2,097,152 is not met.

If the data type is BINARY:

The condition 1 data-type-length 2,147,483,647 is not met.

If the data type is TIMESTAMP, or the CURRENT_TIMESTAMP value function is used:

The number of digits of fractional seconds is not 0, 2, 4, or 6.

aa....aa: See below.

bb....bb: See below.

cc....cc: See below.

S: Ignores this SQL statement.

P:

Correct the length, precision, or scale and re-execute.

Following is the correspondence between the invalid data type specification locations and items aa....aa, "bb....bb", and cc....cc:

Data type specification location | aa....aa | "bb....bb" | cc....cc
Column definition | definition of column | Column name | --
SQL parameter declaration | declaration of SQL parameter | SQL parameter name | --
SQL variable declaration | declaration of SQL variable | SQL variable name | --
Attribute definition | definition of attribute | Attribute name | --
In a DROP FUNCTION function specification | function specification | Function name | (nth argument)
RETURNS clause of the function body | RETURNS clause in function definition | Function name | --
AS clause in an argument for the function invocation | function invocation | Function name | (nth argument)
AS clause of a CAST specification | AS clause in CAST specification | ******** | --
CURRENT_TIMESTAMP | CURRENT_TIMESTAMP | ******** | --
AS clause specified for the ? parameter or embedded variable | AS clause for ? parameter or embedded variable | ******** | --
AS clause in a substructure specification in CREATE INDEX | AS clause in CREATE INDEX statement | ******** | (nth partial structure specification, where n is the substructure specification number)
AS clause in the argument of an XML constructor function | AS clause in XML constructor | Function name | --
AS clause in the argument of an SQL/XML scalar function | AS clause in SQL/XML scalar function | Function name | --

Legend:

--: Not applicable

KFPA11605-E A

Unable to specify "SUPPRESS" for "FIX" table

SUPPRESS cannot be specified for a table with the FIX attribute.

S: Ignores this SQL statement.

P: Delete the specification of SUPPRESS or the specification of FIX, then re-execute.

KFPA11607-E A

Unable to use definition SQL on other user's aa....aa

The following processing cannot be executed:

Creation of a base table, viewed table, or index owned by another user

Deletion of a base table, viewed table, or index owned by another user

Modification to the definition of a base table or index owned by another user

Addition of a comment to a base table or viewed table owned by another user

Creation or deletion of a procedure owned by another user

Specification to assign to memory, or release from memory, a base table owned by another user

Creation or deletion of a function owned by another user

Creation or deletion of a data type owned by another user

Creation or deletion of an index type owned by another user

Modification of a data type owned by another user

Modification of an index type owned by another user

Definition or deletion of a trigger owned by another user

Creation or deletion of a sequence generator owned by another user

In the Windows edition of HiRDB, this message is also output if the authorization identifier specified in a table in a definition SQL is different from the authorization identifier that was used for connecting. In the case of a utility, such as the database definition utility (pddef), that does not require entry of an authorization identifier for connection, check the PDUSER value of the client environment definition (hirdb.ini). The entire PDUSER value must be enclosed in apostrophes (') in the environment definition (hirdb.ini).

Example

PDUSER='"root"/"root"'

aa....aa: {table|index|procedure|trigger|function|datatype|indextype|sequence}

S: Ignores this SQL statement.

P: Make sure that the execution user and the owner are the same, and then retry the operation.

KFPA11608-E A

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

The user does not have RDAREA usage privileges for the specified RDAREA. As a result, the table, index, or sequence generator cannot be created.

aa....aa: RDAREA name

S: Ignores this SQL statement.

P: Either specify the RDAREA for which you have usage privilege, or have the RDAREA usage privilege granted for the RDAREA, and then re-execute.

KFPA11609-E A

Unable to define aa....aa column in "FIX" table

A column aa....aa cannot be defined for a table with a FIX attribute.

aa....aa:

variable length: variable length

user data type: user-defined data type

multi-value: repetition column

S: Ignores this SQL statement.

P:

In the case of CREATE TABLE, change the specification for a variable-length column, a user-defined type column, or a repetition column. Or, delete the specification for the FIX attribute, and then re-execute.

In the case of ALTER TABLE, re-execute the SQL statement without specifying a variable-length column, user-defined column, or repetition column.

KFPA11610-E A

No more available public user RDAREA

A table or sequence generator cannot be defined, because there is no available public user RDAREA, or there is an available public user RDAREA, but it cannot be used for one of the reasons listed below.

For a table definition:

In HiRDB/Parallel Server, an unshared RDAREA is required when defining an unshared table, and a shared RDAREA is required when defining a shared table. In HiRDB/Single Server, an unshared RDAREA is required when defining both unshared tables and shared tables.

The number of tables defined per RDAREA has reached the maximum (500).

If a primary key or a cluster key is specified, the number of indexes defined per RDAREA has reached the maximum (500).

For a table with the FIX attribute, the page length is not sufficient for the specified row length.

The RDAREA is in shutdown status.

A table using the rebalancing facility is defined (applicable only for defining unshared tables).

If a cluster key or primary key is specified, the key length of the index relative to the RDAREA page length has exceeded the maximum length. It is calculated as follows:
key-length MIN((page-length-of-RDAREA-for-index-storage 2) - 1,242, 4,036)
For details about how to calculate key lengths, see the description of CREATE INDEX in the manual HiRDB Version 9 SQL Reference.

For a sequence generator definition:

The total number of tables and sequence generators defined per RDAREA has reached the maximum (500).

The RDAREA is in shutdown status.

The RDAREA is using the inner replica facility.

S: Ignores this SQL statement.

P: Define a public RDAREA that can be used, and then re-execute. Or, specify a private user RDAREA that can be used, and then re-execute. A usable RDAREA is an RDAREA that does not match the conditions of the previously described unusable RDAREA.

KFPA11611-E A

Unable to aa....aa bb....bb

Hash function change or RDAREA addition is not possible because the table is not a hash partitioned table.

aa....aa: Processing to be executed

{ change |add }

bb....bb: Operation target {HASH|RDAREA}

S: Ignores this SQL statement.

P: Delete this SQL statement.

KFPA11612-E A

Duplicate column name "aa....aa"

A column with the same name cannot be defined more than once for the same table.

aa....aa: Column name resulting in the error

S: Ignores this SQL statement.

P: Correct the SQL statement so that the column name is not duplicated and re-execute.

KFPA11613-E A

Unable to aa....aa for not empty table

Operation aa....aa cannot be performed on a table containing data.

aa....aa: Invalid specification:

add column: Addition of a column that has the NOT NULL constraint or DEFAULT clause specification, or addition of a column in a FIX table

add rdarea:

Addition of an RDAREA to a table with FIX hash partitioning that does not use the rebalancing facility

change no split:

Change in the no-split option

change split:

Change in the no-split option

change set default:

Set or change the default

change drop default:

Delete the default

change cluster key:

Modification of the cluster key attribute

change hash:

Modification of the hash function for a table with FIX hash partitioning

drop column:

Deletion of a column

change insert only:

Change of a non-falsification-prevented table to a falsification-prevented table

S: Ignores this SQL statement.

P: Specify a table containing no data and re-execute. Or, with the PURGE TABLE statement, delete all data from the table and re-execute (create a backup copy before executing the PURGE TABLE statement in case an error occurs).

KFPA11614-E A

Unable to bb....bb on column "aa....aa"

When bb....bb is create index or define foreign key:

A column with one of the following data types cannot be specified for an index, primary key, cluster key, or foreign key component column:

BLOB

User-defined type

BINARY

When bb....bb is create partial structure index:

Only an XML type column can be specified for a column comprising a substructure index.

aa....aa: Name of the column with the invalid data type

bb....bb: {create index|define foreign key|create partial structure index}

S: Ignores this SQL statement.

P: Delete this SQL statement.

KFPA11615-E A

Unable to create multi column index on column "aa....aa"

A column with one of the following data types cannot be specified for a multicolumn index, multicolumn primary key, or multicolumn cluster key:

FLOAT

SMALLFLT

aa....aa: Name of the column with the invalid data type

S: Ignores this SQL statement.

P: Delete this SQL statement.

KFPA11616-E A

Index key length is too long

The index key exceeds the maximum length. Calculate the key length as follows:
key-length MIN((page-length-of-RDAREA-for-index-storage 2) - 1242, 4036)
For details about how to calculate key lengths, see the description of CREATE INDEX in the manual HiRDB Version 9 SQL Reference.

S: Ignores this SQL statement.

P: For a single-column index, delete this SQL statement because it cannot be executed. For a multicolumn index, correct the key length to not exceed maximum and re-execute.

KFPA11617-E A

More than 16 columns specified for index

The number of CREATE INDEX columns or the number of values comprising the exception key value exceeded the maximum specifiable number of 16.

S: Ignores this SQL statement.

P: Correct the number of columns comprising an index or the number of values that comprise exclusion key values to less than or equal to 16 and re-execute.

KFPA11619-E A

Duplicate column name "aa....aa" in constructed index columns

The column name specified by CREATE INDEX , the column name comprising the primary key, or the column name comprising the cluster key is duplicated.

aa....aa: Duplicated column name

S: Ignores this SQL statement.

P: Correct the SQL statement so that the names of the index component columns are not duplicated, then re-execute.

KFPA11620-E A

Unable to specify "aa....aa" for flexible HASH partitioning table

UNIQUE or PRIMARY KEY cannot be specified for a table with flexible hash partitioning or a matrix partitioning table using flexible hash partitioning.

aa....aa:

UNIQUE: Unique

PRIMARY KEY: Primary key

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute the job.

KFPA11621-E A

Unable to define unique index for multi-value column "aa....aa"

An index with a UNIQUE specification cannot be defined on the repetition column "aa....aa".

aa....aa: Name of the repetition column

S: Ignores this SQL statement.

P: Correct the SQL statement or delete the SQL statement and re-execute.

KFPA11622-E A

Invalid HASH function name "aa....aa"

One of the following errors was found in the hash function specification:

The specified hash function name could not be found.

The column length of the hash partitioning key is shorter that the key length of the specified hash function.
Following are the hash functions and the key length of each:

HASH3: 2 bytes or more

HASH4: 4 bytes or more

HASH5: 3 bytes or more

HASHC: 2 bytes or more

HASHD: 4 bytes or more

HASHE: 3 bytes or more

The hash function of tables not using the rebalancing facility cannot be changed to HASHA, HASHB, HASHC, HASHD, HASHE, or HASHF.

The hash function for tables using the rebalancing facility cannot be changed to HASH1, HASH2, HASH3, HASH4, HASH5, HASH6, HASH0 or HASHZ.

HASHA, HASHB, HASHC, HASHD, HASHE, or HASHF cannot be specified in a table hash function defining a cluster key or primary key.

The SEGMENT REUSE option cannot be specified (the SEGMENT REUSE NO option can be specified) in a table specifying HASHA, HASHB, HASHC, HASHD, HASHE, or HASHF.

If HASH0 or HASHZ was specified, one of the following errors occurred:
An incorrect data type was specified for the partitioning key. For details about data types that can be specified, see hash-function-name under CREATE TABLE (Define table) in the manual HiRDB Version 9 SQL Reference.
Multiple columns were specified for the partitioning key.

aa....aa: Hash function name

Following are the hash function names and their minimum key lengths:

HASH3: 2 bytes

HASH4: 4 bytes

HASH5: 3 bytes

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute the job.

KFPA11625-E A

Unable to define "aa....aa" on multi-value column

The table restriction definition "aa....aa" cannot be specified for a repetition column.

aa....aa:

CLUSTER KEY: cluster key

PRIMARY KEY: Primary key

FOREIGN KEY: Foreign key

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11626-E A

Unable to specify "aa....aa" for bb....bb

aa....aa cannot be specified for bb....bb.

aa....aa: {FOR RESERVED|INTO}

bb....bb: {except "FIX" table|INSERT ONLY table}

S: Ignores this SQL statement.

P:

When bb....bb is except "FIX" table:

Correct the SQL statement so that aa....aa is specified for a FIX attribute table and re-execute.

When bb....bb is INSERT ONLY table:

Correct the SQL statement so that a reserved column is added to a table other than a falsification prevented table, and then retry the operation.

KFPA11628-E A

Unable to define aa....aa for multi-value column

When defining a table or modifying a table definition, aa....aa cannot be specified for a repetition column.

aa....aa: {"NOT NULL" constraint|character set}

"NOT NULL" constraint: NOT NULL constraint

character set: Character set

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11631-E A

Unable to aaaaaa "bb....bb" column

When "bb....bb" is not abstract data, aaaaaa cannot process "bb....bb".
If "bb....bb" is an abstract data type, the processing aaaaaa cannot be performed on the tables that include "bb....bb".

aaaaaa: Processing that cannot be executed:

{ change |drop }

bb....bb: Type of column:

CLUSTER KEY: Column comprising the cluster key

FOREIGN KEY: Column comprising the foreign key

PRIMARY KEY: Column comprising the primary key

PARTITION KEY: Column comprising the partition key

REFERENCED PRIMARY KEY: Column comprising the primary key of a referenced table

TRIGGER: Column in the trigger definition that is qualified and referenced by the old or new correlation name values

CHECK: Check constraint definition

abstract data: abstract data type

S: Ignores this SQL statement.

P: Delete this SQL statement.

KFPA11632-E A

Unable to drop column from aa....aa

If there is no reserved column in the table, the column cannot be deleted because there is only one column in the table.
If there is a reserved column in the table, the column cannot be deleted because there is only one non-reserved column in the table.

aa....aa: {single column table|single column table except reserved column}

S: Ignores this SQL statement.

P: Execute the DROP TABLE statement, not the ALTER TABLE statement.

KFPA11633-E A

Column for divided key must be "NOT NULL"

The storage condition column, boundary-value partitioning column, or hash partitioning key column does not have the NOT NULL constraint.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11634-E A

More than aaaa partitions or bbbb RDAREA specifications in storage for cc....cc

The number of partitions for cc....cc storage exceeds aaaa. Or, the specifications of RDAREA names for cc....cc storage exceed bbbb.

aaaa:

{1024|4096}

bbbb:

4096

cc....cc: Storage processing type:

{ TABLE |COLUMN |CLUSTER KEY |PRIMARY KEY |INDEX }

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11636-E A

More than 15000 constants in partitioning condition

The total number of literals specified for the table storage conditions exceeds 15,000.

S: Ignores this SQL statement.

P: Correct the SQL statement so that specification of literals for the storage condition does not exceed 15,000 and re-execute.

KFPA11637-E A

More than 30000 SQL parameters defined in aa....aa definition

The number of SQL parameters defined in aa....aa is greater than 30,000.

aa....aa:

{ FUNCTION |PROCEDURE }

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11638-E A

Unable to specify self-join for view or "WITH" query which derives internal table

In a query specification for creating an internal derived table, joining of the same table is specified.
The conditions for creating an internal derived table are as follows:

In a query for a named derived table, derived by specifying SELECT DISTINCT, the named derived table is included in a subquery or directly includes one of the following:

GROUP BY clause, HAVING clause, or set function

SELECT DISTINCT

Table join (including outer join and inner join)

Value expression other than a column specification was specified in the selection expression

None of the columns of the named derived table specified in the FROM clause is specified singularly in the selection expression.

NEXT VALUE expression

A query for a named derived table, derived by specifying a GROUP BY clause, HAVING clause, or a set function, directly includes one of the following:

GROUP BY clause, HAVING clause, or set function

Table join (including outer join and inner join)

Window function

NEXT VALUE expression

A query for a named derived table, derived by specifying a value expression other than a column specification as the selection expression, directly includes one of the following:

GROUP BY clause, HAVING clause, or set function

Window function

Joined table

A query for a named derived table, derived by specifying a set function with DISTINCT, directly includes one of the following:

GROUP BY clause, HAVING clause, or set function

SELECT DISTINCT

Window function

A query for a named derived table, derived by specifying a table join (including both outer joins and inner joins), directly includes a table join (including both outer joins and inner joins) and one of the specified table join operations specifies a table join.

A query for a named derived table, derived by specifying a scalar subquery in the selection expression, directly includes one of the following:

SELECT DISTINCT

GROUP BY clause, HAVING clause, or set function

Table join (including both outer joins and inner joins)

A value expression other than a column specification in a selection expression

A scalar subquery specified in a selection expression

The same column, derived from a value expression containing a subquery, specified more than once in the selection expression for a named derived table

A column, derived from a value expression containing a subquery, specified as an external reference column in the selection expression for a named derived table

A viewed table defined before HiRDB version 07-02

A query for a named derived table, derived from a set operation, which satisfies one of the following:

One of the operators of the set operation includes an internal derived table query, a query that specifies a derived table, or a query that specifies a subquery in a selection expression.

One of the operators of the set operation and the query for the named derived table satisfy one of the conditions of 1 through 6 above

A query for a named derived table, derived from a set operation that includes other than UNION ALL, which directly includes one of the following:

GROUP BY clause, HAVING clause, or set function

SELECT DISTINCT

Table join (including both outer joins and inner joins)

WHERE clause

Subquery

Value expression, other than a column specification, in a selection expression

Selection expression in which the columns of a named derived table specified in the FROM clause are not each specified once

NEXT VALUE expression

A query for a named derived table derived from a set operation that includes only UNION ALL, which directly includes one of the following:

GROUP BY clause, HAVING clause, or a set function

Window function

WHERE clause or subquery (however, only a subquery, a set operation operator, or an INSERT statement query)

Function call or system definition scalar function

Component specification

WRITE specification

GET_JAVA_STORED_ROUTINE_SOURCE specification

Sort specification with items not in the selection expression

Subquery for a named derived table derived from a set operation specified in the FROM clause

Subquery that specifies a derived table

Subquery specified in a value expression other than a column specification in the GROUP BY clause

The data type of an SQL variable specified in a selection expression or an SQL parameter is one of the following:
BLOB type
BINARY type 32,001 bytes or larger
Abstract data type
BOOLEAN type

The query specification specified for the table-joining of named derived tables derived by a set operation consisting solely of UNION ALL specifies one of the following:

A named derived table in a table reference other than at the leftmost outer table for an outer join

The FROM clause specifying a named derived table, which specifies a comma join (that is, specifies a different table reference than the joined table for which a derived table is specified)

A subquery or a derived table

A query specification contained either in a subquery or in the operation term for a set operation

A set operation term that derives named derived tables and contains one of the following:
Table join
GROUP BY clause, HAVING clause, or a set function
SELECT DISTINCT
A value expression in a selection expression other than a column specification
A query that creates an inner derived table
A query specifying a derived table

A named derived table derived by specifying a set operation (in addition to a named derived table)

One of the following, in the table reference to a joined table specifying a named derived table:
A named derived table derived by specifying the joining of tables
A named derived table derived by specifying a GROUP BY clause, a HAVING clause, or a set function
A named derived table derived by specifying SELECT DISTINCT
A named derived table derived by specifying a value expression other than a column specification in a selection expression
A named derived table derived by specifying a query that creates an inner derived table
A named derived table derived by specifying a subquery

The total number of tables obtained by the following expression is greater than 65:
Total number of tables = a + b c + d
a: Total number of tables from which named derived tables are derived
b: Number of set operations from which named derived tables are derived + 1
c: Total number of tables specified on the right side of an outer join
d: If a query other than a query for which a named derived table is specified is also specified, the total number of tables specified in the query

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11639-E A

Distinct view specified in "FROM" clause of subquery in view definition, in "WITH" query, or in query with grouping by expression

A derived query in the view definition or the WITH clause or a query specifying a value expression (except for column specifications) in the GROUP BY clause specifies a named derived table that was derived by specifying a duplication elimination in the subquery's FROM clause.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11640-E A

Outer reference specified for column derived from "aa....aa" in view or "WITH" query

Outer reference was specified for one of the following columns:

A column in a viewed table defined from COUNT(*) or COUNT_FLOAT(*)

A column derived from the COUNT(*) or COUNT_FLOAT(*) specified in a selection expression in a derived query expression in the WITH clause

aa....aa: Set function: {COUNT(*) | COUNT_FLOAT(*)}

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11641-E A

Unable to specify derived table in joined table

A named derived table derived under the following condition cannot be specified in a joined table:

A named derived table was derived by specifying a set operation

Also, a viewed table cannot be specified in a derived query expression joined table if the viewed table or the base table comprising the viewed table is defined as follows:

With subquery specified

By specifying the joining of tables, SELECT DISTINCT, a GROUP BY clause, or a HAVING clause

Viewed table defined by specifying a value expression other than a column specification in the SELECT clause.

S: Ignores this SQL statement

P: Correct the SQL statement and re-execute.

KFPA11642-E A

Grouping specified for derived table having derived column in view definition, in "WITH" query, or in query with grouping by expression

A GROUP BY clause, a HAVING clause, or a set function is specified in a view definition query, in a derived query in the WITH clause query, or in a value expression (except when a column specifies a value expression) in the GROUP BY clause for a named derived table with columns derived by a value expression other than a column specification.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11643-E A

Join specified for group view in view definition, in "WITH" query, or in query with grouping by expression

A table join is specified in a query specifying a value expression (except when a column specifies a value expression) in a view definition, in a derived query for a query in the WITH clause, or in the GROUP BY clause for a named derived table that was derived by specifying a GROUP BY clause, a HAVING clause, or a set function.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11644-E A

Grouping specified for group view in view definition, in "WITH" query, or in query with grouping by expression

One of the following specifications was made in a query specifying a value expression (except when a column specifies a value expression) in a view definition, or in a derived query expression in the WITH clause for a named derived table that was derived by a query specifying a GROUP BY clause, a HAVING clause, or a set function:

GROUP BY clause

HAVING clause

Set function

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11645-E A

Constant or value expression in "SELECT" clause specified for distinct view in view definition or "WITH" query

A value expression other than a column specification was specified in a view definition or the SELECT clause in a derived query expression in a query in the WITH clause for a viewed table specifying a duplication elimination (DISTINCT).

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11646-E A

Join specified for distinct view in view definition or "WITH" query

A viewed table specifying duplication elimination (DISTINCT) was searched by specifying the joining of tables in either a view definition or a derived query expression in a query in the WITH clause.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11647-E A

Distinct specified for distinct view in view definition, in "WITH" query, or in query with grouping by expression

A value expression other than a column specification was specified in a view definition, a derived query expression in a query in the WITH clause, or in the GROUP BY clause for a named derived table that was derived by specifying a duplication elimination (DISTINCT).

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11648-E A

Unable to derive internal table in query or in where subquery with grouping by expression

A query specification for creating an internal derived table cannot be specified in the following:

A query in which a value expression other than a column specification is specified in a GROUP BY clause

A subquery of a WHERE clause of a query in which a value expression other than a column specification is specified in a GROUP BY clause

The conditions for creating an internal derived table are as follows:

In a query in a named derived table that was derived by specifying SELECT DISTINCT, the named derived table is either included in a subquery or directly includes one of the following:

GROUP BY clause, HAVING clause, or set function

SELECT DISTINCT

Table join (including outer join and inner join)

Specification of a value expression other than a column specification in the selection expression

None of the columns of the named derived table specified in the FROM clause is specified singularly in the selection expression.

A query for a named derived table, derived by specifying a GROUP BY clause, HAVING clause, or a set function, directly includes one of the following:

GROUP BY clause

HAVING clause

Set function

Table join (including outer join and inner join)

A query for a named derived table, derived by specifying a value expression other than a column specification as a selection expression, directly includes one of the following:

GROUP BY clause

HAVING clause

Set function

Joined table

A query for a named derived table, derived by specifying a set function with DISTINCT specification, directly includes SELECT DISTINCT specification.

A query for a named derived table, derived by specifying a joined table, directly includes one of the following:

Table join (including outer join and inner join)

Subquery

A query for a named derived table, derived by specifying table join or a subquery, directly includes a joined table specification.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11649-E A

Grouping specified for distinct view in view definition, in "WITH" query, or in query with grouping by expression

A query specified by a value expression (except when the value expression is a column specification) in a view definition, a derived query expression in a query in the WITH clause, or in the GROUP BY clause, for a named derived table that was derived by specifying a duplication elimination (DISTINCT), directly specifies one of the following:

GROUP BY clause

HAVING clause

Set function

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11650-E A

Number of view columns or "WITH" query columns not equal to number of select columns

The number of items to be retrieved in the SELECT clause does not match the following value:

Number of columns comprising the viewed table

Number of columns in the table specified in the query name of the WITH clause

S: Ignores this SQL statement.

P: Check that the number of columns comprising the viewed table or the number of columns in the table derived as the query name matches the number of items subject to retrieval in the SELECT clause, then re-execute.

KFPA11651-E A

Unable to specify aa....aa in view definition

The following items cannot be specified in a view definition:

? parameters or embedded variables

Structured repetition predicates

IN (RDAREA-name-specification)

aa....aa:

{ ? parameter or embedded variable |ARRAY predicate |RDAREA name specification}

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11652-E A

Specified RDAREA "aa....aa" not defined

The RDAREA specified in one of the following SQL statements was not found:

ALTER TABLE

CREATE INDEX

CREATE SEQUENCE

CREATE TABLE

GRANT RDAREA

aa....aa: RDAREA name

S: Ignores this SQL statement.

P: Either specify a defined user RDAREA or correct the RDAREA name and re-execute.

KFPA11653-E A

Specified RDAREA aa....aa bb....bb

One of the following errors was detected:

When bb....bb is not for user:

The user cannot use aa....aa.

When bb....bb is replicated rdarea:

aa....aa is a replicated RDAREA.

When bb....bb is used by inner replica facility:

The following resources cannot be created in RDAREA aa....aa, which uses the inner replica facility:

Falsification prevented table

Sequence generator

When bb....bb is RDAREA for temporary table:

aa....aa is a temporary table RDAREA.

For these reasons, the following SQL statements cannot be executed:

ALTER TABLE

CREATE INDEX

CREATE SEQUENCE

CREATE TABLE

GRANT RDAREA

DROP INDEX

DROP TABLE

DROP SCHEMA

REVOKE RDAREA

aa....aa: RDAREA-name

bb....bb: {not for user|replicated rdarea|used by inner replica facility|RDAREA for temporary table}

S: Ignores this SQL statement.

P:

bb....bb is not for user:

Specify the user RDAREA and re-execute.

bb....bb is replicated rdarea:

Specify the original RDAREA and re-execute.

bb....bb is used by inner replica facility:

Specify an RDAREA not applying the inner replica facility and re-execute. Alternatively, cancel application of the inner replica facility and re-execute.

When bb....bb is RDAREA for temporary table:

Specify a user RDAREA that is not a temporary table RDAREA, and then retry the operation.

KFPA11654-E A

Number of aa....aa exceeds bbb

When aa....aa is tables and sequences:

The total number of tables and sequence generators in the RDAREA exceeded the maximum.

The maximum total number of tables and sequence generators that can be specified in an RDAREA is 500.

When aa....aa is indexes:

The number of indexes in the RDAREA exceeded the maximum.

The maximum number of indexes that can be specified in an RDAREA is 500.

aa....aa: One of the following is displayed:

tables and sequences

indexes

bbb: 500

S: Ignores this SQL statement.

P: Specify another RDAREA and re-execute.

KFPA11656-E A

No schema for aa....aa

Because a schema is missing, the following SQL statements cannot be executed:

ALTER PROCEDURE

ALTER ROUTINE

CREATE FUNCTION

CREATE INDEX

CREATE PROCEDURE

CREATE SEQUENCE

CREATE TABLE

CREATE TRIGGER

CREATE TYPE

CREATE VIEW

DROP SCHEMA

aa....aa: Authorization identifier of the user without the schema

S: Ignores this SQL statement.

P: To execute CREATE TABLE, CREATE INDEX, CREATE PROCEDURE, CREATE TYPE, CREATE FUNCTION, CREATE TRIGGER, CREATE VIEW, or CREATE SEQUENCE, use the CREATE SCHEMA statement to create a schema before executing the desired statement. In the case of DROP SCHEMA, ALTER PROCEDURE, and ALTER ROUTINE, they do not have to be executed because no schema was defined.

KFPA11657-E A

Too small page size aa....aa for row length bb....bb

The page length of a specified RDAREA is insufficient.

aa....aa: Page length of the specified RDAREA

bb....bb: Row length (in bytes)

For national character data, the specified value times 2 is displayed in the message as the row length.

S: Ignores this SQL statement.

P: Either specify an RDAREA satisfying the condition shown below or reduce the row length, then re-execute:

Condition:

Note

means that the value is to be rounded down.

KFPA11658-E A

Unable to specify "ALL" as table identifier

ALL cannot be used as a table identifier.

S: Ignores this SQL statement.

P: Correct the table identifier and re-execute.

KFPA11659-E A

Invalid data type or data length

The data type or data length specified in the CHANGE clause is invalid for one of the following reasons:

An attempt was made to reduce the data length.

An attempt was made to change the length of fixed-length data.

An attempt was made to change an unchangeable data type.

An attempt was made to change the data type of a column that has a character set specification.

A character set was specified for a character string data type after it was changed.

For a column whose character set is UTF16, an attempt was made to change the data length to a value that is not a multiple of 2.

S: Ignores this SQL statement.

P: Correct the error and re-execute.

KFPA11660-E A

Unable to aa....aa on the bb....bb

One of the following errors was detected in the table manipulation:

Index creation, trigger creation, or table definition change cannot be performed on a viewed table.

Table definition change cannot be performed on an audit trail table.

Index creation or table definition change cannot be performed on a temporary table.

aa....aa: One of the following items is displayed:

alter table

create index

create trigger

alter index

bb....bb: One of the following items is displayed:

view

table

audit trail table

temporary table

S: Ignores this SQL statement.

P: Delete this SQL statement.

KFPA11661-E A

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

Index aa....aa."bb....bb" is already defined in HiRDB.
For a substructure index, substructure index aa....aa."bb....bb", whose key is the same substructure of the same column, is already defined in HiRDB.

aa....aa: Authorization identifier

bb....bb: Index identifier

S: Ignores this SQL statement.

P: Delete this SQL statement.

KFPA11662-E A

Unable to cc....cc because of key length of index aa....aa."bb....bb" too long

Cannot cc....cc because the key length of index aa....aa."bb....bb" exceeded the maximum specifiable length. Calculate the correct key length in the following formula:
key-length MIN ((page-length-of-index-storage-RDAREA 2) - 1242, 4037)
For details about how to calculate key lengths, see the description of CREATE INDEX in the manual HiRDB Version 9 SQL Reference.

aa....aa: Authorization identifier

bb....bb: Index identifier

cc....cc: {change data length|add rdarea}

S: Ignores this SQL statement.

P:

When cc....cc is change data length:
To prevent the key length of the index key from exceeding the maximum length, either modify ALTER TABLE or delete the index, and then re-execute.

When cc....cc is add rdarea:
Change the RDAREA storing the index.

KFPA11664-E A

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

The specified schema has already been defined.

aa....aa: Schema

bb....bb: Authorization identifier

S: Ignores this SQL statement.

P: Delete this SQL statement.

KFPA11665-E A

No available parameter found for "ALTER TABLE"

The contents (the maximum number of elements in a repetition column, the data type, the data size, the WITH DEFAULT, or the no-split option specification) specified in the CHANGE clause of ALTER TABLE have not changed from the previous contents.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11667-E A

Invalid maximum number of elements for "ALTER TABLE"

The maximum number of elements specified in the CHANGE clause of ALTER TABLE contains one of the following errors:

An attempt was made to reduce the maximum number of elements.

An attempt was made to change a repetition column into a non-repetition column or a non-repetition column into a repetition column.

The symbol * was not specified, even when the maximum number of elements was not changed.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11669-E A

Invalid table name in view definition

The name of a base table for a viewed table or the name of the viewed table is invalid. Or, the name of a base table for a viewed table is the same as the name of the viewed table.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11670-E A

Update specified for aa....aa

A problem occurred during update processing of a read-only viewed table, falsification-prevented table, or audit trail table, as indicated by aa....aa.

aa....aa: {read only view|INSERT ONLY table|view table derived from INSERT ONLY table|UPDATE ONLY FROM NULL column|AUDIT TRAIL TABLE}

read only view:

An INSERT, UPDATE, or DELETE statement was executed on a read-only viewed table.

INSERT ONLY table or view table derived from INSERT ONLY table:

UPDATE was executed on a column for which update is not permitted on a falsification-prevented table or a viewed table using a falsification-prevented table as its base table.

UPDATE was executed specifying ROW for a falsification-prevented table or a viewed table using a falsification-prevented table as its base table.

A DELETE statement is being executed on a falsification-prevented duration for which a deletion-prevented duration is not specified, or on a viewed table having a falsification-prevented duration as a base table.

UPDATE ONLY FROM NULL column:

UPDATE (element update, add, or delete) was executed with a subscript for a repetition column with the UPDATE ONLY FROM NULL attribute.

UPDATE was executed using a component specification for an abstract data type column with the UPDATE ONLY FROM NULL attribute.

AUDIT TRAIL TABLE:

The INSERT or UPDATE statement was executed for an audit trail table.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11671-E A

As a result of changing data length, invalid use of variable length column occurred in view definition

The following columns in a view definition cannot be changed to BINARY with a length of 32,001 bytes or larger:

A column specified in a comparison predicate, quantified predicate, IN predicate, BETWEEN predicate, NULL predicate, LIKE predicate, or SIMILAR predicate

A column specified in a subquery in a comparison predicate, quantified predicate, or IN predicate

A base table column specified in duplication elimination

A column specified in a selection expression in a query that a set operation is to be performed on

A base table column specified in a grouping or set function

A column specified to define a viewed table developed as an internal derived table in a query specification that satisfies one of the conditions to create an internal derived table

The conditions for creating an internal derived table are as follows:

In a query for a named derived table, derived by specifying SELECT DISTINCT, the named derived table is included in a subquery or directly includes one of the following:

GROUP BY clause, HAVING clause, or set function

SELECT DISTINCT

Table join (including outer join and inner join)

A value expression other than a column specification specified in the selection expression

None of the columns of the named derived table specified in the FROM clause is specified singly in the selection expression

NEXT VALUE expression

A query for a named derived table, derived by specifying a GROUP BY clause, HAVING clause, or set function, directly includes one of the following:

GROUP BY clause, HAVING clause, or set function

Table join (including outer join and inner join)

Window function

NEXT VALUE expression

One of the following is directly included in the query for a named derived table specified by a selection expression that is a value expression other than a column specification:

GROUP BY clause, HAVING clause, or set function

Window function

Joined table

A query on a named derived table derived by directly specifying a set function with DISTINCT contains one of the following:

GROUP BY clause, HAVING clause, or set function

SELECT DISTINCT

Window function

A query for a named derived table derived by specifying a table join (including outer join and inner join) directly includes a table join (including outer join and inner join), and one of the specified table joins specifies a joined table.

A query on a named derived table derived by directly specifying a scalar subquery as a selection expression contains one of the following:

SELECT DISTINCT

GROUP BY clause, HAVING clause, or set function

Table join (including outer join and inner join)

A value expression other than a column specification specified in a selection expression

A scalar subquery specified in a selection expression

The same column derived from a value expression containing a subquery, specified more than once in the selection expression for a named derived table

A column derived from a value expression containing a subquery, specified as an external reference column in the selection expression for a named derived table

A viewed table defined before HiRDB version 07-02

A query for a named derived table derived from a set operation, which satisfies one of the following:

One of the operators of the set operation includes an internal derived table query, a query that specifies a derived table, or a query that specifies a subquery in a selection expression.

One of the operators of the set operation and the query for the named derived table satisfy one of the conditions of 1 through 6 above.

A query for a named derived table derived from a set operation that includes other than UNION ALL, which directly includes one of the following:

GROUP BY clause, HAVING clause, or a set function

SELECT DISTINCT

Table join (including external or internal joins)

WHERE clause

Subquery

Value expression other than a column specification in a selection expression

In a selection expression, the columns of a named derived table specified in the FROM clause are not specified once each

NEXT VALUE expression

A query for a named derived table derived from a set operation that includes only UNION ALL, which directly includes one of the following:

GROUP BY clause, HAVING clause, or a set function

Window function

WHERE clause or subquery (however, only a subquery, a set operation operator, or an INSERT statement query)

Function call or system definition scalar function

Component specification

WRITE specification

GET_JAVA_STORED_ROUTINE_SOURCE specification

Sort specification with items not in the selection expression

Subquery for a named derived table derived from a set operation specified in the FROM clause

Subquery that specifies a derived table

Subquery specified in a value expression other than a column specification in the GROUP BY clause

The data type of an SQL variable specified in a selection expression or an SQL parameter is one of the following:
BLOB type
BINARY type 32,001 bytes or larger
Abstract data type
BOOLEAN type

The query specification specified for the table-joining of named derived tables derived by a set operation consisting solely of UNION ALL specifies one of the following:

A named derived table in a table reference other than at the leftmost outer table for an outer join

The FROM clause specifying a named derived table, which specifies a comma join (that is, specifies a different table reference than the joined table for which a derived table is specified)

A subquery or a derived table

A query specification contained either in a subquery or in the operation term for a set operation

A set operation term that derives named derived tables and contains one of the following:
Table join
GROUP BY clause, HAVING clause, or a set function
SELECT DISTINCT
A value expression in a selection expression other than a column specification
A query that creates an inner derived table
A query specifying a derived table

A named derived table derived by specifying a set operation (in addition to a named derived table)

One of the following, in the table reference to a joined table specifying a named derived table:
A named derived table derived by specifying the joining of tables
A named derived table derived by specifying a GROUP BY clause, a HAVING clause, or a set function
A named derived table derived by specifying SELECT DISTINCT
A named derived table derived by specifying a value expression other than a column specification in a selection expression
A named derived table derived by specifying a query that creates an inner derived table
A named derived table derived by specifying a subquery

The total number of tables obtained by the following expression is greater than 65:
Total number of tables = a + b c + d
a: Total number of tables from which named derived tables are derived
b: Number of set operations from which named derived tables are derived + 1
c: Total number of tables specified on the right side of an outer join
d: If a query other than a query for which a named derived table is specified is also specified, the total number of tables specified in the query

S: Ignores this SQL statement.

P: Correct the SQL statement or delete the viewed table, and then re-execute.

KFPA11672-E A

Each column of distinct view can be specified only once in "SELECT" clause in view definition, or in "WITH" query

One or more columns comprising the viewed table were not specified once each in the view definition or SELECT clause in the derived query expression in the WITH clause for a viewed table defined by specifying duplication elimination (DISTINCT).

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11673-E A

Duplicate "aa....aa" in "bb....bb" statement

"aa....aa" was specified more than once in "bb....bb".

aa....aa: Item specified two or more times

{CLUSTER KEY|PRIMARY KEY|PCTFREE|SUPPRESS

|LOCK ROW/PAGE|WITHOUT ROLLBACK|UNBALANCED SPLIT

|EMPTY|EXCEPT VALUES|INDEXLOCK|ISOLATION LEVEL

|OPTIMIZE LEVEL|ADD OPTIMIZE LEVEL|SUBSTR LENGTH

|OPTIONS SCHEMA|OPTIONS TABLE

|OPTIONS COLLATING_SEQUENCE|OPTIONS TRAILING_SPACE

|OPTIONS NULLABLE|OPTIONS USING_BES|OPTIONS_USER

|OPTIONS PASSWD|SEGMENT REUSE|INSERT ONLY|NOT NULL

|CONNECT|PASSWORD|AS DATA TYPE|START WITH

|INCREMENT BY|MAXVALUE|MINVALUE|CYCLE|LOG INTERVAL

|FOR RESERVED}

bb....bb: Specified statement

{CREATE TABLE|CREATE INDEX|CREATE PROCEDURE

|CREATE FUNCTION|PROCEDURE definition in CREATE TYPE

|FUNCTION definition in CREATE TYPE|ALTER TABLE

|ALTER PROCEDURE|ALTER ROUTINE|CREATE TRIGGER

|ALTER TRIGGER|CREATE CONNECTION SECURITY

|DROP CONNECTION SECURITY|CREATE SEQUENCE}

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11674-E A

Unable to specify more than 16 columns for "aa....aa"

The number of columns in aa....aa exceeds the maximum (16).

aa....aa: {CLUSTER KEY|HASH KEY|PRIMARY KEY|FOREIGN KEY}

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11676-E A

"aa....aa" cannot be specified in ALTER TABLE statement

"aa....aa" cannot be specified in the ALTER TABLE statement for a column to be added or modified.

aa....aa: Nature of error:

{ CLUSTER KEY |NOT NULL }

Note that the NOT NULL constraint can be specified in the ADD clause.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11677-E A

Unable to purge aa....aa

The PURGE TABLE statement cannot be executed on a viewed table, falsification prevented table, or memory database allocation table.

aa....aa: {viewed table|INSERT ONLY table|memory table}

S: Ignores this SQL statement.

P: In the case of a viewed table, use the DELETE statement to delete the rows. In the case of a falsification prevented table, use the DELETE statement to delete only the rows that have exceeded the deletion prevented duration. In the case of a memory database allocation table, execute the PURGE TABLE statement after releasing the memory database allocation.

KFPA11678-E A

No Column-definition in "CREATE TABLE" statement

There is no column definition in the CREATE TABLE statement.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11680-E A

Unable to aa....aa LIST due to executing same user bb....bb

A user having the same authorization identifier bb....bb is accessing the list; therefore, operation aa....aa cannot be performed on the list.

aa....aa: List processing:

{ assign |select |drop }

bb....bb: Authorization identifier

S: Ignores this SQL statement.

P: Re-execute the SQL statement after the active transaction has terminated.

KFPA11681-E A

Unable to specify reserved column on aa....aa column

A reserved column cannot be specified on configuration column aa....aa.

aa....aa: Type of configuration column

{cluster key|primary key|foreign key|divided key|index}

S: Ignores this SQL statement.

P: Correct the SQL statement so that a reserved column is not specified on aa....aa, and then retry the operation.

KFPA11682-E A

Unable to change definition reserved column "aa....aa"

The data type of the reserved column cannot be changed.

aa....aa: Name of reserved column

S: Ignores this SQL statement.

P: Correcting the SQL statement so that the data type of the reserved column indicated in aa....aa is not changed, and then retry the operation.

KFPA11683-E A

Unable to specify unsupported data type for reserved column

An unsupported data type was specified for the reserved column. In a reserved column, you must specify a data type whose default character set is CHAR.

S: Ignores this SQL statement.

P: Correct the data type of the reserved column so that the default character set is CHAR, and then retry the operation.

KFPA11684-E A

Unable to add column for table with reserved column

Unable to add a column to a table with a reserved column.

S: Ignores this SQL statement.

P: Add the column by excising it from a reserved column, or delete the reserved column, and then add the column.

KFPA11685-E A

Unable to create table with only reserved column

You cannot define a table with only reserved columns.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA11690-E A

Unable to drop referenced table

A referenced table with a referential constraint cannot be dropped.

S: Ignores this SQL statement.

P: Drop all referencing tables, and then re-execute.

KFPA11692-E A

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

This SQL statement or operation command cannot be executed because another user is using cc....cc aa....aa."bb....bb".

aa....aa: Authorization identifier

bb....bb: Table identifier, or sequence generator identifier

cc....cc:

table: Table

sequence: Sequence generator

S: Ignores this SQL statement.

P: Re-execute the SQL statement after the other user has finished using the cc....cc.

Action

Check the SQL being executed for an error. If there is no error, execute the SQL statement or operation command after the other user finishes using the cc....cc. The command pdls -d lck -a can be used to determine whether the cc....cc is being used by another user.

KFPA11693-E A

Unable to define same columns construction for primary key and cluster key

A cluster key clause and a primary key clause with the same column structure cannot be specified simultaneously.

S: Ignores this SQL statement.

P: To define a cluster key and a primary key with the same column structure, define them in a PRIMARY CLUSTER KEY clause.

KFPA11694-E A

Unable to change cluster key because of invalid key attribute

One of the following errors was detected in attempting to change attributes of a cluster key:

An attempt was made to change to UNIQUE a cluster key for which UNIQUE was already specified, or an attempt was made to change from UNIQUE a cluster key for which UNIQUE was not specified.

An attempt was made to change a flexible hash partitioning table or a matrix partitioning table using flexible hash partitioning to UNIQUE.

S: Ignores this SQL statement.

P: Delete this SQL statement.

KFPA11695-E A

Unable to specify "WITH DEFAULT" for reserved column

WITH DEFAULT cannot be specified for a reserved column.

S: Ignores this SQL statement.

P: If you are defining a table or adding a column, re-execute the SQL statement after correcting it so that it does not specify WITH DEFAULT.

If you are changing a table definition change, delete this SQL statement.

KFPA11696-E A

Unable to specify "aa....aa" column,reason=bb....bb

The column indicated in aa....aa cannot be specified due to the reason indicated in bb....bb.

aa....aa: Column name

bb....bb: Cause of error

invalid data length:

The column cannot be excised because the data length of the column indicated in aa....aa is greater than the data length of the reserved column.

duplicate column name:

The same name as the reserved column cannot be specified because the data length of the column indicated in aa....aa is not equal to the data length of the reserved column.

not reserved column:

The column cannot be excised because the column indicated in aa....aa is not a reserved column.

S: Ignores this SQL statement.

P: Take corrective action as described in the following table:

Cause of error (bb....bb) | Action
invalid data length | Correct the SQL statement so that the data length of the column indicated in aa....aa does not exceed the data length of the reserved column, and then re-execute it.
duplicate column name | Correct the SQL statement after changing the column indicated in aa....aa to a name different from the reserved column, and then re-execute it.
not reserved column | Correct the SQL statement after changing it so that a reserved column is specified, and then re-execute it.

KFPA11697-E A

Unable to specify "WITH DEFAULT" except for "NOT NULL"

When defining a table or modifying a table definition, "WITH DEFAULT" cannot be specified for a column without the "NOT NULL" value restriction.

S: Ignores this SQL statement.

P: Specify "NOT NULL" and re-execute.

KFPA11698-E A

Unable to specify "bb....bb" for "aa....aa" column

The item "bb....bb" cannot be specified for a column that comprises "aa....aa".

aa....aa: abstract data (abstract data type)

bb....bb: NOT NULL

S: Ignores this SQL statement.

P: Delete this SQL statement.

KFPA11699-E A

Unable to specify "WITH DEFAULT" because of column already "WITH DEFAULT"

WITH DEFAULT has already been specified for the specified column.

S: Ignores this SQL statement.

P: Delete this SQL statement.

KFPA11702-E A

Unable to create unique index, because unique key not include all partitioning key columns

An index with the UNIQUE specification could not be defined for one of the following reasons:

In a table that is row-partitioned among multiple back-end servers, not all the columns specified as table-partitioning keys are included in the columns comprising the index.

In a rebalancing table with FIX hash partitioning at a single server or at only one back-end server, not all the columns specified as table-partitioning keys are included in the columns comprising the index.

S: Ignores this SQL statement.

P: Correct so that all columns specified as table-partitioning keys are included in the columns comprising the index (in any sequence), and re-execute the SQL statement.

KFPA11703-E A

Unable to partition table more than 4097 servers

A table cannot be defined to be partitioned into more than 4,097 back-end servers.

S: Ignores this SQL statement.

P: Set the number of back-end servers for partitioning to no more than 4,096 and re-execute.

KFPA11704-E A

Unable to specify aa....aa for bb....bb

aa....aa cannot be specified for bb....bb.

When bb....bb is "FIX" table:

Cannot specify a data type BLOB statement or BINARY statement for a FIX attribute table.

When bb....bb is attribute name:

A character set cannot be specified for an attribute name in a type definition.

aa....aa: {"BLOB"|"BINARY"|long data|character set}

bb....bb: {"FIX" table|attribute name}

S: Ignores this SQL statement.

P:

When bb....bb is "FIX" table:

Do not specify the BLOB or BINARY data type statement, or delete the FIX attribute specification, and then retry the operation.

When bb....bb is attribute name:

Revise the specification of the data type, and then retry the operation.

KFPA11705-E A

Invalid option "aa....aa" number cc....cc in "bb....bb" statement

The value of option "aa....aa" in statement "bb....bb" exceeds the permitted maximum.

aa....aa: Name of erroneous option:

{ PCTFREE |SEGMENT REUSE }

bb....bb: Name of erroneous SQL statement:

{ CREATE TABLE |CREATE INDEX |ALTER TABLE }

cc....cc: Erroneous value

S: Ignores this SQL statement.

P: Change the option specification and re-execute.

KFPA11706-E A

Number of defined indexes on table aa....aa."bb....bb" exceeds 255

The number of indexes specified for a table exceeded the maximum (255).

aa....aa: Authorization identifier

bb....bb: Table identifier

S: Ignores this SQL statement.

P: If this SQL statement needs to be executed, delete the index. If this SQL statement need not be executed, delete it.

KFPA11707-E A

Invalid "LOB" RDAREA for table partitions

One of the items listed below is not consistent with the table storage RDAREA specification, either because it has the same name as the table storage RDAREA name, or ALTER TABLE ADD RDAREA was used to specify a table storage RDAREA that is already in use by the target table.

LOB column storage RDAREA

LOB attribute storage RDAREA

S: Ignores this SQL statement.

P: If the same name as the table storage RDAREA was specified, make sure that the LOB column storage RDAREA or LOB attribute storage RDAREA is in the same location as the table storage RDAREA, and then retry the operation.

KFPA11708-E A

Not specified "LOB" RDAREA "aa....aa" in same server as table RDAREA

The specified LOB RDAREA is not on the same server as the table storage RDAREA.

aa....aa: LOB RDAREA name

S: Ignores this SQL statement.

P: Specify a LOB RDAREA on the same server as the corresponding table storage RDAREA.

KFPA11709-E A

Specified RDAREA "aa....aa" already used

The specified LOB RDAREA is already being used for another table.

aa....aa: LOB RDAREA name

S: Ignores this SQL statement.

P: Specify a LOB RDAREA that is not being used for another table.

KFPA11710-E A

Specific name for aa....aa."bb....bb" conflict with another routine

The specific name for the routine aa....aa."bb....bb" is in conflict with another routine.

aa....aa: Authorization identifier

bb....bb: Routine identifier

S: Ignores this SQL statement.

P: Correct the routine identifier and re-execute.

KFPA11711-E A

Invalid update in execution of query with cursor

One of the following errors was detected:

An attempt was made to update, delete, or insert data in a table being retrieved using a cursor that was declared or assigned without specifying the FOR UPDATE clause.

An attempt was made to delete or insert data in a table being retrieved using a cursor that was declared or assigned with FOR UPDATE OF specified.

An attempt was made to update a column for which FOR UPDATE OF is not specified in a table being retrieved using a cursor that was declared or assigned with FOR UPDATE OF specified.

An attempt was made to update or delete data using a cursor that was declared or assigned with FOR READ ONLY specified.

S: Ignores this SQL statement.

P: Correct the UAP and re-execute.

KFPA11712-E A

Duplicate attribute name "aa....aa"

The name of an attribute comprising a data type must be unique for all the abstract data types that are in an inheritance relationship.

aa....aa: Attribute name that is duplicated

S: Ignores this SQL statement.

P: Correct the attribute name so that it is unique and re-execute.

KFPA11713-E A

Unable to aa....aa work file due to insufficient HiRDB file system area bb....bb

During internal processing to create a work table file, a space shortage occurred in the HiRDB file system area specified in pdwork of the server definition.

aa....aa: Type of operation on the work table HiRDB file:

create: Creation of work table HiRDB file

expand: Expansion of work table HiRDB file

bb....bb: Name of the HiRDB file system area resulting in the space shortage

If the path name of the HiRDB file system area exceeds 117 characters, the last 117 characters of the HiRDB file system area path name are output.

S: Invalidates this transaction.

P: Contact the HiRDB administrator.

Action

When creating a work table HiRDB file (create):

Add a HiRDB file system area using the pdwork operand of the server definition. Or, increase the size of the HiRDB file system area specified in the pdwork operand and start the server.

When expanding a work table HiRDB file (expand):

Increase the size of the HiRDB file system area specified in the server definition pdwork operand and start the server.

KFPA11714-E A

Number of "aa....aa" exceeds bb....bb

The value of "aa....aa" exceeds the system maximum value bb....bb.

aa....aa: Applicable item

{ ADT LEVEL (number of generations of abstract data types) }

bb....bb: System maximum value

{ 30000 }

S: Ignores this SQL statement.

P: This problem cannot be resolved due to a system limitation. This SQL statement cannot be executed. If the problem is with the SQL statement, correct the error and re-execute.

KFPA11716-E A

Unable to change definition of column specified in aa....aa operand in view definition

The data type or definition length of a column in a base table specified in one of the following items in the view definition cannot be changed:

Concatenation operation

Scalar function

CASE function

CAST specification

Function invocation

If one of the following facilities is specified in a view definition statement, the data type and definition length of columns used by the view definition cannot be changed.

Row subquery

Scalar subquery that specified a set operation

Table subquery that specified a set operation

A table subquery with two or more results columns, other than with the EXISTS predicate

Scalar subquery of a selection expression

Scalar subquery in the left side row value constructor of a comparison predicate, IN predicate, or quantified predicate

Scalar subquery in a BETWEEN predicate, LIKE predicate, XLIKE predicate, and SIMILAR predicate

aa....aa: Nature of error:

{ concatenation |scalar function |CASE expression
|function invocation |CAST specification subquery }

S: Ignores this SQL statement.

P: Correct the SQL statement or delete the viewed table, then re-execute.

KFPA11717-E A

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

The name of the table, column, or index cannot be changed for the following reason:

A viewed table has been created based on the table to be changed.

A trigger is defined in the table to be changed.

A check constraint is defined in the table to be changed.

The column to be changed is used in the search condition of a check constraint.

A referential constraint (foreign key) is defined in the table to be changed.

The column to be changed is comprised of a foreign key.

The table to be changed is a referenced table of a referential constraint.

The column to be changed is comprised of the primary key of a referenced table of a referential constraint.

The table to be changed, or the table on which the index to be changed is defined, is specified in a stored procedure or trigger SQL statement.

An attempt was made to change a column name of a viewed table.

An attempt was made to change the column name specified by the trigger execution event.

An attempt was made to change the name of the column referred to using the old or new values correlation name in the search conditions of the trigger operation.

An attempt was made to change the name of the column referred to using the old or new values correlation name in the trigger SQL statement.

An attempt was made to change the table name or column name of the falsification prevented table.

aa....aa: Item to be changed:

COLUMN: Column name

TABLE: Table name

INDEX: Index name

bb....bb: The table, viewed table, or index

cc....cc: Error:

used on view: View is defined

used on trigger: Trigger is defined.

check constraint: Check constraint is defined.

check column: Column name used in a check constraint search condition.

referential constraint: Referential constraint (foreign key) is defined.

foreign key column: Name of a column comprised of a foreign key.

referenced table: Referenced table of a referential constraint.

referenced primary key: Column comprised of the primary key of a referenced table of a referential constraint.

used on stored procedure: Used by a stored procedure or a trigger SQL statement.

view's column: Column name to be changed is a column name in a viewed table

trigger column: Column name to be changed was defined in the trigger event.

triggered action condition: Column name to be changed referred to an old or new correlation name in the search condition of a trigger operation.

triggered SQL statement: Column name to be changed referred to an old or new correlation name in the trigger SQL statement.

INSERT ONLY table: Table to be changed is a falsification prevented table.

S: Ignores this SQL statement.

P:

cc....cc is used on stored procedure or used on view:

Delete the viewed table, stored procedure, or trigger that uses the table to be changed or on which the index to be changed is defined, and then re-execute the ALTER TABLE or ALTER INDEX statement. Then, re-create the viewed table, stored procedure, or trigger.

cc....cc is view's column

Execute DROP VIEW, then execute CREATE VIEW using a different column name, then change the column name.

cc....cc is used on trigger:

Drop the trigger defined for the table to be changed, and re-execute ALTER TABLE. Then re-create the trigger.

cc....cc is check constraint:

Revise the table name, and re-execute.

cc....cc is check column:

Revise the column name, and re-execute.

cc....cc is referential constraint:

Revise the table name, and re-execute.

cc....cc is foreign key column:

Revise the column name, and re-execute.

cc....cc is referenced table:

Revise the table name, and re-execute.

cc....cc is referenced primary key:

Revise the column name, and re-execute.

cc....cc is trigger column, triggered action condition, or triggered SQL statement:

Delete the trigger using the column that attempted to change the column name and re-execute ALTER TABLE. Then re-create the trigger.

cc....cc is an INSERT ONLY table:

The falsification prevented table cannot change the table name or alias. Review the table name and re-execute.

KFPA11718-E A

Invalid use of column suppress specification

One of the following errors was detected in the definition of column data restriction:

Specified for a FIX table

Specified for a column whose data type is not CHAR, MCHAR, or NCHAR

The column suppress specification is specified for a repetition column.

S: Ignores this SQL statement and terminates the transaction.

P: Correct the SQL statement and re-execute.

KFPA11720-E L+A

Error occurred in HiRDB/client, inf1=aa....aa, inf2=bbbb

Internal conflict occurred in the client library of the HiRDB system.
The error may be due to either of the following factors:

The host specified in the pdstart command and the host specified in PDHOST on one hand and the client-side system on the other hand are in a condition that prevents them from communicating with each other on the network

The communications load is high

If an X/Open-compliant UAP is executed under the OLTP environment, a transaction was not started by using the tx_begin function.

aa....aa: Name of the source file in which the error was detected

bbbb: Location of the error (line number)

S: Terminates processing.

Action

Make a backup of the client error log file where the error was output and contact the customer support center.

If this message is output, the connection with the HiRDB server was disrupted. To execute the UAP, re-execute it beginning with the CONNECT statement.

KFPA11722-E A

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

SQL processing was interrupted by a communication error.

aa....aa: Nature of error:

INVALID DATA: Invalid data was received from the server.

SERVER PROCESS DOWN: Server process was shut down.

S: Terminates processing and releases connection with the server.

P: Contact the HiRDB administrator.

Action

Contact the customer support center, and be prepared to provide the contents of the client error log files (pderr1.trc, pderr2.trc). If in XDS was output, also provide the XDS logs (pdxdslog1, pdxdslog2) to the customer support center.

If this message is output, the connection with the HiRDB server was disrupted. To execute the UAP, re-execute it beginning with the CONNECT statement.

SERVER PROCESS DOWN:

Check the cause of the server process shutdown, correct the error, and then re-execute the UAP.

If the high-speed connection facility (PDSERVICEPORT in the client environment definition) is used, the value specified for PDSERVICEPORT might be invalid. Check if message KFPS00860-W was output during HiRDB startup, or if the value of PDSERVICEPORT is the same as the value of the scheduler port number (the -s option of the pd_service_port, pd_scd_port, or pdunit operand in the system definition). If applicable, correct the value of the PDSERVICEPORT specification, and then re-execute the UAP.

KFPA11723-E L+A

Communication error occurred [ in XDS], reason=aa....aa

A communication error occurred between the HiRDB system or the HiRDB server. Or, the HiRDB system or HiRDB server is down.
If an error occurred in XDS, in XDS is displayed in the message text.

aa....aa: Character string indicating the nature of the error:

CLIENT MEMORY:

A memory shortage occurred in the client library.

FES(SDS) CLOSE:

The server (SDS for HiRDB/Single Server, FES for HiRDB/Parallel Server) is engaged in termination processing.

FES(SDS) NOT UP:

The server (SDS for HiRDB/Single Server, FES for HiRDB/Parallel Server) is not running, is undergoing startup processing, or is running as a log application site.

HiRDB BUSY:

Connection cannot be established because HiRDB (server) is BUSY.

HiRDB DATA ERROR:

Communication data from the HiRDB system or HiRDB server is invalid.

HiRDB INITIALIZE:

The HiRDB system or HiRDB server is now initializing.

HiRDB NOT UP:

The HiRDB system or the HiRDB server is not running, or the Listen queue on the HiRDB server side is insufficient.

HiRDB SYSTEM ERROR:

A system error was detected in the HiRDB system or the HiRDB server.

HiRDB MEMORY:

Memory on the HiRDB system or HiRDB server is low.

INIT ERROR:

An error occurred in the initialization process of the communication.

INVALID SERVER TYPE:

The HiRDB (server) server type differs from the PDSRVTYPE (client environment definition).

NETWORK:

A network failure occurred, or the HiRDB server abnormally terminated and disconnected itself from the network.

INSUFFICIENT NETWORK PORT:

An attempt to allocate a communication port number failed.

S: Terminates processing.

O:

Check the error log file (created in the current directory or under the directory specified in the PDCLTPATH operand) that the HiRDB client outputs for the cause of the failure, eliminate the cause, and then retry the operation. If this message is output, the connection with the HiRDB server was disrupted. You might have to re-execute the command beginning with the CONNECT statement.

If this message (aa....aa is HiRDB NOT UP) continues to be output when the UAP starts, even though the connection target HiRDB has started, review the value specified for the connection destination. The information below describes how to specify the connection destination.

When using an XDS client:

Embedded application:
See Specifying a connection destination under Connection from an XDS Client in the HiRDB Version 9 UAP Development Guide.

Windows-edition ODBC 3.5 driver-compliant application:
See ODBC-compliant application programs under Connection from an XDS Client in the HiRDB Version 9 UAP Development Guide.

Linux-edition ODBC 3.5 driver-compliant application:
See ODBC-compliant application programs under Connection from an XDS Client in the HiRDB Version 9 UAP Development Guide.

Type 4 JDBC driver-compliant application:
See Connection to XDS using the getConnection method under Connection from an XDS Client in the HiRDB Version 9 UAP Development Guide.

When using a client of the server providing the primary facilities:

Embedded application:
See Environment variables and connection types for HiRDB servers in the HiRDB Version 9 UAP Development Guide.

Windows-edition ODBC 2.0 driver-compliant application:
See Installing the ODBC 2.0 driver in the HiRDB Version 9 UAP Development Guide.

Windows-edition ODBC 3.5 driver-compliant application:
See Installing the ODBC 3.5 driver and setting the environment variables in the HiRDB Version 9 UAP Development Guide.

Linux-edition ODBC 3.5 driver-compliant application:
See Installing the ODBC 3.5 driver and setting the environment variables in the HiRDB Version 9 UAP Development Guide.

Type 2 JDBC driver-compliant application:
See Database connection using the DriverManager in the HiRDB Version 9 UAP Development Guide.

Type 4 JDBC driver-compliant application:
See Database connection using the DriverManager class in the HiRDB Version 9 UAP Development Guide.

ADO .NET 1.1-compliant application:
See HiRDBConnection in the HiRDB Version 9 UAP Development Guide.

ADO .NET 2.0-compliant application:
See HiRDBConnection in the HiRDB Version 9 UAP Development Guide.

OLE DB-compliant application:
See Connection properties in the HiRDB Version 9 UAP Development Guide.

SQLJ-compliant application:
See Description of connection to and disconnection from a HiRDB server in the HiRDB Version 9 UAP Development Guide.

If the values in the client environment definition are correct and message KFPZ02444-E (func=connect and the value indicated for errno is either ETIMEDOUT or ECONNREFUSED) is output to the error log file, it is possible that there are too many connection requests for the HiRDB server. Wait for a while, and then retry the operation. For details about the actions to take, see Listen queue specified values in the HiRDB Version 9 Installation and Design Guide.

If the connection destination HiRDB is using Real Time SAN Replication with the log-only synchronous method and aa....aa is FES(SDS) NOT UP, it is possible that the HiRDB is running as a log application site. If this is the case, ask the HiRDB administrator about the condition. If necessary, change the connection destination to an application site HiRDB, and then re-execute the command.

If in XDS was output, report the nature of the error to the HiRDB administrator, correct the error, and then retry the operation.

P:

When aa....aa is HiRDB BUSY:

Wait for a while, and then retry the operation. If the same message is issued again, contact the HiRDB administrator.

When aa....aa is something other than HiRDB BUSY:

Report the nature of the error to the HiRDB administrator, correct the error, and then retry the operation.

Action

When using an XDS client or a client of the server providing the primary facilities:

If aa....aa is INIT ERROR or NETWORK and message KFPZ02444-E (func=bind or connect and the value indicated for errno is EADDRNOTAVAIL, EADDRINUSE, or ENOBUFS) is output to the error log file, there might not be enough ports automatically allocated by the OS on the client side. For details about corrective actions, see the administrator actions for message KFPS00349-E.

If there is an attempt to connect to multiple FES groups and all connections fail, in the following cases the contents of the last error that occurred are returned:
You are using an XDS client, and multiple FES groups are specified in PDFESGRP in the XDS environment definition.
You are using a client of the server providing the primary facilities, and multiple FES groups are specified in PDFESGRP in the client environment definition.
Use the error log files and the troubleshooting information collected by the server to determine the cause of the error that occurred in the connection to each FES group.
If the number of users connected to the HiRDB server exceeds the maximum number of concurrent connections, a connection error is returned but the troubleshooting information collected by the server cannot be used to determine whether the maximum number of concurrent connections has been exceeded. Instead, use the command pdls -d act to check the number of connected users.
For details about corrective actions when maximum number of concurrent connections has been exceeded, see the administrator actions for message KFPA11932-E.

When using an XDS client:

If aa....aa is INSUFFICIENT NETWORK PORT, there might not be enough ports automatically allocated by the OS on the connection destination server side. For details about corrective actions, see the administrator actions for message KFPS00349-E.

If in XDS was output, determine the cause of the error from the error log files (pderr1.trc, pderr2.trc) and XDS log (pdxdslog1, pdxdslog2), eliminate the cause of the error, and then retry the operation.
To specify the values for the connection destinations, revise the XDS environment definition. For details about the XDS environment definition, see XDS environment definition in the HiRDB Version 9 Memory Database Installation and Operation Guide.

KFPA11724-E L+A

Environment definition error, variable=aa....aa, reason=bb....bb, identifier="cc....cc"

An environment variable is invalid.

aa....aa: Name of invalid environment variable

If the environment variable begins with PDPLUGIN, either the length of the plug-in environment variable is excessive or there are too many environment variables to be stored in the buffer.

bb....bb: Reason for the error:

INVALID CHAR: An invalid character was detected.

NET ENVIRONMENT: Specification does not match the network environment.

NO VALUE: A specification value is missing.

OUT OF RANGE: Specified value is outside the permitted range.

NOT ENVIRONMENT GROUP: The environment variable group specified in the registry does not exist.

INVALID IDENTIFIER: The identifier is invalid.

cc....cc:

Invalid identifier (first 30 bytes only if the identifier is longer than 30 bytes)

This is displayed if the cause is INVALID IDENTIFIER; it is not displayed in all other cases.

S: Terminates processing.

P: Correct the specification of the environment variable and re-execute.

KFPA11725-E L+A

Other SQL executing cannot execute next SQL

The next SQL statement is executed before the execution of the previous SQL statement was completed. Or, for a multi-threaded UAP, the same connection handle is being used by multiple threads, or the SQL statement is executing without a connection handle.

S: Terminates processing.

O: Wait for the processing of the first SQL to terminate, and then re-execute the next SQL.

KFPA11727-E L+A

Unable to execute SQL, for termination process HiRDB

An SQL statement cannot be executed, because the HiRDB system or server is engaged in termination processing.

S: Terminates processing.

P: Check that the HiRDB system or server is active, and re-execute the UAP.

KFPA11728-E L+A

Error occurred in HiRDB, reason=aa....aa

The HiRDB system or server made an error control return.

aa....aa: Character string indicating the reason:

FALSE:

Locking of a resource failed.

NO FES(SDS):

Either an available server (single server (SDS) or front-end server (FES)) does not exist or an attempt was made to connect to a log application site.

SHUTDOWN:

The HiRDB system is engaged in shutdown processing.

S: Terminates processing.

P: If the reason code is FALSE

Retry the command.

If the reason code is either NO FES(SDS) or SHUTDOWN

Confirm that the HiRDB has started, and then re-execute the UAP. If this message is output, the connection with the HiRDB server was disrupted. It may be necessary to re-execute the UAP beginning with the CONNECT statement.

If the HiRDB is running in NO FES(SDS) as a log application site, specify a transaction execution site as a connection destination, and re-execute the UAP.

KFPA11729-E A

Insufficient memory on aa....aa, size=bbbbb

There is not enough memory to execute an SQL statement.

aa....aa: Character string indicating the type of area that was to be allocated:

DYNAMIC_SHMPOOL: Dynamic shared memory

PROCESS: Process private area

STATIC_SHMPOOL: Static shared memory

bbbbb: Size of the area that was to be allocated (in bytes)

S: Terminates processing.

Action

Allocate the memory required for execution and re-execute.

KFPA11731-E L+A

System call error, func=aa....aa, errno=bbb

System call aa....aa resulted in an error.

aa....aa: Name of the system call resulting in the error

bbb: Error number returned from the system call

S: Terminates processing.

P: Check the meaning of the error indicator value, eliminate the cause of the error by referencing errno.h and the applicable OS manual, then re-execute.

KFPA11732-E A

Time over, no response from HiRDB[ in XDS][,WAITTIME=aaaaa]

Because the HiRDB server was shut down or HiRDB server processing was not completed within the timer monitoring interval, a query cannot be sent to the HiRDB server.
The [,WAITTIME=aaaaa] message can be output when the Type 4 JDBC driver is being used.
If an error occurred in XDS, in XDS is displayed in the message text.

aaaaa: The client's maximum wait time

The timer monitoring interval that is output is as follows:

If there is a connection to the HiRDB server:
The value of PDCONNECTWAITTIME in the client environment definition

If the CALL COMMAND statement was executed:
The value of PDCALCMDWAITTIME in the client environment definition

Other than above
The value of PDCWAITTIME in the client environment definition, or the value of Statement#setQueryTimeout

S: Terminates processing.

O:

When using a client of the server providing the primary facilities:

This error can occur if an invalid IP address (an address that cannot be accessed from the HiRDB server) or a host name is specified in PDCLTRCVADDR. From the host containing an FES (SDS) for the HiRDB server, check whether the IP address specified in the PDCLTRCVADDR variable can be transmitted using the ping command. This error can also occur if the address associated with the host name specified in PDCLTRCVADDR is different for the host containing the HiRDB server and the host containing the UAP. Make sure that the address associated with the host name assigned to PDCLTRCVADDR is correct.

When using an XDS client or a client of the server providing the primary facilities:

If this error occurs while attempting a connection and the automatic reconnect facility is used, check the KFPA11723-E message, which is output to the error log file, to find and eliminate the cause of the communication error with the HiRDB server, and then retry the operation.

P: If the HiRDB server is stopped, make sure that the HiRDB server has started, and then retry the operation.

If the HiRDB server is not stopped, increase the timer monitoring interval and re-execute the UAP. The value used for the timer monitoring interval is as follows:

If there is a connection to the HiRDB server

The value of PDCONNECTWAITTIME in the client environment definition

If the CALL COMMAND statement was executed:

The value of PDCALCMDWAITTIME in the client environment definition

Other than above

The value of PDCWAITTIME in the client environment definition, or the value of Statement#setQueryTimeout

If this message is output, the connection with the HiRDB server was disrupted. You might have to re-execute the UAP beginning with the CONNECT statement.

Action

If in XDS was output, revise the values specified in the XDS environment definition. For details about the XDS environment definition, see XDS environment definition in the HiRDB Version 9 Memory Database Installation and Operation Guide.

KFPA11733-E L+A

Error occurred in HiRDB, inf1=aa....aa, inf2=bbbb

Invalid data was received from the HiRDB server.

aa....aa: Name of source file in which the error was detected

bbbb: Location where the error was detected (line number)

S: Terminates processing.

Action

When the client error log file is output, back up the client error log file, eliminate the cause of the error on the server, and then contact the customer support center.

KFPA11734-E L

Unable to get IPaddr of FES(SDS) host, hostname=aa....aa

The IP address of the host name where the HiRDB/Single Server (SDS) or the HiRDB/Parallel Server (FES) is located cannot be obtained.

aa....aa: Name of the host whose IP address was to be obtained

S: Terminates processing.

P: Refer to the contents of the hosts file at the host where the UAP was executed, add the definition of the host name displayed in the message, and then re-execute the UAP.

KFPA11735-E L

aa....aa canceled

SQL execution was canceled due to a cancellation request received from the UAP, and the transaction was invalidated.

aa....aa:

FES(SDS): When using a client of the server providing the primary facilities

Transaction: When using an XDS client

S: Terminates processing.

O: Because the requested processing has been canceled, re-execute the UAP if necessary.

P: Modify the program to re-execute the SQL code for the transaction that was invalidated.

KFPA11736-E A

aa....aa bb....bb."cc....cc" not convert to 64-bit

The specified aa....aa bb....bb."cc....cc" is not compatible with the 64-bit mode.

aa....aa: Type:

View: Viewed table

Routine: Routine

Trigger: Trigger

bb....bb: Authorization identifier

cc....cc: Table identifier, routine identifier, or trigger identifier

S: Ignores this SQL statement.

Action

Use the pdobjconv command to make the viewed table or the routine 64-bit mode compatible. Then, re-execute the UAP statement.

KFPA11737-E A

RDAREA for specified aa....aa already removed, server=bb....bb

The RDAREA at server bb....bb for storage of aa....aa, as specified by the SQL statement, has already been deleted by the database structure modification utility (pdmod).

aa....aa: LIST (list)

bb....bb: Server name

S: Ignores this SQL statement.

P: First delete the list specified by the SQL statement, then re-create the list and re-execute.

KFPA11738-E A

No RDAREA for aa....aa, server=bb....bb

The SQL statement cannot be executed because no RDAREA for aa....aa exists at server bb....bb.
Or, the SQL statement cannot be executed because all RDAREAs for aa....aa at server bb....bb are on shutdown status.

aa....aa: LIST (list)

bb....bb: Server name

S: Ignores this SQL statement.

P:

Use the database structure modification utility (pdmod) to allocate an RDAREA, and then re-execute the SQL statement.

Or, release the RDAREAs from shutdown status by removing the error cause, and then re-execute the SQL statement.

If this message is output, the connection with the HiRDB server was disrupted. It may be necessary to re-execute the UAP beginning with the CONNECT statement.

KFPA11740-E A

Unable to execute SQL for definition due to cc....cc aa....aa."bb....bb"

The routine aa....aa."bb....bb" is part of an SQL object that uses the resource to be deleted or changed. Therefore, the following definition SQL statements that invalidate SQL objects cannot be executed. Another possibility is that the following definition SQL statements could not be executed because the routine aa....aa."bb....bb" in the SQL object that uses the resource to be deleted or changed is being executed:
ALLOCATE MEMORY TABLE (set table to memory database allocation)
ALTER INDEX (change index definition)
ALTER PROCEDURE (change procedure)
ALTER ROUTINE (change routine)
ALTER TABLE (change the table definition)
ALTER TRIGGER (change trigger)
CREATE FUNCTION (define a function)
CREATE INDEX (define an index)
CREATE TABLE (define a table)
CREATE TRIGGER (define a trigger)
CREATE TYPE (define data type (subtype))
DROP DATA TYPE (delete data type)
DROP FUNCTION (delete function)
DROP INDEX (delete index)
DROP PROCEDURE (delete procedure)
DROP SCHEMA (delete schema)
DROP SEQUENCE (delete sequence generator)
DROP TABLE (delete table)
DROP TRIGGER (delete trigger)
DROP VIEW (delete view)
REVOKE access privilege (delete access privilege)

The viewed table aa....aa."bb....bb" that uses the resource to be deleted exists. Therefore, the following definition SQL statements cannot be executed:
DROP FUNCTION (delete function)
DROP DATA TYPE (delete data type)
DROP SCHEMA (delete schema)

The trigger aa....aa."bb....bb", used in the search conditions of a trigger operation, exists for the deleted function. Therefore, the following definition SQL statements cannot be executed:
DROP FUNCTION (delete function)
DROP SCHEMA (delete schema)

Among the resources invalidated by the definition SQL, there is a viewed table aa....aa."bb....bb" that uses a resource that has an abstract data type parameter or return value. Therefore, the following definition SQL statements cannot be executed:
CREATE FUNCTION (define function)
CREATE TYPE (define data type (subtype))
DROP DATA TYPE (delete data type)
DROP FUNCTION (delete function)

aa....aa: Authorization identifier

bb....bb: Routing identifier, table identifier, or trigger identifier

cc....cc: {ROUTINE|TABLE|TRIGGER}

S: Invalidates this transaction.

P:

cc....cc is ROUTINE

If you can delete the SQL object, specify WITH PROGRAM and re-execute. If a routine is being executed, terminate the routine before re-executing.

cc....cc is TABLE

Re-execute after deleting viewed table aa....aa."bb....bb".

cc....cc is TRIGGER

Delete trigger aa....aa."bb....bb" and then re-execute. Alternatively, if you can invalidate a trigger for the DROP FUNCTION, specify WITH PROGRAM and re-execute.

KFPA11741-E A

Unable to drop datatype due to used by aa....aa bb....bb."cc....cc"

The specified data type is used by bb....bb."cc....cc" of aa....aa. Therefore, it cannot be deleted.

aa....aa: Resource using the data type

{TABLE, INDEX, DATATYPE, INDEXTYPE}

bb....bb: Authorization identifier (owner of the resource being used)

cc....cc: Name of the resource being used

S: Ignores this SQL statement.

P: Check whether the definition of the resource being used can be deleted. If it can be deleted, delete the definition and re-execute this SQL statement.

KFPA11743-E A

Foreign key aa....aa."bb....bb" mismatch primary key code=cc(dd....dd)

Foreign key aa....aa."bb....bb" does not match the primary key that the foreign key references.

aa....aa: Authorization identifier

bb....bb: Constraint name

cc: Reason code

dd....dd: Additional error information

S: Ignores this SQL statement.

P: The reason codes and the additional error information are listed below. Eliminate the cause of the error, and re-execute the SQL statement.

Reason code (cc) | Additional error information (dd....dd) | Explanation
01 | number of columns | The number of columns that comprise the foreign key and the primary key are different.
02 | data types | The data types of the columns that correspond to the foreign key and the primary key are different.
03 | data length | The data lengths of the columns that correspond to the foreign key and the primary key are different.
04 | character set | The character sets of the columns corresponding to the foreign key and primary key are different.

KFPA11744-E A

Unable to define referential constraint aa....aa."bb....bb" for ee....ee."ff....ff" code=cc(dd....dd)

Unable to define referential constraint aa....aa."bb....bb" for referenced table ee....ee."ff....ff", for the reason shown in cc.

aa....aa: Authorization identifier

bb....bb: Constraint name

cc: Reason code

dd....dd: Additional error information

ee....ee: Authorization identifier

ff....ff: Table identifier

S: Ignores this SQL statement.

P: The reason codes and the additional error information are listed below. Eliminate the cause of the error, and re-execute the SQL statement.

Reason code (cc) | Additional error information (dd....dd) | Explanation
01 | view | A table that is not a permanent base table cannot be specified in a referenced table.
02 | Primary key not defined | No primary key has been defined for the referenced table.
03 | WITHOUT ROLLBACK table | In a referenced table, a table with the WITHOUT ROLLBACK specification cannot be specified.
04 | own table | One's own table cannot be specified in a referenced table.
05 | another user's table | The table of another user cannot be specified in a referenced table.

KFPA11745-E A

Unable to specify partitioning key on column "aa....aa"

A partitioning key cannot be specified on the following columns:

CHAR, VARCHAR, MCHAR, or MVARCHAR with a definition length of 256 bytes or more

NCHAR or NVARCHAR with a definition length of 128 characters or more

For single column partitioning, a column that is not the first column comprising the cluster key
For multicolumn partitioning or matrix partitioning, a column for which the sequence of columns specified in the partitioning key is different from the sequence of columns specified in the cluster key

BLOB

A column duplicated in a multicolumn partition or the partitioning key of a matrix partition

Repetition column

BINARY

TIMESTAMP with fractional second precision greater than 0

Column that specifies CURRENT_TIMESTAMP USING BES as the default value

Abstract data type

aa....aa: Column name where the error occurred

S: Ignores this SQL statement.

P: Specify an allowed column as the partitioning key, and then retry the operation.

If a cluster key is specified, specify the columns in the cluster key in the same sequence as the columns specified in the partitioning key, starting from the beginning and including all of the columns, and then retry the operation.

KFPA11746-E A

Incompatible data type specified at partitioning condition aaaa for column "bb....bb"

One of the following errors was detected in the condition value of storage condition aaaa specified in the "bb....bb" column:

The data type of the condition value cannot be converted into the data type of the column specified in the storage condition.

The data length of the condition value exceeds the data length of the column specified in the storage condition.

The condition value is logically invalid.

The condition value data is invalid.

The data length of the condition value converted in the character set specification exceeds the data length of the column specified in the partitioning condition.

A non-convertible condition value was specified for the character set of the column specifying the storage condition.

aaaa: Sequential number of the storage condition

bb....bb: Column name specifying the storage condition value that caused the error

S: Ignores this SQL statement.

P: Revise the partitioning storage condition, and then retry the operation.

KFPA11747-E A

Invalid partitioning condition aaaa for column "bb....bb"

One of the following errors was detected in storage condition aaaa specified in partitioning key "bb....bb".

When the storage conditions were evaluated in the specified order, there was no row to store according to storage condition aaaa.

A storage condition was specified in more than one column.

The length of a character strings in the storage condition is 0.

aaaa: Sequential number of the storage condition

bb....bb: The column name specifying the storage condition value that caused the error (******** is displayed when the column name specifying the partitioning condition cannot be determined)

S: Ignores this SQL statement.

P: Correct the value specified as the storage condition and re-execute.

KFPA11748-E A

Number of defined foreign keys referencing primary key in a table exceeds 255,table=aa....aa."bb....bb"

The number of foreign keys that reference the primary key of referenced table aa....aa."bb....bb" exceeds the maximum number (255).

aa....aa: Authorization identifier

bb....bb: Table identifier

S: Ignores this SQL statement.

P: Drop the table that defines the foreign key, and then re-execute the SQL statement.

KFPA11749-E A

Duplicate column name "aa....aa" in foreign key bb....bb."cc....cc"

Column name "aa....aa" is duplicated in foreign key bb....bb."cc....cc".

aa....aa: Column name that comprises the foreign key

bb....bb: Authorization identifier

cc....cc: Constraint name

S: Ignores this SQL statement.

P: Revise the column names that comprise the foreign key to remove duplicates, and then re-execute.

KFPA11750-E A

Invalid ALLOCATE clause for column "aa....aa"

An error was detected in the ALLOCATE clause specified in the "aa....aa" column.
If the column data is an abstract data type, you have to specify an RDAREA for storing each LOB for all BLOB attributes included in the abstract data type. Or, the BLOB attribute is defined in the super type of the specified abstract data type.

aa....aa: Column name specifying the ALLOCATE clause

S: Ignores this SQL statement.

P: Correct the ALLOCATE clause of the SQL statement and re-execute. However, if the BLOB attribute is defined in the super type of the specified abstract data type, this SQL statement cannot be executed.

KFPA11751-E A

Unable to specify aa....aa in ALTER TABLE statement,reason=bb....bb

For the reason indicated in bb....bb, aa....aa cannot be specified in ALTER TABLE.

aa....aa: Processing that cannot be executed

CHANGE SEGMENT REUSE OPTION

bb....bb: Cause of error

not segment reuse table

The table does not use the free space reusage facility.

S: Ignores this SQL statement.

P: When executing the SQL statement, make sure that the reuse option value is specified for a table that uses the free space reusage facility.

KFPA11752-E L+A

Already connected

The CONNECT statement was already issued. The CONNECT statement cannot be issued again after connecting to the HiRDB system.

S: Terminates the process.

P: Re-evaluate the program and check for errors in the order the SQL statements were issued. If necessary, either delete this CONNECT statement or add a DISCONNECT statement in front of this CONNECT statement.

KFPA11753-E A

Invalid option specified for column "aa....aa"

An error was detected in the option specification of column "aa....aa".

The with default option cannot be specified in an abstract data type column.

PLUGIN cannot be specified for columns other than abstract data type columns provided by the plug-in developer.

aa....aa: Column name with an invalid option specified

S: Ignores this SQL statement.

P: Correct the specification of the column definition in the SQL statement and re-execute.

KFPA11754-E A

Duplicate routine name aa....aa."bb....bb"

The routine name specified by the FOR clause in the CREATE INDEX statement was duplicated.

aa....aa: Authorization identifier

bb....bb: Routine identifier

S: Ignores the SQL statement.

P: Correct the routine name and re-execute.

KFPA11756-E L+A

No available pages in RDAREA, RDAREA=aa....aa

A page shortage occurred in the RDAREA.

aa....aa: Name of the RDAREA with insufficient free space

S: Ignores this transaction.

Action

Perform one of the following actions, and then re-execute the SQL statement in this transaction:

RDAREA expansion
Expand the capacity of the RDAREA with insufficient space using the pdmod utility.

Table reorganization or batch index creation
Reorganize the table stored in the applicable RDAREA using the pdrorg utility. Alternatively, execute batch index creation.

Release the free page
Use the pddbst utility to analyze the status of the applicable RDAREA and execute the pdreclaim utility on an index when necessary. Also, if variable length character string type, BINARY type, or abstract data type data with a definition length of 256 bytes or more or branching lines of a repetition column is stored, execute the pdreclaim utility on a table if necessary.

If this message is output during execution of pdload or pdrorg, execute one of the following processing functions, and then re-execute the command.

RDAREA extension
Use the database structure modification utility to expand the size of the insufficient RDAREA.

Change the storage format of variable length character column data
For tables with VARCHAR, NVARCHAR, or MVARCHAR columns with a defined length of 256 or more bytes, if the no split option can be specified, redefine the table using CREATE TABLE. The number of pages required for data storage can be deleted.

Change the percentage of unused space or percentage of empty pages (action when the RDAREA cannot be expanded immediately)
Change using one of the following methods:
Reduce the value specified in the PCTFREE operand specified in CREATE TABLE and CREATE INDEX, and then redefine the table or index.
Specify the tblfree or idxfree operand in the option control statement of the database load utility (pdload) or the database reorganization utility (pdrorg), and change the specified value to a value less that the value specified in the PCTFREE operand.

KFPA11758-E A

Invalid "EXCEPT VALUES" for aa....aa

One of the following errors was detected in the exception key value for the specified index:

NULL was specified as a value comprising an exception key value in the column of a NOT NULL constraint.

An exception key value was specified in the index of a repetition column.

aa....aa: CREATE INDEX

S: Ignores this SQL statement.

P: Correct this SQL statement, and then re-execute it.

KFPA11761-E A

PLUGIN for aa....aa."bb....bb" not registered

This SQL cannot be executed because a plug-in is not registered.
Plug-ins must be registered in the index type specified by the plug-in index definition.

aa....aa: Authorization identifier

bb....bb: Data type or index type identifier

S: Ignores this SQL statement.

P: Register the plug-in, and then re-execute.

KFPA11764-E A

Number of index columns unequals to number of "EXCEPT VALUES" columns

The number of columns comprising the index and the number of values comprising the exception key value do not match.

S: Ignores this SQL statement.

P: Set the number of columns comprising the index and the number of values comprising the exception key value to the same value.

KFPA11766-E A

Unable to define aa....aa cc....cc "bb....bb" for specified data type

aa....aa cannot be defined in column "bb....bb".

The following columns cannot be specified when aa....aa is multi-value:

BLOB column

Abstract data type column

BINARY type column

The following columns cannot be specified when aa....aa is no-split or split:

Columns other than VARCHAR, MVARCHAR, or NVARCHAR

The following columns cannot be specified when aa....aa is collating-sequence:

CHAR, VARCHAR, MCHAR, MVARCHAR, NCHAR or NVARCHAR

The following columns cannot be specified when aa....aa is trailing-space:

VARCHAR, MVARCHAR, or NVARCHAR

If aa....aa is recovery, the following columns cannot be specified:

BLOB and non-BLOB attribute columns

If aa....aa is with default, the following columns cannot be specified:

Columns of the abstract data type

aa....aa:

multi-value: A repetition column

no-split: A column with the no-split option specified

split: A column without the no-split option specified

collating-sequence: A column with the COLLATING-SEQUENCE option specified

trailing-space: A column with the TRAILING-SPACE option specified

recovery: Columns with a RECOVERY specification

with default: Columns with a WITH DEFAULT clause specification

bb....bb: Column name

cc....cc:

column: The column name

attribute: The attribute

S: Ignores this SQL statement.

P: Correct the SQL statement then re-execute.

KFPA11769-E A

Unable to lock aa....aa table

When aa....aa is system:
LOCK statements cannot be executed on a system table or on a viewed table that is based on a system table.

When aa....aa is memory:
LOCK statements cannot be executed on a memory database allocation table.

aa....aa: {system|memory}

S: Ignores this SQL statement.

P: If aa....aa is system, do not execute a LOCK statement on a system table or on a viewed table that is based on a system table. If aa....aa is memory, do not execute a LOCK statement, or execute it on a table after releasing the memory database allocation.

KFPA11770-I A

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

An SQL statement cannot be executed because the resource indicated by resource ID dd....dd is in use by another transaction.
Unless the SQL statement has a NO WAIT specification (including a NOWAIT specified in a FOR UPDATE clause), this message is output when the wait time timeout is reached.

aaaa: Resource type alias

bb....bb: Resource name 1

cc....cc: Resource name 2

dd....dd: Resource information

For details on resource type names, resource names, and resource information, see the HiRDB Version 9 System Operation Guide. In HiRDB/Parallel Server, resource name 1 is always ****.

S:

For an SQL statement with a NO WAIT specification (including a NOWAIT specified in a FOR UPDATE clause), ignores this SQL statement.

For an SQL statement with a WITH ROLLBACK specification, rolls back and invalidates the transaction.

O:

Re-execute. For details, see the explanation of measures for deadlocks and timeouts in the HiRDB Version 9 System Operation Guide.

If a shared table is used with a HiRDB/Parallel Server, verify that an updatable back-end server is active. If not, re-start the server, and then retry the operation.

KFPA11771-E A

Not specified index RDAREA in same server as table RDAREA

The specified index storage RDAREA was not found on the server. The index storage RDAREA includes an RDAREA for storing cluster key indexes and an RDAREA for storing a primary key index.

S: Ignores this SQL statement.

P: Specify the index storage RDAREA on the server containing the table storage RDAREA and re-execute the SQL statement.

KFPA11773-E A

Invalid specification of base tables for LIST

One of the following errors was detected in the specification of the tables on which to base the list to be created:

A viewed table was specified

A shared table was specified

A table created with WITHOUT ROLLBACK was specified

A table that contains a column that specifies a character set was specified

A memory database allocation table was specified

A temporary table was specified

S: Ignores this SQL statement.

P: Correct the specification of the tables on which to base the list.

KFPA11774-E A

Base tables for LIST conflict

A base table for a list used for performing a set operation in the ASSIGN LIST statement differs from the base tables of the other list.

S: Ignores this SQL statement.

P: Correct the specified list name if there is an error, and then re-execute the SQL statement.

KFPA11775-E A

Unable to define function "aa....aa"."bb....bb" because of same signature as system function

The specified function "aa....aa"."bb....bb" cannot be defined because it has the same name and SQL parameter configuration as a function provided by the system.

aa....aa: Authorization identifier

bb....bb: Routine identifier

S: Ignores this SQL statement.

P: Change the routine identifier and re-execute this SQL statement.

KFPA11776-E A

Invalid specification in ASSIGN LIST statement

One of the following errors occurred in the ASSIGN LIST statement.

An arithmetic operation, date operation, concatenation operation scalar function, CASE expression, CAST specification, or component specification is specified in a search condition.

A column in a search condition is qualified by a table name or a correlation name.

A column is specified on both sides of the comparison operator in a search condition.

A column is specified in value expression 2 or 3 of the BETWEEN predicate in a search condition.

A literal, or a USER, CURRENT_DATE, CURRENT_TIME, or CURRENT_TIMESTAMP value function is specified on both sides of the comparison operator in a search condition.

A literal, or a USER, CURRENT_DATE, CURRENT_TIME, or CURRENT_TIMESTAMP value function is specified on the left side of the IN predicate in a search condition.

A literal, or a USER, CURRENT_DATE, CURRENT_TIME, or CURRENT_TIMESTAMP value function is specified in value expression 1 of the BETWEEN predicate in a search condition.

A literal, or a USER, CURRENT_DATE, CURRENT_TIME, or CURRENT_TIMESTAMP value function is specified on the left side of the LIKE predicate or XLIKE predicate in a search condition.

A literal, or a USER, CURRENT_DATE, CURRENT_TIME, or CURRENT_TIMESTAMP value function is specified on the left side of the SIMILAR predicate in a search condition.

A user-defined function other than a plug-in function for packaging logic that uses an index is specified.

No ANY subscript is specified in the repetition column in a search condition.

A predicate for a repetition column is negated by NOT.

A condition expression specifying ANDNOT is negated by NOT.

An IS FALSE or IS UNKNOWN Boolean predicate is specified.

An IN predicate specifying a subquery is negated by NOT.

A Boolean predicate is negated by NOT.

Two or more send functions for passing inter-function values that can store inter-function values were specified in a list.

Set operations cannot be performed on a list that stores inter-function values (for details on set operations on lists that store inter-function values, see the HiRDB Version 9 UAP Development Guide).

An XMLQUERY function, XMLSERIALIZE function, XMLPARSE function, or an XMLEXISTS predicate without an XML query context item for a column specification was specified.

S: This SQL statement is ignored.

P: Correct the SQL statement, and then re-execute it.

KFPA11777-E A

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

During pre-processing of the SQL statement, the resource indicated in the message was being used by another user. For this reason, the SQL statement cannot be executed.

aa....aa: Type of resource being used

type: Abstract data type

routine: Routine

bb....bb: Authorization identifier

If the type of resource being used is a routine, ******** is output because the authorization identifier cannot be determined.

cc....cc: Data type identifier, or routine identifier

S: Ignores this SQL statement.

P: After the pre-processing of the SQL statement is completed, re-execute the SQL statement.

KFPA11778-E A

Invalid specification in query with LIST

One of the following errors occurred in the specification in a query using a list.

A set function was specified in the SELECT clause of the outermost query.

A window function is specified in the SELECT clause in the outermost query.

A subquery was specified in the SELECT clause of the outermost query.

ROW was specified in the SELECT clause of the outermost query.

Table-specification.* was specified in the SELECT clause of the outermost query.

A column specification with a table qualifier was specified in the SELECT clause of the outermost query.

A column name with a qualifier was specified in the ORDER BY clause.

For a list that does not store inter-function values, a receive function for passing inter-function values was specified in a projection column.

More receive functions for passing inter-function values were specified in the projection column than the number of inter-function values that were stored in the list.

S: Ignores this SQL statement.

P: Correct the SELECT statement using the list and re-execute.

KFPA11780-E A

No appropriate index on table aa....aa."bb....bb"

One of the following indexes must be defined in table aa....aa."bb....bb" when the ASSIGN LIST statement is executed:

The column specified in the search condition requires an index (excluding an index that has an exception key value).

When a structured repetition predicate is specified in the search condition, an index is required that includes the column specified in the search condition in the structured repetition predicate of the configuration column.

When an XMLEXISTS predicate is specified in the search condition, the index cannot be used if the index's usage conditions are not satisfied. For details about the usage conditions of indexes, see the HiRDB Version 9 Installation and Design Guide.

When no search condition is specified, an index (except an index with an exceptional key value, or a plug-in index) is required on the columns (except a repetition column) of the table.

When using an index that includes repetition columns and other columns in a configuration column and evaluating the predicate for a column that is not a repetition column, an index can be used if a condition is specified in one of the columns in the repetition column.

A single column index is required in the column of the IN predicate specifying a subquery.

One of the following indexes must be defined in the column of an IN predicate that specifies a subquery. Case (b) applies only when the SQL optimization mode is set to optimizing mode 2 based on cost.
(a) Single column index
(b) Multicolumn index starting at the column in the IN predicate specifying a query:
Even when the column in the IN predicate that specifies a subquery is not the beginning of a multicolumn index, a comparison predicate (=), NULL predicate (IS-NULL) or IN predicate (IN) with a value specified for the right side, must be specified in the index configuration column in front of this column. However, this excludes indexes that include a repetition column in the index configuration column. For an IN predicate (IN) with a value specified for the right side, the number of values specified must meet one of the following conditions:
When there is one IN column, there are no more than 5 values specified.
When there are two or more IN columns, the total number of values specified in each column must be 5 or less.

aa....aa: Authorization identifier

bb....bb: Table identifier

S: Ignores this SQL statement.

P: Create the required index, and then re-execute the ASSIGN LIST statement.

KFPA11781-E A

Authorization identifier unable to specified for LIST

An authorization identifier cannot be specified for a list.

S: Ignores this SQL statement.

P: Delete the authorization identifier specified for the list and re-execute the SQL statement.

KFPA11782-E A

Column qualified with table specification in ASSIGN LIST statement

A column name in the search condition of an ASSIGN LIST statement cannot be qualified with a table name or correlation name.

S: Ignores this SQL statement.

P: Correct so that the column name is not qualified with a table name or correlation name, and re-execute.

KFPA11783-E A

LIST aa....aa not found in system

The specified list aa....aa does not exist.

aa....aa: List name

S: Ignores this SQL statement.

P:

Correct the list name if it is incorrect, and re-execute.

If the list name is correct, create the list, and then retry the operation.

KFPA11785-E A

List already dropped or altered

The SQL statement cannot be executed because the list referenced in the SQL statement has already been deleted or re-created.

S: Ignores this SQL statement.

P: Change the sequence of this SQL statement so that it will be executed before the list being referenced is deleted or re-created. If there is no need to change the sequence, perform pre-processing again and re-execute.

KFPA11787-E A

Unable to execute "aa....aa" due to existence of bb....bb's LIST "cc....cc" based on the table

"aa....aa" cannot be executed because of an operation on the base table of list "cc....cc" owned by bb....bb.

aa....aa

{ DROP TABLE |ALTER TABLE |DROP SCHEMA }

bb....bb: Authorization identifier

cc....cc: List name

S: Ignores this SQL statement.

P: Delete all lists based on the table in question, and then retry the operation.

KFPA11791-E A

Number of RDAREAs not equal to that of table partitions

The specified number of index-storage RDAREAs is invalid.

In the case of a partitioning key index, specify the same number of index-storage RDAREAs as the number of RDAREAs for storing the row-partitioned table.

In the case of a non-partitioning key index, specify the same number of index-storage RDAREAs as the number of RDAREAs for storing the row-partitioned table. Or, specify the same number of index-storage RDAREAs as the number of back-end servers.

If TYPE is specified (format 2), specify the same number of index-storage RDAREAs as the number of table-storage RDAREAs.

For matrix partitioning tables, specify the same number of index storage RDAREAs as RDAREAs storing matrix partitioning tables.

Or, an error was detected in the number of RDAREAs storing columns specifying the BLOB type or LOB columns with LOB attributes.

S: Ignores this SQL statement.

P: Match the specified number of index-storage RDAREAs or the number of LOB column storage RDAREAs and re-execute.

KFPA11793-E A

Invalid RDAREA "aa....aa" for index

Index-storage RDAREA aa....aa with partitioning specified does not correspond to an RDAREA with boundary-value partitioning or hash partitioning.

aa....aa: Name of the invalid index-storage RDAREA

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute the job.

KFPA11795-E A

Number of partitioning aa....aa exceed bbbb

The number of duplicates-exclusion RDAREAs that can be specified during table or index partitioning has exceeded the maximum.

aa....aa: Processing subject

{ table |index }

bbbb: Maximum number of duplicates-exclusion RDAREAs { 1024 | 4096 }

S: Ignores this SQL statement.

P: Correct so that the number of duplicates-exclusion RDAREAs does not exceed the maximum and re-execute.

KFPA11796-E A

Unable to specify same RDAREA "aa....aa"

RDAREA that is the same as the previous storage RDAREA cannot be specified.

aa....aa: Table storage RDAREA

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute the job.

KFPA11797-E A

Invalid specification for "WITHOUT ROLLBACK" table

The WITHOUT ROLLBACK option cannot be specified for any of the following tables:

Non-FIX tables

Tables containing a BLOB

Tables with a LOCK PAGE specification

Tables defining a foreign key

The following items cannot be specified for a table for which the WITHOUT ROLLBACK option is specified:

CHANGE LOCK PAGE option of ALTER TABLE

S: Invalidates the transaction.

P: If the executed SQL statement is CREATE TABLE, correct the SQL statement and re-execute. If the executed SQL statement is ALTER TABLE, delete the SQL statement.

KFPA11798-E A

Invalid usage of DEFAULT clause for column or SQL variable "aa....aa", code=bb

The DEFAULT clause specification is invalid in the following cases:

During table definition

During table definition update (during DEFAULT clause setting or DEFAULT clause deletion)

During SQL variable declaration in routine definition

aa....aa: Alias

bb: Reason code

The meanings of the reason codes are as follows:

Reason code
Meaning

01
The DEFAULT clause and WITH DEFAULT cannot be specified simultaneously.

02
The DEFAULT clause cannot be specified for a repetition column.

04
The DEFAULT clause cannot be specified for a reserved column.

06
One of the following values, that cannot be specified as the DEFAULT clause, was specified:

A value that cannot be converted into the data type of the specified column or SQL variable

A value greater than the definition length of the specified column or SQL variable

A value whose upper valid digit becomes invalid

A value that exceeds the definition length of the column as a result of conversion due to the character set specification

A value that cannot be converted into the character set of the specified column

07
The USER value function cannot be specified in a column or SQL variable with a data type other than CHAR, MCHAR, VARCHAR, or MVARCHAR.

08
The CURRENT_DATE value function cannot be specified in a column or SQL variable with a data type other than DATE or CHAR(10).

09
The CURRENT_TIME value function cannot be specified in a column or SQL variable with a data type other than TIME or CHAR(8).

10
NULL cannot be specified in a column with the NOT NULL constraint.

12
A DEFAULT clause cannot be specified for columns or SQL variables of the following data types:

BLOB

Abstract data type

BINARY 32,001 bytes or larger

14
The CURRENT_TIMESTAMP value function cannot be specified in a column or SQL variable with a data type other than TIMESTAMP, CHAR(19), CHAR(22), CHAR(24), or CHAR(26).

15
The following cannot be specified in a DEFAULT clause when a character set is defined on the column:

CURRENT_TIME value function

CURRENT_DATE value function

CURRENT_TIMESTAMP value function

31
DROP DEFAULT cannot be specified for a column for which no DEFAULT clause was specified.

32
WITH DEFAULT cannot be specified for a column for which a DEFAULT clause was specified.

33
The following cannot be specified in a DEFAULT clause which is also specifying the character set:

CURRENT_TIME value function

CURRENT_DATE value function

CURRENT_TIMESTAMP value function

34
A DEFAULT clause cannot be specified for an insert history maintenance column in a falsification prevented table where a deletion prevented duration has been specified.

S: Ignores this SQL statement.

P: Correct the SQL statement, and then re-execute (for reason code 31 or 32, delete the SQL statement).

KFPA11800-E A

Zero divisor in arithmetic operation for aa....aa data type

Division by zero error occurred during an arithmetic operation on data type aa....aa.

aa....aa: Data type resulting in the division by zero error:

{ INTEGER |DECIMAL |SMALLFLT |FLOAT
|INTERVAL YEAR TO DAY
|INTERVAL HOUR TO SECOND |SMALLINT }

S: Ignores this SQL statement.

P: Modify the arithmetic expression so that division by zero does not occur, then re-execute.

KFPA11801-E A

Overflow in aa....aa for bb....bb data type

Overflow occurred during operation aa....aa on data type bb....bb.

aa....aa: Type of operation resulting in the overflow:

{ addition |subtraction |division |multiplication
|sign inversion |scalar function "INTEGER"
|scalar function "DECIMAL" |scalar function "DAYS"
|scalar function "DATE" |correction
|scalar function "ABS" |scalar function "MOD"
|java routine | c routine}

bb....bb: Data type resulting in the overflow

{ integer |smallint |decimal |smallflt |float
|date |interval year to day |time
|interval hour to second }

S: Ignores this SQL statement.

P: Modify the arithmetic expression so that overflow does not occur, then re-execute.

Action

In either of the following circumstances, overflow might be avoidable if 38 is specified in the operand pd_sql_dec_op_maxprec:

The type of operation resulting in the overflow is scalar function DECIMAL and the data type resulting in the overflow is FLOAT.

The type of operation resulting in the overflow is scalar function MOD and the data type resulting in the overflow is DECIMAL.

KFPA11802-E A

Overflow in aa....aa FUNCTION "bb....bb" for cc....cc data type

An overflow occurred during the processing of the set or window function bb....bb whose other data type is cc....cc.

If SUM or AVG is displayed as the function, overflow occurred while adding the data subject to processing.

If COUNT is displayed as the function, the number of data items subject to processing exceeded 2,147,483,647.

If COUNT_FLOAT is displayed as the function, the number of data items subject to processing exceeded the range that can be represented in a floating-point number#.

aa....aa: specified function:

{ SET |WINDOW }

bb....bb: the type of the set or window function:

{ SUM |AVG |COUNT | COUNT_FLOAT }

cc....cc: Data type resulting in the overflow:

{ integer |smallint |decimal |smallflt |float }

S: Ignores this SQL statement.

P: Eliminate the cause of the error, such as by reducing the number of data items subject to processing, then re-execute.

#: The range of floating-point numeric values depends on the hardware representation.

Action

If overflow occurred while adding the data subject to processing using the set function SUM or AVG and the data type resulting in the overflow is DECIMAL, overflow might be avoidable if 38 is specified in the operand pd_sql_dec_op_maxprec.

KFPA11803-E A

Duplicate key value in unique index id=aa....aa

An attempt was made to add a duplicated column value to an index with UNIQUE specified or with a primary key. Or, an attempt was made to update a column value to a duplicated value.

aa....aa: Index number

S: Ignores this SQL statement.

P: Correct the duplicated column value and re-execute the SQL statement.

Search the dictionary table if you want to identify the index name from the index number.

KFPA11804-E A

Invalid operation code aaaa

RPC interface from the client is invalid:

Specified operation code is invalid.

Specified system type is invalid.

aaaa: Operation code

S: Ignores this request.

P: Check the UAP preprocess, compilation, or linkage for an error. If there is no error, contact the HiRDB administrator.

Action

Contact the customer support center.

KFPA11805-E A

Invalid section number

Section number is outside the range 1 to 4095.

S: Ignores this request.

P: Check the UAP preprocess, compilation, or linkage for an error. If there is no error, contact the HiRDB administrator.

Action

Contact the customer support center.

KFPA11806-E A

Current number of elements exceeds aa....aa, columnid=bb....bb

The number of elements in the column added by the ADD clause in the UPDATE statement is greater than the maximum allowable number of elements.

aa....aa: Maximum number of elements

bb....bb: The column number that indicates which column caused the error

S: Invalidates this transaction.

Action

Use the ALTER TABLE statement to increase the maximum number of elements and re-execute.

KFPA11807-E A

Invalid update option

Update option is invalid for DECLARE CURSOR.

S: Ignores this request.

P: Check the UAP preprocess, compilation, or linkage for an error. If there is no error, contact the HiRDB administrator.

Action

Contact the customer support center.

KFPA11808-E A

Row length for work list bbbbbbb exceeds maximum list row length aaaaa

Row length bbbbbbb is greater than maximum length aaaaa that can be stored as a work table.

aaaaa: Maximum length of row that can be stored

bbbbbbb: Length of row that was to be stored

S: Invalidates this transaction.

P: Re-evaluate the number of columns and column size specified in the SELECT statement and specify a value that is no greater than the maximum length of the work table.

KFPA11809-I A

Row length bb....bb exceeds aa....aa in RDAREA cc....cc

Storage length bb....bb for the row for which INSERT or UPDATE SET is specified, or for which a data load was attempted, exceeds maximum row length aa....aa.

aa....aa: Maximum length of row that can be stored

bb....bb: Length of row that was to be stored

cc....cc: RDAREA name

S: Invalidates this transaction.

Action

When issued by an operation on a non-FIX temporary table

Take one of the following actions, and then re-execute the operation:

When the client environment variable PDTMPTBLRDAREA is specified:
Change the page length of all the temporary table RDAREAs specified in PDTMPTBLRDAREA to a value greater than bb....bb.

When the client environment variable PDTMPTBLRDAREA is not specified, or an XDS client is used:
Change the page length of all the temporary table RDAREAs with attributes shared between SQL sessions to a value greater than bb....bb.

When issued by the SQL statement

Unload the table, redefine the table in an RDAREA with a page length longer than bb....bb, and then reload the table.

When issued by the database load utility (pdload)

Use the database structure modification utility (pdmod) to change the page length of the RDAREA to a value greater than bb....bb, and then re-execute the command.

KFPA11810-E A

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

This message is output in either of the following circumstances:

A duplicated key value was detected while loading an index for which UNIQUE is specified or an index for the primary key.

A non-FIX table was unloaded in binary format, and then an attempt was made to load the data into a FIX table.

aa....aa: Index identifier

S: Invalidates this transaction.

P:

When a duplicated key value was detected:

Delete the index, correct the duplicated key value, and then execute CREATE INDEX. If CLUSTER KEY or PRIMARY KEY is specified for the table, restore the RDAREA from a backup that was made before execution of the pdload command, correct the duplicated column values in the input data, and then re-execute the pdload command.

When a non-FIX table was unloaded in binary format, and an attempt was made to load the data into a FIX table:

When a non-FIX table is unloaded in binary format, the data cannot be loaded into a FIX table. However, depending on the data type, invalid input data might have gone undetected and been improperly loaded, resulting in this duplicate key value error message being output. In that case, check and correct the conditions under which the data is loaded, and then retry the operation.

KFPA11811-E A

MASTER DIRECTORY RDAREA full

The master directory RDAREA does not have enough space for an RDAREA, table, index, or viewed table to be defined.

S: Invalidates the processing and terminates abnormally.

Action

Expand the master directory RDAREA with the database structure modification utility. Or, delete unneeded tables or indexes and re-execute.

KFPA11812-E A

Number of aa....aa exceeds bbbb in RDAREA "cc....cc"dd....dd

The definition information for the specified table and sequence generator, or index definition information, exceeds the maximum bbbb that can be defined in RDAREA cc....cc.
Or, the number of list definitions exceeds the maximum bbbb that can be defined in a list RDAREA where the list definitions are not on hold (server name dd....dd).

aa....aa: Type of definition information:

TABLE and SEQUENCE: Table and sequence generator

INDEX: Index

LIST: List

bbbb: Maximum number of definitions

cc....cc: RDAREA name

******* is displayed in the case of a list RDAREA.

dd....dd: Server name

The following is displayed in the case of a list RDAREA:

server=server-name

S: Invalidates this processing.

P: Take one of the following actions:

When the attempt was to define a table and sequence generator or index
Either define the table and sequence generator, or index, in another RDAREA, or delete the table and sequence generator, or the index, from the applicable RDAREA.

When the attempt was to define a list:
Delete unneeded lists that have been defined in the applicable server. If the same error occurs, even after unneeded lists have been deleted, contact the HiRDB administrator.

Action

When the attempt was to define a list:
Use the database structure modification utility (pdmod) to add a list RDAREA to the applicable server. If the list RDAREA is shut down, release it from shutdown status by correcting the error.
If the number of lists that can be created in the list RDAREA is insufficient, the KFPA11812-E error may occur temporarily when the following occurs:
After a server process terminates, the same user reconnects to the client and executes an ASSIGN LIST statement before completion of the recovery process called for by the return of the KFPA11812-E error.

KFPA11813-E A

SQL cannot be executed because aa....aa in XDS

This SQL statement cannot be executed because the work table and index cannot be defined.

aa....aa: Cause of the error

the row length is too long: The row length exceeds the page length.

the index key length is too long: The index key length exceeds the maximum length.

the number of columns exceeds 3000: The number of columns exceeds 3,000.

S: Ignores this SQL statement.

P:

If aa....aa is the row length is too long:

Either correct the SQL statement so that the row length of the work table decreases, or increase the page length of the work table DB area, and then re-execute. For details about how to calculate row lengths, see the common rules for CREATE TABLE in the manual HiRDB Version 9 SQL Reference.

If aa....aa is the index key length is too long:

Either correct the SQL statement so that the key length of the work table index column decreases, or increase the page length of the work table DB area, and then re-execute.

For details about how to calculate key lengths, see the description of CREATE INDEX in the manual HiRDB Version 9 SQL Reference.

If aa....aa is the number of columns exceeds 3000:

P: Correct the SQL statement so that the work table number of columns decreases, and then re-execute.

For details about the work table and index configuration columns, see HiRDB Version 9 UAP Development Guide.

KFPA11814-E A

DATA DIRECTORY RDAREA full

The data directory RDAREA does not have enough space for storing the management information about a table partitioned by values or an index.

S: Invalidates the processing and terminates abnormally.

Action

Expand the data directory RDAREA with the database structure modification utility. Or, delete an unneeded index or table stored in a partition in a different RDAREA and re-execute.

KFPA11815-E A

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

No definition information for the table, index, list, or sequence generator to be processed was found in RDAREA bb....bb.

aa....aa: Table, index, list, or sequence generator type:

{TABLE|INDEX|LIST|SEQUENCE}

bb....bb: RDAREA name

cc....cc: Table, index, list number, or sequence generator

S: Terminates abnormally.

P: Take one of the following actions:

Table, index, or sequence generator
Ensure that the procedure for RDAREA "bb....bb" is correct and restore the RDAREA.

List
Re-create the list specified by the SQL statement.

KFPA11821-E A

More than aa....aa or invalid length in SQL

The length of an SQL statement exceeds aa....aa bytes. Or, the length is invalid.

aa....aa: Length of SQL statement

S: Ignores this request.

P: Correct the length of the SQL statement and re-execute.

KFPA11822-E A

Unable to access table due to check pending status, tableID=aa....aa, RDAREA="bb....bb", constraint type=ccccccc

The table denoted by aa....aa is unavailable for retrieval or updating because it is in check pending status.

aa....aa: Table number for the table in check pending status

bb....bb: Name of the RDAREA storing a table in check pending status

ccccccc: Type of constraint defined in the table

REF: Reference constraint

CHK: Check constraint

REF: CHK: Reference and check constraints

S: Ignores this SQL statement.

Action

Use the integrity check (pdconstck) to reset check pending status. For the procedure for resetting check pending status, see the manual HiRDB Version 9 Installation and Design Guide.

KFPA11823-E A

Unable to execute SQL for definition "aa....aa".bb....bb used by pdrbal

The following SQL statements cannot be executed because the rebalancing utility is being executed:

ALTER TABLE

CREATE INDEX (you cannot define an index for which the number of index-storage RDAREAs does not match the number of table-storage RDAREAs)

aa....aa: Authorization identifier

bb....bb: Table identifier

S: Ignores this SQL statement.

P: When execution of the rebalancing utility terminates, re-execute the SQL statement.

KFPA11824-E A+L

aa....aa file access error occurred,file name=bb....bb, func=cc....cc, errno=dddd

Loading of environment variable group file, JAR file, or C library file bb....bb failed.

aa....aa:

Environment group: environment variable group file

JAR: JAR file

CLIB: C library file

bb....bb: Name of file (the last 100 bytes only if the file name is longer than 100 bytes)

cc....cc: Name of function in which error occurred:

fopen: Open processing

open: Open processing

fgets: Read processing

read: Read processing

stat: Status acquisition processing

getcwd: Current directory acquisition processing

dddd: Error code (errno)

S: Terminates processing.

P: Correct the error based on the error code, and then re-execute the operation.

KFPA11827-E A

No available LOB DIRECTORY in RDAREA, RDAREA=aa....aa

The number of data items in the LOB RDAREA exceeded the management value for the RDAREA.

aa....aa: Applicable RDAREA name

S: Ignores this SQL statement.

Action

Re-estimate the required size of the applicable RDAREA and expand it. When estimating the required RDAREA size, remember to take into account rows of data length 0. For details about estimating the required RDAREA size, see the HiRDB Version 9 Installation and Design Guide.

KFPA11828-E A

Unable to set non null value at BLOB attribute of sub type because its allocation is not defined, column no=aa....aa, type id=bb....bb, attribute no=cc....cc

Values of the abstract data type including the BLOB attribute for which a LOB RDAREA name was not specified during table definition cannot be stored in a column of abstract data type or in an attribute of abstract data type.

aa....aa: The column number indicating which column in the table to be updated caused the error

bb....bb: Type ID of the abstract data type that includes the BLOB attribute that cannot be stored

cc....cc: The attribute number that indicates which attribute in the abstract data type is the BLOB attribute that cannot be stored

S: Invalidates this transaction.

P: Do not specify a value of the abstract data type including the BLOB attribute for which a LOB RDAREA name was not specified during table definition as an insert value or an update value for the column or attribute that caused the error. Review the data type of the table definition for the column that caused the error.

KFPA11845-E A

Invalid use of RDAREA "aa....aa" errno=b

One of the following errors was detected:

When errno=1
Because the specified user RDAREA stores a rebalancing table, it cannot store other tables or indexes.

When errno=2
Because the specified user RDAREA already stores other tables or indexes, it cannot store a rebalancing table.

When errno=3
When an index for a rebalancing table is defined, specification of an index-storage RDAREA cannot be omitted.

aa....aa: RDAREA name

b: Error code

S: Ignores this SQL statement.

P:

When errno=1 or 2
Change the specified RDAREA name and re-execute the SQL.

When errno=3
Specify an RDAREA for the index and re-execute the SQL.

KFPA11850-E A

aa....aa was modified after first blocked fetch

The contents of an SQL descriptor area or character set descriptor area were changed by a FETCH statement during a batch search.

aa....aa: Name of area that was changed

SQLDA: SQL descriptor area

SQLCSNA: Character set descriptor area

S: Ignores this SQL statement.

P: Correct the SQL statement so that the contents of the SQL descriptor area or character set descriptor area are not changed.

KFPA11855-E A

Unable to execute remote access SQL. REASON=aa....aa

Remote access is disabled due to the reason indicated by aa....aa.

aa....aa: Detailed reason

MAX RDNODE:

The maximum number of distributed servers that can be connected simultaneously exceeds the maximum value.

CHARACTER SET NOT SUPPORTED:

The current character codes used at the local system are not appropriate for remote access.

DF NOT SUPPORTED:

A distributed database facility cannot be used with this HiRDB.

S: Ignores this SQL statement.

P: Take one of the following actions:

MAX RDNODE

Ensure that the number of distributed servers to be connected simultaneously does not exceed the maximum value. In the HiRDB distributed client facility, a UAP is permitted to connect to only one distributed server at a time.

CHARACTER SET NOT SUPPORTED

Do not execute remote access.

DF NOT SUPPORTED

Do not perform remote access.

Action

CHARACTER SET NOT SUPPORTED or DF NOT SUPPORTED:
The distributed database facility cannot be used in HiRDB Version 9 or later. Check whether the pd_node_name operand is specified in the single-server definition or front-end server definition. If it is specified, delete the pd_node_name operand.

KFPA11875-E A

Specified index already created

An attempt was made to execute batch index creation for an existing index.

S: Ignores batch index creation for the specified index and resumes processing.

Action

There is no need to execute batch index creation.

KFPA11876-E A

Unable to assign index information file due to not defined "pd_plugin_ixmk_dir", server name=aa....aa

Although the delayed batch creation of a plug-in index is specified, the name of the directory in which the index information file or HiRDB file system area is to be created is not specified in the pd_plugin_ixmk_dir operand in the server definition aa....aa. Therefore, the index information file cannot be created.

aa....aa: Server name

S: Invalidates this transaction.

P: If the delayed batch creation of a plug-in index is not needed, specify PDPLGIXMK=NO in the client environment definition.

Action

If the delayed batch creation of a plug-in index is needed, specify the name of the directory in which the index information file or HiRDB file system area is to be created in the pd_plugin_ixmk_dir operand in the server definition aa....aa.

KFPA11877-E A

Unable to assign index information file due to no such directory, server name=aa....aa, directory name=bb....bb

The directory in which the index information file or HiRDB file system area (bb....bb) is to be created, specified in the pd_plugin_ixmk_dir operand in the server definition aa....aa, has not been created. Therefore, the index information file cannot be created.

aa....aa: Server name

bb....bb: Name of the directory in which the index information file or HiRDB file system area is to be created, as specified in the pd_plugin_ixmk_dir operand

S: Invalidates this transaction.

P: If the delayed batch creation of a plug-in index is not needed, specify PDPLGIXMK=NO in the client environment definition.

Action

If the delayed batch creation of a plug-in index is needed, create the index information file directory or HiRDB file system area specified in the pd_plugin_ixmk_dir operand in the server definition aa....aa. Alternatively, specify the name of the directory in which the index information file is to be created in the pd_plugin_ixmk_dir operand in the server definition aa....aa.

KFPA11878-E A

Index information file not available, file=aa....aa, server name=bb....bb

The contents of the index information file named aa....aa do not match the condition of the database.

aa....aa: Name of the index information file

If the name of the index information file exceeds 80 characters, the last 80 characters of the file name are output.

bb....bb: Server name

S: Invalidates this transaction.

Action

Utility:

Check whether there are utilities that are simultaneously using the same index information file, and re-execute the database load utility, database reorganization utility, or rebalancing utility.

UAP:

Because the index information file cannot be created together with the plug-in index, use the database reorganization utility (pdrorg -k ixrc command) to re-create the plug-in index.

KFPA11879-E A

Index aa....aa in cc....cc must be bb....bb to access table

Index aa....aa stored in RDAREA cc....cc was not created by the batch method. Or, the table cannot be accessed because its index is unusable (is not completed).
This error occurs primarily in situations where the following operations were performed:

The database load utility (pdload -i n) or the database reorganization utility was used to reload table data (pdrorg -k rorg/reld -i n), but it accessed an index that was not batch-created.

For table data stored in partitions in multiple RDAREAs, after performing the reorganization of the table data stored in a specific RDAREA, an attempt was made to access an index that had not yet been created.

If a memory database is used, this error occurs primarily in situations where the following operations were performed:

DEALLOCATE MEMORY TABLE was executed after XDS terminated, and an attempt was made to access the index of a table for which an index was not recreated

While XDS is running, an attempt was made to access the index of a table waiting to be allocated to memory, but the index is unfinished. This occurs in the following cases:
While XDS is running, ALLOCATE MEMORY TABLE was executed on a table whose index was unfinished, and the access was attempted before XDS restarted.
If the system switchover facility is used, while XDS was stopped, it switched over to the standby system when an error occurred in database export processing, and then accessed the memory database allocation table on the disk database.

aa....aa: Accessed index number

bb....bb: Code indicating batch index creation:

{ loaded }

cc....cc: Name of RDAREA storing the index

S: Ignores this SQL statement, or invalidates the transaction.

Action

Take one of the following corrective actions, and then re-execute the SQL statement in this transaction:

If you have the required index information file, execute batch index creation (pdrorg -k ixmk).

Re-create the index (pdrorg -k ixrc).

In addition, review operations to make sure that indexes are not accessed in an unfinished state.

KFPA11880-E A

Index information file open error,file name =aa....aa errno=bb....bb

Index information file open processing failed during index information file creation.

aa....aa: Name of index information file

bb....bb: Error code

If the error occurred in a HiRDB file system area, a HiRDB file system area error code is displayed. For the HiRDB file system area error codes, see 5.1 Error codes returned from HiRDB file system access requests.

S: Invalidates this transaction.

Action

Refer to errno.h or the applicable OS manual to check the cause of the error indicated by the error code (external integer variable indicating the error status) and take action appropriate to the error cause as listed below, then re-execute the database load utility, database reorganization utility, rebalancing utility, or UAP.

Error cause | Explanation | Action
ENOENT, ENAMETOOLONG | File name is invalid. | Specify the correct index information file name and path name.
EMFILE | The maximum number of files that can be opened for processing was reached. | Revise the estimate of the number of files that can be opened per process of the OS parameter, or specify the index creation method as the index update mode (-i s), and re-execute.

KFPA11881-E A

Index information file aa....aa error, file name=bb....bb errno=cc....cc

Processing aa....aa on an index information file failed during creation of the index information file.

aa....aa: Type of error

bb....bb: Name of the index information file

cc....cc: Error code

If the error occurred in a HiRDB file system area, a HiRDB file system area error code is displayed. For the HiRDB file system area error codes, see 5.1 Error codes returned from HiRDB file system access requests.

S: Invalidates either this utility or the UAP.

Action

Based on the error code (an external integer variable that indicates the error status), check the cause of the error by referring to the errno.h file and the OS manual. Take an appropriate action according to the following list of causes of the error. After taking corrective action, take either of the following measures:

For a utility:

To create an index, re-execute the database load utility, database reorganization utility, or rebalancing utility to create a new index information file.

For a UAP:

If the error code is EIO, re-create the index. In other cases, re-execute the UAP.

Error cause | Explanation | Action
ENOSPC | Directory containing the index information file is full. | Delete unneeded files from the directory.

KFPA11882-E A

System call error func=aa....aa, errno=bb....bb

A system call error occurred during creation of an index information file.

aa....aa: Type of system call

bb....bb: Error code

S: Invalidates this utility.

Action

Refer to errno.h or the applicable OS manual to eliminate the cause of the error indicated by the error code (external integer variable indicating the error status), then re-execute the database load utility or database reorganization utility.

KFPA11883-E A

Unable to use index records in aa....aa for bb....bb.cc....cc

Because the contents of the specified index information file do not match the table data, the index information file cannot be used for batch creation of the index.

aa....aa: Name of index information file

bb....bb: Authorization identifier

cc....cc: Table identifier

S: Ignores batch index creation for the specified index and resumes processing.

Action

If an index with batch index creation specified is necessary, reorganize the table (pdrorg -k rorg -t table-name control-information-file-name).

KFPA11884-E A

Index information file used by other job filename=aa....aa

An attempt was made to execute the database load utility, database reorganization utility, or rebalancing utility by specifying file aa....aa in an index information file while it was being accessed by another process.

aa....aa: Name of the index information file

S: Invalidates this utility.

Action

Change the name of the index information file and re-execute the database load utility, database reorganization utility, or rebalancing utility.

KFPA11886-E A

Multi-value columns in multi-column index must have same number of elements [, indexid=aa....aa]

The repetition columns comprising an index have mismatched numbers of elements. Therefore, the following SQL statements and utility cannot be executed:

CREATE INDEX

INSERT statement

UPDATE statement

Database Load Utility (pdload)

S: Invalidates this transaction.

P: Correct the UAP so that the repetition columns comprising the index have consistent numbers of elements, and then re-execute.

KFPA11890-E A

Unable to call PLUGIN aa....aa, reason code="bb....bb"

The plug-in aa....aa was not called due to the reason indicated in "bb....bb".

aa....aa: Plug-in name

bb....bb: Reason code

UNAVAILABLE:

The plug-in aa....aa is unavailable.

UNDEFINED:

The pdplugin operand for the plug-in aa....aa is not defined. Or, an error occurred during the initialization of the plug-in.

S: If this error was caused by the execution of the SQL, the system cancels the execution of the SQL.

Action

Reason code UNAVAILABLE:

Take an appropriate action based on the KFPYnnnnn (nnnnn: a 5-digit message number) message that was output prior to this message. Alternatively, execute only those SQL statements that do not require the plug-in aa....aa.

Reason code UNDEFINED:

Stop the HiRDB system, code a use declaration (pdplugin operand) for the plug-in aa....aa in the system common definition, and then activate the HiRDB system.

In other cases, take an appropriate action based on the KFPYnnnnn (nnnnn: a 5-digit message number) message that was output prior to this message.

Alternatively, execute only those SQL statements that do not require the plug-in aa....aa.

KFPA11891-E A

Unable to access LOB RDAREA, RDAREA name=aa....aa, tableID=bb....bb, reason code=c

The area aa....aa in LOB RDAREA with the table ID bb....bb could not be accessed due to reason code c.

aa....aa: Name of the RDAREA to which access was attempted

bb....bb: The number of the table to which access was attempted

c: Reason code indicating the condition of the LOB RDAREA

1: LOB RDAREA initialization status

3: LOB RDAREA is in reload-not-completed data status

S: Invalidates this transaction.

O:

If the reason code is 1, execute the PURGE TABLE statement, pdload (with -d specified), or the reinitialization of the table storage RDAREA associated with the LOB RDAREA, to put the area in an available status. If the reason code is 3, restore the LOB RDAREA from the backup data and enable the LOB RDAREA.

KFPA11892-E A

Too many duplicate element values within row in index on aa....aa column, index id=bb....bb

The number of duplicate elements in the same row in a repetition column exceeded the maximum value of the number of duplicate keys for a repetition column index.
Another possibility is that the number of duplicate XML element values in the same row in an XML-type column exceeded the maximum value for the number of duplicate keys in a substructure index.

aa....aa:

For a repetition column (repetition column index): Multi-value

For an XML-type column (substructure index): XML TYPE

bb....bb:

If a data manipulation SQL statement is executed:

The index ID

If either CREATE INDEX or the batch creation of an index is executed:

CREATE

S: Invalidates this transaction.

P:

When aa....aa is Multi-value (when data manipulation SQL or batch index creation was executed):

Check the data specified in the repetition column index so that the number of duplicate elements per row does not exceed the value obtained from the formula below.

When aa....aa is XML TYPE (when data manipulation SQL or batch index creation was executed):

Check the data specified in the XML-type column index so that the number of duplicate XML element values per row does not exceed the value obtained from the following formula:

number-of-duplicates = (index-storage-RDAREA-page-size 0.95 - 82) 4 - 1

O:

When aa....aa is Multi-value (when CREATE INDEX was executed):

Check the data in the repetition column on which an attempt to define an index was made to ensure that the number of duplicate elements per row does not exceed the value obtained from the formula below.

When aa....aa is XML TYPE (when CREATE INDEX was executed):

Check the data in the XML-type column on which an attempt to define an index was made to ensure that the number of duplicate XML element values per row does not exceed the value obtained from the following formula:

number-of-duplicates = (index-storage-RDAREA-page-size 0.95 - 82) 4 - 1

KFPA11893-E A

RDAREA not specified for aa....aa bb....bb

No storage RDAREA is specified in ALTER TABLE ADD RDAREA for the index, primary key, cluster key, or column.

aa....aa:

(INDEX |CLUSTER KEY |PRIMARY KEY |COLUMN}

bb....bb:

When aa....aa is INDEX
index-identifier

When aa....aa is COLUMN
column-name

When aa....aa is CLUSTER KEY or PRIMARY KEY
Blank (nothing is output)

S: Ignores this SQL statement.

O: Specify a storage RDAREA and re-execute.

KFPA11894-E A

Duplicate aa....aa "bb....bb" specified

A column name or index name is specified more than once in ALTER TABLE ADD RDAREA.

aa....aa:

{ INDEX |COLUMN }

bb....bb:

When aa....aa is INDEX
index-identifier

When aa....aa is COLUMN
column-name

S: Ignores this SQL statement.

O: Specify the column name or index name only once and re-execute.

KFPA11895-E A

Failed to load PLUGIN, shared library=aa....aa, external function=bb....bb, reason=cc....cc

The plug-in could not be loaded.

aa....aa: Name of the shared library#

bb....bb: Name of the external routine#

#: If the name of the shared library or the external routine is less than or equal to 64 bytes, HiRDB outputs the entire name; if it is greater than 64 bytes, HiRDB outputs the first 62 bytes followed by two periods (..).

cc....cc: Reason for the error

NO LIBRARY:

The specified library was not found.

NO FUNCTION:

The specified external routine was not found.

NO PERMISSION:

The user does not have access privilege for the library.

NO SPACE:

Either the area in which to load the library was unavailable or a memory shortage occurred.

BROKEN:

Either a non-library file was specified or the library is damaged.

S: Either ignores this SQL statement or invalidates the transaction.

Action

cc....cc: NO LIBRARY

Specify an existing library name and re-execute.

cc....cc: NO FUNCTION

Specify an existing external routine name and re-execute.

cc....cc: NO PERMISSION

Grant the user the necessary access privilege and re-execute.

cc....cc: NO SPACE

Re-execute the UAP. If this error persists, notify the HiRDB administrator.

cc....cc: BROKEN

Specify the correct library and re-execute.

KFPA11896-E E+L

Invalid return information for PLUGIN function, shared library=aa....aa, external function=bb....bb

The information returned by the plug-in implementation function is invalid.

aa....aa: Name of the plug-in shared library#

bb....bb: Name of the plug-in implementation function (external routine name)#

#: If the name of the shared library or the plug-in implementation function is less than or equal to 64 bytes, HiRDB outputs the entire name; if it is greater than 64 bytes, HiRDB outputs the first 62 bytes followed by two periods (..).

S: Terminates abnormally.

P: Notify the HiRDB administrator.

Action

Contact the customer support center.

KFPA11897-E A

Registry access error,code=a

When code=1 is displayed, processing cannot continue because the referenced registry information has been updated.
When code=2 is displayed, other processing tried to update the referenced registry information.

a: Error code

S: Terminates processing.

P: When code=1 is displayed, re-execute the SQL; when code=2 is displayed, re-execute the command that caused the error.

KFPA11898-E A

Unable to add RDAREA for column "bb....bb"

One of the following errors was detected for a column specified in ALTER TABLE:

The column is not a BLOB type column or an abstract data type column.

An ALLOCATE clause is specified for the BLOB type.

A storage RDAREA is specified for an abstract data type column without specifying an ALLOCATE clause.

aa....aa: Name of column involved in the error

S: Ignores this SQL statement.

P: Correct the error concerning the column and re-execute.

KFPA11899-E A

Unable to use "aa....aa", due to unsupported facility in XDS

Facility aa....aa is not supported in the XDS, so it cannot be used.

aa....aa: Unsupported facility name

aa....aa | Unsupported facility name
ARRAY | Facility that uses an array
EXTENDED STATEMENT NAME | Extended statement name
EXTENDED CURSOR NAME | Extended cursor name
CHARACTER SET | Character set
MULTI-VALUE COLUMN | Repeated column
GET DIAGNOSTICS | Getting diagnostic information
JAR | INSTALL JAR, REPLACE JAR, and REMOVE JAR
CLIB | INSTALL CLIB, REPLACE CLIB, and REMOVE CLIB
XA INTERFACE | XA interface
COMMAND EXECUTE | Execute command from UAP
OPNR | Open cursor declared multiple times for the same SQL statement identifier
CALL COMMAND | CALL COMMAND statement
DEFINITION SQL | Call for the definition SQL or the routine that contains the definition SQL
PURGE TABLE | Call for the PURGE TABLE statement or the routine that contains the PURGE TABLE statement
COMMIT IN ROUTINE | Call for the routine that contains the COMMIT statement
ROLLBACK IN ROUTINE | Call for the routine that contains the ROLLBACK statement
WRITE SPECIFICATION | Execution of the SQL statement that specified WRITE to the table in the RDAREA (if an XDS client was used)

S: Ignores this SQL statement.

P:

If aa....aa is DEFINITION SQL:

Execute the facility in the client library used for the server providing the primary facilities or in the database definition utility (pddef).

Execute the routine containing the definition SQL from the client for the server providing the primary facilities.

If aa....aa is other than DEFINITION SQL:

Correct the SQL statement so that the unsupported facilities are not used, and then re-execute.

If you are working on a table that is not the memory database allocation table, execute from the client for the server providing the primary facilities.

For a list of unsupported facilities, see Limitations regarding SQL when using the memory database description of the relevant scalar function in the manual HiRDB Version 9 SQL Reference.

KFPA11900-E A

Thread lock error occurs in management for LIST

A lock error occurred during list management.

S: Performs the following:

SQL statement
Ignores this SQL statement.

pdmod
Continues processing.

P: Perform the following:

SQL statement
Re-execute the SQL.

pdmod
Re-create the list.

KFPA11901-E A

Execution or reference of SQL requested without normal preparation

Dynamic execution of an SQL statement was requested before its preprocessing was completed. Or, the FETCH or CLOSE statement for a query specified in the cursor declaration (format 1) was executed before cursor open preprocessing was completed.

S: Ignores this SQL statement.

P: Complete the preprocessing and re-execute the UAP.

KFPA11902-E A

Unable to grant access privileges except SELECT privilege on audit trail table

INSERT, UPDATE, and DELETE privileges for the audit trail table or the viewed table using an audit trail table as its base table were not granted for users other than auditors.

S: Ignores this SQL statement.

P: Specify SELECT as the only privilege that can be granted for the audit trail table or the viewed table using an audit trail table as its base table for users other than auditors, and re-execute.

KFPA11903-E A

Unable to grant DBA or connect privilege to auditor aa....aa

DBA privilege cannot be granted to auditor aa....aa, or the password of auditor aa....aa cannot be changed using GRANT CONNECT.

aa....aa: Authorization identifier of the auditor

S: Ignores this SQL statement.

P: Grant DBA privilege to a user other than the auditor. Alternatively, change the auditor's password using GRANT AUDIT.

KFPA11904-E A

Unable to grant RDAREA use privileges for RDAREA "aa....aa" because only auditor has privilege to use this RDAREA

Only the auditor holds use privileges for the RDAREA for storing audit trail tables. Use privileges for the RDAREA for storing audit trail tables cannot be granted to users other than the auditor.

aa....aa: RDAREA name

S: Ignores this SQL statement.

P: Grant usage privilege of another RDAREA.

KFPA11905-E A

Unable to execute aa....aa due to lack of audit privilege

aa....aa cannot be executed due to lack of the audit privilege.

aa....aa: One of the following is displayed:

"CREATE AUDIT"

"DROP AUDIT"

"GRANT AUDIT"

"DROP TABLE" for audit trail table

S: Ignores this SQL statement.

P: The auditor must perform this operation.

KFPA11906-E A

Unable to execute "DROP SCHEMA" due to audit trail table existence

The auditor's schema cannot be deleted because there is an audit trail table.

S: Ignores this SQL statement.

P: To delete the auditor's schema, delete the audit trail table before executing this SQL statement.

KFPA11907-E A

Unable to revoke schema or connect privilege of auditor

The auditor's schema definition privilege or CONNECT privilege cannot be deleted.

S: Ignores this SQL statement.

P: Confirm that the privileges will be deleted from the correct user. When deleting the auditor's privileges, delete other privileges also.

KFPA11908-E A

Duplicate audit for "aa....aa" whenever "bb....bb" audittype "cc....cc"

The audit event specified by CREATE AUDIT was already defined.

aa....aa: Operation type and index type

Operation type | Event type
ANY | Not applicable
SESSION | CONNECT
DISCONNECT
AUTHORIZATION
ANY
PRIVILEGE | GRANT
REVOKE
ANY
DEFINITION | CREATE
DROP
ALTER
ANY
ACCESS | SELECT
INSERT
UPDATE
DELETE
PURGE
ASSIGN
CALL
LOCK
NEXT VALUE
ANY
UTILITY | PDLOAD
PDRORG
PDEXP
PDCONSTCK
ANY

Note: A space is displayed between the operation type and the index type.

bb....bb: Value specified in the WHENEVER clause

ANY

SUCCESSFUL

UNSUCCESSFUL

cc....cc: Value specified in the AUDITTYPE clause

ANY

PRIVILEGE

EVENT

S: Ignores this SQL statement.

P: Change the audit event and re-execute.

KFPA11909-E A

Specified audit for "aa....aa" whenever "bb....bb" audittype "cc....cc" not defined

The audit event specified by DROP AUDIT is not specified.

aa....aa: Operation type and index type

Operation type | Index type
ANY | Not applicable
SESSION | CONNECT
DISCONNECT
AUTHORIZATION
ANY
PRIVILEGE | GRANT
REVOKE
ANY
DEFINITION | CREATE
DROP
ALTER
ANY
ACCESS | SELECT
INSERT
UPDATE
DELETE
PURGE
ASSIGN
CALL
LOCK
NEXT VALUE
ANY
UTILITY | PDLOAD
PDRORG
PDEXP
PDCONSTCK
ANY

Note: A space is displayed between the operation type and the index type.

bb....bb: Value specified in the WHENEVER clause

ANY

SUCCESSFUL

UNSUCCESSFUL

cc....cc: Value specified in the AUDITTYPE clause

ANY

PRIVILEGE

EVENT

S: This SQL statement is ignored.

P: Change the audit event and re-execute.

KFPA11911-E A

Deadlock occurred on aa....aa resource id=bb....bb

Deadlock occurred.

aa....aa: Type of resource

bb....bb: Resource information

S: Ignores this SQL statement.

P: Re-execute the SQL statement.

KFPA11912-E A

Insufficient memory for DB exclusive control, reason code=a

There is not enough work area for exclusive control to function.

a: Reason code

1: There was a shortage of exclusive control resources.

2: The number of locked resource requests exceeded the maximum value specified in PDLOCKLIMIT.

3: A memory shortage occurred.

4: The number of table lock requests exceeded 63 + the value specified in pd_max_access_tables.

S: Ignores this SQL statement or aborts processing of the utility.

P:

If the reason code is 1 or 2:

Re-evaluate the program from the following viewpoints:

Can the LOCK statement can be specified. Specify EXCLUSIVE if this is an update SQL statement.

Can WITHOUT LOCK NOWAIT can be specified. If the program can be modified, modify it, and then re-execute it.

If the above actions do not resolve the problem, contact the HiRDB administrator.

If the reason code is 3 or 4:

Contact the HiRDB administrator.

Action

If the reason code is 1:

Increase the values set in pd_fes_lck_pool_size, pd_lck_pool_size, or pd_lck_until_disconnect_cnt. For details, see the KFPS00443-I message, which is output to the event log (in UNIX, syslogfile) or the message log file.

If the reason code is 2:

Increase PDLOCKLIMIT in the client environment definition. For details, see the KFPS00444-I message, which is output to the event log (in UNIX, syslogfile) or the message log file.

If the reason code is 3:

Take the following steps to increase the amount of available memory:

Reduce the number of concurrently executing processes.

Increase the real memory.

Increase the swap area.

Reduce the number of resident processes on the server (the value of pd_process_count).

If the reason code is 4:

Start HiRDB with a higher value specified in pd_max_access_tables.

KFPA11913-E A

DB exclusive control error occurred on aa....aa resource id=bb....bb code=cc....cc

A lock error occurred.

aa....aa: Type of resource

bb....bb: Resource information

cc....cc: Error code

S: Ignores this SQL statement.

O: Contact the HiRDB administrator.

Action

Contact the customer support center.

KFPA11914-E A

Insufficient memory on DYNAMIC_SHMPOOL for DB exclusive control

Shared memory used for exclusive control is insufficient.

S: Ignores this SQL statement.

P: Check whether the UNTIL DISCONNECT specification for LOCK TABLE can be deleted.

Action

The value of pd_lck_until_disconnect_cnt in the server definition is incorrect. Check the value and increase it, and then restart the system.

KFPA11917-E A

Closed RDAREA "aa....aa"

The indicated RDAREA is closed.

aa....aa: RDAREA name

S: Terminates processing.

P: Ask the HiRDB administrator to open the RDAREA, and then re-execute the UAP or utility.

Action

Open the RDAREA with the pdopen command.

KFPA11918-E A

Global buffer pool undefined, RDAREA="aa....aa"

No global buffer pool is defined.

aa....aa: RDAREA name

S: Terminates processing.

P: Contact the HiRDB administrator.

Action

With the pdbuffer operand of the system common definition, define a global buffer pool for the corresponding RDAREA.

KFPA11919-E A

Insufficient global buffer, global buffer pool=aa....aa

There are not enough global buffer sectors.

aa....aa: Name of global buffer pool

S: Terminates processing.

P: Re-execute the UAP. If the same error recurs, contact the HiRDB administrator.

Action

Re-evaluate the estimated number of buffer sectors; if necessary, change the number of buffer sectors with the pdbuffer operand of the system common definition.

KFPA11920-E A

RDAREA "aa....aa" held

The indicated RDAREA is shut down or was shut down due to an error.

aa....aa: RDAREA name

S: Terminates processing.

P: Contact the HiRDB administrator. Reset the RDAREA shutdown status, and then re-execute the UAP or utility.

Action

Error shutdown:

After the RDAREA has been recovered by the database recovery utility, release the RDAREA from shutdown status with the pdrels command.

Command shutdown:

Release the RDAREA from shutdown status with the pdrels command.

KFPA11925-E A

Cannot load compression library, name "aa....aa", return code bb, errno=cc....cc

Compression library aa....aa cannot be loaded for the reason indicated in return code bb and error code cc....cc.

aa....aa: Name of compression library

PDZLIB

bb: Return code

8: An error occurred when loading the compression library aa....aa.

12: The compression library loaded successfully, but an error occurred during symbol resolution.

cc....cc: Error code (errno)

When bb is 8: errno when loading the compression library

When bb is 12: errno during symbol resolution in the compression library

S: Invalidates the transaction.

Action

Contact the customer support center.

KFPA11927-E A

aa....aa processing error occurred in "bb....bb", rc=cc....cc

An error occurred in compression or expansion processing, with error return information cc....cc.

aa....aa: Processing

Compress: Compression

Expand: Expansion

bb....bb: Name of compression library

PDZLIB

cc....cc: Error return information

Return information for the error that occurred in bb....bb while processing aa....aa

S: Invalidates the transaction.

P: Contact the HiRDB administrator, and then re-execute the transaction after the HiRDB administrator takes corrective action.

Action

Eliminate the cause of the error based on the error return information, and then retry the operation.

Error return information | Action
A value (-1nnn) less than -1000 | Letting the absolute value of the error return information be the value that results when you add 1,000 to errno (nnn), look up errno (value 1 to 151) in errno.h and in the documentation of the applicable OS.
-4 | Add the memory required to execute the compression library, about 260 KB, and then retry the operation.
Other than the above | Contact the customer support center.

Legend: nnn: A numeric value from 1 to 151

KFPA11928-I L

RDAREA aa....aa held pdhold command in process

Specified RDAREA aa....aa is being shut down by the pdhold command.

aa....aa: RDAREA name

S: Invalidates this transaction.

Action

Recover the RDAREA and re-execute this transaction.

KFPA11929-E A

Insufficient work pool, size=aa....aa, pool size=bb....bb

There is not enough memory to process an SQL statement.

aa....aa: Size (in bytes) of area that was to be allocated

bb....bb: Size (in bytes) of memory pool

S: Ignores this SQL statement.

O: Contact the HiRDB administrator.

Action

Contact the customer support center.

KFPA11930-E A

Insufficient memory on aa....aa, size=bb....bb

There is not enough memory to process an SQL statement.

aa....aa: Character string indicating the type of area:

PROCESS: Process private area

SHARED: Shared memory

bb....bb: Size (in bytes) of area that was to be allocated

If the size of the area cannot be determined, the size is indicated as ********.

S: Ignores this SQL statement. If a server process is being activated, cancels activation of the process. If there are connections, connection processing is terminated.

O: Re-execute the UAP. If the same error recurs, contact the HiRDB administrator.

Action

Increase the available memory space by the following methods:

Reduce the number of processes executed concurrently.

Increase the swap area.

Add real memory.

Reduce the value specified in the pd_work_buff_size operand if a large value was specified.

If this message was issued during activation of a server process, reduce the number of resident server processes (pd_process_count).

KFPA11931-E A

Insufficient pd_max_access_tables,resource id=aa....aa,resource count=bb....bb

An attempt was made to access more tables or sequence generators than the value of the pd_max_access_tables operand specified in the system common definition (the total number of tables and sequence generators concurrently accessible by one user in one transaction).

aa....aa: Maintenance information

bb....bb: Maintenance information

S: Invalidates the transaction being processed.

P: Increase the number of times the COMMIT statement is issued and re-execute. If the same message is reissued, contact the HiRDB administrator.

Action

Check if the COMMIT statement was issued before the pd_max_access_tables operand value in the common system definition was reached. Or, re-evaluate whether or not the pd_max_access_tables operand value is appropriate to the entire system.

KFPA11932-E A

Number of connect users exceeded max users

The number of connections to the HiRDB server exceeded the maximum number of concurrent connections. Another possibility is that the maximum number of startup processes was changed to 0 with the pdchprc command.

S: Ignores this SQL statement. However, if the utility is executing, processing is terminated.

P: Wait for other user processes to end, and then re-execute the UAP or utility. Use the pdls -d act command to check the user connection status.

Action

When HiRDB is operating:

If you can increase the maximum number of startup processes on an SDS or FES (which you can check with the pdchprc command), use the pdchprc command to set the maximum number of startup processes to a value that is greater than or equal to the total number of UAPs, utilities, and pdorend application processes# that you want to execute simultaneously.
#
The total number of pdorend application processes is calculated as follows:

n: Number of simultaneous executions of the pdorend command

Take the following actions when the maximum number of startup processes on an SDS or FES is less than the total number of UAPs, utilities, and pdorend application processes that can be executed simultaneously:
(1) If this error message is output when executing a UAP or utility process:
Decrease the number of UAPs or utility processes that can be executed simultaneously.
(2) Take the following actions if this error message is output when executing the pdorend command (if message KFPH27043-E, code=-52 is output after this message):
(a) Decrease the number of pdorend commands that can be executed simultaneously.
(b) Decrease the number of servers that can be executed simultaneously (the number of servers specified in the -s option) for each pdorend command executed.
(c) Reduce the pdorend application process multiplicity (the value specified in the -m option) each time the pdorend command is executed.

Actions to take before the next normal startup:

If this error message is output when executing a UAP or utility process:
Specify a large value for the pd_max_users operand if possible.
Specify the pdcltgrp operand in the system definition for the UAP or utility (only pddef is applicable) to be guaranteed.

If this error message is output when executing the pdorend command (if message KFPH27043-E, code=-52 is output after this message)
Set the specification value of the pd_max_reflect_process_count operand in the system definition to a large value.

KFPA11934-E A

Insufficient memory on communication header, size=aa....aa or communication buffer, size=bb....bb

A memory shortage occurred in the communication buffer.

aa....aa: Size of communication header that was to be acquired

bb....bb: Size of communication buffer that was to be acquired

S: Invalidates this transaction.

P: Re-execute the UAP. If the same error recurs, contact the HiRDB administrator.

Action

Contact the customer support center.

KFPA11935-E A

Unable to execute definition SQL for executing data processing SQL

A definition SQL cannot be issued from within a transaction that issued a data manipulation SQL.

S: Ignores this SQL statement.

P: To issue a definition SQL after issuing a data manipulation SQL, specify the commit (COMMIT) statement and then specify the definition SQL.

KFPA11937-E A

Unable to execute this SQL in XA environment

This SQL statement cannot be executed in the XA environment.

S: Ignores this SQL statement.

P: Delete this SQL statement.

KFPA11938-E A

Unable to modify attributes of abstract data type in which value is NULL

The value of the abstract data type, which is a NULL value, has not been generated by the constructor function; its attributes cannot be updated.

S: Ignores this SQL statement.

P: Use the constructor function to generate the necessary values, and then update the attributes of the abstract data type.

KFPA11939-E A

Total length of attributes of abstract data type too long

The total length of the attributes of the defined abstract data type is too large.

S: Ignores this SQL statement.

P: Reduce the total length by reducing the number of attributes and re-execute. For a description of how to estimate the total length or the maximum allowable value for the total length, see Syntax Create Type in the HiRDB Version 9 SQL Reference.

KFPA11940-E A

Connect command ignored, HiRDB is initializing or terminating

Connection to HiRDB is disabled because HiRDB is starting or terminating.

S: Ignores this SQL statement.

O: If HiRDB is starting, re-execute the UAP after the startup processing terminates.

If HiRDB is terminating, restart HiRDB and then execute the UAP.

KFPA11941-E A

HiRDB is under termination process

An execution request was issued during HiRDB termination processing.

S: Disconnects HiRDB.

P: Terminate the UAP.

O: Restart HiRDB, and then re-execute the UAP.

KFPA11945-E A

Unable to expand stack area for thread. size=aa....aa

The attempt to expand the thread stack area by aa....aa bytes failed.

aa....aa: Attempted expansion size (in bytes)

If the area size cannot be determined, the size is indicated as ********.

S: Either ignores this SQL statement or invalidates the transaction.

P: Notify the HiRDB administrator.

O: Notify the HiRDB administrator.

Action

Increase the maximum value for the thread stack size maximum value option pd_thread_max_stack_size in the system common definition.

KFPA11948-E A

Unable to aa....aa bb....bb without cc....cc

Process bb....bb cannot perform aa....aa because cc....cc is not embedded.
When bb....bb is "PARTITIONED BY MULTIDIM", a matrix-partitioned table cannot be defined because HiRDB Advanced High Availability# is not embedded.

#

HiRDB Advanced Partitioning Option in version 08-05 and earlier.

aa....aa: {specify|use|invoke}

bb....bb: {"PARTITIONED BY MULTIDIM"

|"ALTER TABLE CHANGE RDAREA" statement}

cc....cc: {Advanced High Availability}

S: Ignores this SQL statement.

P: Delete this SQL statement. Alternatively, embed the cc....cc option, and then re-execute the SQL statement.

KFPA11952-E A

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

An attempt was made to perform the following processing with a value that exceeded the value defined in bb....bb:

List creation

aa....aa: assign LIST

bb....bb: Defined operand name{pd_max_list_users|pd_max_list_count}

S: Ignores this SQL statement.

P:

When bb....bb is pd_max_list_users:

This SQL statement cannot be executed. To execute this SQL statement, increase the specification value of the pd_max_list_users operand.

When bb....bb is pd_max_list_count:

Either delete unnecessary lists and re-execute this SQL statement, or increase the specification value of the pd_max_list_count operand and re-execute this SQL statement.

Action

Check that the value of bb....bb in the system definition is appropriate.

KFPA11953-E A+L

Unable to execute aa....aa due to bb....bb, cc....cc

Processing aa....aa cannot be executed because of bb....bb.

aa....aa: Processing (See Actions.)

bb....bb: Reason (See Actions.)

cc....cc: Additional information (See Actions.)

S: Cancels this transaction.

Actions

Processing (aa....aa)
Reason (bb....bb)
Additional information (cc....cc)
Action

HASH JOIN Hash join or subquery hash execution
Insufficient work buffer
size=dd....dd,
server=ee....ee
dd....dd: Shortfall (in KB)
ee....ee: Server name
Displayed shortfall is the shortfall at the location where the first shortage was detected, not the entire shortage.
Take one of the following actions:

Increase the specified value of the pd_work_buff_size operand or the pd_work_buff_expand_limit operand. Alternatively, decrease the specified value of the PDHASHTBLSIZE or pd_hash_table_size operand in the client environment definition.

Do not select hash join, subquery hash execution using the client environment definition PDADDITIONALOPTLVL or the pd_additional_optimize_level operand. Also, do not specify HASH in the SQL optimization specification for the join method in the SQL statement or the SQL optimization specification in the subquery execution method.

Invalid work buffer allocation mode
server=dd....dd
dd....dd: Server name
Take one of the following actions:

Specify pool in the pd_work_buff_mode operand.

Do not select hash join, subquery hash execution using the client environment definition PDADDITIONALOPTLVL or the pd_additional_optimize_level operand. Also, do not specify HASH in the SQL optimization specification for the join method in the SQL statement or the SQL optimization specification in the subquery execution method.

HASH JOIN Hash join or subquery hash execution
Insufficient private process area
size=dd....dd,server=ee....ee,pid=ff....ff
dd.....dd: Total buffer length for work table in the applicable server process (KB)
ee....ee: server-name
ff....ff: Process-ID
An attempt was made to secure increased buffer area for work tables as specified by the pd_work_buff_expand_limit operand, but was not successful because there was insufficient private process area. Take one of the following actions to ensure there is sufficient memory available:

Reduce the number of concurrently executing processes.

Increase the swap area.

Expand real memory.

Alternatively, take one of the following actions and reduce the usage amount of the work table buffer:

Decrease the value of the PDHASHTBLSIZE operand in the client environment definition or the pd_hash_table_size operand.

Do not use hash join, subquery hash execution in the PDADDITIONALOPTLVL operand in the client environment definition, pd_additional_optimize_level operand, or ADD OPTIMIZE LEVEL in the SQL compile options. Also, do not specify HASH in the SQL optimization specification of the join method in the SQL statement or the SQL optimization specification of the subquery execution method.

KFPA11958-E A

No work HiRDB file system area

An available HiRDB file system area was not specified for storing a work table.

S: Invalidates this transaction.

P: Contact the HiRDB administrator. After the HiRDB administrator finishes the corrective actions, re-execute the transaction.

Action

During execution of the database initialization utility:

Use the pdwork operand in the dictionary server definition or single server definition to specify a HiRDB file system area for storing a work table, then re-execute the database initialization utility.

Other than above:

If the pdwork operand is not specified in the server definition, specify the HiRDB file system area with the pdwork operand, and then restart HiRDB or the server.

If the pdwork operand is specified in the server definition, eliminate the cause of the error based on the KFPH20006-W message that was output when the server starts, and then restart HiRDB or the server.

KFPA11959-E A

HiRDB file "aa....aa" failed, return code=bbbbb,HiRDB file name=cc....cc

"aa....aa" for HiRDB file cc....cc terminated with return code bbbbb.

aa....aa: HiRDB file system function

close: Close HiRDB file.

create: Create HiRDB file.

expand: Expand HiRDB file.

open: Open HiRDB file.

read: Read HiRDB file.

write: Write to HiRDB file.

fstat: Acquire HiRDB file information.

statfs: Acquire HiRDB file system area information.

statdk: Acquire disk information.

bbbbb: Return code

cc....cc: Name-of-HiRDB-file-system-area\Name-of-HiRDB-file

If the path name of the HiRDB file exceeds 143 characters, the last 143 characters of the HiRDB file path name are output.

S: Invalidates this transaction.

P: Contact the HiRDB administrator.

Action

"aa....aa" is expand during execution of the database initialization utility:

If a HiRDB file system area with no expansion specification in the pdwork operand in the server definition is specified, specify a HiRDB file system area with expansion specified and re-execute the database initialization utility. If this error message is output even though the specified HiRDB file system area includes an expansion specification, either specify the HiRDB file system area with the expansion count increased in the pdwork operand in the server definition, or specify the HiRDB file system area with the area length expanded. Then, re-execute the database initialization utility.

"aa....aa" is expand during execution of a utility other than the database initialization utility:

If a HiRDB file system area with no expansion specification in the pdwork operand in the server definition is specified, specify a HiRDB file system area with expansion specified and restart the server. If this error message is output even though the HiRDB file system area includes an expansion specification, either specify the HiRDB file system area with the expansion count increased in the pdwork operand in the server definition, or specify the HiRDB file system with the area length expanded. Then, restart the server.

In other cases:

See 5. HiRDB File System Error Codes to eliminate the cause of the error.

KFPA11964-E A

HiRDB file aa....aa error, errno=bb....bb, HiRDB file name=cc....cc

HiRDB file open or close processing failed.

aa....aa: HiRDB file system function:

{ open |close }

bb....bb: Error code for HiRDB file system

cc....cc: Name-of-HiRDB-file-system-area\Name-of-HiRDB-file

If the path name of the HiRDB file exceeds 131 characters, the last 131 characters of the HiRDB file path name are output.

S: Terminates processing.

P: Contact the HiRDB administrator. After correcting the error, re-execute the UAP.

Action

See 5. HiRDB File System Error Codes to eliminate the cause of the error.

KFPA11966-E A+L

Error occurred on transaction transfer, inf1=aa....aa, inf2=bbbb

An error occurred in transaction processing of the X/Open XA interface.

aa....aa: Processing during which error occurred:

Connect: Reconnection with HiRDB

bbbb: SQL code for the processing during which the error occurred

S: Terminates processing.

P: Eliminate the cause of the error based on the SQL code for the processing underway when the error occurred and the client error log trace information (pderr process-number-*.trc), and then retry the operation.

KFPA11980-E A

Transaction branch already determined

This transaction branch already accepted a completion request from another transaction branch and it has been completed.

S: Ignores this SQL statement.

P: SQL cannot be executed in this transaction branch. Terminate the transaction branch.

O: Inasmuch as a completion request occurred while this transaction branch was being executed, an error may have occurred in the transaction manager. Check the transaction manager's log information.

KFPA11981-E A

Communication error occurred from aa....aa to bb....bb event cc....cc dd....dd ee....ee

Processing cannot continue due to a communication error.

aa....aa: Server name (send side)

If the server name cannot be identified, ******** is displayed.

bb....bb: Server name (receive side)

If the server name cannot be identified, ******** is displayed.

cc....cc: Event that occurred:

Init: Server initialization

Netdown: Network error

System: System error

Termin: Server termination processing

Timeout: Timeout

dd....dd: Debug information 1 (name of the function resulting in the error)

ee....ee: Debug information 2 (return code from the function resulting in the error)

S: Ignores this SQL statement, or invalidates the transaction.

P:

Take an action appropriate to the event:

Init: Re-execute after contacting the HiRDB administrator to start the server.

Termin: Start the server and re-execute.

Other: Contact the HiRDB administrator.

Action

Take an action appropriate to the event:

Init:

Start the server.

Netdown:

Eliminate the cause of the communication error.

Termin:

Start the server.

Timeout:

Correct the communication monitoring interval (pd_lck_wait_timeout) specified in the system definition.

System:

If the server name on the receiving side is that of a dictionary server, and the value of debug information 2 is -330, the process count set for the dictionary server or for the back-end servers is insufficient. If this occurs, increase the value of operand pd_max_dic_process or pd_max_bes_process. In particular, this error tends to occur in multiple front-end server environments when several front-end servers are attempting to acquire definition information from the dictionary server, if the number of processes running on the dictionary server are fewer than the total of those running on the front-end servers.

If the value of debug information 2 is -310, it is possible that the server on the receiving side has stopped. Use the pdls command to confirm that the server has stopped, start the server on the receiving side, and then re-execute.

If the value of debug information 2 is one of the detail codes listed in 4.1 Detail codes for RPC-related errors, take the corresponding action.

Other:

Contact the customer support center.

KFPA11984-E A

Client version incompatible,HiRDB version=aa....aa, client version=bb....bb

The version of the HiRDB client is invalid. The HiRDB client version in use is not supported by the HiRDB system.

aa....aa: Version of HiRDB system

bb....bb: Version of HiRDB client

S: Ignores this request.

P: Check the UAP preprocess, compilation, or linkage for an error. If there is no error, contact the HiRDB administrator.

Action

Contact the customer support center.

KFPA11986-E A

Function "aa....aa"."bb....bb"(cc....cc) executed no "RETURN" statement

Execution of the function "aa....aa"."bb....bb" did not terminate at the RETURN statement.

aa....aa: Authorization identifier

bb....bb: Routine identifier

cc....cc: Special name

S: Either ignores this SQL statement or nullifies the transaction.

P: Redefine the function and re-execute.

KFPA11987-E A

Unable to execute SQL except for rollback and disconnect

Only the ROLLBACK or DISCONNECT SQL statement can be executed.

S: Ignores this SQL statement.

P: Execute the ROLLBACK or DISCONNECT statement.

KFPA11988-E A

Required function [aa....aa] is not supported

The requested function aa....aa is not supported in this system.

aa....aa: Requested, unsupported function (this is output only when the problem is detected on the client side)

DESCRIBE TYPE: DESCRIBE TYPE statement

TYPE OPTION: TYPE OPTION specified in PREPARE statement

XA INTERFACE: XA interface used by the XDM/RD E2 connection facility

ARRAY INSERT: Insert function that uses a matrix

SET SESSION AUTHORIZATION: SET SESSION AUTHORIZATION statement

JAR: INSTALL JAR, REPLACE JAR or REMOVE JAR

SET: SET statement (assignment statement)

SINGLE ROW SELECT: Dynamic single row retrieval

ALLOCATE CURSOR: ALLOCATE CURSOR statement

DEALLOCATE PREPARE: DEALLOCATE PREPARE statement

DESCRIBE: Information acquired by DESCRIBE in a PREPARE statement

EXTENDED STATEMENT NAME: Extended statement name specification

EXTENDED CURSOR NAME: Extended cursor name specification

CLIB: INSTALL CLIB, REPLACE CLIB, or REMOVE CLIB

S: Ignores this SQL statement.

P: When not using function aa....aa, delete the locations where this function is used. To upgrade HiRDB or XDM/RD E2 and use function aa....aa, contact the HiRDB administrator or the XDM/RD E2 system administrator.

O: Confirm the client library linked to the UAP and the version of the server.

Action

Check the client libraries linked to the UAP and the server version. To use the functionality provided by aa....aa, upgrade HiRDB or XDM/RD E2.

KFPA11989-E A

Commit error

An error occurred during commit processing.

S: Invalidates this transaction.

O: Refer to message KFPS00900-I or KFPS00972-I to eliminate the cause of the error and re-execute the UAP.

KFPA11990-E A

Incompatible character code set, HiRDB=aa....aa, client=bb....bb

HiRDB system and client use different character codes.

aa....aa: Character codes at the HiRDB system

bb....bb: Character codes at the HiRDB client

CHINESE: EUC Chinese kanji codes

CHINESE-GB18030: Chinese character encoding GB18030

LANG-C: One-byte character codes

SJIS: Shift JIS kanji codes

UJIS: EUC Japanese kanji codes

UTF-8: Unicode

********: no supported character codes

S: Declines connection to HiRDB.

O: Check that the environmental variables when compiling the UAP (PDCLTLANG or LANG) or the environmental variables when executing (LANG or PDLANG) correspond to the character code classification supported by the HiRDB server. Contact the HiRDB administrator if there are no errors.

KFPA11992-E A

More than 32M bytes SQL OBJECT, size=aa....aa

The SQL object's size exceeded 32MB.

aa....aa: Size of the SQL object that was to be created (in bytes)

S: Invalidates this transaction.

P: Correct the SQL statement so that the size of the SQL object does not exceed 32MB, and re-execute.

KFPA11993-E A

Input data invalid for HASH function

One of the following errors occurred in the input data for a partitioning column:

The input data for the hash function specified in the table definition is too short.

The following data type error occurred:
If the column data type is CHAR(8) (CHAR(16) if the character set is UTF16)
HASH0 or HASHZ was used as the hash function, but the format is not 'YYYYMMDD'.
If the column data type is CHAR(6) (CHAR(12) if the character set is UTF16)
HASH0 was used as the hash function, but the format is not 'YYYYMM'.
YYYY: 0001 to 9999 (year)
MM: 01 to 12 (month)
DD: 01 to the last day of the relevant month and year (day)

S: Ignores this SQL statement.

P: Check whether the hash function specified in the table definition is correct, and correct the table definition if it is incorrect.

If HASH0 or HASHZ is used as the hash function, check whether there is an error in the data type of the input data, and if so, correct the input data.

Make sure that the data length of the hashing target column into which INSERT is being done is no shorter than the minimum data length possible for the hash function specified in the table definition.

If HASH0 is used as the hash function, make sure that the data in the hashing target column uses the format YYYYMMDD or YYYYMM.

If HASHZ is used as the hash function, make sure that the data in the hashing target column uses the format YYYYMMDD.

KFPA11994-E A

Unable to execute definition SQL for holdable cursor opened

Definition SQL cannot be issued because a holdable cursor is open.

S: Ignores this SQL statement.

P: Issue the definition SQL after closing all holdable cursors.

KFPA11996-E A

Holdable cursor lost because of server process down

The holdable cursor could not be inherited. Also, the unit, server, or server process that was opened in the cursor might have terminated abnormally.

S: Ignores this transaction.

P: Eliminate the cause of the error, and then re-execute.

KFPA11997-E

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

An error occurred during the execution of the plug-in (implementation) function.
For queries that include an RDAREA name specification, retrieval is not possible because no index exists for an index-type plug-in-dependent function, or the index is not usable because the number of partitions of the index is different from the number of partitions of the table.

aa....aa: Error detail message

S: Ignores this SQL statement or invalidates the transaction.

P: Take one of the following actions:

Resolve the problem identified in the detailed error message (aa....aa) by referring to the corresponding plug-in manual and re-execute the SQL.

When aa....aa is Enable to use n-gram index (when the error detail message indicates that the necessary index for executing the index-type plug-in-dependent function does not exist) or something similar, and the query includes an RDAREA name specification, not only check whether the index-type plug-in-dependent function exists, but also make sure that the number of partitions of the index is equal to the number of partitions of the table, and then re-execute the SQL statement.

KFPA11998-E A

Unable to manipulate LIST yet, because transaction determination uncomplete

An attempt was made to create, delete, or search a list before the previous transaction had completed. This error occurs when reconnect is performed before recovery processing is completed after processing in a single server or back-end server has aborted.

S: Takes one of the following actions:

SQL statement
Ignores this SQL statement.

pdmod
Continues processing.

P: Take one of the following actions:

SQL statement
Wait for the transaction to be completed or complete the transaction manually, and then re-execute the SQL statement.

pdmod
Wait for the transaction to be completed or complete the transaction manually, and then re-create or delete the list.

KFPA12000-I A

Processing of SQL completed

Execution of SQL statement has been completed.

S: Executes processing.

KFPA12100-I A

No rows satisfying search condition

No row satisfies the condition. Or, row fetch has been completed.

S: Resumes processing.

KFPA12110-I A

Row already deleted or updated

Row that was to be retrieved via a search using a list had been deleted; the row's attribute value had been deleted or updated.

S: Continues processing.

KFPA12120-I A

Processing of SQL completed, dynamic result set returned

SQL statement execution has been completed, and a dynamic results set has been returned.

S: Continues processing

KFPA12121-I A

Processing of SQL completed, additional result set returned

Execution of the SQL statement has been completed. Furthermore, there is an additional result set.

S: Continues processing.

KFPA12300-I A

RDAREA usage aaa%, RDAREA="bb....bb"cc....cc

Meaning depends on the circumstances:

System definition pd_rdarea_warning_point not specified:

User RDAREA, user LOB RDAREA:

The system started using the segment with relative location aaa% among all the segments of the last file in RDAREA "bb....bb".

System definition pd_rdarea_warning_point specified:

User RDAREA:

The system started using the segment with usage factor aaa% among all the segments in the entire RDAREA "bb....bb". The current number of unused segments is cc....cc.

User LOB RDAREA:

The system started using the segment with relative location aaa% among all the segments in the entire RDAREA "bb....bb". The number of remaining segments for maintaining effective performance is cc....cc.#

#: Effective performance:

In the case of a user LOB RDAREA, the highest throughput can be achieved when the database area has not been used through the end. The effective performance indicates the high throughput status. Once a database is used through the end, throughput becomes lower. Therefore, some action such as database reorganization must be taken beforehand.

aaa: One of the following is displayed:

Relative location of the segment being used in the last file in the RDAREA

Segment usage factor in the entire RDAREA

Relative location in the RDAREA of the segment being used

bb....bb: Applicable RDAREA name

cc....cc: Additional information about segment usage factor, dd....dd segments unused (dd....dd: number of remaining segments)

S:

Resumes processing.

If there is not enough space to allocate a new segment in this RDAREA but there is some space in existing segments used for addition or updating, the system continues processing using those segments.

This message is displayed again if the indicated segment is used after it was released due to table deletion, reorganization, etc.

P: Contact the HiRDB administrator.

Action

Use the command or utility shown below to check the remaining space in the RDAREA, then take the appropriate action shown in the table.

Command for checking the remaining space:

Database status display command (pddbls):
Specifying the -a option displays the RDAREA usage status. This command can be used for all RDAREAs.

Database condition analysis utility (pddbst):
Physical or logical analysis displays the RDAREA usage status. This utility can be used for data dictionaries, user RDAREAs, and LOB RDAREAs.

Action

The table below shows the action:

Type of RDAREA
System definition pd_rdarea_warning_point not specified
System definition pd_rdarea_warning_point specified

User RDAREA

Check the usage status of the RDAREA by using the database status display command (pddbls) or the database condition analysis utility (pddbst).

Reorganize the table in the RDAREA according to the usage status. Or, extend the RDAREA.

Check the usage status of the RDAREA by using the database status display command (pddbls) or the database condition analysis utility (pddbst) or check the additional information about segment usage factor displayed in the message.

Reorganize the RDAREA in units of table RDAREAs or tables according to the usage status. Or, extend the RDAREA.

User LOB RDAREA

Check the usage status of the RDAREA by using the database status display command (pddbls) or the database condition analysis utility (pddbst).

Reorganize the user LOB RDAREA in units of user LOB areas or tables according to the usage status. Or, extend the RDAREA.

Check the usage status of the RDAREA by using the database status display command (pddbls) or the database condition analysis utility (pddbst) or check the additional information about segment usage factor displayed in the message.

Reorganize the user LOB RDAREA in units of user LOB RDAREAs or tables according to the usage status. Or, extend the RDAREA.

KFPA12350-W A+L

Column "aa....aa" added to FIX table "bb....bb"."cc....cc"

Column aa....aa was added to FIX table bb....bb.cc....cc using ALTER TABLE.

aa....aa: Name of added column

bb....bb: Authorization identifier of the table to which the column was added

cc....cc: Table identifier of the table to which the column was added

S: Continues processing.

P: Column aa....aa, which was added to table bb....bb.cc....cc, was added by excising it from a reserved column. Because 0x00 is stored regardless of the data type when the values are added, update the added column with meaningful values before using it.

KFPA19101-E A

Invalid SQL optimization specification for aa....aa

The following error was detected in the SQL optimization specification:

An SQL optimization specification in the subquery execution method was specified in a subquery other than the one in the predicate.

aa....aa: subquery

S: Ignores this SQL statement.

P: Correct this SQL statement and re-execute.

KFPA19102-E A

Invalid file name "aa....aa" specified in client environment definition PDDELRSVWDFILE

The following error occurred in the value specified for the client environment definition PDDELRSVWDFILE.

This specifies a file name other than that specified by the system common definition pd_delete_reserve_word_file operand.

aa....aa: File name specified in the client environment definition PDDELRSVWDFILE.

S: Rejects the connection with HiRDB.

P: Set the value specified in the client environment definition PDDELRSVWDFILE to the value specified in the system common definition pd_delete_reserve_word_file operand.

KFPA19104-E A

Invalid aa....aa "bb....bb" in character set specification

One of the following specification errors was found:

Schema name

Character set name

aa....aa: {schema name|character set name}

bb....bb: {schema-name-other-than-MASTER|character-set-that-has-not-been-defined}

S: Ignores this SQL statement.

P: Correct the SQL statement as explained below, and then re-execute.

If a schema name is invalid, correct it by changing the schema to MASTER or omitting it.

If a character set name is invalid, change it to the correct character set name.

KFPA19105-E A

Specified value specification invalid in RDAREA name specification

One of the following values was invalidly specified in the RDAREA name.

A character string literal or a literal other than a mixed character string literal.

A data type that is an SQL variable or SQL parameter other than CHAR, VARCHAR, MCHAR, or MVARCHAR.

USER value function

CURRENT_DATE value function

CURRENT_TIME value function

CURRENT_TIMESTAMP value function

SQLCODE

SQLCOUNT

SQLCODE_OF_LAST_CONDITION

SQLERRM_OF_LAST_CONDITION

S: Ignores this SQL statement.

P: For the RDAREA name specification, use values other than those listed above to specify VARCHAR, MCHAR, and MVARCHAR data type values, and then re-execute.

KFPA19106-E A

Unable to define reserved column except as last column in table

Only the last column of the table can be specified as a reserved column. No other columns are permitted.

S: Ignores this SQL statement.

P: Correct the SQL so that the last column of the table is specified as the reserved column, and then retry the operation.

KFPA19110-E A

Unable to specify "aa....aa" statement in FOR statement because cursor is not holdable

If there is no holdable cursor declared by the FOR statement, the SQL procedure statements in the FOR statement cannot specify the COMMIT, ROLLBACK, or PURGE TABLE statements.

aa....aa: SQL statements that cannot be specified:

{COMMIT | ROLLBACK | PURGE TABLE}

S: Ignores this SQL statement and rolls back.

P: Revise the SQL statement, and re-execute.

KFPA19111-E A

Table name missing except preparable dynamic "aa....aa" statement:positioned.

A table name is missing when preprocessing of an UPDATE or DELETE statement using a cursor is not being performed.

aa....aa: Erroneous SQL statement

{UPDATE | DELETE}

S: Ignores this SQL statement.

P: Revise the SQL statement, and re-execute.

KFPA19130-E A

Authorization identifier specified for public aa....aa in bb....bb

An authorization identifier cannot be specified in a public routine.

aa....aa: routine

bb....bb: Statement in which the authorization identifier was specified

{CREATE PUBLIC FUNCTION

|CREATE PUBLIC PROCEDURE

|DROP PUBLIC FUNCTION

|DROP PUBLIC PROCEDURE}

S: Ignores this SQL statement.

P: Delete the authorization identifier.

KFPA19140-E A

aa....aa specified in definition of bb....bb

One of the following errors was detected in the specification for the SQL procedure statement or external routine:

If aa....aa is EXTERNAL NAME

The external routine is specified if SQL was specified for the LANGUAGE clause or if the LANGUAGE clause has been omitted.

If aa....aa is SQL procedure statement

The SQL procedure statement is specified if JAVA or C has been specified for the LANGUAGE clause.

aa....aa: {External name|SQL procedure statement}

bb....bb: {SQL routine|external routine}

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA19150-E A

Unable to specify data type other than DATE or TIME type for column "aa....aa" with "SYSTEM GENERATED"

The data type of the column specifying SYSTEM GENERATED was not the DATE type or the TIME type.

aa....aa: The alias specified by mistake

S: Ignores this SQL statement.

P: Correct this SQL statement and re-execute.

KFPA19170-E A

Invalid argument of SQL/XML scalar function or SQL/XML predicate

One of the following errors occurred in an SQL/XML scalar function or predicate argument.

The XML query context items of the XMLQUERY or XMLEXISTS argument are specified two or more times.

The VERSION or XMLSERIALIZE argument is specified as a value other than 1.0.

An XML query context item is specified as an XQuery query in an XMLQUERY argument that specifies an XQuery transform expression.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA19171-E A

Invalid token "aa....aa" appeared in bb....bb, query-no=ccc

The term aa....aa specified in the bb....bb argument is invalid. Another possibility is that aa....aa was specified at the end of the bb....bb name without using the left parenthesis.

aa....aa: Invalid term that does not follow the structure rules

bb....bb: { XML constructor | XMLQUERY | XMLSERIALIZE | XMLPARSE | XMLAGG | XMLEXISTS }

ccc: Query number

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA19180-E A

Duplicate prefix "aa....aa" in XQuery expression or partial structure path

The aa....aa prefix specified in the XQuery or substructure is specified more than once. The same prefix cannot be declared more than once for an XML namespace.

aa....aa: Duplicate prefix (first 30 characters)

S: Ignores this XQuery specification or substructure specification.

P: Correct the duplicate prefix and re-execute.

KFPA19181-E A

Prefix "aa....aa" not declared in XQuery expression or partial structure path

The aa....aa prefix specified in the XQuery or substructure has not been declared in the XML namespace.

aa....aa: Prefix without declaration (first 30 characters)

S: Ignores this XQuery specification or substructure specification.

P: Correct the prefix or declare it in the XML namespace, and then re-execute.

KFPA19182-E A

Invalid floating point numeric literal aa....aa in XQuery expression

The format of the floating-point numeric literal specified in the XQuery is invalid.

aa....aa: invalid floating-point numeric literal (first 30 characters)

S: Ignores this XQuery specification.

P: Correct the floating-point numeric literal and re-execute.

KFPA19183-E A

Invalid part "aa....aa" in XQuery expression or partial structure path

One of the following errors was detected in an XQuery or substructure specification:

Excess characters were detected at the end of the XQuery or substructure specification.

A syntactically invalid character or keyword was specified.

The first keyword in the XQuery specification or substructure specification is invalid.

aa....aa: The first 30 characters and hexadecimal digits that follow enclosed in parentheses, corresponding to the invalid part or syntactically invalid characters in the XQuery or substructure specification

S: Ignores this XQuery specification or substructure specification.

P: Correct the syntax of the XQuery or substructure specification, and then re-execute.

KFPA19184-E A

Incomplete XQuery expression or partial structure path

An XQuery specification or substructure specification is not complete.

S: Ignores this XQuery specification or substructure specification.

P: Complete the XQuery or substructure specification, and re-execute.

KFPA19185-E A

Invalid token "bb....bb" after token "aa....aa" in XQuery expression or partial structure path

Syntactically, bb....bb cannot follow aa....aa in an XQuery or substructure specification.

aa....aa: Last character string that satisfies the syntax rules (first 30 characters)

bb....bb: Syntactically invalid character string (first 30 characters)

S: Ignores this XQuery specification or substructure specification.

P: Because either of the following errors is possible, correct the XQuery or substructure specification accordingly and then re-execute.

The specification contains a syntax error.

The order of expressions is invalid.

KFPA19186-E A

Invalid numeric literal aa....aa in XQuery expression

The numeric literal specified in the XQuery contains a syntax error.

aa....aa: Invalid numeric literal (first 30 characters)

S: Ignores this XQuery specification.

P: Correct the numeric literal and re-execute.

KFPA19187-E A

Numeric literal out of range in XQuery expression

A numeric literal specified in the XQuery is outside the following permitted range:
Integer literal: -2,147,483,648 to 2,147,483,647
Decimal numeric literal: there are 38 or fewer displayed digits, and 10³⁸ to (10³⁹ - 1)
Floating point numeric literal: 4.9E-324 to 1.7E+308

S: Ignores this XQuery specification.

P: Correct the specification of the numeric literal and re-execute.

KFPA19188-E A

Invalid XQuery function "aa....aa" in XQuery expression

The XQuery function aa....aa specified in the XQuery was not found.

aa....aa: XQuery function name that does not exist (first 30 characters)

S: Ignores this XQuery specification.

P: Make sure that there are no invalid or unsupported XQuery function name prefixes or local names. Then correct the XQuery specification as needed and re-execute.

KFPA19189-E A

XQuery variable in "return" clause different from XQuery variable in "copy" clause, in transform expression of XQuery, XQuery-no=aaa

You cannot specify an XQuery transform in the return clause of an XQuery transform expression that is different from the XQuery transform specified in the copy clause. Specify the same XQuery transform specified in the copy clause in the return clause of the XQuery transform.

aaa: Query number of the XQuery resulting in an error

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA19198-E A

aa....aa missing in bb....bb statement for memory table access in XDS

The lock option WITHOUT LOCK NOWAIT was not specified in the SELECT statement that searches the memory database allocation table. When the memory database allocation table is searched, either the lock option WITHOUT LOCK NOWAIT must be specified in the SELECT statement or 0 must be specified in the client environment definition PDISLLVL.

aa....aa: WITHOUT LOCK NOWAIT

bb....bb: SELECT

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA19200-E A

Unable to specify referential constraint or check constraint without specifying "pd_check_pending" operand

Because there is no system common definition pd_check_pending specification, a referential constraint or check constraint is not allowed.

S: Ignores this SQL statement.

P: Remove the referential constraint or check constraint definition statement part of the SQL statement, and re-execute. Or, ask the HiRDB administrator for the addition of a system common definition pd_check_pending.

KFPA19203-E A

Invalid value expression "aa....aa", query-no=bbb

An invalid specification exists in the value expression aa....aa.

If aa....aa is NEXT VALUE:

The NEXT VALUE expression cannot be specified in the following locations:

A location other than the selection expression and insertion value of the query specification of the INSERT statement query, or other than the update value of the UPDATE statement.

Subquery

CASE expression

Scalar function VALUE

Set function

Query containing WINDOW function

Query containing DISTINCT function

Query containing GROUP BY clause, the HAVING clause, and the set function.

Query containing a set operation other than UNION ALL

aa....aa: NEXT VALUE

bbb: Query number

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA19212-E A

Unable to specify expression except embedded variable or ? parameter in assignment statement for embedded SQL

One of the following errors occurred in the specification of the assignment target or assignment value of the assignment statement:

A value expression other than an embedded variable or ? parameter is specified as the assignment target.

A value expression other than an embedded variable, ? parameter, scalar function LENGTH, scalar function SUBSTR, or scalar function POSITION is specified as the assignment target.

An item other than an embedded variable or a ? parameter is specified as the value expression in the scalar function LENGTH, the value expression 1 of the scalar function SUBSTR, or the value expression 2 of the scalar function POSITION specified in the assignment value.

One of the following is specified as the assignment value:
A value expression that includes a column specification
A value expression that includes a component specification that shows the attribute of an abstract data type column

S: Ignores this SQL statement.

P: Revise this SQL statement, and re-execute.

KFPA19219-E A

Unable to specify column "aa....aa" in "ORDER BY" clause,due to derived column, in XDS

When you are accessing the memory database allocation table, you cannot specify the column name aa....aa in the ORDER BY clause, because it is not a colum that is output based on only a column specification.

aa....aa: Column name specified in the ORDER BY clause

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA19220-E A

Invalid cursor name "aa....aa" in "bb....bb" statement

The cursor name declared in the FOR statement cannot be specified in the OPEN, CLOSE, or FETCH statement.

aa....aa: Cursor name

bb....bb: SQL statement that cannot be specified

{OPEN | CLOSE | FETCH}

S: Ignores this SQL statement and rolls back.

P: Revise the SQL statement, and re-execute.

KFPA19221-E A

Invalid cursor specification in FOR statement.

One of the following errors occurred in the cursor specification specified in the FOR statement:

An unnamed column is specified in a derived column.

In the FROM clause of a derived column, a repetition column with no unnesting specification and no subscript was specified.

There are duplicate instances of the derived column name of a derived column.

S: Ignores this SQL statement and rolls back.

P: Revise the SQL statement, and re-execute.

KFPA19222-E A

Specified view aa....aa."bb....bb" unusable,because "pd_sql_dec_op_maxprec" changed

If you change the specification value of the pd_sql_dec_op_maxprec operand in the system common definition, no operations can be performed on the following viewed tables of those viewed tables defined prior to the change.

A viewed table defined in a version prior to 08-04

A viewed table that was defined specifying any of the following operations:
- Arithmetic operation for DECIMAL type data of 29 digits or less only
- Set function AVG/SUM for DECIMAL type data of 29 digits or less only
- Scalar function MOD for DECIMAL type data of 29 digits or less only
- Scalar function in which precision was omitted because the argument type is FLOAT

aa....aa: Authorization identifier

bb....bb: Viewed table identifier

S: Ignores this SQL statement.

P: Delete the invalid viewed table(s), revise the definition, and then re-execute.

KFPA19225-E A

Invalid use of memory table due to aa....aa

The method of using the memory database allocation table is invalid.

aa....aa: Detailed information on error

aa....aa
Meaning
Action to take

access to memory table from compatible client library
S: One of the following operations is being performed:

A memory database allocation table operation is being performed from the UAP that used the client library for the server providing the primary facilities.

A utility that does not support the memory database allocation table is being executed on the memory database allocation table.

If 1:
When performing an operation on the memory database allocation table, use the XDS client library.
If 2:
Revise the table to be processed by the utility, specify a correct table if there are any errors, and then re-execute the command.
To execute the utility on the memory database allocation table, release memory database allocation of the table once, and then re-execute the utility.

access to different XDS from connected XDS
The specified memory database allocation table is stored in a different XDS than the one to which you are connected.
Revise the connection destination and connect to the host on which the XDS exists that is stored in the specification table.

unsupported memory table and disk table mixing
A mix of tables has been specified in one SQL statement: tables to be added and tables not to be added to the memory database.
Revise the SQL statement so that tables to be added to the memory database are not mixed with other tables in a single SQL statement.

memory table in WITH clause
The memory database allocation table is specified in the WITH clause query.
Either correct the SQL statement so that the memory database allocation table is not specified in the WITH clause query, or deallocate the specified table from the memory database.

memory table in Java stored procedure
The memory database allocation table is specified in the Java stored procedure.
Either correct the memory database allocation table so that it is not specified in the Java stored procedure, or release memory database allocation of the table.

S:

When the SQL statement executes: ignores this SQL statement.

When the utility executes: terminates the processing.

P: When the SQL statement executes, revise the SQL statement according to the aa....aa action procedure, and then re-execute.

O: When the utility executes, revise the utility command line according to the aa....aa action procedure, and then re-execute.

KFPA19254-E A

Subquery specified in aa....aa

A subquery was specified in an invalid location.

aa....aa: {set function|assignment statement|RETURN statement|CALL statement|WRITE specification|WRITE LINE statement}

S: Ignores this SQL statement.

P: Revise the SQL statement, and re-execute.

KFPA19270-E A

Invalid item specified AS aa....aa in bb....bb,query-no=ccc,arg-no=ddddd

One of the following errors was detected in aa....aa specified in the bb....bb argument.

If aa....aa is value expression:

When bb....bb is XML constructor
An item other than an SQL variable, SQL parameter, embedded variable, or ? parameter is specified in a value expression.

When bb....bb is XMLSERIALIZE
An item other than a column specification, XMLQUERY, or XMLAGG is specified in a value expression.
Another possibility is that a named derived table column derived from an item other than a column specification is specified.

When bb....bb is XMLAGG
An item other than a column specification or XMLQUERY is specified in a value expression.
Another possibility is that a named derived table column derived from an item other than a column specification is specified.

When bb....bb is XMLPARSE:
A labeled interval is specified in a value expression.

If aa....aa is XML query context item:

Either a value expression other than a column specification, or a column of a table whose name was derived according to a value expression other than a column specification, is specified in the XML query context item that was specified as the ddddd XML query argument.

If aa....aa is XML query context item:

One of the following items is specified in the value expression of the XML query variable specified as the ddddd XML query argument:

Component specification

A table whose name was derived according to a component specification.

Unary operation for the ? parameter or embedded variable

SQLCODE, SQLCODE_OF_LAST_CONDITION, SQLCOUNT, or SQLERRM_OF_LAST_CONDITION

aa....aa: {value expression|XML query context item|XML query variable}

bb....bb: {XML constructor|XMLQUERY|XMLSERIALIZE|XMLAGG| XMLEXISTS|XMLPARSE}

ccc: Query number

ddddd: Argument or XML query argument number

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA19271-E A

Invalid data type of aa....aa in bb....bb, query-no=ccc, arg-no=ddddd

An error was detected in the aa....aa data type specified in bb....bb.

If bb....bb is XMLQUERY, XMLSERIALIZE, XMLAGG, or XMLEXISTS:

A data type other than XML is specified in the ddddd aa....aa.

If bb....bb is XML constructor:

A data type other than BINARY is specified in the argument.

If bb....bb is XMLPARSE:

A data type other than the displayed data type is specified in the argument. Alternatively, a character set is specified in the argument.

Character string data type (CHAR, VARCHAR)

Mixed character string data type (MCHAR, MVARCHAR)

BINARY type

aa....aa: {argument|XML query context item}

bb....bb: {XML constructor|XMLQUERY|XMLSERIALIZE|XMLPARSE|XMLAGG|XMLEXISTS}

ccc: Query number

ddddd: Argument or XML query argument number

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA19272-E A

Data type of XML query variable in aa....aa inconvertible to XQuery data type, query-no=bbb, arg-no=ccccc

The data type for the value expression specified in the XML query variable in the aa....aa argument cannot be converted to the XQuery data type.

The data type cannot be converted to an XQuery data type.

INTERVAL YEAR TO DAY

INTERVAL HOUR TO SECOND

BLOB

BINARY

BOOLEAN

Abstract data type

aa....aa: { XMLQUERY | XMLEXISTS }

bbb: Query number

ccccc: XML query argument number

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA19273-E A

Unable to specify "BY VALUE" for variable except XML type in aa....aa, query-no=bbb, arg-no=ccccc

BY VALUE cannot be specified to an XML query for which a value expression result is a data type other than an XML data type.

aa....aa: { XMLQUERY | XMLEXISTS }

bbb: Query number

ccccc: XML query argument number

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA19274-E A

XML query variable "aa....aa" duplicate in bb....bb, query-no=ccc, arg-no=ddddd

The name of the XML query variable aa....aa that was specified in bb....bb is a duplicate.

aa....aa: XML query variable

bb....bb: { XMLQUERY | XMLEXISTS }

ccc: Query number

ddddd: XML query argument number

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA19275-E A

No input value to XQuery variable "aa....aa" in bb....bb, query-no=ccc

There is no input value for the XQuery variable aa....aa in bb....bb.

aa....aa: XQuery variable (maximum of 30 bytes displayed)

bb....bb: { XMLQUERY | XMLEXISTS }

ccc: Query number

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA19277-E A

Unable to specify RDAREA name specification for bb....bb aa....aa

The RDAREA name cannot be specified in aa....aa.
The RDAREA name could not be specified in the following table bb....bb.

Read-only viewed table (read-only view)

Query name (query name)

Temporary table (temporary table)

aa....aa: authorization-identifier."table-identifer", or the query name.

bb....bb: { read-only view|query name|temporary table }

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA19290-E A

Unable to specify aa....aa in bb....bb

The following items cannot be specified in the search condition of a check constraint definition or in a trigger action condition.

Search condition of a check constraint

Subquery

Set function, or SQL/XML set function

Repetition column

Embedded variable or ? parameter

USER value function

CURRENT DATE value function

CURRENT TIME value function

CURRENT TIMESTAMP value function

Columns not defined in a table definition

For a single column check constraint, a column not defined in the column specification

A value expression of an abstract data type

User-defined function

Structured repetition predicate

CAST specification that specified conversion from TIME to TIMESTAMP

Scalar function VARCHAR_FORMAT that specifies TIME in the value expression

Scalar function IS_USER_CONTAINED_IN_HDS_GROUP

Window function

SQL/XML scalar function

Reserved column

Trigger action condition

Subquery

Set function

Repetition column

Embedded variable, or ? parameter

A column not qualified by an old or new values correlation name

Value expression in the abstract data type

Plug-in function

Java stored function

Structured repetition predicate

Window function

SQL/XML scalar function

Reserved column

aa....aa: Error causing conditions:

{ subquery| set function| SQL/XML set function| array column

| variable or parameter

| column "column-name" unqualified by old or new values correlation name

| value expression of abstract data type

| PLUGIN function| JAVA function| ARRAY predicate

| function invocation| USER| CURRENT_DATE

| CURRENT_TIME| CURRENT_TIMESTAMP| column "column-name"

| CURRENT_DATE implied by scalar function VARCHAR_FORMAT or cast specification

| scalar function IS_USER_CONTAINED_IN_HDS_GROUP

| window function

| SQL/XML scalar function

| reserved column "column name"}

bb....bb:{triggered action condition|check constraint definition}

S: Ignores this SQL statement and rolls back.

P: Correct this SQL statement and re-execute.

KFPA19291-E A

Invalid use of "LIMIT" clause

One of the following errors was detected in the usage of the LIMIT clause:

A column qualified by an old or new values correlation name was specified as the maximum row count or offset row count.

The total value that can be specified in the maximum row count and offset row count exceeds 2,147,483,647.

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Correct the SQL statement and re-execute.

KFPA19292-E A

Unable to specify outer reference column "aa....aa" with data type "BINARY", query-no=bbb

The BINARY data type cannot be specified for a column that makes an external reference.

aa....aa: Name of column that made an external reference

However, when an incorrectly specified column is in a named derived table, the column name of the base table for the applicable named derived table is displayed.

bbb: The number of the query specifying the column that made an external reference.

S: Ignores this SQL statement. However, a definition SQL statement rolls back.

P: Correct this SQL statement and re-execute.

KFPA19293-E A

Invalid handler declaration or condition declaration code=aa(bb....bb)

An error was detected in the condition declaration or handler declaration.

aa: Reason code

bb....bb: Additional error information

The following table shows each reason code and the corresponding additional information or meaning.

Reason code (aa) | Additional information (bb....bb) | Meaning
01 | Condition name "cc....cc" already declared | Condition name cc....cc specified in the condition declaration was already defined.
02 | SQLCODE value "dd....dd" in condition "cc....cc" already declared in other condition declaration | SQLCODE value dd....dd specified in condition declaration cc....cc was already defined as the SQLCODE value of another condition declaration.
03 | Condition name "cc....cc" in handler declaration not found | The condition name cc....cc specified in the handler declaration was not found.
04 | Unable to specify SQLCODE value or condition name together with "SQLERROR" or "NOT FOUND" | If either SQLERROR or NOT FOUND is specified in the condition value for the handler declaration, the SQLCODE value or condition name cannot be specified in the same handler declaration.
05 | Duplicate condition value | The same SQLCODE value or condition name cannot be specified multiple times in the condition value of the handler declaration. Also, a condition name expressing the same SQLCODE as the SQLCODE value cannot be specified.
06 | Unable to specify same condition as condition in other handler declaration | A condition value expressing the same condition cannot be specified in another handler declaration.
07 | Zero specified in SQLCODE value | 0 is specified in the SQLCODE value of the condition declaration or handler declaration.

S: Ignores this SQL statement and rolls back.

P: Correct this SQL statement and re-execute.

KFPA19294-E A

Invalid signal value aa....aa

One of the following errors was detected in the signal value:

(1) The condition name aa....aa specified in the signal value was not found.

(2) One of the following errors was detected in SQLSTATE value aa....aa specified in the signal value:

A literal other than a character literal less than 5 digits long was specified.

Values other than uppercase letters between A and Z or numerals 0-9 were specified.

The numerals 0-5, the uppercase letters A-I, and R were specified in the first character.

aa....aa: {"condition-name"|SQLSTATE "SQLSTATE-value"}

S: Ignores this SQL statement and rolls back.

P: Correct the SQL statement and re-execute.

KFPA19295-E A

Invalid specification in UPDATE statement with update trigger

The following manipulations cannot be performed on a table with a trigger that uses UPDATE as an event:

Updating using component specifications on tables with a trigger defined that uses a new values correlation name

Updating BLOB type data using a concatenation operation or BINARY type data with a definition length of 32,001 bytes or more in a table defining UPDATE as the trigger.

S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).

P: Correct this SQL statement and re-execute.

KFPA19296-E A

Unable to translate character string literal from default character set to character set aa....aa

You cannot compare or convert the character string literal of a pre-existing character set to a character string of an assignment target character set.

aa....aa: UTF16

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA19311-E A

Unable to generate aa....aa type key from value on specified partial structure due to bb....bb, index ID=cc....cc

aa....aa data type key values cannot be generated from substructure values specified in substructure index definitions.

If bb....bb is unmatched types:

Substructure XQuery data types that are not xs:untypedAtomic or key value SQL data types are not supported.

If bb....bb is invalid format:

Character string formats for substructure values that are xs:untypedAtomic type are invalid.

If bb....bb is invalid length:

The substructure value length is invalid.

aa....aa: Data type of a key value in the substructure index.

{INTEGER|DECIMAL|FLOAT|VARCHAR}

bb....bb: Reason for the error

{unmatched types|invalid format|invalid length}

cc....cc: Index number

For CREATE INDEX, ********** is displayed.

S: Ignores this SQL statement. The system may also invalidate this transaction.

P:

When bb....bb is unmatched types:

If the executed SQL is data manipulation SQL, correct the XML schema so that the XQuery data type of the substructure supports xs:untypedAtomic types or key value SQL data types, re-parse the XML text, and then re-execute.

If the executed SQL is a definition in the substructure index, correct the SQL data type of the key value to a data type corresponding to the XQuery data type for the substructure, and then re-execute.

For details about compatibility between the XQuery data type and SQL data type, see the manual HiRDB Version 9 SQL Reference.

If bb....bb is invalid format:

If the executed SQL is data manipulation SQL, correct the substructure value so that it is a format that can be converted to a key value SQL data type, and then re-execute.

If the executed SQL is a definition in the substructure index, correct the SQL data type of the key value to a data type that can be converted to the substructure value, and then re-execute.

If bb....bb is invalid length:

If the executed SQL is data manipulation SQL, correct the substructure to a value that can be stored in the SQL data type length of the key value, and then re-execute.

If the executed SQL is a definition in the substructure index, correct the length of the SQL data type of the key value to a length that can be stored by the substructure value, and then re-execute.

KFPA19313-E A

Result of XML serialization too long

The result of changing XML type values to value columns (conversion to character string) is too long.
The value must be equal to or less than the maximum length of the data type specified in AS data type of the XMLSERIALIZE function.

S: Ignores this SQL statement. The system may also invalidate this transaction.

P: Change the maximum length of the data type specified in the AS data type of the XMLSERIALIZE function to a length that can be stored in the value column change result. Also, if 32,000 bytes is exceeded, specify the BINARY type.

KFPA19318-E A

Unable to specify XQuery function "aa....aa", because IXXML index unavailable, XQuery-no=bb....bb

The XML type full-text search index cannot be used for one of the following reasons. Therefore, the XQuery function aa....aa cannot be used.

The XML type full-text search index was not defined in the column specified in the XML query context item.

The substructure path specified in the first argument does not match the usage conditions of the XML type full-text search index.

aa....aa: XQuery function name {hi-fn:contains}

bb....bb: Number of the XQuery query resulting in an error

S: Ignores this SQL statement.

P: If the XML type full-text search index was not defined in the column specified in the XML query context item, define it. If the XML type full-text search index is defined in the column specified in the XML query context item, check the usage conditions of the XML type full-text search index, and correct them so that the substructure path specified in the first argument matches the usage conditions of the XML type full-text search index. For details about the usage conditions of the XML type full-text search index, see the HiRDB Version 9 Installation and Design Guide.

KFPA19319-E A

Conflicting types "aa....aa" and "bb....bb" in XQuery sequence for XQuery function "cc....cc", XQuery-no=dd....dd

XQuery sequences into which non-comparable XQuery data type values have been mixed are specified as XQuery sequence cc....cc.

aa....aa: The XQuery data type 1 value included in the XQuery sequence.

{xs:string | xs:decimal | xs:int

| xs:double | xs:dateTime | xs:date

| xs:time | xs:hexBinary | xs:boolean | xs:untypedAtomic}

bb....bb: The XQuery data type 2 value included in the XQuery sequence.

{xs:string | xs:decimal | xs:int

| xs:double | xs:dateTime | xs:date

| xs:time | xs:hexBinary | xs:boolean | xs:untypedAtomic}

cc....cc: XQuery function name

{fn:max|fn:min}

dd....dd: Number of the XQuery query resulting in an error

S: Ignores this SQL statement.

P: Correct the XQuery query so that the evaluation results of the argument specified in the XQuery function become an XQuery sequence configured from comparable XQuery data type values only, and then re-execute.

KFPA19320-E A

Unable to convert "aa....aa" type value to "bb....bb" type in XQuery due to cc....cc, XQuery-no=dd....dd

The XQuery data type aa....aa value cannot be converted to the XQuery data type bb....bb value.

If cc....cc is invalid format:

The format of a character string prior to conversion is invalid.

If cc....cc is out of range:

The value prior to conversion cannot be reflected in the XQuery data type after conversion.

If cc....cc is incompatible types:

The XQuery data type prior to conversion and the type after conversion are not a combination that can be converted.

aa....aa: XQuery data type prior to conversion

{ xs:string | xs:decimal | xs:int | xs:double | xs:dateTime | xs:date | xs:time | xs:hexBinary | xs:boolean | xs:untypedAtomic}

bb....bb: XQuery data type after conversion

{ xs:decimal | xs:int | xs:double | xs:dateTime | xs:date | xs:time | xs:hexBinary | xs:boolean }

cc....cc: Reason for the error

{ invalid format | out of range | incompatible types }

dd....dd: Number of the XQuery query resulting in an error

S: Ignores this SQL statement.

P:

If cc....cc is invalid format:

P: Correct the XQuery query so that the format of the character string prior to conversion is correct, and then re-execute. For details about the format of XQuery data type character strings, see the manual HiRDB Version 9 SQL Reference.

If cc....cc is out of range:

P: Correct the XQuery query so that the value prior to conversion can be expressed in the XQuery data type after conversion, and then re-execute.

If cc....cc is incompatible types:

P: Correct the XQuery query so that the XQuery data type prior to conversion and the data type after conversion become a convertible combination, and then re-execute. For details about the combinations of XQuery data types that can be converted, see the manual HiRDB Version 9 SQL Reference.

KFPA19321-E A

Unable to compare "aa....aa" type value with "bb....bb" type value in XQuery, XQuery-no=cc....cc

The aa....aa and bb....bb XQuery data type values cannot be compared.

aa....aa: XQuery data type of first operation item

{ xs:string | xs:decimal | xs:int | xs:double | xs:dateTime | xs:date | xs:time | xs:hexBinary | xs:boolean | xs:untypedAtomic}

bb....bb: XQuery data type of second operation item

{ xs:string | xs:decimal | xs:int | xs:double | xs:dateTime | xs:date | xs:time | xs:hexBinary | xs:boolean | xs:untypedAtomic}

cc....cc: Number of the XQuery query resulting in an error

S: Ignores this SQL statement.

P: Correct the XQuery query so that the XQuery data types of the first and second operation items become a combination that can be compared, and then re-execute. For details about combinations of XQuery data types that can be compared, see the manual HiRDB Version 9 SQL Reference.

KFPA19322-E A

Unable to perform aa....aa operation between "bb....bb" type value and "cc....cc" type value in XQuery, XQuery-no=dd....dd

In the bb....bb and cc....cc XQuery data type values, it is not possible to execute the aa....aa arithmetic operation.

aa....aa: Type of arithmetic operation in which the error occurred

{ addition | subtraction | division | multiplication | idiv | mod }

addition: Addition

subtraction: Subtraction

division: Division

multiplication: Multiplication

idiv: Integer division

mod: Modulus calculation

bb....bb: XQuery data type of first operation item

{ xs:string | xs:decimal | xs:int | xs:double | xs:dateTime | xs:date | xs:time | xs:hexBinary | xs:boolean | xs:untypedAtomic}

cc....cc: XQuery data type of second operation item

{ xs:string | xs:decimal | xs:int | xs:double | xs:dateTime | xs:date | xs:time | xs:hexBinary | xs:boolean | xs:untypedAtomic}

dd....dd: Number of the XQuery query resulting in an error

S: Ignores this SQL statement.

P: Correct the arithmetic operation so that the XQuery data types of the first and second operation items become a combination that can be compared, and then re-execute. For details about the combinations of XQuery data types that can be used in arithmetic operations, see the manual HiRDB Version 9 SQL Reference.

KFPA19323-E A

Invalid operand of aa....aa expression in XQuery due to bb....bb, XQuery-no=cc....cc

One of the following errors was detected in the operand of the XQuery expression:

If bb....bb is two or more items:

An XQuery sequence has two or more XQuery items in the XQuery comparison (value comparison or node comparison), XQuery range, or XQuery monomial.

If bb....bb is item except node:

An XQuery sequence containing XQuery items other than nodes is specified in the XQuery comparison expression (node comparison) or in the XQuery set operation expression.

If bb....bb is value except "xs:int" type:

A non-integer value is specified in the XQuery range expression.

aa....aa: Processing during which the error occurred:

{value comparison | node comparison | range | union | intersect | except | unary | arithmetic}

value comparison: XQuery comparison expression (value comparison)

node comparison: XQuery comparison expression (node comparison)

range: XQuery range expression

union: XQuery union expression

intersect: XQuery intersection expression

except: XQuery union expression

unary: XQuery monomial expression

arithmetic: XQuery arithmetic expression

bb....bb: Reason for the error

{ two or more items | item except node | value except "xs:int" type }

cc....cc: Number of the XQuery query resulting in an error

S: Ignores this SQL statement.

P:

Correct the XQuery query as follows, and then re-execute:

If bb....bb is two or more items:

Specify either an XQuery sequence that has only one XQuery item or an empty XQuery sequence in the XQuery comparison (value comparison or node comparison), XQuery range, or XQuery monomial.

If bb....bb is item except node:

Specify an XQuery sequence that does not contain XQuery items other than nodes in the XQuery comparison expression (node comparison) or in the XQuery Set Operation expression.

If bb....bb is value except "xs:int" type:

Specify an integer value in the XQuery range expression.

KFPA19324-E A

Invalid context item for aa....aa in XQuery, XQuery-no=bb....bb

During evaluation of XQuery expression aa....aa during an XQuery query, context items were found that are not nodes.

aa....aa: Type of XQuery expression

{ path expression | function "fn:local-name" | function "fn:name" | function "fn:namespace-uri" }

path expression: XQuery path expression

function "fn: local-name": XQuery function fn:local-name

function "fn: name": XQuery function fn:name

function "fn namespace-uri": XQuery function fn:namespace-uri

bb....bb: Number of the XQuery query resulting in an error

S: Ignores this SQL statement.

P: Correct the XQuery query so that the context items are nodes, and then re-execute.

KFPA19325-E A

Overflow in aa....aa for "bb....bb" type in XQuery, XQuery-no=cc....cc

An overflow occurred during operation aa....aa of XQuery data type bb....bb in an XQuery query.

aa....aa: Operation type in which the overflow occurred:

addition: Addition

subtraction: Subtraction

division: Division

multiplication: Multiplication

idiv: Integer division

mod: Modulus calculation

sign inversion: Sign inversion

function "fn:abs": XQuery function fn:abs

bb....bb: Data type resulting in the overflow:

{ xs:decimal | xs:int | xs:double}

cc....cc: Number of the XQuery query resulting in an error

S: Ignores this SQL statement.

P: Correct the XQuery query so that overflow does not occur, and then re-execute.

KFPA19326-E A

Zero divisor in arithmetic operation for"aa....aa" type in XQuery, XQuery-no=bb....bb

A division by zero error occurred during an arithmetic operation on XQuery data type aa....aa in an XQuery query.

aa....aa: XQuery data type resulting in the division by zero error:

{ xs:decimal | xs:int | xs:double }

bb....bb: Number of the XQuery query resulting in an error

S: Ignores this SQL statement.

P: Correct the XQuery query so that division by zero does not occur, and then re-execute.

KFPA19327-E A

Invalid argument of function fn:boolean in XQuery, XQuery-no=aa....aa

The XQuery function fn:boolean argument in the XQuery query does not apply to any of the following:

Empty XQuery sequence

The initial XQuery item is the elemental node XQuery sequence.

xs:boolean (basic unit value of type)

xs:string type or xs:untypedAtomic type basic unit value

Numeric data type basic unit value

aa....aa: Number of the XQuery query resulting in an error

S: Ignores this SQL statement.

P: Correct the XQuery query so that the argument of the XQuery function fn:boolean is one of the following, and then re-execute.

Empty XQuery sequence

The initial XQuery item is the elemental node XQuery sequence.

xs:boolean (basic unit value of type)

xs:string type or xs:untypedAtomic type basic unit value

Numeric data type basic unit value

KFPA19328-E A

Unable to evaluate aa....aa-th argument value for parameter of function "bb....bb" in XQuery, XQuery-no=cc....cc

The argument specified in the XQuery function bb....bb cannot be evaluated as a parameter.

aa....aa: Parameter number

bb....bb: XQuery function name

{xs:string | xs:decimal | xs:int | xs:double | xs:dateTime | xs:date

| xs:time | xs:hexBinary | xs:boolean

| xs:untypedAtomic | fn:abs | fn:boolean | fn:ceiling

| fn:compare | fn:concat | fn:contains | fn:count | fn:data

| fn:day-from-date | fn:day-from-dateTime

| fn:deep-equal | fn:distinct-values | fn:ends-with

| fn:floor | fn:hour-from-dateTime | fn:hour-from-time

| fn:index-of | fn:insert-before | fn:local-name

| fn:max | fn:min | fn:minutes-from-dateTime

| fn:minutes-from-time

|fn:month-from-date | fn:month-from-dateTime

| fn:name

| fn:namespace-uri | fn:normalize-space

| fn:number | fn:remove | fn:reverse

| fn:round | fn:seconds-from-dateTime

| fn:seconds-from-time

| fn:starts-with | fn:string

| fn:string-length | fn:subsequence | fn:substring

| fn:substring-after | fn:substring-before | fn:sum

| fn:translate | fn:year-from-date | fn:year-from-dateTime}

cc....cc: Number of the XQuery query resulting in an error

S: Ignores this SQL statement.

P: Correct the XQuery query so that the evaluation results of the argument specified in the XQuery function become XQuery data type values of compatible parameters, and then re-execute.

KFPA19329-E A

Unable to specify unary operation "a" for "bb....bb" type value in XQuery, XQuery-no=cc....cc

The unary operation cannot be executed on the bb....bb value of the XQuery data type.

a: Unary operation type

{ +|- }

bb....bb: XQuery data type of operation item

{ xs:string | xs:dateTime | xs:date | xs:time

| xs:hexBinary | xs:boolean }

cc....cc: Number of the XQuery query resulting in an error

S: Ignores this SQL statement.

P:

Correct the XQuery query so that the XQuery data types of the operation items are numeric data or xs:untypedAtomic, and then re-execute.

Note that for xs:untypedAtomic type, it must be a value that can be convert to xs:double type.

KFPA19330-E A

Result of last step expression in path expression contains both nodes and atomic values in XQuery, XQuery-no=aa....aa

Nodes and basic unit values cannot be included in XQuery path expression XQuery sequences of the final step expression results.

aa....aa: Number of the XQuery query resulting in an error

S: Ignores this SQL statement.

P: Correct the XQuery query so that the evaluation results of the last step expression of the XQuery path expression become one of the following, and then re-execute.

XQuery sequence containing nodes only

XQuery sequence containing basic unit values only

KFPA19331-E A

Unable to evaluate aa....aa, because context item not defined in XQuery, XQuery-no=bb....bb

aa....aa cannot be evaluated because a context item is not defined.

aa....aa: Processing during which the error occurred:

path expression: XQuery path expression

context item expression: context item expression

function "fn:last": XQuery function fn:last

function "fn:local-name": XQuery function fn:local-name

function "fn:name": XQuery function fn:name

function "fn:namespace-uri": XQuery function fn:namespace-uri

function "fn:normalize-space": XQuery function fn:normalize-space

function "fn:number": XQuery function fn:number

function "fn:position": XQuery function fn:position

function "fn:string": XQuery function fn:string

function "fn:string-length": XQuery function fn:string-length

bb....bb: Number of the XQuery query resulting in an error

S: Ignores this SQL statement.

P: Use one of the following methods to define the context item at the time the invalid XQuery expression is evaluated, and then re-execute.

Specifies XML query context items.

An XQuery expression different from the invalid Xquery expression in the XQuery query is specified in front of that invalid XQuery expression.

KFPA19332-E A

Unable to execute CALL COMMAND statement for command or utility "aa....aa", because bb....bb

Failed to execute a command or utility using the CALL COMMAND statement.

aa....aa: Name of the command or utility that failed to execute

If a command or utility name has not been specified, asterisks (*) are shown.

bb....bb: Reason

command not found

No command or utility was specified.

environment specification invalid

An environment variable that cannot be set has been set in the environment specification.

of no command execution privilege

You do not have privileges to execute the command or utility.

specified server not found

Either the server specified in the server operand does not exist or it is not operating.

child process creation failed

A child process cannot be created.

temporary file creation failed

A temporary file cannot be created.

use is restricted

System configuration in which use of the CALL COMMAND statement has been restricted.

child process terminated abnormally

The child process terminated abnormally.

S: Ignores this SQL statement.

P:

If bb....bb is command not found:

Correct the specified command or utility file name and re-execute.

If bb....bb is environment specification invalid:

Check the list of environment variables that can be set in the environment specification, and then re-execute.

If bb....bb is of no command execution privilege:

Use the authorization identifier specified in pd_sql_command_exec_users operand.

If bb....bb is specified server not found:

Specify the name of another operating server, and then re-execute.

If bb....bb is use is restricted:

Release the invalid CALL COMMAND statement, and then re-execute.

O:

If bb....bb is child process creation failed:

Use the following method to ensure that there is sufficient memory or a sufficient number of process that can be used:

Reduce the number of processes that execute concurrently.

Increase the number of processes that can be executed.

Increase the swapping size.

If bb....bb is temporary file creation failed:

In UNIX, increase free space on disks that have CALL COMMAND. In Windows, increase free space on disks that have %PDDIR%\tmp.

If bb....bb is child process terminated abnormally:

Check if one of the following situations applies. Then, perform all applicable corrective actions and re-execute. If neither of the following situations is applicable, contact the customer support center.

If the control command (pdcmdexec) process is being terminated by the pdkill command (In UNIX: the OS kill command), re-execute the CALL COMMAND statement so that the process will not be terminated by the pdkill command (or kill command).

If the host that is executing the command or utility shut down, restart the host and re-execute the CALL COMMAND statement.

KFPA19333-E A

System function aa....aa error, code=bb....bb, during execution of CALL COMMAND statement

An error occurred in an operating system function while the CALL COMMAND statement was executing.

aa....aa: System function names

bb....bb: Error code (errno)

S: Ignores this SQL statement.

Action

Refer to 4.3 System call return codes, and investigate and eliminate the cause of the system function errno, and then re-execute the command.

KFPA19335-E A

Error returned from C function for aa....aa bb....bb.cc....cc, query-no=ddd, SQLSTATE=eeeee, detail="ff....ff"

An error occurred during execution of the external C stored routine bb....bb.

aa....aa: External C stored routine type{PROCEDURE|FUNCTION}

bb....bb: Authorization identifier

cc....cc: Routine identifier

ddd: SQL query number

eeeee: SQLSTATE value set ins the C function implementing the external C stored routine.

ff....ff: Message text that was set in the C function packaging an external C stored routine, and that displays the detailed reason for an error occurrence.

S: Ignores this SQL statement.

P: Follow the specifications that are provided by the programmer of the implemented external C stored routine, and take corrective action according to the SQLSTATE that was set.

Action

If there is a problem in the C function that implemented the external C stored routine, contact the programmer who implemented the C function, and request correction of the program.

KFPA19336-E A

Invalid value appeared in output aa....aa parameter of C function for bb....bb cc....cc.dd....dd, inf=ee....ee, query-no=fff

An invalid output parameter value was specified by the C function that implemented the external C stored routine dd....dd.

If aa....aa is data(n):

An invalid value was set in the data part of the nth parameter.

If aa....aa is SQLSTATE:

An invalid value was set in SQLSTATE.

If aa....aa is MESSAGE_TEXT:

Invalid message text length.

aa....aa: Output parameter types

data(n): SQL parameter data part or return value data part.

n is the sequence number for the parameter of the C function that implemented the external C stored routine. However, return values of the C stored function are 0.

SQLSTATE: SQLSTATE

MESSAGE_TEXT: Message text

bb....bb: External C stored routine type{PROCEDURE|FUNCTION}

cc....cc: Authorization identifier

dd....dd: Routine identifier

ee....ee: Additional information for the output parameter type aa....aa

If aa....aa is data(n):

SQL parameter data type
Additional information
Meaning

DECIMAL
INTERVAL YEAR TO DAY
INTERVAL HOUR TO SECOND
DATE
TIME
TIMESTAMP
Character string with data that was converted to hexadecimals
Invalid data format

NCHAR
NVARCHAR(n)
Data length (unit: byte)
Invalid data length (odd number value)

For details about data types, data formats and data lengths, see the manual HiRDB Version 9 SQL Reference.

If aa....aa is SQLSTATE:

SQLSTATE value

If aa....aa is MESSAGE_TEXT:

Message text length

fff: SQL query number

S: Ignores this SQL statement.

P: Use the following procedure to re-register the C library file, and then re-execute the SQL statement:

Eliminate the cause of the error, and correct the library source.
For details about the values to set in each output parameter, see CREATE FUNCTION or CREATE PROCEDURE in the manual HiRDB Version 9 SQL Reference.

Recreate the C library file from the corrected source.

Use one of the following methods to re-register the C library file that you created:
- Create a UAP that executes REPLACE CLIB, and execute that UAP.
- Ask the administrator to execute the pdclibsync command.

Action

Contact the programmer who implemented the C function dd....dd, and request correction of the program. If a pdclibsync command must be executed according to the corrective action for the program, re-execute the command.

KFPA19342-E A

Failed to load aa....aa, C library file=bb....bb, external function=cc....cc

Failed to load the C library file or external function specified in the routine.

aa....aa: type{C library file | external function}

bb....bb: C library file name (truncated just before the 51st character)

cc....cc: External function identifier (truncated just before the 51st character)

S: Ignores this SQL statement.

P:

If aa....aa is C library file:

Define the routine using the correct C library file name, and then re-execute. Alternatively, re-register the C library file bb....bb that holds the function cc....cc, and then re-execute.

If aa....aa is external function:

Define the routine using the correct external function identifier, and then re-execute. Alternatively, add the function cc....cc to the C library file bb....bb, and then re-execute.

KFPA19345-E A

Unexpected SQL value of floating point numeric

The following values are used as an SQL floating point:

NaN (not a number)

+INF (+ infinity)

-INF (- infinity)

S: Ignores this SQL statement.

P: Change so that NaN, +INF, and -INF, are not used in the SQL floating point value, and then re-execute.

KFPA19346-E A

Unable to specify attribute node after non-attribute node in aa....aa in XQuery, XQuery-no=bb....bb, modify-no=cccc

The attribute node in aa....aa was specified after a non-attribute node. Specify the attribute node before the non-attribute node.

aa....aa: Type of XQuery expression resulting in the error

{content sequence in element constructor|source expression in insert expression}

content sequence in element constructor: XQuery expression in an XQuery element constructor

source expression in insert expression: XQuery source expression in an XQuery insert expression

bb....bb: Query number of the XQuery resulting in an error

cccc: Number indicating the position of the XQuery modify expression within the XQuery transform expression resulting in an error, numbered starting from the first expression

S: Ignores this SQL statement or invalidates the transaction.

P: Correct the SQL statement and re-execute.

KFPA19347-E A

Invalid target expression in aa....aa in XQuery, XQuery-no=bb....bb, modify-no=cccc

An error occurred in the XQuery target expression in aa....aa.

aa....aa: Type of XQuery expression resulting in the error

{insert expression with "into"|insert expression with "as first into"|insert expression with "as last into"|insert expression with "before"|insert expression with "after"|delete expression|rename expression|replace expression}

bb....bb: Query number of the XQuery resulting in an error

cccc: Number indicating the position of the XQuery modify expression within the XQuery transform expression resulting in an error, numbered starting from the first expression

S: Ignores this SQL statement or invalidates the transaction.

P: Correct the SQL statement as described in the following table, and then retry the operation:

Type of XQuery expression resulting in an error (aa....aa)
Explanation
Action

Any of the following:

insert expression with "into" (XQuery insert expression with into specified)

insert expression with "as first into" (XQuery insert expression with as first into specified)

insert expression with "as last into" (XQuery insert expression with as last into specified)

Only an XQuery sequence consisting of a single element node can be specified in the XQuery target expression.
Specify an XQuery sequence consisting of a single element node in the XQuery target expression.

Either of the following:

insert expression with "before" (XQuery insert expression with before specified)

insert expression with "after" (XQuery insert expression with after specified)

An XQuery sequence consisting of multiple nodes cannot be specified in the XQuery target expression. In addition, an XQuery sequence consisting of a document node, attribute node, or atomic value cannot be specified.
Specify an XQuery sequence consisting of a single element node, text node, comment node, or processing instruction node in the XQuery target expression.

delete expression (XQuery delete expression)
An atomic value cannot be specified in the XQuery target expression.
Specify an XQuery sequence consisting of zero or more nodes in the XQuery target expression.

rename expression (XQuery name change expression)
An XQuery sequence consisting of multiple nodes cannot be specified in the XQuery target expression. In addition, an XQuery sequence consisting of a document node, text node, comment node, or atomic value cannot be specified.
Specify an XQuery sequence consisting of a single element node, attribute node, or processing instruction node in the XQuery target expression.

replace expression (XQuery replace expression)
An XQuery sequence consisting of multiple nodes cannot be specified in the XQuery target expression. In addition, an XQuery sequence consisting of a document node or atomic value cannot be specified.
Specify a single element node, attribute node, text node, comment node, or processing instruction node in the XQuery target expression.

KFPA19348-E A

Node type of source expression conflicts with target expression in replace expression without "value of" in XQuery, XQuery-no=aa....aa, modify-no=bbbb

An error occurred in an XQuery source expression in an XQuery replace expression that does not have a value of specification.

If the XQuery target expression is an element node, text node, comment node, or processing instruction node:
You cannot specify attribute nodes in the XQuery source expression. Specify an XQuery sequence consisting of zero or more element nodes, text nodes, comment nodes, or processing instruction nodes in the XQuery source expression.

If the XQuery target expression is an attribute node:
Only attribute nodes can be specified in the XQuery source expression. Specify an XQuery sequence of zero or more attribute nodes in the XQuery source expression.

aa....aa: Query number of the XQuery resulting in an error

bbbb: Number indicating the position of the XQuery modify expression within the XQuery transform expression resulting in an error, numbered starting from the first expression

S: Ignores this SQL statement or invalidates the transaction.

P: Correct the SQL statement and re-execute.

KFPA19349-E A

Target expression in "modify" clause not created by "copy" clause, in transform expression of XQuery, XQuery-no=aa....aa, modify-no=bbbb

In the XQuery transform expression, only a node created by the copy clause can be specified in the XQuery target expression that specifies the target of the modify clause. Specify a node created by the copy clause in the XQuery target expression.

aa....aa: Query number of the XQuery resulting in an error

bbbb: Number indicating the position of the XQuery modify expression within the XQuery transform expression resulting in an error, numbered starting from the first expression

S: Ignores this SQL statement or invalidates the transaction.

P: Correct the SQL statement and re-execute.

KFPA19350-E A

Same target expression specified in more than one aa....aa in XQuery, XQuery-no=bb....bb, modify-no=cccc

You cannot specify the same node for the XQuery target expression in more than one aa....aa. Specify different nodes for the XQuery target expression in each aa....aa.

aa....aa: Type of XQuery expressions resulting in the error

{rename expressions|replace expressions without "value of"|replace expressions with "value of"}

rename expressions: XQuery name change expression

replace expressions without "value of": XQuery replace expression without value of specified

replace expressions with "value of": XQuery replace expression with value of specified

bb....bb: Query number of the XQuery resulting in an error

cccc: Number indicating the position of the XQuery modify expression within the XQuery transform expression resulting in an error, numbered starting from the first expression

S: Ignores this SQL statement or invalidates the transaction.

P: Correct the SQL statement and re-execute.

KFPA19351-E A

Empty sequence specified as target expression in aa....aa in XQuery, XQuery-no=bb....bb, modify-no=cccc

An empty XQuery sequence cannot be specified in the XQuery target expression in aa....aa. Specify a non-empty XQuery sequence in the XQuery target expression.

aa....aa: Type of XQuery expression resulting in the error

{insert expression|rename expression|replace expression}

insert expression: XQuery insert expression

rename expression: XQuery name change expression

replace expression: XQuery replace expression

bb....bb: Query number of the XQuery resulting in an error

cccc: Number indicating the position of the XQuery modify expression within the XQuery transform expression resulting in an error, numbered starting from the first expression

S: Ignores this SQL statement or invalidates the transaction.

P: Correct the SQL statement and re-execute.

KFPA19352-E A

Inserting attribute node "after" or "before" node without parent element node specified in XQuery, XQuery-no=aa....aa, modify-no=bbbb

When you specify an attribute node in an XQuery source expression in an XQuery insert expression which specifies before or after, you cannot specify a node that does not have a parent element node in the XQuery target expression.

aa....aa: Query number of the XQuery resulting in an error

bbbb: Number indicating the position of the XQuery modify expression within the XQuery transform expression resulting in an error, numbered starting from the first expression

S: Ignores this SQL statement or invalidates the transaction.

P: Correct the SQL statement and re-execute.

KFPA19353-E A

Unable to specify constructor expression in source expression of replace expression with "value of" in XQuery, XQuery-no=aa....aa, modify-no=bbbb

An XQuery constructor cannot be specified in an XQuery source expression in an XQuery replace expression which specifies value of. Specify an XQuery expression alone in the XQuery source expression.

aa....aa: Query number of the XQuery resulting in an error

bbbb: Number indicating the position of the XQuery modify expression within the XQuery transform expression resulting in an error, numbered from the first expression

S: Ignores this SQL statement or invalidates the transaction.

P: Correct the SQL statement and re-execute.

KFPA19354-E A

Result of atomization applied to new name expression in rename expression in XQuery not a single atomic value of type xs:string or xs:untypedAtomic, XQuery-no=aa....aa, modify-no=bbbb

The result of atomizing an XQuery expression alone in an XQuery name change expression must be a single node or atomic value of type xs:string or xs:untypedAtomic. Specify an expression that will resolve to a single node or atomic value of type xs:string or xs:untypedAtomic.

aa....aa: Query number of the XQuery resulting in an error

bbbb: Number indicating the position of the XQuery modify expression within the XQuery transform expression resulting in an error, numbered from the first expression

S: Ignores this SQL statement or invalidates the transaction.

P: Correct the SQL statement and re-execute.

KFPA19400-E A

aa....aa statement executed, signal value=bb....bb

The aa....aa statement caused an error.

aa....aa: SQL statement types {SIGNAL|RESIGNAL}

bb....bb: The signal values specified in the SIGNAL statement or RESIGNAL statement.

If a condition name is specified in the signal name:

condition-name

When SQLSTATE is specified in the signal value:

SQLSTATE:XXXXX (XXXXX is the SQLSTATE value).

S: Ignores this SQL statement, or invalidates this transaction.

P: Refer to the SQL procedure or trigger definition to check the reason why the SIGNAL statement or RESIGNAL statement was executed. If the RESIGNAL statement is executed, you can check the error information history by referring to the GET DIAGNOSTICS diagnostic information.

KFPA19403-E A

No error occurred before executing RESIGNAL statement

No SQL procedure statement was found that caused an error before executing the RESIGNAL statement.

S: Ignores this SQL statement, or invalidates this transaction.

P: Correct the SQL procedure or trigger definition and re-execute the SQL statement. To cause an error after executing the SQL procedure statement that does not cause an error, use the SIGNAL statement.

KFPA19404-E A

Handler raised recursively

The same handler was invoked recursively.

S: Ignores this SQL statement, or invalidates this transaction.

P: To prevent the same handler from being invoked again when handler operation is delayed, redefine the SQL routine or trigger and re-execute this SQL statement.

KFPA19405-E A

Invalid aa....aa of parameter in "LIMIT"clause.

The value of the variable specified in the LIMIT clause is an invalid data type.

aa....aa: Invalid type

data type: The data type is not INTEGER or SMALLINT.

value: The value of the variable either is not in the range 1-2,147,483,647 or is a null value.

S: Ignores this SQL statement.

P: When aa....aa is data type, change the data type of the variable specified in the LIMIT clause to INTEGER or SMALLINT, and then re-execute this SQL statement. If aa....aa is value, change the value of the variable specified in the LIMIT clause to between 1 and 2,147,483,647 inclusive, and then re-execute this SQL statement.

KFPA19406-E A

Unable to specify condition name associated with SQLCODE value in aa....aa statement, condition name=bb....bb

The condition name associated with the SQLCODE value in the SIGNAL statement or RESIGNAL statement could not be specified.

aa....aa: Type of SQL statement {SIGNAL|RESIGNAL}

bb....bb: The condition name specified as the signal value in the SIGNAL statement or RESIGNAL statement

S: Ignores this SQL statement, or invalidates this transaction.

P: Re-evaluate the SQL procedure or trigger definition and check whether the condition name associated with the SQLCODE value in the SIGNAL statement or RESIGNAL statement was specified. When specifying the condition name in the SIGNAL statement or RESIGNAL statement, do not specify the SQLCODE value in the condition declaration.

KFPA19407-E A

Invalid specification in aaaaaaa statement with bbb clause

The format of the INSERT, UPDATE, or DELETE statement specified in the FOR clause or the format of the EXECUTE statement specified in the BY clause is invalid.

aaaaaaa: Type of SQL statement {INSERT|UPDATE|DELETE|EXECUTE}

bbb: Clause name {FOR|BY}

S: Ignores this SQL statement.

P: Correct either the SQL statement or the UAP as follows, and then re-execute:

To specify an embedded variable array and insert multiple columns into the table in column units:
FOR: Embedded variable
INSERT INTO [authorization-identifier.]table-identifier [(column-name[,column-name]...)]
VALUES(:embedded-variable-array[:indicator-variable-array]
[,:embedded-variable-array[:indicator-variable-array]]...)
[WITH ROLLBACK]

To specify an embedded variable array and insert multiple columns into the FIX attributes table in column units:
FOR: Embedded variable
INSERT INTO [authorization-identifier.]table-identifier (ROW)
VALUES(:embedded-variable-array[:index-variable-array])
[WITH ROLLBACK]

To preprocess SQL (the INSERT statement) and execute using the EXECUTE statement:
(SQL to be preprocessed)
INSERT INTO [authorization-identifier.]table-identifier [(column-name[,column-name]...)]
VALUES (? parameter [,? parameter]...)
[WITH ROLLBACK]
INSERT INTO [authorization-identifier.]table-identifier (ROW)
VALUES (? parameter)
[WITH ROLLBACK]

KFPA19408-E A

Unable to execute SQL except INSERT, UPDATE or DELETE using EXECUTE statement with BY clause

The EXECUTE statement specified by the BY clause can only execute the INSERT, UPDATE, or DELETE statement.

S: Ignores this SQL statement.

P: When executing a query other than the INSERT, UPDATE, or DELETE statement in the EXECUTE statement, correct the SQL statement or the UAP to remove the specification of the BY clause, and then re-execute the SQL statement.

KFPA19409-E A

Unable to insert into aa....aa using bb....bb statement with cc....cc clause

When inserting an INSERT statement specifying the FOR clause or an EXECUTE statement specifying the BY clause, insertions cannot be made into the following items:

A BINARY type column with a definition length of 32,001 bytes or more

A table with a BINARY column with a definition length of 32,001 bytes or more in the WITH DEFAULT specification

A BLOB type column

A table with a BLOB column in the WITH DEFAULT specification

A column with the abstract data type

aa....aa: Insertion target

{column of BINARY data type (length over 32000)|table which has BINARY data type (length over 32000) column with WITH DEFAULT|column of BLOB data type|table which has BLOB data type column with WITH DEFAULT|column of abstract data type}

bb....bb: Type of SQL statement {INSERT|EXECUTE}

cc....cc: Clause name {FOR|BY}

S: Ignores this SQL statement.

P: When executing the INSERT statement specified in the FOR clause or the EXECUTE statement specified in the BY clause, correct the SQL statement or the UAP as follows and re-execute the SQL statement:

Do not insert anything into a BINARY type column with a definition length of 32,001 bytes or more.

Do not insert anything into a table with any BINARY columns with a definition length of 32,001 bytes or more specified in WITH DEFAULT.

Do not insert anything into a BLOB type column (do not specify the null value as the insertion value).

Do not insert anything into a table with any BLOB columns specified in WITH DEFAULT.

Do not insert anything into an abstract data type column.

KFPA19411-E A

Unable to lock shared table in RDAREA which containing table used by cursor

An attempt was made to execute the LOCK statement using the EXCLUSIVE specification for a shared table by an RDAREA that stores a shared table for which a cursor is open.

S: Ignores this SQL statement.

P: If the LOCK statement was executed using the EXCLUSIVE specification for a shared table, close the open cursor for the other shared table that is stored in the RDAREA that stores the target shared table, and then execute the LOCK statement.

KFPA19450-E A

Invalid trigger definition code=aa(bb....bb)

An error was detected in the trigger definition.

aa: Reason code

bb....bb: Additional error information

Reason code (aa)
Additional information (bb....bb)
Meaning

01
Another user's table
The trigger cannot be defined in another user's table.

02
Non base table cc....cc
The trigger can only be defined in a permanent base table.
cc....cc: { view table | temporary table}

03
Table not found
A table for defining the trigger cannot be found.

04
Duplicate "OLD ROW" or "NEW ROW"
OLD ROW and NEW ROW can only be specified one time each in the old or new values alias list.

05
"OLD ROW" in insert trigger
When specifying INSERT in a trigger execution event, OLD ROW cannot be specified.

06
"NEW ROW" in delete trigger
When specifying DELETE in a trigger execution event, NEW ROW cannot be specified.

07
Duplicate name in old or new values alias
The same name cannot be specified in OLD ROW and NEW ROW.

08
"OLD ROW" or "NEW ROW" in "STATEMENT TRIGGER"
When specifying FOR EACH STATEMENT, NEW ROW or OLD ROW cannot be specified.

09
Num of trigger columns exceed 30000
The number of columns specified by the trigger execution event exceeds 30,000.

10
Duplicate trigger columns "dd....dd"
The trigger execution event specified duplicate column names.
dd....dd: Column name

11
Trigger column "dd....dd" not found in table
The column specified by the trigger execution event was not found in the table defining triggers.
dd....dd: Column name

12
SQL data change statement in "BEFORE TRIGGER"
A trigger definition specifying BEFORE during the trigger action time cannot specify the update SQL statements (INSERT, UPDATE or DELETE) in the trigger SQL statement.

13
Invalid column reference "dd....dd"
A repetition column, abstract data type column, or reserved column cannot be referenced by an old or new values correlation name.
dd....dd: Column name

14
Invalid triggered SQL statement
A PURGE TABLE statement, COMMIT statement, or ROLLBACK statement cannot be specified in the trigger SQL statement.

15
Trigger table in triggered SQL statement
A table defining triggers cannot be specified in the trigger SQL statement.

16
SQL function invocation in "BEFORE TRIGGER"
Only function invocation of the default constructor can be specified in the trigger SQL statement in the trigger definition specifying BEFORE during the trigger action time.

17
ROW for old or new values alias
ROW cannot be specified in the new or old values correlation name.

19
Unqualified column of trigger table in triggered action
To specify the column name of a table specified in the trigger action search condition or the trigger definition in the trigger SQL statement, you must qualify the column name in the new or old values correlation name.

20
Invalid use of ? parameter
The ? parameter cannot be specified in the trigger SQL statement.

21
Call statement in "BEFORE TRIGGER"
A CALL statement cannot be specified in the trigger SQL statement in the trigger definition specifying BEFORE during the trigger action time.

22
Invalid use of JAVA procedure or function
A Java stored procedure or a Java stored function cannot be specified in the trigger SQL statement.

23
Invalid use of GET_JAVA_STORED_ROUTINE_SOURCE specification
GET_JAVA_STORED_ROUTINE_SOURCE cannot be specified in the trigger SQL statement.

24
Invalid use of default specification
If the default value specifies the CURRENT_TIMESTAMP column of the USING BES specification in the assignment target of the assignment statement, DEFAULT cannot be specified as the assignment value.

25
Invalid use of reserved column "dd....dd" in trigger columns
A reserved column cannot be specified in the trigger event column.
dd....dd: Column name

S: Ignores this SQL statement.

P: Correct this SQL statement, and then re-execute.

KFPA19451-E A

Unable to execute trigger aa....aa.bb....bb due to cc....cc

Trigger aa....aa.bb....bb cannot be executed due to the constraint indicated in cc....cc.

aa....aa: Authorization identifier

bb....bb: Trigger identifier

cc....cc: Constraint

more than 16 nest:

The number of nesting levels exceeded 16 during trigger execution.

COMMIT/ROLLBACK/PURGE TABLE statement:

The COMMIT, ROLLBACK or PURGE TABLE statements cannot be executed by a trigger.

Java routine:

External Java stored routines cannot be executed by a trigger.

S: Ignores this transaction.

P: Take the following actions for each constraint:

For more than 16 nest:

Correct the trigger definition so the number of trigger nesting levels does not exceed 16, and then re-execute.

For a COMMIT/ROLLBACK/PURGE TABLE statement:

Correct the SQL stored procedure invoked by the CALL statement from inside a trigger so neither COMMIT nor ROLLBACK is executed, and then re-execute the statement.

For Java routine:

Make corrections so that the external Java stored routine is not executed by the trigger, and then retry the operation.

KFPA19452-E A

Unable to specify SQL optimization specification for "aaaaa" in query for table derived from "bb....bb"

The following SQL optimization specifications cannot be specified by queries to a table join (including joined tables) and derived or by queries to tables derived by specifying set operations:

SQL optimization specification of the index used

SQL optimization specification of the joining format (joining type SQL optimization specifications can be specified for named derived tables generating internal derived tables)

The following are the conditions for creating internal derived tables:

One of the following items is either included in a subquery that is a named derived table in a query to a named derived table derived by specifying SELECT DISTINCT, or is directly included:

GROUP BY clause, a HAVING clause, or a set function

SELECT DISTINCT

Table join (including outer join and inner join)

Specification of value expressions other than a column specification in the selection expression

One or more columns of a name derived table specified by the FROM clause are not specified one time each

NEXT VALUE expression

One of the following items is directly included in a query to a named derived table derived by specifying the GROUP BY clause, HAVING clause, or a set function:

GROUP BY clause, a HAVING clause, or a set function

Table join (including outer join and inner join)

Window function

NEXT VALUE expression

A query for a named derived table, derived by specifying a value expression other than a column specification as the selection expression, directly includes one of the following:

GROUP BY clause, HAVING clause, or set function

Window function

Joined table

A query for a named derived table, derived by specifying a set function with DISTINCT, directly includes one of the following:

GROUP BY clause, HAVING clause, or set function

SELECT DISTINCT

Window function

A query for a named derived table, derived by specifying a table join (including both outer joins and inner joins), directly includes a table join (including both outer joins and inner joins) and one of the specified table join operations is a table join specification.

A query for a named derived table, derived by specifying a scalar subquery as a selection expression, directly includes one of the following:

SELECT DISTINCT

GROUP BY clause, HAVING clause, or set function

Table join (including both outer joins and inner joins)

A value expression other than a column specification in a selection expression

A scalar subquery specified in a selection expression

The same column derived from a value expression containing a subquery, specified more than once in the selection expression for a named derived table

A column derived from a value expression containing a subquery, specified as an external reference column in the selection expression for a named derived table

A viewed table defined before HiRDB version 07-02

A query for a named derived table, derived from a set operation, which satisfies one of the following:

One of the operators of the set operation includes an internal derived table query, a query that specifies a derived table, or a query that specifies a subquery in a selection expression.

One of the operators of the set operation and the query for the named derived table satisfy one of the conditions of 1 through 6.

A query for a named derived table, derived from a set operation that includes other than UNION ALL, which directly includes one of the following:

GROUP BY clause, HAVING clause, or set function

SELECT DISTINCT

Table join (including both outer joins and inner joins)

WHERE clause

Subquery

Value expression other than a column specification in a selection expression

Selection expression in which all of the columns of a named derived table specified in the FROM clause are not each specified once

NEXT VALUE expression

A query for a named derived table derived from a set operation that includes only UNION ALL, which directly includes one of the following:

GROUP BY clause, HAVING clause, or a set function

Window function

WHERE clause or subquery (however, only a subquery, a set operation operator, or an INSERT statement query)

Function call or system definition scalar function

Component specification

WRITE specification

GET_JAVA_STORED_ROUTINE_SOURCE specification

Sort specification with items not in the selection expression

Subquery for a named derived table derived from a set operation specified in the FROM clause

Subquery that specifies a derived table

Subquery specified in a value expression other than a column specification in the GROUP BY clause

The data type of an SQL variable specified in a selection expression or an SQL parameter is one of the following:
BLOB type
BINARY type 32,001 bytes or larger
Abstract data type
BOOLEAN type

The query specification specified for the table-joining of named derived tables derived by a set operation consisting solely of UNION ALL specifies one of the following:

A named derived table in a table reference other than at the leftmost outer table for an outer join

The FROM clause specifying a named derived table, which specifies a comma join (that is, specifies a different table reference than the joined table for which a derived table is specified)

A subquery or a derived table

A query specification contained either in a subquery or in the operation term for a set operation

A set operation term that derives named derived tables and contains one of the following:
Table join
GROUP BY clause, HAVING clause, or a set function
SELECT DISTINCT
A value expression in a selection expression other than a column specification
A query that creates an inner derived table
A query specifying a derived table

A named derived table derived by specifying a set operation (in addition to a named derived table)

One of the following, in the table reference to a joined table specifying a named derived table:
A named derived table derived by specifying the joining of tables
A named derived table derived by specifying a GROUP BY clause, a HAVING clause, or a set function
A named derived table derived by specifying SELECT DISTINCT
A named derived table derived by specifying a value expression other than a column specification in a selection expression
A named derived table derived by specifying a query that creates an inner derived table
A named derived table derived by specifying a subquery

The total number of tables obtained by the following expression is greater than 65:
Total number of tables = a + b c + d
a: Total number of tables from which named derived tables are derived
b: Number of set operations from which named derived tables are derived + 1
c: Total number of tables specified on the right side of an outer join
d: If a query other than a query for which a named derived table is specified is also specified, the total number of tables specified in the query

aaaaa: {index|join}

bb....bb: {join|set operation}

S: Ignores this SQL statement.

P: Correct this SQL statement and re-execute.

KFPA19453-E A

Unable to specify SQL optimization specification for index to view or "WITH" query which derives internal table

The following SQL optimization specifications for the used index cannot be specified by a query creating internal derived tables:
The following are the conditions for creating internal derived tables:

One of the following items is either included in a subquery that is a named derived table in a query to a named derived table derived by specifying SELECT DISTINCT, or is directly included:

GROUP BY clause, HAVING clause, or set function

SELECT DISTINCT

Table join (including outer join and inner join)

Specification of value expressions other than a column specification in the selection expression

One or more columns of a name derived table specified by the FROM clause are not specified one time each

One of the following items is directly included in a query to a named derived table derived by specifying the GROUP BY clause, HAVING clause, or a set function:

GROUP BY clause, HAVING clause, or set function

Table join (including outer join and inner join)

Window function

One of the following items is directly included in a query to a named derived table derived by specifying a value expression other than a column specification as a selection expression:

GROUP BY clause, HAVING clause, or set function

Window function

Joined table

A query on a named derived table derived by directly specifying a set function with DISTINCT contains one of the following:

GROUP BY clause, HAVING clause, or set function

SELECT DISTINCT

Window function

An inquiry to a named derived table derived by specifying a table join (including outer join and inner join) directly includes a table join (including outer join and inner join), and specifies the table join.

A query on a named derived table derived by directly specifying a scalar subquery as a selection expression contains one of the following:

SELECT DISTINCT

GROUP BY clause, HAVING clause, or set function

Table join (including outer join and inner join)

A value expression other than a column specification specified in a selection expression

A scalar subquery specified in a selection expression

The same column derived from a value expression containing a subquery, specified more than once in the selection expression for a named derived table

A column derived from a value expression containing a subquery, specified as an external reference column in the selection expression for a named derived table

A viewed table defined before HiRDB version 07-02

A query for a named derived table derived from a set operation, which satisfies one of the following:

One of the operators of the set operation includes an internal derived table query, a query that specifies a derived table, or a query that specifies a subquery in a selection expression.

One of the operators of the set operation and the query for the named derived table satisfy one of the conditions of 1 through 6 above.

A query for a named derived table derived from a set operation that includes other than UNION ALL, which directly includes one of the following:

GROUP BY clause, HAVING clause, or a set function

SELECT DISTINCT

Table join (including external or internal joins)

WHERE clause

Subquery

Value expression other than a column specification in a selection expression

In a selection expression, the columns of a named derived table specified in the FROM clause are not specified once each

A query for a named derived table derived from a set operation that includes only UNION ALL, which directly includes one of the following:

GROUP BY clause, HAVING clause, or a set function

Window function

WHERE clause or subquery (however, only a subquery, a set operation operator, or an INSERT statement query)

Function call or system definition scalar function

Component specification

WRITE specification

GET_JAVA_STORED_ROUTINE_SOURCE specification

Sort specification with items not in the selection expression

Subquery for a named derived table derived from a set operation specified in the FROM clause

Subquery that specifies a derived table

Subquery specified in a value expression other than a column specification in the GROUP BY clause

The data type of an SQL variable specified in a selection expression or an SQL parameter is one of the following:
BLOB type
BINARY type 32,001 bytes or larger
Abstract data type
BOOLEAN type

The query specification specified for the table-joining of named derived tables derived by a set operation consisting solely of UNION ALL specifies one of the following:

A named derived table in a table reference other than at the leftmost outer table for an outer join

The FROM clause specifying a named derived table, which specifies a comma join (that is, specifies a different table reference than the joined table for which a derived table is specified)

A subquery or a derived table

A query specification contained either in a subquery or in the operation term for a set operation

A set operation term that derives named derived tables and contains one of the following:
Table join
GROUP BY clause, HAVING clause, or a set function
SELECT DISTINCT
A value expression in a selection expression other than a column specification
A query that creates an inner derived table
A query specifying a derived table

A named derived table derived by specifying a set operation (in addition to a named derived table)

One of the following, in the table reference to a joined table specifying a named derived table:
A named derived table derived by specifying the joining of tables
A named derived table derived by specifying a GROUP BY clause, a HAVING clause, or a set function
A named derived table derived by specifying SELECT DISTINCT
A named derived table derived by specifying a value expression other than a column specification in a selection expression
A named derived table derived by specifying a query that creates an inner derived table
A named derived table derived by specifying a subquery

The total number of tables obtained by the following expression is greater than 65:
Total number of tables = a + b c + d
a: Total number of tables from which named derived tables are derived
b: Number of set operations from which named derived tables are derived + 1
c: Total number of tables specified on the right side of an outer join
d: If a query other than a query for which a named derived table is specified is also specified, the total number of tables specified in the query

S: Ignores this SQL statement.

P: Correct the SQL statement, and then re-execute.

KFPA19454-E A

Unable to insert using aa....aa statement with bb....bb clause into table with row-level trigger

The following SQL statements cannot be used to batch-insert multiple rows into a table with row-level triggers defined:

An INSERT statement specifying a FOR clause

An EXECUTE statement specifying a BY clause

aa....aa: {INSERT|EXECUTE}

bb....bb: {FOR|BY}

S: Ignores this SQL statement.

P: Correct the SQL statement or the UAP to enable the insertion of one row at a time, and then re-execute the SQL statement.

KFPA19455-E A

Unable to update specified column using new values correlation name in BEFORE trigger

A trigger definition specifying BEFORE during the trigger action time (BEFORE trigger) cannot use the new values correlation name to qualify and update the following columns:

Columns specifying SYSTEM GENERATED

Also, BEFORE triggers with INSERT trigger execution events cannot use the new values correlation name to qualify and update the following column:

A column specifying the partitioning key of the partitioning table (excluding flexible hash partitioning tables)

S: Invalidates this transaction.

P: Correct the trigger definition so that the new values correlation name does not qualify and update the column specifying SYSTEM GENERATED and the column specified in the partitioning key.

KFPA19456-E A

Unable to execute SQL in 64bit version, because check constraint "aa....aa" in bb....bb."cc....cc" created in 32bit version

HiRDB cannot execute SQL in 64-bit mode, because the table bb....bb."cc....cc" for which the check constraint was defined was created in 32-bit mode.

aa....aa: Name of the check constraint

bb....bb: Authorization identifier of the table that defined the check constraint

cc....cc: Table identifier of the table that defined the check constraint

S: Ignores this SQL statement. If it is a definition SQL statement, it is rolled back.

P: Restart HiRDB in 64-bit mode, and then re-define the check constraint. For details on migrating tables that have a check constraint defined to 64-bit mode, see the HiRDB Version 9 Installation and Design Guide.

KFPA19459-E A

Unable to specify component specification for derived column from abstract data type, query-no=aaa

A component specification cannot be made for an abstract data type column derived by a value expression other than a column specification.

aaa: Query number

S: Ignores this SQL statement. If it is a definition SQL statement, it is rolled back.

P: Correct the SQL statement and re-execute.

KFPA19502-E A

Error occurred in UAP environment file aa....aa, operand=bb....bb,reason code=cc....cc

An error occurred in the UAP environment definition file.

aa....aa: UAP environment definition file name

bb....bb: Name of the operand causing the error

One asterisk (*) is displayed when no operand can be specified.

cc....cc: Reason code

S: Ignores this SQL statement.

P: Take appropriate action for the output reason code.

Action

Take appropriate action for the output reason code.

Reason code
Description
Action by the programmer
Action by the HiRDB administrator

1
A memory shortage occurred.
Re-execute the UAP. If the same error recurs, contact the HiRDB administrator.
Take the following steps to increase the amount of available memory:

Reduce the number of concurrently executing processes.

Increase the swap area.

Increase the real memory.

Reduce the number of RDAREAs specified in the -r option of the pdlbuffer operand. Note that a maximum of 3,200 RDAREAs can be defined with the -r option.

2
Communication to the dictionary server failed.
Confirm that the dictionary server started normally.

3
Dictionary search failed.
None
Correct the status of the data dictionary RDAREA.

99
An internal HiRDB error occurred.
Save the files under %PDDIR%\spool, %PDDIR%\lib\sysconf, or %PDDIR%\lib\sysdef and contact the customer support center.

100
The UAP environment definition file could not be opened.
Confirm that the UAP environment definition file can be found or that the HiRDB administrator can open this file (check the permissions settings of the %PDCONFPATH%\pduapenv directory or the UAP environment definition file).

101
Invalid definition
Take corrective action according to the error message that is output to the event log (in UNIX, syslogfile) on the server machine of the connection target HiRDB server.

300
An error was detected in the RDAREA type specified in the pdlbuffer operand.
Correct the RDAREA name specified in the pdlbuffer operand of the UAP environment definition.

301
Option required for the pdlbuffer operand is missing, or an option that cannot be specified was specified.
Correct the option specification of the pdlbuffer operand in the UAP environment definition.

302
Duplicate local buffer names, RDAREA names, or index names are specified in the pdlbuffer operand.
Correct the local buffer name, RDAREA name, or index names specified in the pdlbuffer operand of the UAP environment definition.

303
The local buffer count exceeded the maximum value.
Set the number of pdlbuffer operands specified in the UAP environment definition to 100 or less. For HiRDB/Parallel Server, set the value for each server to 100 or fewer.

KFPA19503-E A

Unable to begin transaction during maintenance of HiRDB

The pdchgconf command or the pdprgrenew command is executing, or a transaction is queuing due to the pdtrnqing command. As a result, transactions executing a stored procedure, ALTER PROCEDURE, ALTER ROUTINE, or ALTER TRIGGER cannot be started.

S: Ignores this SQL statement, or interrupts.

P: If the pdchgconf or pdprgrenew command is executing, wait until the command terminates, and then re-execute the UAP. In the case of transaction queuing due to the pdtrnqing command, release transaction queuing, and then re-execute the UAP.

KFPA19506-E A

Extended statement name value "aa....aa" already defined

The extended statement name value aa....aa identifies another SQL statement.

aa....aa: SQL statement identifier that is the value of the extended statement name

S: Ignores this SQL statement.

P: Correct this SQL statement and re-execute.

KFPA19507-E A

PREPARE statment missing for extended statement name value "aa....aa"

No PREPARE statement is defined for the SQL statement with the extended statement name value "aa....aa".

aa....aa: SQL statement identifier that is the value of the extended statement name

S: Ignores this SQL statement.

P: Define the PREPARE statement for the extended statement name SQL statement.

KFPA19508-E A

Open cursor associated with prepared statement identified by "aa....aa" exists

Because the associated cursor is open, assignment of the SQL statement for the extended statement name value "aa....aa" cannot be released.

aa....aa: SQL statement identifier that is the value of the extended statement name

S: Ignores this SQL statement.

P: Before executing the DEALLOCATE PREPARE statement, close the associated cursor and re-execute.

KFPA19509-E A

ALLOCATE CURSOR statement missing for cursor "aa....aa"

The cursor assignment is missing for the specified cursor "aa....aa".

aa....aa: Cursor name

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA19510-E A

Procedure aa....aa."bb....bb" not invoked

The procedure aa....aa."bb....bb" is not invoked in the same SQL session.

aa....aa: Authorization identifier

bb....bb: Routine identifier

S: Ignores this SQL statement.

P: Before executing ALLOCATE CURSOR, revise the procedure specified by ALLOCATE CURSOR to be called in the same SQL session, and re-execute.

KFPA19511-E A

Another cursor already allocated for procedure aa....aa."bb....bb"

A cursor is already assigned to the procedure aa....aa."bb....bb".

aa....aa: Authorization identifier

bb....bb: Routine identifier

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA19512-E A

Preparation for requested SQL became invalid

Preprocessing for the SQL statement that requested execution has become invalid.

S: Ignores this SQL statement.

P: Perform preprocessing of the SQL statement again using the PREPARE statement, and request execution of the SQL statement.

KFPA19513-E A

Number of aa....aa exceeds bbbb

The number of aa....aa exceeds the maximum of bbbb.

When aa....aa is extended statement name
The number of extended statement names that identify the preprocessed SQL statement exceeds 4095.

When aa....aa is extended cursor name
The number of extended cursor names that identify the cursors allocated by ALLOCATE CURSOR exceeds 4095.

aa....aa: {extended statement name | extended cursor name}

bbbb: 4095

S: Ignores this SQL statement.

P: Revise the UAP so that the number of aa....aa does not exceed the maximum. By executing the DEALLOCATE PREPARE statement, you can ensure that the extended statement names and extended cursor names do not identify the SQL statements and cursors.

KFPA19517-E A

Error occurred in servers for primary facilities,"aa....aa"

During connection, an error occurred in the server providing the primary facilities.

aa....aa: Detailed error message

If the details of the message exceed 190 characters, all subsequent characters are omitted.

S: Ignores this SQL statement.

P: Refer to the details of the error message that was output by the server providing the primary facilities, and then take one of the following actions:

Refer to the output message, and if there is a programmer measure, resolve the problem and execute the SQL again.

Refer to the output message, and if there is no programmer measure, contact the HiRDB administrator.

O: Contact the HiRDB administrator.

Action

Eliminate the error based on the detailed error message returned by the server providing the primary facilities.

KFPA19518-E A

Unable to access from host aa....aa

It is not possible to execute a related program product or utility from the host aa....aa.

aa....aa: The IP address of the related program product or utility (in the format xxx.xxx.xxx.xxx)

S: Ignores this SQL statement.

Action

Decide whether the host executing the related program product or utility must be added to the pd_security_host_group operand in the system common definition. Add a host if necessary, and then restart HiRDB.

KFPA19520-E A

Unable to execute SQL due to implicit rollback during execution of external routine.

Because an error accompanied by an implicit rollback occurred during external routine execution, the SQL statement cannot be executed. For a Java stored procedure, a database manipulation method other than the close method for the Connection object cannot be executed.

S: Ignores this SQL statement.

P: If an error accompanied by an implicit rollback occurs, correct this so that the external routine terminates.

For a Java stored procedure:
Execute the close method for the Connection object before terminating the Java stored procedure.

KFPA19521-E A

aa....aa in client environment variable PDTMPTBLRDAREA

The error indicated in aa....aa occurred in the specification of the client environment definition PDTMPTBLRDAREA.

aa....aa: Cause of error

S: Terminates connection processing.

O: Based on the cause of the error, take the appropriate corrective action as described in the following table, and then retry the operation:

Cause of error (aa....aa)
Meaning
Action

No avaliable RDAREA names
There are no temporary table RDAREAs available.
Search the dictionary table (the SQL_RDAREAS table) for possible errors in the temporary table RDAREA names specified in PDTMPTBLRDAREA, correcting any names that are not RDAREA names defined in HiRDB.

More than 100 RDAREA names
The number of temporary table RDAREA names exceeds 100.
Reduce the number of temporary table RDAREA names to 100 or fewer.

Duplicate RDAREA name "RDAREA-name"
A temporary table RDAREA name is a duplicate.
RDAREA-name:
The invalid temporary table RDAREA name (maximum of 30 bytes). If the RDAREA name is 0 bytes, "" is shown for RDAREA-name.
Delete the duplicate temporary table RDAREA name.

Invalid character "invalid-character (hexadecimal-representation)" in RDAREA name "RDAREA-name"
A temporary table RDAREA name includes a character that cannot be used in an RDAREA name.
invalid-character:
Character that is not permissible in an RDAREA name. The invalid character is not displayed if it is outside the range of printable ASCII characters (0x20-0x7e).
hexadecimal-representation:
The hexadecimal representation of the invalid character.
RDAREA-name:
A character string (maximum of 30 bytes), starting from the beginning of the temporary table RDAREA name with the invalid character, ending just before the invalid character.
Check the character specified in the temporary table RDAREA name (the character next to the RDAREA name displayed in the message text). If the RDAREA name in the message text is blank, specify a permissible character at the beginning of the RDAREA name.

Invalid length of RDAREA name "RDAREA-name"
The length of a temporary table RDAREA name exceeds 30 bytes, or is 0 bytes.
RDAREA-name:
The invalid temporary table RDAREA name (maximum of 30 bytes). If the RDAREA name is 0 bytes, "" is shown for RDAREA-name.
Revise the specified temporary table RDAREA name.

Invalid characters "invalid-character-string" after RDAREA name "RDAREA-name"#1
An invalid character string was specified after the temporary table RDAREA name.
invalid-character-string:
A character string (maximum of 30 bytes), starting from where the invalid character was detected, ending just before one of the following:
Single-byte space
Double quotation mark (")
Comma (,)
Terminating character of a specified value
Character outside the range of printable ASCII characters (0x20-0x7e)
RDAREA-name:
The temporary table RDAREA name specified immediately before the invalid characters (maximum of 30 bytes).
Separate the temporary table RDAREA names with a comma (,).

Invalid character "(hexadecimal-representation)" after RDAREA name "RDAREA-name"#2
An invalid character was specified after the temporary table RDAREA name.
hexadecimal-representation:
The hexadecimal representation of the invalid character.
RDAREA-name:
The temporary table RDAREA name specified immediately before the invalid character (maximum of 30 bytes).
Delete the invalid character or correct the RDAREA name.

Double quote missing after RDAREA name "RDAREA-name"
The ending double quotation mark (") is missing from a temporary table RDAREA name that begins with a double quotation mark (").
RDAREA-name:
The invalid temporary table RDAREA name (maximum of 30 bytes). If the RDAREA name is 0 bytes, "" is shown for RDAREA-name.
Enclose the temporary table RDAREA name in double quotation marks (").

#1

The codes of the invalid characters are displayed if they are within the range of printable ASCII characters (0x20 to 0x7e).

#2

The code of the invalid character is displayed if is outside the range of printable ASCII characters (0x20 to 0x7e).

KFPA19522-E A

"ON COMMIT" clause specified in table definition for persistent base table

ON COMMIT was specified when defining a permanent base table.

S: Ignores the SQL statement.

O: To define the permanent base table, delete ON COMMIT, and then retry the operation. To define a temporary table, specify GLOBAL TEMPORARY, and then retry the operation.

KFPA19575-E A

Invalid shared table/index definition code=aa(bb....bb)

There is an error in the shared table or shared index definition.

aa: Reason code

bb....bb: Additional error information

S: Ignores this SQL statement.

P: Reason codes and additional error information are shown below. Correct the SQL statement, and re-execute the job.

Reason code
Additional error information
Explanation

01
Invalid specification for partitioning table
A shared table cannot use partitioned storage.

02
Invalid specification for WITHOUT ROLLBACK table
WITHOUT ROLLBACK cannot be specified for a shared table.

03
Specified RDAREA cc....cc for table not shared rdarea
When a shared table is defined for a HiRDB/Parallel Server, the shared table can only be stored in a shared RDAREA.
cc....cc: RDAREA name

04
Specified RDAREA cc....cc for index not shared rdarea
When a shared index is defined for a HiRDB/Parallel Server, the shared index can only be stored in a shared RDAREA.
cc....cc: RDAREA name

KFPA19576-E A

Specified RDAREA aa....aa is shared RDAREA

Because the specified RDAREA is a shared RDAREA, the following operations are invalid:

Definition of a table other than a shared table

Definition of an index other than a shared index

Addition of an RDAREA

Changing partitioned storage conditions

Definition of a sequence generator

aa....aa: RDAREA name

S: Ignores this SQL statement.

P: Specify an RDAREA that is not a shared RDAREA, and then retry the operation.

KFPA19577-E A

Unable to create partial structure index due to invalid data type for partial structure path

Because of an invalid data type specified in the substructure path, the substructure index cannot be defined.
The data types that can be specified in the substructure path are as follows:

INTEGER

DECIMAL

FLOAT

VARCHAR

S: Ignores this SQL statement.

P: Eliminate the cause of the error and re-execute the SQL statement.

KFPA19581-E A

Invalid constraint definition for table aa....aa."bb....bb" code=cc(dd....dd)

There is an error in the referential constraint definition or the check constraint definition of table aa....aa."bb....bb".

aa....aa: Authorization identifier

bb....bb: Table identifier

cc: Reason code

dd....dd: Additional error information

S: Ignores this SQL statement.

P: Reason codes and additional error information are shown below. Correct the SQL statement, and re-execute the job.

Reason code | Additional error information | Explanation
01 | shared table | Referential constraints cannot be defined for shared tables.
02 | INSERT ONLY table | Referential constraints and checked constraints cannot be defined for falsification-prevented tables.

KFPA19582-E A

Unable to drop column on aa....aa."bb....bb" due to cc....cc

The column cannot be deleted, for one of the following reason:

A check constraint has been defined for the table with the column is to be deleted.

A referential constraint (foreign key) has been defined for the table with the column to be deleted.

The table with a column to be deleted is a referential constraint referenced table.

aa....aa: Authorization identifier

bb....bb: Table identifier

cc....cc:

check constraint: A check constraint has been defined.

referential constraint: A referential constraint (foreign key) has been defined.

referenced table: This is a referential constraint referenced table.

S: Ignores this SQL statement.

P: Review the table name. Revise it as necessary, and re-execute the UAP.

KFPA19583-E A

Number of defined foreign keys on table aa....aa."bb....bb" exceeds 255

The number of foreign keys that can be specified for a single table has exceeded the maximum (255).

aa....aa: Authorization identifier

bb....bb: Table identifier

S: Ignores this SQL statement.

P: Correct the number of CREATE TABLE foreign keys and re-execute.

KFPA19584-E A

More than 254 check constraint limits in aa....aa."bb....bb"

Because the restriction on the number of check constraints (total number of Boolean operators specified in the check constraint search conditions [number of AND and OR, excluding the number of AND and OR in a CASE form's WHEN search conditions] and the total number of check constraints) that can be defined for a table has exceeded the maximum value (254), a check constraint cannot be defined.

aa....aa: Authorization identifier

bb....bb: Table identifier

S: Ignores this SQL statement.

P: Make the check restraint limit value 254 or less and re-execute.

KFPA19587-E A

Unable to change check pending status for table aa....aa."bb....bb",code=cc(dd....dd)

The check pending status of table aa....aa."bb....bb" cannot be changed.

aa....aa: Authorization identifier

bb....bb: table identifier

cc: reason code

dd....dd: optional information about the error

S: Terminates the processing.

O: The table below explains the reason codes for error-related optional information. Resolve the error, and then re-execute the command as necessary.

Reason code (cc) | Optional information (dd....dd) | Explanation
01 | Table not found in system | The table definition to be processed was deleted during the execution of the utility.
02 | Table definition altered | The table definition to be processed was modified during the execution of the utility.

KFPA19602-E A

Unable to define referential constraint aa....aa."bb....bb" due to duplicated constraint

In a referential constraint, the same referenced table foreign key cannot be referenced from the same foreign key configuration column (independent of the order).

aa....aa: Authorization identifier

bb....bb: Constraint name

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA19603-E A

Unable to alter table,due to aa....aa

A column could not be altered for the following reasons:

The applicable column used an old or new values correlation number under the search condition of the trigger action to reference another column. This column cannot be altered or deleted.

The applicable column uses an old or new values correlation number in the trigger SQL statement to reference another column. This column cannot be altered or deleted.

aa....aa:

triggered action condition:

The column that could not be altered is being used under the trigger action search condition.

triggered SQL statement:

The column that could not be altered is being used by the trigger SQL statement.

S: Ignores this SQL statement.

P: When the SQL object can be invalidated, specify WITH PROGRAM and re-execute the job.

KFPA19604-E A

COMPRESSED specification for column "aa....aa" invalid, due to bb....bb

An error occurred in the compression specification in column aa....aa for the reason indicated in bb....bb.

aa....aa: Column name

bb....bb:

unsupported data type:

The specified column has a data type that cannot be compressed.

data length less than 256:

Compression was specified for a column whose defined length is less than 256 bytes.

out of range partition size for compress:

The compression partition size is outside of the range of permissible values.

S: Ignores this SQL statement.

P:

When bb....bb is unsupported data type:

If you want to compress the data, change the data type of the column to a data type that can be compressed. If you do not want to compress the data, delete the compression specification. For the data types that can be compressed, see the manual HiRDB Version 9 SQL Reference.

When bb....bb is data length less than 256:

Compression is not effective on a column with a defined length that is less than 256 bytes. Delete the compression specification.

When bb....bb is out of range partition size for compress:

For details about the range of compression partition size values, see Range of values that can be specified for the compression partition size in the manual HiRDB Version 9 SQL Reference.

KFPA19610-E A

Unable to aa....aa except bbb due to cc....cc

Due to cc....cc, cannot grant or revoke privileges other than bbb.

aa....aa: {grant access privileges|revoke access privileges}

bbb: ALL

cc....cc: temporary table

S: Ignores this SQL statement.

P: For a temporary table, it is not possible to grant only some privileges. Specify ALL when granting or revoking privileges on a temporary table to another user.

KFPA19612-E A

Invalid usage of MULTIDIM partitioning table code=aa,reason=bb....bb cc....cc dd....dd

An error was detected in the specification of the matrix partitioning table.

aa: Reason code

bb....bb: Error information

The following table shows the reason code (aa) and error information (bb....bb):

Error code (aa)
Error information (bb....bb)
Description

01
only one RDAREA
Only one RDAREA was specified.

03
boundary values over
The sum of specified boundary values exceeds 4,096.

04
value and RDAREA unmatch
The number of boundary values and RDAREAs does not match.

05
RDAREA specification
An error was detected in the RDAREA specification.
Possible causes:

The specified table storage RDAREA does not match the specified BLOB or index storage RDAREA.

For ALTER TABLE or CREATE INDEX, the specification does not match the specification for table definition.

No non-partitioning key index storage RDAREA was specified.

06
RDAREA LIST unmatch
The number of RDAREAs for each matrix partitioning RDAREAs list does not match.

08
invalid hash name
One of the following errors occurred in a hash function specification:

The hash function name is invalid

The column length of the partition key is invalid

09
more than 15 columns for HASH KEY
The number of columns specified in the partition key of the hash partition exceeds 15.

10
invalid HASH function "HASH0"
One of the following errors occurred when HASH0 was specified as the hash function:

An impermissible data type was specified for the partitioning key.
For details about data types that can be specified, see hash-function-name under CREATE TABLE (Define table) in the manual HiRDB Version 9 SQL Reference.

More than one column was specified in the partitioning key.

11
invalid HASH function "HASHZ"
One of the following errors occurred when HASHZ was specified as the hash function:

An impermissible data type was specified for the partitioning key.
For details about data types that can be specified, see hash-function-name under CREATE TABLE (Define table) in the manual HiRDB Version 9 SQL Reference.

More than one column was specified as the partitioning key.

cc....cc: RDAREA specified location causing the error

table: Table

column: Column

index: Index

cluster key: Cluster key

primary key: Primary key

Otherwise, nothing is output.

dd....dd: Nothing is output when the table name, column name, or index name cc....cc specifying the RDAREA causing the error is the cluster key or primary key.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute.

KFPA19613-E A

Unable to ALTER TABLE aa....aa,bb....bb, code=cc

Cannot execute aa....aa in ALTER TABLE for the reason indicated in bb....bb.

aa....aa:

ADD PRIMARY KEY: Add a primary key

DROP PRIMARY KEY: Delete the primary key

bb....bb: Additional error information

cc: Reason code

The following table lists the reason codes and provides additional error information:

Reason code | Additional error information | Meaning
01 | because primary key already exist | Cannot add a primary key because there already is a primary key.
02 | because referencing table exists | Cannot delete the primary key because it is referenced from a foreign key.
03 | because primary key not exist | Cannot delete the primary key because there is no primary key.
04 | because nullable column specified | Cannot add a primary key because a column without the NOT NULL constraint was specified for the primary key configuration column.
05 | due to primary cluster key | Cannot delete the primary key because it is a cluster key with PRIMARY specified.

S: Ignores this SQL statement.

P: Eliminate the cause of error, which is indicated in reason code cc and the additional error information bb....bb, and then re-execute the SQL statement.

KFPA19615-E A

Unable to aa....aa because INSERT ONLY table bb....bb."cc....cc" not empty

The definition SQL aa....aa cannot be executed for falsification prevented table bb....bb."cc....cc", in which data is stored.

aa....aa: Definition SQL

DROP TABLE: Delete the table

DROP SCHEMA: Delete the schema

bb....bb: Authorization identifier

cc....cc: Table name

S: Ignores this SQL statement.

P: Falsification prevented tables in which data is stored cannot be deleted. Change the table name, and then re-execute this SQL statement.

KFPA19616-E A

Unable to drop insertion history column on INSERT ONLY table

The insert history maintenance column specified during the deletion prevented duration of the falsification prevented table cannot be deleted.

S: Ignores this SQL statement.

KFPA19617-E A

Only DATE type column with "SYSTEM GENERATED" can be specified for insertion history column on INSERT ONLY table

Only DATE type columns with SYSTEM GENERATED specified can be specified in the insert history maintenance column of a falsification prevented table.

S: Ignores this SQL statement.

P: Specify a DATE type column with SYSTEM GENERATED specified in the insertion history column, and then re-execute this SQL statement.

KFPA19620-E A

Invalid delete prohibition interval for INSERT ONLY table

An error was detected in the deletion prevented duration of the falsification prevented table.

S: Ignores this SQL statement.

P: Correct the specification of the deletion prevented duration and re-execute this SQL statement.

When date interval data is specified:
As a decimal value, specify a 99-day interval between Year 0000 Month 00 Day 01 and Year 9999 Month 11 Day 99 (YYYYMMDD).

When a label duration is specified:
Specify each value within the following ranges:
YEAR[S]: 1-9,998
MONTH [S]: 1-119,987
DAY [S]: 1-3,652,058

KFPA19621-E A

Unable to CREATE aa....aa TEMPORARY TABLE due to bb....bb, code=cc

The temporary table cannot be defined due to bb....bb.

aa....aa: GLOBAL

bb....bb: Additional error information

cc: Reason code

S: Ignores this SQL statement.

P: The reason codes and additional error information are described below. Eliminate the cause of the error, correct the SQL statement, and then retry the operation.

Reason code | Additional error information | Meaning
01 | insert only table | The falsification prevention option was specified.
03 | WITHOUT ROLLBACK specification | The WITHOUT ROLLBACK option was specified.
04 | SEGMENT REUSE specification | The SEGMENT REUSE option was specified.
05 | invalid data type | The specified data type cannot be specified in a temporary table. For the data types that can be specified in a temporary table, see GLOBAL TEMPORARY under CREATE TABLE (Define table) in the manual HiRDB Version 9 SQL Reference.
06 | updatable column specification | An updatable column was specified.
07 | reserved column specification | A reserved column was specified.
08 | cluster key specification | A cluster key was specified.
09 | foreign key specification | A foreign key was specified.
10 | check constraint | A check constraint was defined.
11 | rdarea specification | RDAREA was specified.
12 | shared table | SHARE was specified to try to use the temporary table as a shared table.

KFPA19622-E A

Unable to CREATE aa....aa for temporary table due to bb....bb, code=cc

The aa....aa for the temporary table cannot be defined due to bb....bb.

aa....aa: INDEX

bb....bb: Additional error information

cc: Reason code

S: Ignores this SQL statement.

P: The reason codes and additional error information are described below. Eliminate the cause of the error, correct the SQL statement, and then retry the operation.

Reason code | Additional error information | Meaning
01 | rdarea specification | RDAREA was specified.
02 | EMPTY specification | The EMPTY option was specified.

KFPA19624-E A

Unable to aa....aa SEQUENCE because of "bb....bb",code=cc

Because this is for bb....bb, it is not possible to use aa....aa in the sequence generator.

aa....aa: CREATE

bb....bb: Additional error information

cc: Reason code

S: Ignores this SQL statement.

P: Reason codes and additional error information are shown below. Eliminate the cause of the error, correct the SQL statement and re-execute.

Reason code
Additional information on errors
Meaning

01
DATA TYPE INVALID
There is an invalid data type specification.

02
START VALUE INVALID
There was an error in the specification of the sequence generator start option.

A specification other than an integer literal or scale 0 decimal literal was made.

The specification is outside the range of values permitted for the data type.

The start option value of the sequence generator is smaller than the smallest option value of the sequence generator.

The start option value of the sequence generator is larger than the largest option value of the sequence generator.

04
INCREMENT VALUE INVALID
There was an error in the specification of the sequence generator extension option.

A specification other than an integer literal or scale 0 decimal literal was made.

The specification is outside the range of values permitted for the data type.

A specification of 0 is made for the value of the sequence generator extension option.

05
MAX VALUE INVALID
There was an error in the specification of the sequence generator maximum value option.

A specification other than an integer literal or scale 0 decimal literal was made.

The specification is outside the range of values permitted for the data type.

The smallest option value of the sequence generator is larger than the largest option value of the sequence generator.

06
MIN VALUE INVALID
There was an error in the specification of the sequence generator minimum value option.

A specification other than an integer literal or scale 0 decimal literal was made.

The specification is outside the range of values permitted for the data type.

07
LOG INTERVAL INVALID
The specification for the acquiring count is invalid.

A specification other than an integer literal was made.

The specification exceeds the 1 to 2³¹-1 range.

The specification exceeds the specifiable range.

KFPA19625-E A

Invalid usage on ALTER TABLE CHANGE RDAREA,code=aa(bb....bb)

The ALTER TABLE CHANGE RDAREA is incorrectly specified.

aa: Reason code

bb....bb: Additional error information

S: Ignores this SQL statement.

P: Reason codes and additional error information are shown below.

Reason code 03:
Delete the index, execute ALTER TABLE, and then redefine the index.

Reason code 22:
Unload the table, define the table without specifying the same value more than once# in a storage condition, and then reload the table.
#: The term same value refers to two or more literals that are identical, or a literal specified by HiRDB that, when corrected, produces a value that is the same.

All other reason codes:
Revise the SQL statement, and re-execute the job.

Reason code
Additional error information
Explanation

01
Non partition divided table
A non boundary value partitioned table is specified.

02
Insert only table
A falsification-prevented table is specified.

03
Not divided index exist on table
One of the following errors has occurred:

When attempting to modify a row partition table on the server, the non-partitioning key index for the table is not row-partitioned.

When attempting to modify a table not row-partitioned on the server, multiple partitioning storage conditions are stored in the same RDAREA and a non-partitioning key index is defined.

When attempting to modify a table for which an index in a single RDAREA is defined, an attempt was made to change the RDAREA storing the table.

04
Invalid partition value
The specified boundary value or storage condition value contains the following errors:

Boundary value:

The length of the boundary value character string is 0.

The boundary value data type cannot be converted into the data type of a column specified in the partitioned storage conditions.

The boundary value data length exceeds the data length of the column specified in the partitioned storage conditions.

The boundary value is logically inappropriate.

The boundary value data contents are invalid.

The boundary value to be changed is not in an existing definition.

The boundary value to be changed is not in ascending order.

The boundary value to be changed is not continuous.

After the change, the boundary values are not in ascending order.

After the change, the boundary values contain duplicate specifications.

After the change, there is an error in the specification range of boundary values.

For a matrix-partitioned table, the boundary value specified last in the list of boundary values after the change does not match the boundary value specified last in the list of boundary values before the change.

Storage condition value:

The character string length in the storage condition value is 0.

The data type of the storage condition value cannot be converted to a partitioning key column data type.

The data length specified in the storage condition is greater than the data length for the partitioning key column.

05
Invalid result
The result of partitioning or combining is as follows:

One RDAREA is used.

The total number of RDAREA partitions exceeds the maximum value. The maximum value is 4,096 including duplicates.

The total number of literals specified in the partitioned storage condition is greater than 15,000.

After combining, the total number of RDAREAs will be 1. Therefore, you cannot specify OTHERS, or an RDAREA for which storage conditions have not been specified.

For a table with an index in a row-partitioned RDAREA, the number of RDAREAs for the table after the change will be 1.

For a matrix-partitioned table, the number of first-dimension partitions or the number of second-dimension partitions will be 1.

06
Index not found on table
The specified index, primary key, or cluster key is not defined for the relevant table.

07
Not specify all index
FOR INDEX, FOR PRIMARY KEY, or FOR CLUSTER KEY is not specified for all indexes.

08
Unmatch number of RDAREA
The number of RDAREAs specified in the modified boundary value partitioning specification, the modified storage condition partitioning specification, or the matrix-partitioned table storage RDAREA change specification is different from the number specified in the modified index storage RDAREA name list or the LOB column storage RDAREA change specification.

09
Invalid RDAREA for index or "LOB"
One of the following errors occurred in the relationship between the tables and indexes or between the tables and the RDAREAs that store the BLOB columns:

The position in which a duplicated RDAREA is specified in the modified index storage RDAREA name list or the LOB column storage RDAREA change specification is different from the modified boundary value partitioning specification or the matrix-partitioned table storage RDAREA change specification.

The position in which a new RDAREA is specified in the modified index storage RDAREA name list or the LOB column storage RDAREA change specification is different from the modified boundary value partitioning specification, the modified storage condition partitioning specification, or the matrix-partitioned table storage RDAREA change specification.

The position in which an existing RDAREA is specified in the modified index storage RDAREA name list or the LOB column storage RDAREA change specification is different from the modified boundary value partitioning specification, the modified storage condition partitioning specification, or the matrix-partitioned table storage RDAREA change specification.

If OTHERS is specified, the modified table storage RDAREAs, index storage RDAREAs, and LOB column storage RDAREAs do not have the correct correspondence with one another.

11
Duplicate RDAREA
In an RDAREA that stores different LOB columns, the same RDAREA has multiple specifications, or an attempt was made to add an RDAREA that is already stored.

12
Invalid matrix table
One of the following errors occurred in the matrix-partitioned table change specification:

MULTIDIM was specified for a table that is not a matrix-partitioned table.

A dimensional partitioning column name that was specified is not assigned key range partitioning with boundary values.

The number of partitions does not correspond to the number of RDAREA specifications.

13
Invalid usage WITHOUT PURGE
There is an error in the WITHOUT PURGE specification.

WITHOUT PURGE is specified, but the pre-change RDAREA is not specified as the post-change RDAREA.

14
Invalid RDAREA
One of the following errors occurred in the RDAREA specification when changing the partitioning storage condition:

If a boundary value was specified:
Identify the error by referring to the table Cause of an RDAREA specification error when modifying partitioning storage conditions (boundary value specification) following this table.

If a storage condition was specified:
Identify the error by referring to the table Cause of an RDAREA specification error when modifying partitioning storage conditions (storage condition specification) following this table.

For matrix partitioning:
Identify the error by referring to the table Cause of an RDAREA specification error when modifying partitioning storage conditions (for matrix partitioning) following this table.

15
FOR COLUMN clause invalid
There is an error in the specified column.

It is not a BLOB column,

16
Duplicate INDEX name
Duplicate index names are specified.

17
Invalid index type
The type of the index specified in the FOR PRIMARY, FOR CLUSTER, or FOR INDEX clause is invalid.

18
Duplicate column name
Duplicate column names are specified.

19
Not specify all "LOB"
The FOR COLUMN clause is not specified for all LOB columns.

20
Invalid partitioning condition
When an attempt was made to specify partitioning storage conditions, one of the following errors occurred:

A column name different from the partitioning key was specified.

An RDAREA specifying storage conditions for the RDAREA to be partitioned was specified:

Storage conditions for the RDAREA to be partitioned are not specified for all RDAREAs to be partitioned.

A storage condition not contained in the storage conditions for the RDAREA to be partitioned is specified for partitioned RDAREAs.

An RDAREA not specifying storage conditions for the RDAREA to be partitioned was specified, or OTHERS was specified:

If the object of partitioning is an RDAREA for which no storage conditions are specified, or OTHERS, the storage conditions specified following partitioning already exist.

Duplicate storage conditions are specified.

21
Invalid partitioning condition table
Storage conditions on any of the following tables cannot be modified:

Tables other than row-partitioned tables with a storage condition specified

Row-partitioned tables for which a storage condition other than = is specified in a comparison operator

22
Table with same values in partitioning condition
Partitioning storage conditions cannot be modified in a table for which the same value is specified more than once in a storage condition. The same value means that, given identical literals, and if literals for which HiRDB is specified are corrected, the same result is produced. For example, if the data type for a table partitioning key member column is INTEGER, same values means tables for which storage condition C1=(1,1,1) is specified or tables for which storage condition C1=(1.1,1.2,1.3) is specified.

51
Too many number of value
The number of specified boundary values exceeds the number that can be changed.

During partitioning: The maximum to be changed is 1, and the maximum after changing is 16.

During combining: The maximum to be changed is 16, and the maximum after changing is 1.

52
Too many specify "FOR INDEX"
FOR INDEX was specified 256 or more times.

53
Too many specify "FOR PRIMARY" or "FOR CLUSTER"
FOR PRIMARY or FOR CLUSTER was specified 2 or more times.

54
Invalid duplicate columns
A column was specified twice when specifying a matrix-partitioned table.

99
User data type
The partition storage conditions cannot be changed for row partitioned tables used for abstract data type columns

Cause of an RDAREA specification error when modifying partitioning storage conditions (boundary value specification)

Error type
Cause

During partitioning
During combining

Error in modified boundary value partitioning specification

A nonexistent RDAREA is specified.

Contiguous boundary values are specified on the same RDAREA.

A nonexistent RDAREA is specified.

The specified RDAREA is the same as the RDAREAs specified for the previous and next storage ranges.

Error in modified index storage RDAREA name list or LOB column storage RDAREA change specification

A nonexistent RDAREA is specified.

An RDAREA with OTHERS is specified.

A nonexistent RDAREA is specified.

An RDAREA with OTHERS is specified.

Cause of an RDAREA specification error when modifying partitioning storage conditions (storage condition specification)

Error type
Cause

During partitioning
During combining

Error in the RDAREA information list before change

An RDAREA storing the table to be modified is not specified.

An RDAREA with one storage condition is specified.

OTHERS is specified on a table containing an RDAREA devoid of storage conditions.

An RDAREA storing the table to be modified is not specified.

OTHERS is specified on a table containing an RDAREA devoid of storage conditions.

Duplicate RDAREA names are specified.

Error in the storage condition partitioning specification after change

After partitioning, there will be only one RDAREA.

Duplicate RDAREA names are specified.

A nonexistent RDAREA is specified.

An RDAREA used in other storage conditions for the table to be modified is specified.

Two or more RDAREAs are specified.

A nonexistent RDAREA is specified.

An RDAREA used in other storage conditions for the table to be modified is specified.

Error in the combination between the RDAREA information list before change and the storage condition partitioning specification after change
Refer to the table Invalid combination between an RDAREA information list before change and a storage condition partitioning specification after change following this table.
OTHERS is specified after combination but an RDAREA without storage conditions or OTHERS specified is not included in the items to be combined.

Error in the index storage RDAREA name list after change or the LOB column storage RDAREA modification specification after change

A nonexistent RDAREA is specified.

Duplicate RDAREA names are specified.

An RDAREA for storage of indexes other than the table to be modified is specified.

A LOB storage RDAREA other than the table to be modified is specified.

A nonexistent RDAREA is specified.

An RDAREA for storage of indexes other than the table to be modified is specified.

A LOB storage RDAREA other than the table to be modified is specified.

Invalid combination between an RDAREA information list before change and a storage condition partitioning specification after change

RDAREA specified in an RDAREA information list before change
RDAREA specified in a storage condition partitioning specification after change

RDAREA with storage conditions

An RDAREA without storage conditions is specified.

An RDAREA with OTHERS is specified.

RDAREA without storage conditions
An RDAREA without storage conditions or with OTHERS specification is not specified.

RDAREA with OTHERS specified

Cause of an RDAREA specification error when modifying partitioning storage conditions (for matrix partitioning)

Error type
Cause

During partitioning
During combining

Error in the matrix-partitioned table storage RDAREA modification specification.
A nonexistent RDAREA is specified.
A nonexistent RDAREA is specified.

Error in the index storage RDAREA name list after change or the LOB column storage RDAREA modification specification after change.

A nonexistent RDAREA is specified.

An RDAREA with OTHERS is specified.

A nonexistent RDAREA is specified.

An RDAREA with OTHERS is specified.

KFPA19631-E A

Definition for INSERT ONLY table aa....aa."bb....bb" failed, code=cc(dd....dd)

An error has occurred in a falsification-prevented table related definition.

aa....aa: Authorization identifier

bb....bb: Table identifier

cc: Reason code

dd....dd: Additional error information

S: Ignores this SQL statement.

P: Reason codes and additional error information are shown below. Correct the SQL statement, and re-execute the job.

Reason code
Additional error information
Explanation
Action

01
INSERT ONLY table
Consider the following causes:

The INSERT ONLY option was specified for a falsification-prevented table.

An updatable column attribute was specified for a falsification-prevented table.

Revise the specified table name.

02
referential constraint
A table with a referential constraint defined cannot be a falsification-prevented table.

03
check constraint
A table with a check constraint defined cannot be a falsification-prevented table.

04
data type
UPDATE ONLY FROM NULL cannot be specified for the following data types:

BLOB column

BINARY type column 32,001 bytes or larger

Revise the specified column name.

05
already defined
Consider the following causes:

An updatable column attribute was specified for an updatable column.

An attempt was made to change the data length for a BINARY type column, for which UPDATE ONLY FROM NULL is specified in the updatable column attribute, to 32,001 bytes or greater.

06
SYSTEM GENERATED
An updatable attribute cannot be specified for a column with SYSTEM GENERATED specified.

07
NOT NULL
UPDATE ONLY FROM NULL cannot be specified for a column with a non-null attribute.

08
can not update
Consider the following causes:

An updatable attribute was specified for a cluster key.

An updatable attribute was specified for a column composed of a distributed key. However, for columns composed of a partitioning key that is a flexible hash partition, only the UPDATE specification is allowed.

09
only UPDATE columns
Consider the following causes:

An attempt was made to make a table for which all columns were specified with the updatable attribute into a falsification- prevented table.

The result of operation on a falsification- prevented table cannot specify that all columns be updatable.

When CREATE TABLE is executed:
Specify at least one column without the updatable attribute.

When ALTER TABLE CHANGE INSERT ONLY is executed:
Add a column without the updatable attribute.

When ALTER TABLE DROP column name is executed:
Revise the column name.

10
reserved column
Consider the following causes:

An updatable attribute was specified for a reserved column.

An attempt was made to make a table with a reserved column into a falsification-prevented table.

When CREATE TABLE is specified with the falsification prevention option:
Do not specify a reserved column.

When a reserved column is defined with CREATE TABLE or a reserved column is added with ALTER TABLE:
Do not specify the updatable column attribute.

When a table is changed to a falsification prevented table with ALTER TABLE:
Delete the reserved column before executing.

When an updatable column attribute is changed with ALTER TABLE:
Check whether the column to be changed is a reserved column.

KFPA19632-E A

User aa....aa unable to execute CONNECT

User with authorization identifier aa....aa cannot connect (CONNECT) to HiRDB.

aa....aa: Authorization identifier

S: Ignores this SQL statement.

P: The following shows causes and actions:

Cause
Action

There is no CONNECT privilege.
Ask a user with the DBA privilege to grant the CONNECT privilege, and then retry the operation.

An error occurred in the specified password.
If this message is output when connecting to HiRDB, specify the correct password, and then retry the operation.

Consecutive certification failure account lock state.
Check with a user with the DBA privilege to be sure that the system is in consecutive certification failure account lock state. If it is in consecutive certification failure account lock state, have the HiRDB administrator release the consecutive certification failure account lock state, and then re-execute.

Password-invalid account lock state.
Check with a user with the DBA privilege to be sure that the system is in password-invalid account lock state.
If it is in password-invalid account lock state, have the HiRDB administrator change the password to one that satisfies the character column restrictions, and then re-execute.

KFPA19633-E A

Unable to execute SQL for connection security,code=aa(bb....bb)

Due to reason aa, connection security facility SQL statements cannot be executed.

aa: Reason code

bb....bb: Additional error information

S: Ignores this SQL statement.

P: Based on the output reason code and additional error information, eliminate the cause of the error and re-execute the SQL.

Reason code | Additional error information | Explanation
01 | Lack of privilege | This cannot be executed due to lack of the DBA privilege. Or, this cannot be executed because the password of a user with the DBA privilege is not registered with HiRDB.
02 | Specified value for "PASSWORD MIN LENGTH" out of range | The specification for the minimum password length is out of range.
03 | Specified value for "CONNECT PERMISSION COUNT" out of range | The specification for the permitted number of consecutive certification failures is out of range.
04 | Specified value for "CONNECT LOCK" out of range | The specification for the account lock period is out of range.
05 | Invalid Password of DBA or auditor | The DBA or auditor password violates the character string restrictions.
06 | Already defined | The specified connection security facility is already defined.
07 | Undefined | The specified connection security facility is not defined.

KFPA19634-E A

Unable to execute "GRANT aa....aa" to bb....bb due to invalid password (cc....cc)

The password violates one of the following restrictions, and therefore the GRANT statement cannot be executed.

Minimum byte count

Specification restrictions on the authorization identifier

Specification restrictions on single character types

aa....aa:

DBA

AUDIT

CONNECT

bb....bb: Authorization identifier

cc....cc:

min length

user identifier

similar

S: Ignores this SQL statement.

P: Change to a password that satisfies the password character string restrictions, and re-execute the SQL statement.

KFPA19635-E A

Unable to execute "GRANT DBA" to aa....aa for password account locked

User aa....aa is in password-invalid account lock state, and therefore the DBA privilege cannot be granted by the GRANT DBA statement, or the password cannot be changed.

aa....aa: Authorization identifier

S: Ignores this SQL statement.

P: Release the password-invalid account lock state, and execute the GRANT DBA statement. For details on how to release the password-invalid account lock state, see the HiRDB Version 9 System Operation Guide.

KFPA19670-E A

Unable to access aa....aa bb....bb."cc....cc" due to dd....dd [ee....ee ff....ff] currently in use,resource id=gg....gg

aa....aa bb....bb."cc....cc" is not accessible, because another user is using the applicable resources in the definition SQL or the utility, you cannot access.

aa....aa: {table|routine|sequence}

bb....bb: {authorization identifier | PUBLIC | ********}

If aa....aa is routine and you cannot specify an authorization identifier, eight asterisks (*) are output.

cc....cc:

If aa....aa is table, the table identifier

If aa....aa is routine, the routine identifier

If aa....aa is sequence, the sequence generator identifier

dd....dd: Resource type name

ee....ee: Resource name 1

ff....ff: Resource name 2

gg....gg: Resource information

For details about resource types, resource names, and resource information, see Table 6-1 Resource types, resource names, and resource information for lock control errors.

S: Invalidates this transaction.

P: Re-execute after other users finish using the resources in question. You can use the The command pdls -d lck -a to determine whether resources are being used by another user.

KFPA19671-E A

Unable to access aa....aa of ID bb....bb due to cc....cc [dd....dd ee....ee] currently in use,resource id=ff....ff

IDs that are bb....bb followed by aa....aa or abstract data types are not accessible, because another user is using the applicable resources in the definition SQL or the utility.

aa....aa: {table|routine|sequence|abstract data type}

bb....bb:

If aa....aa is table:

Table ID (value of the TABLE_ID column in the data dictionary table SQL_TABLES)

If aa....aa is routine:

Routine object ID (value of the OBJECT_ID column in the data dictionary table SQL_ROUTINES)

If aa....aa is sequence:

Sequence generator ID (value of the SEQUENCE_ID column in the data dictionary table SQL_SEQUENCES)

If aa....aa is abstract data type:

********

cc....cc: Resource type name

dd....dd: Resource name 1

ee....ee: Resource name 2

ff....ff: Resource information

For details about resource types, resource names, and resource information, see Table 6-1 Resource types, resource names, and resource information for lock control errors.

S: Invalidates this transaction.

P: Re-execute after other users finish using the resources in question. You can use the The command pdls -d lck -a to determine whether resources are being used by another user.

KFPA19680-E A

Invalid event type aa....aa bb....bb for specified audit definition

In the event definition subject to audit, the combination of the operation type indicated by aa....aa, the event type indicated by bb....bb, and other operands is invalid.

aa....aa: Operation type

bb....bb: Event type

The following shows operation types and event types:

Operation types | Event types
ANY | *** (Not applicable)
SESSION | CONNECT
DISCONNECT
AUTHORIZATION
ANY
PRIVILEGE | GRANT
REVOKE
ANY
DEFINITION | CREATE
DROP
ALTER
ANY
ACCESS | SELECT
INSERT
UPDATE
DELETE
PURGE
ASSIGN
CALL
LOCK
NEXT VALUE
ANY
UTILITY | PDLOAD
PDRORG
PDEXP
PDCONSTCK
ANY

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute. For allowable combinations of operation types, event types, and other operands, see CREATE AUDIT in the manual HiRDB Version 9 SQL Reference.

KFPA19681-E A

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

Table aa....aa."bb....bb" cannot be specified in a derived query expression in a public view definition.

The following tables cannot be specified in a public view definition:

A base table or viewed table owned by another user

A public viewed table that was defined by another user

A viewed table that is owned by the user but satisfies either of the following conditions:
(1) It uses a base table or viewed table, owned by another user, as the base table.
(2) It uses a public viewed table that was defined by another user as the base table.

aa....aa: Authorization identifier

bb....bb: Table identifier of the base table, viewed table, or public viewed table

S: Ignores this SQL statement.

P: Revise the base table of the public viewed table.

KFPA19683-E A

Unable to alter public procedure aa....aa."bb....bb", except by routine creator or DBA

The routine cannot be re-created, because the executing agent of the public routine aa....aa."bb....bb" is neither the one who created the public routine nor a DBA privilege holder.

aa....aa: PUBLIC

bb....bb: Routine identifier

S: Ignores this SQL statement.

P: Take one of the following measures:

Execute this SQL statement on the public procedure defined by the executing agent.

Re-execute the public routine as a user with DBA privileges.

KFPA19700-E A

HiRDB is under maintenance code=a

Either the pdchgconf command or the pdprgrenew command is currently running, or a transaction is queuing due to the pdtrnqing command. Therefore, a connection cannot be established to the client and a transaction cannot be started.

a: Internal code

S: Disconnects the client from HiRDB.

P: Terminate the UAP.

O:

When the client library is version 07-00 or later:

The pdchgconf command or pdprgrenew command may have failed. Request the HiRDB administrator to check the HiRDB status. After HiRDB starts, re-execute the UAP.

For transaction queuing due to the pdtrnqing command, release transaction queuing, and then re-execute the UAP.

When the client library is a version earlier than 07-00:

After the pdchgconf command or pdprgrenew command has finished, re-execute the UAP.

For transaction queuing due to the pdtrnqing command, release transaction queuing, and then re-execute the UAP.

KFPA19701-E A

Unable to execute required SQL in Online DB Reorganization, RDAREA = aa....aa

The requested SQL cannot be executed while updatable online reorganization is in progress.

aa....aa: RDAREA name

S: Invalidates the applicable transaction.

O: Contact the HiRDB administrator.

Action

Re-execute after the updatable online reorganization of the applicable RDAREA is released.

To re-execute without releasing, consider the following items:

If you are executing in a no-log environment, consider whether the client environment variable PDDBLOG can be changed to ALL.

During updatable online reorganization, the UAP cannot operate on the original RDAREA. If such operation is desired, specify YES in the client environment definition PDDBORGUAP. For details on operation of the original RDAREA during online reorganization hold, see the manual HiRDB Version 9 Staticizer Option Description and User's Guide. Further, for details on updatable online reorganization commands, see the manual HiRDB Version 9 Command Reference.

KFPA19702-E A

Unable to execute SQL for definition,RDAREA name=aa....aa,tableID=bb....bb,reason code=c

For the reason indicated in c, the definition SQL or utility cannot be executed.

aa....aa: Name of RDAREA where invalid status was detected

Asterisks (********) are displayed when the reason code is 1 or 3.

bb....bb: The number of the table subject to the definition SQL or utility, or the number of the table on which an index subject to a definition SQL is defined

Asterisks (********) are displayed for definition (CREATE TABLE).

c: Reason code

1: Definition SQL or utility execution conditions are not satisfied for the application of the inner replica facility.

2: RDAREA aa....aa related to table number bb....bb is executing updatable online reorganization.

3: The command hold status and the closed status coexist with one or more other statuses in the RDAREA related to table number bb....bb.

S: Ignores this SQL. Terminates the processing of the utility.

Action

For reason code 1:

Execute the pdrdrefls command and check the RDAREA related to the applicable table. Then, execute the pddbls command and confirm that the RDAREA related to the applicable table meets all of the following conditions:

RDAREAs where the inner replica facility is applied are not specified along with RDAREAs where it is not applied.

The definition counts of the replica RDAREA match.

The generation numbers of the replica RDAREA definition match.

After the conditions are satisfied, re-execute the definition SQL or the utility. For details about conditions, see the manual HiRDB Version 9 SQL Reference.

For reason code 2:

Complete the updatable online reorganization, and then re-execute the definition SQL or the utility.

For reason code 3:

Execute the pdrdrefls command and the pddbls command. Check if the RDAREA related to the applicable table is in command hold status and closed status. Then, re-execute the definition SQL or the utility.

KFPA19703-E A

Error occurred during execution of transaction aa....aa, reason=bb....bb, code=cc....cc, server=dd....dd

An error occurred during transaction control processing.

aa....aa: Transaction control process

begin: Transaction start process

branch: Transaction branch process

bb....bb: Error

cc....cc: Reason code

dd....dd: Name of server where the error occurred

Asterisks (********) are displayed when the name of the server where the error occurred cannot be specified.

S: Ignores this SQL statement, or invalidates the transaction.

O: Contact the HiRDB administrator, eliminate the cause of the error, and re-execute the processing.

Action

Take appropriate action for the error or reason code.

Control process (aa....aa)
Error
(bb....bb)
Reason code (cc....cc)
Description
Action by HiRDB administrator

begin
TRNPAUSE
-948
The server (dd....dd) is suppressing the scheduling of new transactions.
If a KFPS01160-E message is output to the event log (in UNIX, syslogfile) of the system manager before or after the output of this message, resolve the problem according to message KFPS01160-E.
If other than the above, if a unit applicable to the standby-less system switchover facility is switching back, wait until the system switchover has completed.

STLSFES
-944
(1) A connection is made from a UAP using the X/Open XA interface to a recovery-unnecessary front-end server (dd....dd).
(2) Because the target HiRDB Datareplicator that uses a two-phase commit method is connected to an FES that uses a recovery-unnecessary front-end server, the target processing failed.
Set the client environment definitions PDFESHOST and PDSERVICEGRP to connect to an FES that does not use a recovery-unnecessary front-end server. Environment variables must be assigned to the following:
(1) A UAP environment variable using the X/Open XA interface
(2) Target side HiRDB Datareplicator environment variable.

branch
TRNPAUSE
-376
The server (dd....dd) is suppressing the scheduling of new transactions.
If a KFPS01160-E message is output to the event log (in UNIX, syslogfile) of the system manager before or after the output of this message, resolve the problem according to message KFPS01160-E.
If other than the above, if a unit applicable to the standby-less system switchover facility is switching back, wait until the system switchover has completed.

KFPA19704-E A

No available RDAREA for temporary table, code=aa....aa, kind="bb....bb", common id=cc....cc, RDAREA="dd....dd", server="ee....ee"

The temporary table or temporary table index could not be stored in a temporary table RDAREA because no temporary table RDAREAs are available.
Note that if more than one temporary table RDAREA is a candidate destination, the cause of the error displayed in this message applies only to the RDAREA that is the first storage destination candidate. If this message is output repeatedly after you have taken corrective action for the RDAREA displayed in it, take corrective action after checking the status of the other temporary table RDAREAs and referring to Processing when there are no available temporary table RDAREAs in the HiRDB Version 9 Installation and Design Guide.

aa....aa: Cause of error

bb....bb: Type

TABLE: Temporary table

INDEX: Temporary table index

If the type cannot be determined, ***** is displayed.

cc....cc: Common ID

If it cannot be determined, 0 is displayed.

dd....dd: Name of the RDAREA in which the error occurred

In HiRDB/Parallel Server, it is the name of the temporary table RDAREA on the back-end server displayed in ee....ee, which is the RDAREA that will be the first storage destination candidate.

If it cannot be determined, ******** is displayed.

ee....ee: Name of server

S: Ignores this SQL statement or invalidates the transaction.

O: Based on the cause of the error, take the appropriate corrective action as described in the table below.

Action

Based on the cause of the error, take the appropriate corrective action as described in the following table, and then retry the operation:

Cause of error (aa....aa)
Meaning
Action

Operator
Administrator

NO_RDAREA
There is no temporary table RDAREA with an attribute shared among SQL sessions in the HiRDB system.
The action depends on whether the client environment definition PDTMPTBLRDAREA is specified.

If specified:
Ask the HiRDB administrator to create a temporary table RDAREA with a specific SQL session lock attribute, and then specify that RDAREA in PDTMPTBLRDAREA.

If not specified:
Contact the HiRDB administrator.

Use pdmod to create a temporary table RDAREA that can be used.

UNUSABLE#1
There are no usable RDAREAs among the temporary table RDAREAs specified in the client environment definition PDTMPTBLRDAREA.
Specify a usable temporary table RDAREA with a specific SQL session lock attribute in the client environment variable PDTMPTBLRDAREA.
If there is no available temporary table RDAREA with a specific SQL session lock attribute, ask the HiRDB administrator to create one, and then specify that RDAREA in PDTMPTBLRDAREA.

MAX_OVER#2
The number of temporary tables or temporary table indexes exceeds the maximum number that can be stored in the temporary table RDAREAs.
Wait for other transactions that are executing to finish, and then re-execute the SQL statement for this transaction.
If the problem persists, contact the HiRDB administrator.

RDAREA_HELD
The temporary table RDAREA cannot be accessed because it is in one of the following states listed:

Close status

Currently holding

pdhold command reception status

None
Use the pddbls command to check the status of the temporary table RDAREA and make it accessible to the UAP by taking steps such as opening the RDAREA or releasing the hold.
In the case of an error shutdown, use pdmod to re-initialize the temporary table RDAREA (initialize rdarea statement).

INVALID_PAGE_SIZE#2
The page size is insufficient for one of the following reasons:

If the temporary table to be stored is a FIX table, the row length of the temporary table exceeds the size that can be stored in the RDAREA.

The total length of the columns in the temporary table index to be stored exceeds the size that can be stored in the RDAREA.

None

(a) If the row length of a FIX table exceeds 3,000 bytes:

Delete the table, and then re-define the temporary table so that the row length of the FIX table can be stored in the temporary table RDAREA.

(b) If the index key length exceeds 4,036 bytes:

If the index is a single-column index, delete it.

If the index is a multi-column index, delete it, and then redefine it so that the key length does not exceed the maximum.

(c) Other than above:

Using pdmod, take either of the following actions:

Create a temporary table RDAREA with a page size that can store the temporary table, or change the page size of the temporary table RDAREA that was already created.

Create a temporary table RDAREA with a page size that is larger than the key length of the temporary table index to be stored, or change the page size of the temporary table RDAREA that was already created.

LOCK_ERROR
A lock error occurred.
A required resource is currently engaged by another transaction. Wait for the executing transaction to finish, and then re-execute the SQL statement for this transaction.
None

NO_SEGMENT#2
There are no unused segments.
All segments are being used by other transactions. Wait for the executing transactions to finish, and then re-execute the SQL statement for this transaction.
If the problem persists, contact the HiRDB administrator.
Use pdmod to take one of the following corrective actions:

Add a temporary table RDAREA (create rdarea statement).

Re-initialize the temporary table RDAREA that was already created (initialize rdarea statement).

Expand the temporary table RDAREA that was already created (expand rdarea statement).

Change the attributes of the temporary table RDAREA that was already created (alter rdarea) to apply automatic extension.

REQUEST_OVER
The number of temporary tables and temporary table indexes has exceeded the maximum number available.
Wait for other transactions that are executing to finish, re-execute the SQL statement for this transaction.
If the problem persists, contact the HiRDB administrator.
Re-estimate and revise the value of the operand pd_max_temporary_object_no.

DEL_RDAREA
There is no temporary table RDAREA with an attribute shared among SQL sessions in the HiRDB system.
The action depends on whether the client environment definition PDTMPTBLRDAREA is specified.

If specified:
Ask the HiRDB administrator to create a temporary table RDAREA with a specific SQL session lock attribute, and then specify that RDAREA in PDTMPTBLRDAREA.

If not specified:
Contact the HiRDB administrator.

Use pdmod to create a temporary table RDAREA that can be used.

#1

The RDAREA name that is displayed is the one specified first in the client environment variable PDTMPTBLRDAREA.

#2

The RDAREA name that is displayed depends on whether the client environment variable PDTMPTBLRDAREA is specified.

If it is specified:

The RDAREA name specified first in the client environment variable PDTMPTBLRDAREA is displayed.

If it is not specified:

Among the RDAREAs with an attribute shared among SQL sessions, the RDAREA that will be the first storage destination candidate name is displayed.

KFPA19705-E A

Failed to allocate local buffer pool,error=aa

Failed to allocate the local buffer.

aa: Error cause code

S: Ignores this SQL statement for HiRDB/Single Server. Rolls back for HiRDB/Parallel Server.

P: Contact the HiRDB administrator.

Action

Take the action corresponding to the error cause code.

Error cause code
Cause
Action

20
A memory shortage occurred.
Take one of the following actions:

Increase the swap area.

Decrease the process count.

Decrease the number of servers in the unit.

32
Digit overflow occurred in the process private memory size calculation for the local buffer.
Digit overflow occurred in the process private memory size calculation for the local buffer. Decrease the number of local buffers or the number of buffer sectors on the server where the error occurred, and then reduce the process private memory size for local buffers to 2³¹-1 or less (2⁶³-1 or less for the 64-bit mode).

KFPA19706-E A

Please reorganize Table,due to LOB DIRECTORY overflow,RDAREA name=aa....aa,tableID=bb....bb

The management information in the LOB RDAREA exceeded the upper limit.

aa....aa: RDAREA name

bb....bb: Table number

S: Ignores this SQL statement.

Action

Take appropriate action for the applicable RDAREA.

For the user LOB RDAREA:
Reorganize the LOB column stored in aa....aa or the table defining the LOB attributes.

For the data dictionary LOB RDAREA:
Reorganize the dictionary table related to the stored procedure or the stored function.

For the registry LOB RDAREA:
Reorganize the registry table.

KFPA19713-E A

There was a conflict between attempts to update rows in XDS. table ID = aa....aa, ROW ID = bb....bb

An attempt was made to update or delete while another transaction was updating or deleting.

aa....aa: DB area table ID (decimal)

bb....bb: DB area row ID (hexadecimal)

S: Invalidates this transaction.

P: Re-execute the SQL statement after the active transaction has terminated. Use the pdvsta command to check the DB area names for the DB area table IDs.

KFPA19716-E A

Unusable page accessed,tableID=aa....aa,RDAREA name=bb....bb,file name=cc....cc

A page that cannot be used was accessed during operations on the table ID aa....aa, which is defined in RDAREA bb....bb. If WAIT was specified in pd_lock_uncommited_delete_data operand, HiRDB file areas in excess of the following sizes cannot be used in the RDAREA stored in the table that defines the index.

If the page length is 4096: 32 GB

If the page length is 6144: 48 GB

aa....aa: table ID

bb....bb: RDAREA name

cc....cc: HiRDB file name

If the path name of the HiRDB file exceeds 120 characters, the last 120 characters of HiRDB file path name are output.

S: Invalidates this transaction.

Action

Revise the HiRDB file size of the RDAREA that stores the table. For details about the maximum HiRDB file size when WAIT is specified in the pd_lock_uncommited_delete_data operand, see the manual HiRDB Version 9 System Definition. If you have exceeded the maximum size for the RDAREA configuration file, use the database structure modification utility (pdmod) to change the configuration so that the maximum size is not exceeded.

KFPA19717-E A

More than two keys in same row created for index with USING UNIQUE TAG,index id=aa....aa

In the substructure index in which USING UNIQUE TAG was specified, two or more index keys were generated in the same row.

aa....aa: Index number

For CREATE INDEX, ****** is displayed.

S: Ignores this SQL statement. The system may also invalidate the transaction.

P: Correct the column value so that a unique XML type column substructure is decided on, and then re-execute the SQL statement or the transaction.

KFPA19718-E A

Failed to allocate in-memory data buffer,reason=aa....aa

Allocation of the in-memory buffer failed.

aa....aa: Reason for the error

S: Invalidates this transaction.

Action

Take corrective action according to the cause of the error, as shown below.

Error cause
Error explanation
Action

process segment over
The number of shared memory segments that can be added in a process exceeded the maximum value for the OS.
Revise the algorithm for the required amount of memory. For details about the amount of memory required during in-memory processing, see the HiRDB Version 9 Installation and Design Guide.
In UNIX, also revise the estimate of the OS operating system parameters. For a description of how to estimate operating system parameters, see the HiRDB Version 9 Installation and Design Guide or the applicable OS documentation.
Note that in order to use the shared memory segments effectively, you must exercise caution when gathering together multiple RDAREAs to be processed in-memory. For details about segment allocation, see the manual HiRDB Version 9 Batch Job Accelerator.

insufficient virtual memory
There is insufficient memory for allocating the in-memory buffer.
Refer to system call = shmat, errno = 12, and mnemonic = ENOMEM in 4.3 System call return codes and take corrective action.

insufficient physical memory
The work area is not sufficient for attaching shared memory.
Either decrease the required amount of shared memory by decreasing the number of in-memory RDAREAs, or provide additional real memory.

KFPA19719-E A

A transaction cannot be executed because the command is being executed or the transaction by UAP is being executed, in XDS.

This transaction cannot be executed because a command or a UAP transaction is executing.

S: Ignores this SQL statement.

P: Re-execute this SQL statement.

KFPA19721-E A+E+S

DBAREA pages are insufficient in XDS. DBAREA = "aa....aa"

A DB area aa....aa page shortage occurred. No more pages can be created in this DB area.

aa....aa: DB area name

S: Invalidates this transaction.

Action

If the target DB area is a data DB area or an index DB area:

After normally terminating the XDS, take one of the following actions, and then restart the XDS.

Take corrective action by following the KFPV46003-W or KFPV46004-W message, both of which were output in the XDS log.

Increase the DB area page size (specification value of -p option of pdxdbarea command in the XDS database definitions).

If the target DB area is a work table DB area:

Terminate the XDS normally, increase the DB area page size (specification value of -p option of pdxdbarea command in the XDS database definitions), and then restart the XDS.

KFPA19724-E A

An error occurred during lock processing in XDS.

An error occurred during lock processing between threads.

S: Ignores this SQL statement. The system may also invalidate this transaction.

P: Re-execute this SQL statement.

KFPA19725-E A

Lock processing timed out in XDS.

An timeout occurred during lock allocation between threads.

S: Ignores this SQL statement. The system may also invalidate this transaction.

P: Re-execute this SQL statement.

KFPA19726-E A

Unable to execute an updating transaction during restart the standby system in XDS.

During the process for recovering operational status for both systems, new update transaction reception is suppressed.

S: Invalidates this transaction.

P: After the suppression of new update transaction reception is released (after the KFPV82004-I message is output), re-execute the transaction.

KFPA19727-E A

Temporary table object not found, server="aa....aa", inf1="bb....bb", inf2="cc....cc"

The SQL statement cannot be executed because the temporary table object does not exist. Before the SQL session terminates, an SQL session-specific temporary table object was not found for one of the following reasons:

The back-end server terminated.

A unit on the back-end server terminated.

A system switchover occurred on the back-end server, or on a unit of the back-end server.

aa....aa: Name of server

bb....bb: Maintenance information 1

cc....cc: Maintenance information 2

S: Invalidates the transaction.

O: Execute the DISCONNECT statement.

KFPA19800-E A

Output file aa....aa error occurred in EXECUTE UTL statment, errno=bb....bb

An error occurred in EXECUTE UTL result file output processing.

aa....aa: File operation contents

open: File open

write: File write

bb....bb: Error code

S: Terminates processing.

P: Check the value of the error code, refer to errno.h and the manual for the OS used by the user, eliminate the cause of the error, and re-execute.

KFPA19801-E A

Invalid value of aa....aa

One of the following errors occurred in the aa....aa value:

The length is 0 or a negative value.

An invalid character was used.

aa....aa: {extended statement name|extended cursor name}

S: Ignores this SQL statement.

P: Take one of the following measures:

Specify a value of 1 or greater in aa....aa.

Specify valid characters in aa....aa.

KFPA19802-E A

Incompatible character code set, HiRDB=aa....aa, PDCLTCNVMODE=bb....bb

The character code for the HiRDB server does not match the value specified in the client environment variable PDCLTCNVMODE.

aa....aa: HiRDB code type

SJIS: Shift JIS kanji code

CHINESE: EUC Chinese kanji code

UJIS: EUC Japanese kanji code

LANG-C: Single-byte code

UTF-8: Unicode

CHINESE-GB18030: Chinese character encoding GB18030

UNKNOWN: Unsupported character code

bb....bb: Specification value in the client environment variable PDCLTCNVMODE

UCS2_UTF8

UCS2_UJIS

UCS2_UJIS2

S: Declines connection to HiRDB.

P: Make sure the character code for the HiRDB server matches the value specified in the client environment variable PDCLTCNVMODE.

KFPA19864-E A

Unable to aa....aa MEMORY TABLE due to bb....bb, code=cc

Because of bb....bb, it is not possible to set the memory database allocation table or memory database deallocation table.

aa....aa: {ALLOCATE|DEALLOCATE}

bb....bb: Additional error information

cc: Reason code

S: Ignores this SQL statement.

P: If the specified table name is invalid, revise the table name and then re-execute. If the table name is valid, follow the additional instructions for error codes and errors, and then take corrective action. The meanings and actions in the additional information are as follows:

Reason code (cc)
Additional information (bb....bb)
Explanation
Action

01
duplicate index names
Duplicate index names are specified.
Correct the SQL statement so that the index name is not duplicated, and then re-execute.

02
duplicate DBAREA names
In the index DB area, specify the same DB area that was specified in the data DB area.
Specify the data DB area in the data DB area name, and specify the index DB area in the index DB area name. Then re-execute.

03
already allocated table
The memory database allocation table was already set.
It is unnecessary to set the memory database allocation table.

04
divided table
Partitioned table
Set as not to be added to the memory database.

05
referential constraint
Referencing table

06
insert only table
Falsification-prevented table

07
shared table
Shared table

09
none-FIX table
Non-FIX table

10
LOCK PAGE table
Table in which LOCK PAGE was specified in the table option
Use ALTER TABLE to alter the minimum unit of locked resources for the table, and then re-execute.#

11
WITHOUT ROLLBACK table
Table in which WITHOUT ROLLBACK was specified in the table option
Set as not to be added to the memory database.

12
check constraint
Table in which the check constraint was defined

13
table with large SEGMENT REUSE value
Table in which a value in excess of 16,777,216 was specified for the number of segments of table option SEGMENT REUSE
Use ALTER TABLE to alter the segment number to 16,777,216 or less, and then re-execute.#

14
trigger table
Table that defined the trigger
Set as not to be added to the memory database.

15
too many columns
Table that defined over 3,000 columns

16
too many indexes
Table in which the number of defined indexes exceeds 16
Decrease the number of indexes defined in the specified table to 16 or less, and then re-execute.#

17
table with DEFAULT clause or WITH DEFAULT
Table with columns that specify the DEFAULT clause or that specify WITH DEFAULT in the NOT NULL constraint
Set as not to be added to the memory database.

18
updatable column for insert only table
Table with columns that specify updatable column attributes for a falsification-prevented table

19
table using character set specification
Table with columns that specify a character set

20
no XDS
For HiRDB/Single Server, the XDS is not specified by the pdxds operand in the system common definition.
For HiRDB/Single Server, the XDS that supports BES storing of the target table is not specified by the pdxds operand in the system common definition.
Contact the HiRDB administrator.

21
XDS in starting or terminating
The XDS is starting or terminating.
Re-execute when the XDS is operating or is shut down. For details about confirming completion of XDS start processing, see Memory database allocation procedure (XDS start) in the HiRDB Version 9 Memory Database Installation and Operation Guide. For details about confirming completion of XDS termination processing, see Memory database deallocation procedure (XDS termination) in the HiRDB Version 9 Memory Database Installation and Operation Guide.

22
insufficient table access privileges to public
Table to which full access privileges have not been granted to PUBLIC
Grant full access privileges to PUBLIC by using GRANT, and then re-execute.#

23
invalid data type
Table with the following data type columns.

SMALLINT type

FLOAT type

SMALLFLT type

NCHAR type

MCHAR type

DATE type

TIME type

INTERVAL YEAR TO DAY type

INTERVAL HOUR TO SECOND type

TIMESTAMP type

DECIMAL TYPE precision that exceeds 29 digits

Set as not to be added to the memory database.

24
large precision of DECIMAL for index column
Delete all of the indexes defined in columns in which DECIMAL type precision exceeds 19 digits, and then re-execute.
Delete all of the indexes defined in columns in which DECIMAL type precision exceeds 19 digits, and then re-execute.#

25
undefined index
The specified indexes have not been defined in the corresponding table.
Revise all of the specified indexes and then re-execute.

26
primary key
Table that defined the primary key
Set as not to be added to the memory database.

27
cluster key
Table that defined the cluster key

28
EXCEPT VALUES index
Table that defined an index that specified exception values in index options

29
UNBALANCED SPLIT index
Table that defined indexes that specified UNBALANCED SPLIT in index options

30
table used in view
Basic viewed table
Delete all of the viewed tables that are based on the specified table, and then re-execute.#

31
table used by inner replica facility
This is the table with the RDAREA to which the inner replica facility was applied or in which the index was defined
Cancel application of the inner replica function and re-execute.#

33
duplicate table name in XDS
The same table identifier as that of the memory database allocation table belonging to another user has been specified in an identical XDS.
Use ALTER TABLE to alter the table name, and then re-execute.#

34
duplicate index name in XDS
The specified table defines in the same XDS the same index defined in the memory database allocation table.
Use ALTER INDEX to alter the index name, and then re-execute.#

35
too many tables in XDS
The number of memory database allocation tables that are stored in the same XDS exceeds 1,024.
Find a way to achieve 1,024 or fewer memory database allocation tables stored in the same XDS.#

36
too many indexes in XDS
There are more than 2,048 index numbers in the memory database allocation table stored in the same XDS.
Find a way to achieve a total of 2,048 or fewer indexes in the memory database allocation table stored in the same XDS.#

37
too many tables in DBAREA
There are more than 200 memory database allocation tables stored in the same DB area.
Specify another DB area and re-execute. Alternatively, find a way to achieve 200 or fewer memory database allocation tables stored in the same DB area.#

38
too many indexes in DBAREA
There are more than 400 index numbers in the memory database allocation table stored in the same DB area.
Specify another DB area and re-execute. Alternatively, find a way to achieve a total of 400 or fewer indexes in the memory database allocation tables stored in the same DB area.#

39
abnormally terminated XDS
After DEALLOCATE MEMORY TABLE executed, the XDS terminated abnormally before memory database deallocation.
Contact the HiRDB administrator.

40
invalid DBAREA name
During cancellation of settings for the memory database deallocation table on which DEALLOCATE MEMORY TABLE was executed during XDS operation, the specifications for the data DB area name and index DB area name differed from what they were previously.
Specify the same data DB area name and index DB area name as when the previous ALLOCATE MEMORY TABLE was executed, and then re-execute. If you are checking the data DB area that was previously specified, see the DBAREA_NAME column of the data dictionary table SQL_TABLES. If you are checking the index DB area that was previously specified, see the DBAREA_NAME column of the data dictionary table SQL_INDEXES.

41
none-memory table
Not the memory database allocation table.
Invalid setting for deallocation of the memory database allocation table.

42
already deallocated table
Table that was already set to be deallocated from the memory database.

44
view
Viewed table
Set as not to be added to the memory database.

45
audit trail table
Audit trail table

46
insufficient index names
None of the indexes that are defined in the table have been specified.
Specify all of the indexes defined in the table, and then re-execute.

47
too many index names
The index identifier is specified 17 times or more.
Correct the syntax so that the number of specified indexes is 16 or less, and then re-execute.#

48
invalid last character in table name
Table that specified single byte spaces in the final characters of the table identifier
Use ALTER TABLE to alter the table name, and then re-execute.#

49
invalid last character in column name
Table with columns that specified single byte spaces in the final characters of the column names
Use ALTER TABLE to alter the column name, and then re-execute.#

50
invalid last character in index name
This is the table with an index in which the last characters of the index identifier are specified as single-byte spaces.
Use ALTER INDEX to alter the index name, and then re-execute.#

51
reserved column table
Table with a reserved column
Exclude from memory database allocation.

52
temporary table
Temporary table
Exclude from memory database allocation.

53
invalid SEGMENT REUSE option
Specify a value other than 0 for the reuse option value in the SEGMENT REUSE table option.
Use ALTER TABLE to change the reuse option value to 0, and then retry the operation.#

#: If you cannot take this corrective action, do not perform memory database processing.

Action

If the reason code is 20, specify XDS using the pdxds operand in the system common definition.

If the reason code is 39, recover the error. For details about how to perform error recovery, see Corrective action to take when an error occurs in the HiRDB Version 9 Memory Database Installation and Operation Guide.

KFPA19865-E A

Unable to execute definition SQL due to memory table aa....aa."bb....bb"

Because the table aa....aa."bb....bb" is the memory database allocation table, the following definition SQL cannot be executed.

CREATE INDEX

CREATE PROCEDURE

CREATE TRIGGER

CREATE TYPE

CREATE VIEW

ALTER INDEX

ALTER PROCEDURE

ALTER ROUTINE

ALTER TRIGGER

ALTER TABLE

DROP INDEX

DROP SCHEMA

DROP TABLE

REVOKE access privileges

aa....aa: Authorization identifier

bb....bb: Table identifier

S: Ignores this SQL statement.

P: Release table aa....aa."bb....bb" from memory database table allocation, and then re-execute.

KFPA19940-E A

PLUGIN "aa....aa"unsupports bbb compression facility

Plug-in aa....aa cannot compress columns of the data type indicated in bbb.

aa....aa: Plug-in name

HiRDB XML Extension

bbb: Data type

XML

S: Invalidates the transaction.

P: Contact the HiRDB administrator, and then re-execute after the HiRDB administrator takes corrective action.

Action

Check the version of the plug-in. Register a version of the plug-in that supports the data compression function, and then restart HiRDB.

KFPA19941-E A

PLUGIN "HiRDB XML Extension" unsupports XML update facility

HiRDB XML Extension plug-in does not support partial update of XML data.

S: Invalidates the transaction.

P: Contact the HiRDB administrator, and then re-execute after the HiRDB administrator takes corrective action.

Action

Check the version of the plug-in. Register a version of the plug-in that supports partial update of XML data, and then restart HiRDB.

KFPA20000-E A

System function error occurred, name=aa....aa, code=bbbb

An error occurred in an internal system function.

aa....aa: Name of function resulting in the error

bbbb: System call errno

S: Terminates abnormally.

O: Based on the system call errno, check the cause of the error; after resolving the problem, re-execute the UAP or the command.

KFPA20001-E L

Communication buffer allocation error occurred, code=aaaa

Allocation of communication buffer failed.

aaaa: Error code

S: Terminates abnormally.

O: Reduce the number of resident processes (pd_process_count) for the server where this message was output.

KFPA20002-E L

Communication error,abort=aa....aa, code=bbbbb

An error occurred during communication processing.

aa....aa: Abort code

bbbbb: Error detail code

S: Resumes processing.

O: See 4. Error Detail Codes to eliminate the cause of the error, then re-execute the UAP or command. If the operator cannot handle the error, contact the HiRDB administrator.

Action

Contact the customer support center.

KFPA20003-E E+L

Insufficient aa....aa memory, server=bb....bb, size=cc....cc

There is not enough memory for HiRDB system processing.

aa....aa: Type of area in which memory shortage occurred:

SHARED: Shared memory

PROCESS: Process private area

bb....bb: Name of the server resulting in the error

cc....cc: Specified size (in bytes)

S:

At server startup:

Cancels server startup processing.

At transaction input:

Terminates abnormally the process that attempted to process the corresponding transaction.

Action

If the error occurred at the startup of a user server (executed by specifying the -s option with the pdstart command) that is not a back-end server using the standby-less system switchover (effects distributed) facility, and the unit terminated abnormally, specify server in the pd_shmpool_control operand in the system common definition and restart the unit. Otherwise, increase the size of the shared memory for the server that has insufficient shared memory, and restart the affected server. The size of shared memory can be specified in the following operands:

pd_sds_shmpool_size (single server definition)

pd_dic_shmpool_size (dictionary server definition)

pd_bes_shmpool_size (back-end server definition)

If the shortage occurred in the process private area, provide more memory space by taking the following actions:

Reduce the number of concurrent processes.

Increase the swap area.

Increase the real memory.

If the current value is large, reduce the pd_work_buff_size operand value in the server definition.

Reduce the number of server resident processes (pd_process_count).

KFPA20004-I E+L

BES aa....aa used as a floatable server for FES bb....bb(cc....cc/dd....dd)

Back-end servers aa....aa are being used as floating servers for SQL processing accepted by front-end server bb....bb.
Up to 12 back-end servers can be listed in aa....aa; this message is output in segments if there are more than 12 back-end servers.

aa....aa: List of names of the back-end servers used as floating servers

bb....bb: Name of the front-end server

cc....cc: Segment number of this message

dd....dd: Total number of message segments

S: Resumes processing.

O:

If pd_floatable_bes and pd_non_floatable_bes are both specified in the front-end server definition, pd_floatable_bes is effective. From the list of servers used as floating servers displayed in this message, check that the specification of the front-end server definition is correct. If it is not correct, stop the front-end server, correct the front-end server definition, and restart the server.

When the message is divided into multiple segments, the segments may not be displayed in the order of the requests.

KFPA20005-E E+L

Invalid value bb....bb specified for operand aa....aa

The value (identifier or unsigned integer) of operand aa....aa specified in the system definition is invalid.

aa....aa: Operand name

bb....bb: Operand specification value (first 30 bytes only if the value is longer than 30 bytes)

S: Halts HiRDB startup processing.

O: Contact the HiRDB administrator.

Action

Correct the specification of operand aa....aa in the system definition, and restart HiRDB.

KFPA20006-E E+L

aa....aa in FES definition bb....bb, file=cc....cc, pos=dd....dd

Error aa....aa occurred in the bb....bb operand of the front-end server definition.

aa....aa: Error cause

Invalid option: The option is invalid.

Invalid value: The option value is invalid.

Duplicate options: The same option operand already exists.

bb....bb: Name of the operand where the error occurred

cc....cc: Definition file name (the first 30 bytes are displayed if the length of the file name exceeds 30 bytes)

dd....dd: Position of the operand where the error occurred (information that indicates the cardinal number of the operand in the definition where the error occurred)

S: Ignores the operand of the definition where the error occurred.

O: Contact the HiRDB administrator.

Action

Respecify the dd....ddth bb....bb operand, and then restart HiRDB.

KFPA20007-E L

Java VM library not found at aa....aa, server=bb....bb, errno=ccc

No Java Virtual Machine library was found.

aa....aa: Library path name of the Java Virtual Machine (if the path name exceeds 160 characters, a hash mark (#) is displayed as the 160th character)

bb....bb: Name of the server that executes the Java Virtual Machine

ccc: Error code from the OS

S: Terminates processing.

Action

Correct the error indicated by error code ccc by referring to errno.h and the OS documentation, and restart HiRDB.

If file aa....aa does not exist, grant read privilege and execution privilege to HiRDB administrator. Also check the settings for the pd_java_runtimepath and pd_java_libpath operands in the system definition.

KFPA20009-W L

SQL inf(aa) bb....bb cc....cc dd....dd ee....ee ff....ff

When the reason code is 00, the SQL information from when a server process was forcibly terminated by a UAP forced termination or other cause is displayed.
When the reason code is 01, the SQL information containing a warning from the SQL runtime warning output facility is displayed.

aa: Reason code

00: The server process abnormally terminated due to forced termination by a UAP or other cause, aborting the process.

01: The SQL runtime was longer than the time set in the SQL runtime warning output facility.

bb....bb: Server information (is output in one of the following formats)

single-server-name, connection-serial-number

front-end-user-name, connection-serial-number

cc....cc: Client information (is output in the following format):

UAP-name UAP-process-ID (UAP-IP-address)

Note that 0 is displayed for the process ID of the UAP if it is connecting from a Type 4 JDBC driver.

dd....dd: Executed SQL information (is output in the following format):

operation-code SQL-counter SQLCODE

operation-code
For details about the operation code, see HiRDB Version 9 UAP Development Guide. When the reason code is 00, there are cases for which the operation code cannot be set. An asterisk (*) is displayed if the operation code cannot be set.

SQL-counter
Expresses a value that is counted each time an SQL statement is received. An asterisk (*) is displayed if the SQL counter cannot be set.

SQLCODE
Displays the SQLCODE of the result the SQL statement executed. When the reason code is 00, there are cases for which the SQLCODE cannot be set. In these cases, asterisks (*) are displayed.

ee....ee: SQL runtime (output in one of the following formats):

Percentage of the maximum wait time is specified as an unsigned integer
SQL-run-starting-time-SQL-run-ending-time
It is displayed in the format hh:mm:ss (hh: hours, mm: minutes, ss: seconds).
When the reason code is 00, there are cases for which the SQL run start time cannot be set. In these cases, asterisks (*) are displayed. Also, the time the SQL aborted is displayed in the SQL run end time.

Percentage of the maximum wait time is specified as an unsigned decimal integer, and the output timing is specified
SQL-run-starting-time-SQL-run-ending-time
It is displayed in the format hh:mm:ss.xxxx (hh: hours, mm: minutes, ss: seconds, xxxx: microseconds).
If the reason code is 00, it may not be possible to set the SQL runtime start time. If it cannot be set, * is displayed. Furthermore, the SQL runtime end time displays the time the SQL statement was interrupted.

ff....ff: Execution termination or the aborted SQL statement

Asterisks (*) are displayed when the SQL statement cannot be set.

Depending on the length of the SQL statement, display of the SQL statement may be truncated. When the display is truncated, a hash mark (#) is added to the end of the message.

S: Executes the process.

Action

Take one of the following actions:

When the reason code is 00
When unplanned forced termination of a server process occurs, refer to other messages to eliminate the cause.

When the reason code is 01
See the SQL runtime warning information file and take one of the following steps:
Re-evaluate whether exclusive contention is occurring.
Re-evaluate whether a network failure occurred.
Fine tune the SQL code.
Increase the specification value of the PDCWAITTIME operand.
Check the increase of the data count to determine if the SQL runtime has increased.
For details about the SQL runtime warning output facility and about the SQL runtime warning information file, see HiRDB Version 9 System Operation Guide.

KFPA20010-W L

Invalid pd_delete_reserved_word_file operand

The following error occurred in the specification of the system common definition pd_delete_reserved_word_file operand:

The specified SQL reserved word deletion file does not exist.

Duplicates of the specified SQL reserved word deletion file exist.

S: Continues processing.

Action

Check that the specification of the system common definition pd_delete_reserved_word_file operand is correct. If not, stop HiRDB, correct the system common definition pd_delete_reserved_word_file operand specification, and re-execute.

KFPA20011-W L

Invalid "SQL_reserved_word_delete_file", file=aa....aa

A reserved word that cannot be deleted is specified in the SQL reserved word deletion file.

aa....aa: Name of the SQL reserved word deletion file that contains the error

S: Continues processing.

Action

Check that the contents of the SQL reserved word deletion file are correct. If not, stop HiRDB, correct the SQL reserved word deletion file, and re-execute.

KFPA20012-W E+L

Invalid pd_sql_command_exec_users operand

Because there is an invalid specification for the pd_sql_command_exec_users operand, ignore this operand. The error may be due to either of the following factors:

A character string of nine characters or more is specified in the authorization identifier.

The specified authorization identifier contains characters that cannot be used.

S: Continues processing.

Action

Make sure that the specification for the pd_sql_command_exec_users operand is correct. If it is not, stop HiRDB, correct the pd_sql_command_exec_users operand value, and then re-execute.

KFPA20013-E L

Error occurred in C function for aa....aa bb....bb.cc....cc, library file=dd....dd, C function=ee....ee

An error occurred during the C function ee....ee that implemented the external C stored routine.

aa....aa: External C stored routine type{PROCEDURE|FUNCTION}

bb....bb: Authorization identifier

cc....cc: Routine identifier

dd....dd: C library file name

ee....ee: Name of the C function that implemented the external C stored routine

S: Ignores this SQL statement.

P: Use the following procedure to re-register the C library file, and then re-execute the SQL statement.

Check the message (such as KFPS01820-E) that was output before this message, eliminate the cause of the error, and correct the library source.

Recreate the C library file from the corrected source.

Use one of the following methods to re-register the C library file that you created:
- Create the UAP that executes REPLACE CLIB, and execute that UAP.
- Ask the administrator to execute the pdclibsync command.

Action

Contact the programmer who implemented the C function dd....dd, and request correction of the program. If a pdclibsync command must be executed according to the corrective action for the program, re-execute the command.

KFPA20014-E E+L

Unable to use XDS in environment using aa....aa character code set

The XDS that was set up with the character encoding aa....aa specified cannot be used in HiRDB.
The character encodings that can be used in XDS are as follows:

sjis

ujis

utf-8

aa....aa: Character code classification

{chinese|lang-c|chinese-gb18030}

S: Interrupts HiRDB startup processing.

O: Contact an HiRDB administrator.

Action

If you are using an XDS, perform setup again using the character encoding that can be used in the XDS and that is described in the message, and then start HiRDB. Note that if a database has already been created, it must be re-created using character encoding that can be used in an XDS.

If an XDS is not used, delete the pdxds operand from the system common definition.

KFPA20015-E E+L

Unable to send message to client,RC=aa....aa,CNCTID=bb....bb,SQLNO=cc....cc,CLIENT=dd....dd,OPCD=eeee,TRANSACTION=ff....ff

The result telegram cannot be sent to the client.

aa....aa: Reason code

bb....bb: connection ID

For DISCONNECT, COMMIT RELEASE, or ROLLBACK RELEASE, an asterisk (*) output.

cc....cc: SQL counter (SQL sequence numbers during connection)

For DISCONNECT, COMMIT RELEASE, or ROLLBACK RELEASE, an asterisk (*) output.

dd....dd: Client information

This information is output in the following format:

oo....oo pp....pp(qq....qq,rr....rr)

oo....oo: UAP identification information (maximum of 30 bytes).

If the client environment definition PDCLTAPNAME is specified:
Displays the value specified in PDCLTAPNAME.
The trailing single-byte spaces are also deleted.

If the client environment definition PDCLTAPNAME is not specified:
Unknown is displayed.

pp....pp: UAP IP address (maximum of 15 bytes)

An IP address is a decimal numerical value delimited by periods (.) after each byte (example: 172.11.22.33).

However, if the UAP is operating on the same machine (except JDBC Type 4 drivers), 0.0.0.0 is output.

qq....qq: UAP process ID (maximum of 10 bytes)

If you are connected from a Type 4 JDBC driver, 0 is output.

rr....rr: UAP thread number (maximum of 10 bytes)

If you are connected from a Type 4 JDBC driver, 0 is output.

Note that for DISCONNECT, COMMIT RELEASE, and ROLLBACK RELEASE, asterisks (*) are output.

eeee: Operation code

For DISCONNECT, COMMIT RELEASE, or ROLLBACK RELEASE, an asterisk (*) output.

ff....ff: Transaction status

ACTIVE: During transaction

The transaction is rolled back.

NONE: Not during transaction

To check transaction completion, refer to the administrator's action transaction completion check method.

S: Interrupts the process and connection to the UAP. Note that if the transaction has not completed, rollback will occur.

O: Contact an HiRDB administrator

Action

Refer to the following and take action as appropriate.

Reason code
Explanation
Action

-306
The UAP has been disconnected.
Check the OS log and make sure that no network-related errors have occurred. Alternatively, check the operational status of the client by using the client information that was output in the message.
After this, eliminate the error, check the results of the transaction completion, and then re-execute the UAP as needed. For details about checking transaction completion, see the explanation of embedded character ff....ff above, which provides details about how to check for transaction completion.

-338
Disconnection with the UAP was detected during SQL statement execution.

-307
A timeout occurred as a result of a network delay.
Take corrective action by following the KFPQ50314-E message, which was simultaneously output.
After this, eliminate the error, check the results of the transaction completion, and then re-execute the UAP as needed. For details about checking transaction completion, see the explanation of embedded character ff....ff above, which provides details about how to check for transaction completion.

-318
A system error occurred.

-41402
-41403
SQL statement execution was cancelled while the telegram was being sent.
If the KFPQ50933-E message was output, take action according to this message.
If it was not output, implement the same corrective action as that for reason code -338.
After this, eliminate the error, check the results of the transaction completion, and then re-execute the UAP as needed. For details about checking transaction completion, see the explanation of embedded character ff....ff above, which provides details about how to check for transaction completion.

Other than the above
--
Back up the files under %PDDIR%\spool, and contact the customer support center.

Legend:

--: Not applicable

Method of checking transaction completion.

When it is necessary to check transaction completion as part of a corrective action taken in response to this message, do so using the following procedure.

Check the value of the embedded character ff....ff.
If it is ACTIVE, rollback is finished.
If it is NONE, follow steps 2 and 3 below.

Specify the transaction that you want to check from the IP address and connection ID of the HiRTM information, based on the UAP IP address and connection ID in this message.

Check the third digit of the HiRTM hexadecimal information status (status) for the transaction.
If the first bit from the left is 1 (0x80), commit is completed.
If the second bit from the left is 1 (0x40), rollback is completed.

For details about HiRTM, see the HiRDB Version 9 Memory Database Installation and Operation Guide.

KFPA20016-E L

pd_max_tmp_table_rdarea_no operand in system definition file unmatch between units

The values specified for the operand pd_max_tmp_table_rdarea_no are inconsistent between units.

S: Terminates processing.

O: Contact the HiRDB administrator.

Action

Run the pdconfchk command to check on the system definition. Eliminate the cause of the error, restart HiRDB, and then re-execute the database structure modification utility (pdmod).

2.2 KFPC messages

KFPC00101-I S+L

Setup for aa....aa complete

HiRDB environment setup has been completed.

aa....aa: Name of the facility that executed environment setup:

DatHardCompress: Hardware compression facility for DAT access

RshPortName: Remote command service port name

ServiceComplete: HiRDB service activation completion timing

ShmFile: Changed shared memory assignment destinations

ShutdownMode: OS shutdown time HiRDB operation specification facility

CharacterCode: Character code classification of HiRDB

RshOnline: Remote command usage specification facility

SetResource: Resource number or resource size specification facility

S: Terminates processing.

KFPC00102-E S+L

Invalid option specified with this command

An invalid option is specified in the command, or an option argument is not specified correctly.

S: Terminates processing.

Action

Specify the option or argument correctly and re-execute the command.

KFPC00103-I S+L

Usage: pdntenv [{-hc {on|off} | -pn service_port_name | -a | -sc {auto|manual} | -c {sjis|lang-c|utf-8|chinese|chinese-gb18030} | -ro {on|off} | -shmfile {regular|page}| -k {none|force}| -os | -sr resource_name value [resource_name value]...| -wd [process_name]}]

The specification format for the pdntenv command option is invalid.

S: Terminates processing.

Action

Specify the option correctly and re-execute the command.

KFPC00104-E S+L

Pdntenv error occurred, reason=aa....aa, value= bb....bb

An error occurred in the pdntenv command.

aa....aa: Reason code:

REGKEY_GET_FAILED: Registry information acquisition failed.

REGKEY_SET_FAILED: Registry information setup failed.

OPTION_ERROR: Invalid option is specified.

SERVICE_ONLINE: HiRDB service is running.

SERVICE_GET_FAILED: Service status acquisition failed.

SERVICE_CHG_FAILED: Change of service state failed

PDDIR_NOT_FOUND: Environment variable %PDDIR% acquisition failed.

FILE_COPY_FAILED: Library copy failed.

OS_GET_FAILED: OS information acquisition failed.

bb....bb: Detailed information

S: Terminates processing.

Action

When reason code is REGKEY_GET_FAILED or REGKEY_SET_FAILED

Check that HiRDB is registered in the registry, or check for a registry operation problem, correct the problem, and then re-execute the command.

When reason code is OPTION_ERROR

Check that the option can be specified in a HiRDB/Parallel Server.

(Reason code: SERVICE_ONLINE)

Stop HiRDB/Single Server or HiRDB/Parallel Server, and re-execute the UAP.

(Reason code: SERVICE_GET_FAILED or SERVICE_CHG_FAILED)

If the HiRDB/Single Server or HiRDB/Parallel Server is engaged in start processing or termination processing, re-execute the UAP after the processing is complete.

(Reason code: Other than above)

Contact the customer support center.

KFPC00105-I S

There is no dump information

No information about the indicated Windows dump output was found.

S: Terminates processing.

KFPC00201-E S

Invalid environment, variable=aa....aa

An environment variable value is invalid.

aa....aa: Name of invalid environment item:

PDDIR: PDDIR environment variable has not been set up.

PDUXPLDIR: PDUXPLDIR environment variable has not been set up, or the value of the PDDIR environment variable does not match the value of the PDUXPLDIR environment variable.

S: Terminates processing.

Action

Specify the correct value in the environment variable and re-execute. PDUXPLDIR must be %PDDIR%\UXPLDIR; correct it if necessary.

KFPC00301-E L

Error occurred in HiRDB service, reason code=aa....aa-bb....bb

An error occurred during HiRDB service processing.

aa....aa: Error information:

ACCESS: File or registry information created during installation cannot be accessed.

DUPLICATE: Service port number is already being used.

NOT_FOUND: Communication port service name or service port number is not set in the SERVICES file.

SHARED: An error occurred during shared memory allocation.

number: Some other error occurred.

bb....bb: Internal information

S: Terminates abnormally.

O: Contact the HiRDB administrator.

Action

When the error information is ACCESS

Ensure that the user who starts the service has administrator's privileges. In this case, the service name of the communication port is not displayed.

When the error information is DUPLICATE

Another program may be using the service port, so check the service port number setting.

When the error information is NOT FOUND

Specify the same service name within HiRDB system, a communication port service name that is unique within the single server, and a service port number in the SERVICES file.

When the error information is SHARED, or a number

Contact the customer support center.

KFPC00405-I S

aa....aa terminated

The aa....aa command terminated normally.

aa....aa: Windows Firewall exception list operation command name

pdsetfw.bat: Set the Windows Firewall exception list.

pddelfw.bat: Delete from the Windows Firewall exception list.

S: Terminates processing.

KFPC00406-E S

Error occurred in aa....aa, reason=bb

The aa....aa command terminated abnormally. The detail code is bb.

aa....aa: Name of Windows Firewall exception list operation command

pdsetfw.bat: Set the Windows Firewall exception list.

pddelfw.bat: Delete from the Windows Firewall exception list.

bb: Detail code

1: Contact the customer support center.

2: Memory shortage

3: Invalid execution privilege

8: Invalid command line

9: Invalid OS environment

10 to 13: Invalid HiRDB environment

S: Terminates processing.

Action

When bb is 1:

Contact the customer support center.

When bb is 2:

Resolve the memory shortage, and then retry the operation.

When bb is 3:

Check the privileges of the executing user.

If the privileges of the executing user are correct, contact the customer support center.

When bb is 8:

Revise the command line and re-execute.

When bb is 9:

Start either of the following services:

Windows Firewall/Internet Connection Sharing (ICS) service

Windows Firewall service

After the service starts, re-execute.

If the service was already started, contact the customer support center.

When bb is 10 to 12:

Re-install HiRDB.

When bb is 13:

Set the HiRDB directory in the OS environment variable PDDIR.

After setting the HiRDB directory, re-execute.

2.3 KFPD messages

KFPD00001-E S

System initialization error occurred aa....aa

An error occurred during system initialization.

aa....aa: The following character string is displayed:

illegal MASTERDIR: Contents of the master directory are invalid.

S: Terminates abnormally.

O: Contact the HiRDB administrator.

Action

Contact the customer support center.

KFPD00003-E S

File I/O error on aa....aa func=bb....bb errno=cc....cc

An error occurred during file I/O processing.

aa....aa: Server name

bb....bb: Name of function resulting in the error

cc....cc: Value of errno

S: Terminates abnormally.

O: Check the cause of the error on the basis of the displayed function name and errno value and take appropriate action.

KFPD00004-E S

System call error occurred on aa....aa func=bb....bb errno=cc....cc

A system call error occurred.

aa....aa: Name of processing resulting in the error

bb....bb: Name of function resulting in the error

cc....cc: Value of errno

S: Resumes processing when code convert is displayed as the name of the processing resulting in the error; otherwise, terminates abnormally.

O: Check the cause of the error on the basis of the displayed function name and errno value and take appropriate action.

Action

Name of process where the error occurred is pdi_olk_thdlock and the value of errno is -20023

An attempt was made to open a file when the number of files that the system can open simultaneously has been exceeded. Increase the maximum number of files that the system can open simultaneously. In UNIX, see Estimating operating system parameters in the manual HiRDB Version 9 Installation and Design Guide. In Windows, increase the memory.

Name of process where the error occurred is pdi_olk_thdlock and the value of errno is -20024

An attempt was made to open a file when the number of files that a process can open simultaneously has been exceeded. Increase the maximum number of files that a process can open simultaneously. In UNIX, see Estimating operating system parameters in the manual HiRDB Version 9 Installation and Design Guide. In Windows, increase the memory.

KFPD00005-E S

Server initialization error occurred on aa....aa func=bb....bb return code=cc....cc

An error occurred during server startup.

aa....aa: Name of server resulting in the error

bb....bb: Name of processing resulting in the error

cc....cc: Error code

S: Terminates abnormally.

Action

Name of process resulting in the error is pdi_omm_mget and the error code is -142:

Reduce the values specified as the buffer length for table definition information (pd_table_def_cache_size), buffer length for user privilege information (pd_auth_cache_size), and buffer length for view analysis information (pd_view_def_cache_size).

Name of process where the error occurred is pdi_omm_mget and the error code is -143

Revise the value specified for the shared memory size (pd_sds_shmpool_size, pd_dic_shmpool_size, or pd_bes_shmpool_size operand) of the server definition of the server where the error occurred. Revise the specification, and restart the server.

Name of process resulting in the error is pdi_adm_pddicinf or pdi_adm_pdbesinf and the error code is -1807:

Because the process private memory size is insufficient, wait until another process terminates and re-execute. Or, increase the swap area.

Other:

Contact the customer support center.

KFPD00008-E S

Internal inconsistency occurred on aa....aa(bb....bb,cc....cc,dd....dd)

Internal conflict occurred.

aa....aa: Name of server resulting in the error

bb....bb: Maintenance information 1

cc....cc: Maintenance information 2

dd....dd: Maintenance information 3

S: Terminates abnormally.

Action

Contact the customer support center. Ignore this message in the following case:

This message was output during normal termination or planned termination, bb....bb in the message is dicsfenv.c, and cc....cc is -949.

KFPD0011-E L

Process initialization error occurred on aa....aa, func=bb....bb return code=cc....cc

An error occurred during processing startup.

aa....aa: Name of server at which the error occurred

bb....bb: Name of processing resulting in the error

cc....cc: Error code

S: Terminates abnormally.

Action

If bb....bb is p_f_dic_hds_start, take action appropriate to the KFPD00026-E message that is output before the current message. In all other cases, contact the customer support center.

KFPD00012-E L

Transaction initialization error occurred on aa....aa func=bb....bb return code=cc....cc

An error occurred during transaction startup processing.

aa....aa: Name of server resulting in the error

bb....bb: Name of processing resulting in the error

cc....cc: Error code

S: Terminates abnormally.

O: Contact the HiRDB administrator.

Action

Name of process where the error occurred is pdi_omm_mget and the error code is -143

Revise the specification of the shared memory size (pd_sds_shmpool_size, pd_dic_shmpool_size, or pd_bes_shmpool_size operand) of the server that issued the error. Revise the specification, and restart the server.

Name of process where the error occurred is pdi_adm_pddicinf or pdi_adm_pdbesinf, and the error code is -1807

The process native memory is insufficient. Wait for the other processes to terminate and then re-execute, or increase the swap area.

Other than the above

Contact the customer support center.

KFPD00013-E L

Transaction termination error occurred on aa....aa func=bb....bb return code=cc....cc

An error occurred during transaction termination processing.

aa....aa: Name of server resulting in the error

bb....bb: Name of processing resulting in the error

cc....cc: Error code

S: Terminates abnormally.

O: Contact the HiRDB administrator.

Action

Name of process where the error occurred is p_f_dic_hds_release_userinfo

See the KFPD00026-E message that was output prior to this message for the action to take.

Name of process where the error occurred is pdi_com_combuf_disconnect or pdi_com_combuf_process_end, and the error code is -300 through -399

See 4.1 Detail codes for RPC-related errors.

Other than the above

Contact the customer support center.

KFPD00014-E L

Process termination error occurred on aa....aa, func=bb....bb return code=cc....cc

An error occurred during processing termination.

aa....aa: Name of server at which the error occurred

bb....bb: Name of processing resulting in the error

cc....cc: Error code

S: Terminates abnormally.

Action

If bb....bb is p_f_dic_hds_end, take action appropriate to the KFPD00026-E message that is output before the current message. In all other cases, contact the customer support center.

KFPD00015-E S

Server termination error occurred on aa....aa func=bb....bb return code=cc....cc

An error occurred during server termination processing.

aa....aa: Name of server resulting in the error

bb....bb: Maintenance information 1

cc....cc: Maintenance information 2

S: Resumes processing.

O: Contact the HiRDB administrator.

Action

Contact the customer support center.

KFPD00016-E S

Transaction termination error occurred on aa....aa func=bb....bb return code=cc....cc

An error occurred during transaction termination processing.

aa....aa: Name of server resulting in the error

bb....bb: Maintenance information 1

cc....cc: Maintenance information 2

S: Terminates abnormally.

O: Contact the HiRDB administrator.

Action

Contact the customer support center.

KFPD00017-E S

Message output error occurred func=aa....aa return code=bb....bb message no=cc....cc

An error occurred during message output.

aa....aa: Maintenance information 1

bb....bb: Maintenance information 2

cc....cc: Message number

S: Resumes processing.

O: Contact the HiRDB administrator.

Action

Maintenance-information-2 is -1902

The process native memory of the process where the error occurred became insufficient. Revise the swap area size.

Maintenance-information-2 is -1909

%PDDIR%\lib\msgtxt was not found. In UNIX, use the pdsetup command to set up HiRDB after HiRDB has terminated. In Windows, re-install HiRDB.

Maintenance-information-2 is -1910

A %PDDIR%\lib\msgtxt I/O error occurred. In UNIX, use the pdsetup command to set up HiRDB after HiRDB has terminated. In Windows, re-install HiRDB.

Maintenance-information-2 is -1911

%PDDIR%\lib\msgtxt cannot be accessed. Revise the access privilege to %PDDIR%\lib\msgtxt.

Other than the above

Contact the customer support center.

KFPD00020-E L

bbb initialization error occurred errorinf=aa....aa

A bbb initialization error occurred due to the reason indicated in aa....aa.

aa....aa: Error message indicating the cause of the initialization error

bbb: Type of server on which the initialization error occurred

FES: Front-end server

SDS: Single server

S: The system takes the following actions:

Front-end server error:
The front-end server is placed in the SUSPEND status. If the error is due to Insufficient pd_max_rdarea_no, the system terminates abnormally.

Single server error:
The system terminates abnormally.

Action

Take the following action:

Front-end server error:
Resolve the cause of the error and then reset the SUSPEND status of the front-end server.
For a description of how to reset the SUSPEND status, see HiRDB Version 9 System Operation Guide.
If the error is due to Insufficient pd_max_rdarea_no, increase the value specified in the pd_max_rdarea_no operand in the system common definition, and then restart the unit on which the front-end server is located.

Single server error:
Resolve the cause of the error, and then restart HiRDB system.

KFPD00021-E L

Insufficient aa....aa memory,server=bb....bb, size=cc....cc

Shared memory or process private memory is insufficient.

aa....aa: Type of area resulting in the memory shortage error:

SHARED: Shared memory

PROCESS: Process private memory

bb....bb: Name of the server resulting in the error

cc....cc: Insufficient memory size (in bytes)

S: If the server has started, stop server startup. During transaction input, abnormally terminate the process that attempted to process the applicable transaction.

Action

Take one of the following actions:

When the type of the area where a memory shortage occurred is SHARED:
If the error occurred at the startup of a user server (executed by specifying the -s option with the pdstart command) that is not a back-end server using the standby-less system switchover (effects distributed) facility, and the unit terminated abnormally, specify server in the pd_shmpool_control operand in the system common definition, and then restart the unit. Otherwise, increase the specification value of the shared memory size in the server definition (pd_sds_shmpool_size, pd_dic_shmpool_size, or pd_bes_shmpool_size operand) for the server where the memory shortage occurred. Then, restart the server where the error occurred.

When the type of the area where a memory shortage occurred is PROCESS
Either wait for another process to end and re-execute, or increase the size of the swap area.

KFPD00022-E E

Not specified definition aa....aa

aa....aa is not defined.

aa....aa: Name of definition operand:

{ pd_max_list_users |pd_max_list_count }

S: Terminates processing.

P: Specify a nonzero value for aa....aa.

KFPD00028-E L

Version incompatible with HiRDB, func=aa....aa

HiRDB and an added PPaa....aa versions do not match.

aa....aa: Added PP name

S: Abnormally terminates HiRDB.

Action

Install an added PP version that is compatible with HiRDB version.

KFPD00029-W L

No RDAREA for db management

An RDAREA that uses a data dictionary for which datadictionary of dbmanagement has been specified is not defined. For this reason, the facility for predicting reorganization time cannot be used.

S: Continues processing.

Action

If the facility for predicting reorganization time is used, create an RDAREA that uses a data dictionary by using pdmod and specifying datadictionary of dbmanagement. If the facility for predicting reorganization time is not used, change the specification of the system definition pd_rorg_predict operand.

KFPD00030-W L

Unable to make an entry SQL_DB_MANAGEMENT, RDID=aa....aa, OBJID=bb....bb, code=cc....cc

Because registering of the database management table failed, the facility for predicting reorganization time is invalid.

aa....aa: RDAREA ID

bb....bb: Table or index ID

cc....cc: SQL code that caused the error

S: Terminates processing.

O: Refer to the SQL code cc....cc that caused the error, and eliminate the cause of the error.

KFPD00031-E L

Insufficient Audit definition buffer memory, size=aa....aa code=bb....bb

HiRDB could not be started because there was a shared memory shortage for the security audit information buffer.

aa....aa: Memory size to be allocated (in bytes)

bb....bb: Error code

01: When HiRDB was started, the shared memory for the security audit information buffer specified in the pd_audit_def_buffer_size operand could not be allocated.

S: Cancels server startup.

O: Take the following action:

Error code 01:

If a KFPD00035-W message is output, follow the instructions given in the message. If the error persists, increase the OS memory by aa....aa, create a free OS memory area, or reduce the size of the pd_audit_def_buffer_size operand, and then restart HiRDB.

KFPD00032-W L

Insufficient Audit definition buffer memory, size=aa....aa code=bb....bb completed size=cc....cc

There was a shared memory shortage for the security audit information buffer.

aa....aa: Memory size to be allocated (in bytes)

bb....bb: Error code

cc....cc: Size that was allocated (in bytes)

S: Continues processing.

O: Take action appropriate to the error code:

Error code | Description | Operator action
01 | When HiRDB was started, the shared memory for the security audit information buffer was allocated based on the value specified in the pd_audit_def_buffer_size operand; however, not all audit event definitions could be registered in the security audit information buffer. | Re-estimate the value of the pd_audit_def_buffer_size operand, and then restart HiRDB.
02 | When HiRDB was started, the size required for the shared memory for the security audit information buffer could not be allocated; therefore, the security audit information buffer could not be created. | If a KFPD00035-W message is output, follow the instructions given in the message. If the error persists, either increase the OS memory by aa....aa or create a free OS memory area.
03 | Audit event definitions increased when HiRDB was running; therefore, not all audit event definitions were registered in the security audit information buffer specified in the pd_audit_def_buffer_size operand. | Re-estimate the value of the pd_audit_def_buffer_size operand, and then restart HiRDB.
04 | Audit event definitions increased when HiRDB was running; therefore, not all audit event definitions could be registered in the security audit information buffer. | Restart HiRDB.

KFPD00033-I L

Refresh Audit definition buffer completed, size=aa....aa code=bb....bb completed size=cc....cc

All audit event definitions were registered in the security audit information buffer.

S: Continues processing.

KFPD00034-W L

Unable to get Audit definition buffer space requirement, code=aa....aa

Unable to calculate a required security audit information buffer size due to a dictionary access error or communication error.

aa....aa: Error code

S: See operator actions.

O: Take action appropriate to the error code:

Error code
Security audit information buffer size specification
System action
Operator action

01
User-specified
Continues processing after acquiring shared memory for the security audit information buffer equal to a specified size. However, in some cases, not all audit event definitions can be registered in the shared memory for the security audit information buffer.
If a KFPD00032-W message is output when HiRDB is running, take corrective action according to that message.

02
Calculated automatically
Continues processing with a 0-byte shared memory size for the security audit information buffer.
To ensure performance, resolve the error, and then restart HiRDB.

03
Terminates abnormally in the case of HiRDB/Single Server.
In the case of HiRDB/Parallel Server, generates a message, and attempts to start the server a fixed number of times. If the dictionary access error is not resolved, places the front-end server in a SUSPEND state.
In the case of HiRDB/Single Server, resolve the error, and then restart HiRDB.
In the case of HiRDB/Parallel Server, resolve the error, and use the pdstart -a command to reset the front-end server from the SUSPEND state.

KFPD00035-W L

Failed to shmget Audit definition buffer,errno=aa

Unable to acquire shared memory segments for the security audit information buffer.

aa: Error code

S: Continues processing.

O: Take action appropriate to the error code:

Error code
Description
Operator action

04
An internal resource shortage in HiRDB occurred.
The maximum number of shared memory segments controlled by HiRDB (16) was exceeded. Increase the specification value in the SHMMAX operand in the system common definition or unit control information definition. If the specification value in the SHMMAX operand is increased, the same OS command must be used to make the value of shmmax greater than or equal to that value. When modifying shmmax, you must restart the OS.

08
A memory shortage occurred.
Refer to system call=shmget, errno=12, mnemonic=ENOMEM in 4.3 System call return codes to investigate and resolve the error, and take corrective action.

12
The maximum size of shared memory segments was exceeded.
Take the following action:
In Unix:
The shared memory size for the security audit information buffer exceeded either the value specified in the OS parameter shmmax or the value specified in the SHMMAX operand of the system common definition or unit control information definition. Change the value specified in the OS parameter shmmax or the value specified in the SHMMAX operand to a value greater than or equal to the estimated shared memory size for the security audit information buffer. Use the sam command to change the OS parameter shmmax. When you make any modification to shmmax, you must restart the OS.
In Windows:
The shared memory size for the security audit information buffer exceeded the value specified in the SHMMAX operand of the system common definition or unit control information definition. Change the value specified in the SHMMAX operand to a value greater than or equal to the estimated shared memory size for the security audit information buffer. If the SHMMAX value was not exceeded, it is possible that a work file in the HiRDB installation directory was deleted when HiRDB was running; if that is the case, restart HiRDB service.

16
The maximum number of shared memory identifiers was exceeded.
Refer to system call=shmget, errno=28, mnemonic=ENOSPC in 4.3 System call return codes to investigate and resolve the error, and take corrective action.

KFPD00036-W L

Failed to attach Audit definition buffer,errno=aa

Unable to attach the shared memory for the security audit information buffer.

aa: Error code

S: Continues processing.

O: Take action appropriate to the error code:

Error code | Description | Operator action
04 | The upper limit on the number of shared memory segments that can be attached was exceeded. | Use the sam command in the OS to increase the value of shmseg. Any change to shmseg requires restarting the OS.
08 | A memory shortage occurred. | Refer to system call=shmget, errno=12, mnemonic=ENOMEM in 4.3 System call return codes to investigate and resolve the error, and take corrective action.

KFPD01001-E E

SQL error occurred, SQLCODE=aa....aa

An error that prevents the continuation of processing occurred in the SQL statement in the command.

aa....aa: SQLCODE

S: Terminates processing.

Action

Check the cause of the error, based on the previously output message; resolve the cause of the error and then re-execute.

KFPD01002-E E

REGISTRY CONTEXT already catalogued

A context with the same name is already in the registry.

S: Terminates processing.

Action

Confirm that the context name is the correct one; if it is incorrect, revise it and re-execute.

KFPD01003-E E

Invalid REGISTRY ACCESS PASSWORD

The access password for the registry context is invalid.

S: Terminates processing.

Action

Specify the correct access password and re-execute.

KFPD01004-E E

REGISTRY CONTEXT not found

The specified context is not in the registry.

S: Terminates processing.

Action

Specify the correct context name and re-execute.

KFPD01005-E E

REGISTRY KEY not found

The specified key is not in the registry.

S: Terminates processing.

Action

Specify the correct key name and re-execute.

KFPD01006-E E

REGISTRY KEY already catalogued

The specified key is already in the registry.

S: Terminates processing.

Action

Confirm that the specified key name is the correct one. If it is incorrect, correct it and re-execute. If the specified key name is the correct one, either delete the previously registered key and register the new one, or register the new one under a different name.

KFPD01007-E E

Invalid value in lock_wait option

The lock_wait option is incorrectly specified (an internal system error).

S: Terminates processing.

Action

Only Y, N, or y, n can be specified in the lock_wait option. Specify the correct value and re-execute. If this error occurred during the execution of a plug-in supplied command, notify the plug-in vendor.

KFPD01008-E E

Invalid value in lock_mode option

The lock_mode option is incorrectly specified (an internal system error).

S: Terminates processing.

Action

Only 'R', 'W', or 'r', 'w' can be specified in the lock_mode option. Specify the correct value and re-execute. If this error occurred during the execution of a plug-in supplied command, notify the plug-in vendor.

KFPD01009-E E

REGISTRY KEY catalogued by long format

The key value is registered in the registry in the long format (long key value) (an internal system error).

S: Terminates processing.

Action

Notify the customer support center.

KFPD01010-E E

REGISTRY KEY catalogued by short format

The key value is registered in the registry in the short format (short key value) (an internal system error).

S: Terminates processing.

Action

Notify the customer support center.

KFPD01011-E E

Over 2147483647 in REGISTRY CONTEXT

The maximum number of registry context items that can be registered was exceeded.

S: Terminates processing.

Action

Use the pdregrmcont command to delete previously registered contexts that are no longer needed and re-execute.

KFPD01012-E E

REGISTRY CONTEXT NAME length is 0 bytes

The name of the specified registry context is 0 bytes.

S: Terminates processing.

Action

Specify the name of the context within the effective length range (1 to 240 bytes) and re-execute. If this error occurred during the execution of a plug-in supplied command, notify the plug-in vendor.

KFPD01013-E E

REGISTRY ACCESS PASSWORD length is 0 bytes

The name of the specified registry access password is 0 bytes.

S: Terminates processing.

Action

Specify the access password within the effective length range (1 to 100 bytes) and re-execute. If this error occurred during the execution of a plug-in supplied command, notify the plug-in vendor.

KFPD01014-E E

REGISTRY KEY NAME length is 0 bytes

The name of the specified registry key name is 0 bytes.

S: Terminates processing.

Action

Specify the name of the key within the effective length range (1 to 240 bytes) and re-execute. If this error occurred during the execution of a plug-in supplied command, notify the plug-in vendor.

KFPD01015-I E

Usage: aa....aa

The command format is invalid.

aa....aa: Command format

S: Terminates processing.

Action

Revise the command format and re-execute. If this error occurred during the execution of a plug-in supplied command, notify the plug-in vendor.

KFPD01016-E E

Insufficient memory, size=aa....aa

A memory shortage occurred.

aa....aa: The size to be allocated (in bytes)

S: Terminates processing.

Action

Either re-execute the UAP after other processes have ended or increase the size of the swap area.

KFPD01017-E E

REGISTRY CONTEXT NAME length exceeds 240 bytes

The name of the specified registry context is greater than the maximum value.

S: Terminates processing.

Action

Specify the name of the context within the effective length range (1 to 240 bytes) and re-execute. If this error occurred during the execution of a plug-in supplied command, notify the plug-in vendor.

KFPD01018-E E

REGISTRY ACCESS PASSWORD length exceeds 100 bytes

The specified registry access password is greater than the maximum value.

S: Terminates processing.

Action

Specify the access password within the effective length range (1 to 100 bytes) and re-execute. If this error occurred during the execution of a plug-in supplied command, notify the plug-in vendor.

KFPD01019-E E

REGISTRY KEY NAME length exceeds 240 bytes

The name of the specified registry key is greater than the maximum value.

S: Terminates processing.

Action

Specify the name of the key within the effective length range (1 to 240 bytes) and re-execute. If this error occurred during the execution of a plug-in supplied command, notify the plug-in vendor.

KFPD01020-E E

Read error occurred on file, file name=aa....aa

The read operation from the specified file failed. Or, the specified file does not exist.

aa....aa: Specified file name

S: Terminates processing.

Action

Resolve the cause of the error and re-execute.

KFPD01021-E E

System error occurred, return code=aaa

An internal system error occurred.

aaa: Return code

-10: An SQL error

-30: An invalid interface

S: Terminates processing.

Action

Notify the customer support center.

KFPD01023-I E

Usage: pdlistls [-d {1 |2}][-u list user name]
[-t base table owner.base table name]

Shows the format of the pdlistls command.

S: Terminates processing.

Action

Specify the command correctly and re-execute it.

KFPD01024-E

Usage: pddef [-e] [-s] [-R]

Shows the format of the database definition utility command.

S: Terminates processing.

Action

Specify the utility command correctly and re-execute it.

KFPD01025-E E

Invalid option for pddef

Specification of the database definition utility command is invalid.

S: Terminates processing.

Action

Specify the utility command correctly and re-execute it.

KFPD01026-E E

Argument of aa option is invalid

Either the option argument is invalid or the specified value is incorrect.

aa: Option name

S: Terminates processing.

Action

Specify the option correctly and re-execute the utility.

KFPD01100-I E

Usage: aa....aa

This message indicates how to specify commands.

aa....aa: Specification method

pdacunlck {auth_id[,auth_id]...|ALL}

S: Terminates processing.

Action

Check the command format and re-execute.

KFPD01103-E E

Invalid option for aa....aa

An error was found in the command option specification format.

aa....aa: Command name

pdacunlck

S: Terminates processing.

Action

Check the command format, and then re-execute the process.

KFPD01104-E E+L

Insufficient memory on PROCESS, size=aa....aa

There is insufficient process private area, so sufficient work area required to execute the command was not secured.

aa....aa: Area size that was to be allocated (in bytes)

S: Terminates processing.

Action

Use one of the following methods to increase the size of the process private area so that sufficient memory is available, then re-execute the command:

Reduce the number of concurrently executing processes

Increase the swap area

Add more real memory

KFPD01105-E E+L

Internal function error, func=aa....aa, return code=bb....bb

An error occurred in the internal processing of the command.

aa....aa: Name of the function in which the error occurred

bb....bb: Detailed code of the system-related error

S: Terminates processing.

Action

Correct the error by referring to 4.2 Detail codes for system-related errors and re-execute the command. If the error code is -310, the server at the communication destination may not have been activated. If an error that cannot be handled by HiRDB administrator has occurred, contact the customer support center.

KFPD01106-E E+L

Invalid execution node

The command cannot be executed from this server machine.

S: Terminates processing.

Action

Check the settings of environment variables (PDHOST, PDNAMEPORT, PDDIR, PDCONFPATH, etc.). If a setting a incorrect, correct it and re-execute the command. If all settings are correct, re-execute the command from the server machine where the system manager (MGR) is located.

KFPD01108-E E+L

Hostname=aa....aa, unable to execute cc....cc command, unit bbbb state not ONLINE

The command cannot be executed because unit bbbb with host name aa....aa is not active.

aa....aa: Name of host where command could not be executed

bbbb: Unit identifier

cc....cc: Command name

pdlistls

pdacunlck

S: Terminates processing.

Action

Start HiRDB or the unit, and then re-execute the command.

KFPD01109-E E+L

Server aa....aa not running

The command cannot be executed because the server is not running.

aa....aa: HiRDB server name

S: Terminates processing.

Action

Start the server, and then re-execute the command.

KFPD01110-E E+L

Server down detected

Abnormal termination of the server was detected.

S: Terminates processing.

Action

Check the message or abort code to find what caused the server to abnormally terminate. Eliminate the cause, and then re-execute the command.

KFPD01112-E E+L

Unable to execute "pdacunlck" command, code=aa(bb....bb)

The pdacunlck command cannot be executed.

aa: Reason code

bb....bb: Additional error information

cc....cc: Authorization identifier

S: Ignores this SQL statement.

Action

From the output reason code and additional error information, remove the error cause, and re-execute the command.

Reason code | Additional error information | Explanation
02 | Not found authorization identifier cc....cc | The authorization identifier specified in the pdacunlck command does not exist.
03 | Duplicate authorization identifier cc....cc | The authorization identifier specified in the pdacunlck command is duplicated.
04 | Number of authorization identifier exceeds 128 | The number of authorization identifier specifications exceeds 128.

KFPD01113-I L+S

"pdacunlck" command ended, return code=a

The pdacunlck command terminated with return code a.

a: Return code

0: Normal termination

8: Abnormal termination

S: Ignores this SQL statement.

Action

If the return code is 8, refer to the output message and eliminate the cause of the error, and then execute the pdacunlck command.

KFPD01114-E E+L

File access error, func=aa....aa, errno=bb....bb, file=cc....cc

A file access error occurred during XDS start processing or termination processing.

aa....aa: Processing code during which the error occurred

open: Open file processing

close: Close file processing

read: Reading

write: Write processing

bb....bb: errno value returned by the system call

cc....cc: File name

If the file name exceeds 128 bytes, two periods (..) are added in the front, the beginning of the file name is truncated, and the last 126-byte portion is output.

S: Terminates processing.

O: Refer to 4.3 System call return codes to eliminate the cause of the error, and perform corrective action by referring to Corrective action to take when an error occurs during XDS start processing or Corrective action to take when an error occurs during XDS end processing in the HiRDB Version 9 Memory Database Installation and Operation Guide.

KFPD01115-E E+L

Unable to execute SQL, SQLCODE=aa....aa, SQLERRMC=bb....bb

An error occurred during execution of the SQL statement for XDS start processing or termination processing.

aa....aa: SQL communication area (SQLCA) SQLCODE

bb....bb: SQL communication area (SQLCA) SQLERRMC

If the information length of the SQLERRMC is 128 bytes or more, the first 128 bytes is output and bytes 129 and following are discarded.

S: Terminates processing.

O: Refer to SQL CODE and follow the corresponding message to eliminate the cause of the error. Also, perform corrective action by referring to Corrective action to take when an error occurs during XDS start processing or Corrective action to take when an error occurs during XDS end processing in the HiRDB Version 9 Memory Database Installation and Operation Guide. If corrective action cannot be performed, contact the customer support center.

KFPD01115-W E+L

Unable to execute SQL, SQLCODE=aa....aa, SQLERRMC=bb....bb

An error occurred during execution of the SQL statement for XDS start processing or termination processing.

aa....aa: SQL communication area (SQLCA) SQLCODE

bb....bb: SQL communication area (SQLCA) SQLERRMC

If the information length of the SQLERRMC is 128 bytes or more, the first 128 bytes is output and bytes 129 and following are discarded.

S: Because an error occurred, processing is retried.

KFPD01116-I L+S

Retried processing executed successfully

The re-tried process was able to be executed normally.

S: Continues processing.

KFPD01117-W E+L

Update of table status for memory DB possibly failed

The status of the memory database allocation table might not have been updated.

S: Continues processing.

Action

No action is necessary for the status of the memory database allocation table to update correctly the next time the XDS starts up. However, if you stop using the memory database, update the memory database allocation table status using the following procedure.

Check the status of the memory database allocation table. For details about how to check this, see Memory database allocation table conditions in the HiRDB Version 9 Memory Database Installation and Operation Guide.

Execute DEALLOCATE MEMORY TABLE on the SQL_TABLES table that has a value of D in the MEMORY_TABLE column.

KFPD01200-I S

"pddivinfgt" command ended,return code=a

The pddivinfgt command terminated with return code a.

a: Return code

0: Normal termination

8: Abnormal termination

S: Terminates processing.

P: If the return code is 8, see the message output prior to this message, eliminate the cause of the error, and then re-execute the command.

KFPD01201-E E

Unable to execute SQL, SQLCODE=aa....aa, SQLERRMC=bb....bb

During execution of the command (pddivinfgt command) for acquiring partitioning conditions, an error occurred in the SQL statement that executes internally.

aa....aa: SQL communication area (SQLCA) SQLCODE

bb....bb: SQL communication area (SQLCA) SQLERRMC

If the information length of the SQLERRMC is 128 bytes or more, output the first 128 bytes and discard bytes 129 and following.

S: Terminates processing.

P: Follow the message corresponding to SQLCODE aa....aa, and eliminate the cause of the error.

KFPD01202-E E

Unable to get partitioning information due to aa....aa,code=bb

Because of aa....aa, the partition conditions of the specified table cannot be acquired.

aa....aa: Additional information

bb: Reason code

S: Terminates processing.

P: If the specified table name is invalid, revise the table name and re-execute. If the table name is not invalid, follow the additional instructions for the error codes and errors shown below, and take corrective action accordingly.

Reason code | Additional information | Explanation | Action
01 | not found table | The specified table does not exist. | Check whether the specified table name is correct.
02 | not base table | It is not a base table. | None (nothing other than a base table can be specified in the command)
03 | HASH partitioning | Hash partitioning table | None (a hash-partitioned table cannot be specified in the command).
04 | matrix-partitioned table | Matrix partitioned table | None (a matrix-partitioned table cannot be specified in the command).
05 | not "=" only partitioning condition | This is not the specified partitioning of stored conditions that were only specified in the comparison operator. | None (you cannot specify anything other than = in the comparison operator of the conditions stored in the command).
06 | not table owner | This table does not belong to you. | Specify the table that belongs to you, and then re-execute. Or the user with DBA privileges should re-execute it.

KFPD01203-E E

File access error,access=aa....aa,func=bb....bb,errno=cc....cc, file=dd....dd

A file operation error occurred.

aa....aa: Processing code during which the error occurred

open: Open file processing

close: Close file processing

write: Write processing

bb....bb: System call resulting in the error

cc....cc: errno value returned by the system call

dd....dd: File name

If the file name is 128 bytes or less, the entire file name is displayed. If the file name exceeds 128 bytes, two periods (..) are added in the front, and the last 126-bytes of the file name are displayed.

S: Terminates processing.

P: Refer to 4.3 System call return codes, eliminate the cause of the error, and then re-execute.

2.4 KFPH messages

KFPH00031-E L

RDAREA "aa....aa" not initialized, file=bb....bb, reason code=cc

HiRDB file bb....bb in RDAREA "aa....aa" has not been initialized.

aa....aa: RDAREA name

bb....bb: Name-of-HiRDB-file-system-area\Name-of-HiRDB-file

If the path name of HiRDB file exceeds 131 characters, the last 131 characters of HiRDB file path name are output.

cc: Reason code:

1: Reinitialization of RDAREA not completed

2: Deletion of RDAREA not completed

3: Integration of the RDAREA is not complete.

10 to 19: RDAREA management information not set

S:

For user RDAREA:

Shuts down the corresponding RDAREA and resumes processing.

For any other RDAREA:

Terminates processing. However, if this message is output when a HiRDB was being executed, continues processing by closing the affected RDAREA.

Action

Check the cause of the error, as listed below, correct the RDAREA, and then re-execute the processing:

This RDAREA cannot be used because the following processes of the database structure modification utility terminated abnormally:
Reinitialization of the RDAREA
Deletion of the RDAREA
Matching of the RDAREAs

Recovery of the RDAREA failed.

HiRDB file system areas are mismatched.

Synchronization was lost between HiRDB file system area containing the master directory RDAREA or the data dictionary RDAREA and HiRDB file system area where the error occurred.

The contents of the RDAREA are damaged.

If none of the above applies, contact the customer support center.

KFPH00035-W L

Global buffer pool not allocated for RDAREA aa....aa

Global buffer pool is not allocated to the RDAREA.

aa....aa: RDAREA name

S: Places the RDAREA on CLOSE status and resumes processing.

Action

Allocate a global buffer pool for the RDAREA with the pdbuffer operand of the system common definition.

KFPH00110-I L+S

aa....aa command completed

Processing of HiRDB command aa....aa has been completed.

aa....aa: Name of command

S: Resumes processing.

KFPH00115-I L+S

aa....aa command failed

HiRDB command aa....aa cannot be processed.

aa....aa: Name of command

S: Ignores the entered command and terminates processing.

However, some processing might be executed in the following cases:

If the pdhold command with the -c option or the pdrels command with the -o option is specified, processing of the command might be only partially executed.

If multiple RDAREAs or servers are specified, command processing might execute on only some of the RDAREAs or servers.

For a shared RDAREA, command processing might execute on only some of the servers.

Action

The following are the administrator's actions corresponding to system actions 1 to 3 above:

After taking corrective action based on the error message that was output immediately before this message, use the pddbls command to check the status of the RDAREAs, and then re-execute the command.

If the pdbufmod command was being executed, after taking corrective action based on the error message that was output immediately before this message, use the pdbufls command to check the status of the global buffer, and then re-execute the command.
If a command other than the pdbufmod command was being executed, after taking corrective action based on the error message that was output immediately before this message, use the pddbls command to check the status of the RDAREAs, and then re-execute the command.

After taking corrective action based on the error message that was output immediately before this message, use the pddbls -m command to check the status of shared RDAREAs on all back-end servers, and if there are any inconsistencies, make sure that the RDAREAs have the same status, and then re-execute the command.

KFPH00130-I L+S

RDAREA aa....aa,RDAREA=bb....bb

The specified RDAREA was shut down, released from shutdown, opened, closed, had updates frozen or unfrozen, or was changed to the current RDAREA.

aa....aa: Type of RDAREA processing:

held: RDAREA was shut down (access prohibited)

held(inq): RDAREA was shut down (referencing permitted)

held(bu i): Reference-possible backup hold

held(bu iw): Reference-possible backup hold (update WAIT mode)

held(bu): Updatable backup-hold

held(bu w): Updatable backup-hold (WAIT mode)

held(sync): Synchronization hold

held(org): Online reorganization hold

released: RDAREA was released from shutdown status

opened: RDAREA was opened

closed: RDAREA was closed

freezed: Updating of RDAREA is frozen

unfreezed: Update freeze of the RDAREA was cancelled

current changed: RDAREA was changed to the current RDAREA

bb....bb: RDAREA name

S: Resumes processing.

KFPH00131-E L+S

pdhold command failed due to RDAREA already held, RDAREA="aa....aa"

The indicated RDAREA cannot be shut down by the command, because it is already on error shutdown status.

aa....aa: RDAREA name

S: Ignores this RDAREA processing and continues processing.

O: Check the RDAREA status with the pddbls command. Eliminate the cause of the RDAREA being placed on error shutdown status, release the RDAREA from shutdown status, then re-execute the command.

KFPH00132-E L+S

aa....aa command failed due to HiRDB error, bb....bb=cc....cc code=ddd[, server = ee....ee]

HiRDB command aa....aa cannot be processed, because a HiRDB server error occurred.

aa....aa: Command name

bb....bb: Invalid specification (one of the following is displayed):

RDAREA

server

buffer pool

index

cc....cc: Name of RDAREA, server, global buffer, or index (if the name cannot be obtained, ***** is displayed)

ddd: Error code:

-2: Access error in dictionary RDAREA

-4: Memory shortage at the communication destination

-7: PRC communication error

-20: Reinitialization of RDAREA not completed

-21: Deletion of RDAREA not completed

-22: Page length longer than the buffer length

-23: Integration of RDAREA not completed

-24: A falsification prevented table with incomplete data was found in the applicable RDAREA

ee....ee: Shared RDAREA runtime server name

This is displayed when an error occurs in a shared RDAREA.

The server name is output only when the error code is -4 or -7. However, if server is output in bb....bb, nothing is output here. In addition, nothing is output if the error code is -2, which indicates an error in the dictionary server.

S:

RDAREA:

Invalidates the applicable RDAREA processing and continues processing.

Server:

Invalidates the server process causing the error and continues processing.

Global buffer:

Invalidates the applicable global buffer process and continues processing.

Index:

Invalidates the applicable index process and continues processing.

O:

Error code is -24:

Use the database reorganization utility (pdrorg) to complete the reloading of falsification prevented tables that are in reload-not-completed data status. Then, use the pdrels command to cancel the hold and resume work.

Error code is not -24:

Refer to the message output to the message log file, eliminate the cause of the error, and then re-execute the command.

When a shared RDAREA is used, and server is output in bb....bb or the server name is displayed:

Refer to the message output to the message log file, remove the cause of the error from the relevant server, and re-execute the command.

KFPH00133-E L+S

RDAREA release failed due to not recovered, RDAREA="aa....aa"

The error shutdown could not be released because RDAREA aa....aa that was shut down due to the error was not recovered.
Or, synchronization hold RDAREA aa....aa could not be released because it was updated with invalid data.

aa....aa: RDAREA name

S: Invalidates the command's processing for this RDAREA and continues processing.

Action

Use the pddbls command to check the status of the RDAREA. If the RDAREA is on error shutdown status, take one of the following actions to release its error shutdown status:

Use the pdrstr command to recover the RDAREA.

Use the pdmod command to reinitialize the RDAREA (note that all data in the RDAREA will be deleted).

Update using a duplicate RDAREA that has valid data in the inner replica group for synchronization holding when using the inner replica facility, and then re-execute the command.

KFPH00134-I L+S

aa....aa command completed, server = bb....bb

Operation command aa....aa processing is complete on server bb....bb.

aa....aa: Command name

bb....bb: Server name

S: Terminates processing.

KFPH00135-E L+S

aa....aa command failed, server = bb....bb

Operation command aa....aa processing could not be performed on server bb....bb.

aa....aa: Command name

bb....bb: Server name

S: Invalidates processing of the server where the error occurred, and then continue processing.

Action

Refer to the output message, eliminate the cause of the error, and then re-execute this command.

KFPH00141-E L+S

aa....aa command failed due to specified name invalid, RDAREA=bb....bb

HiRDB command aa....aa could not be processed because the specified RDAREA name is invalid.
Another possibility is that the specified RDAREA is not subject to processing by HiRDB command aa....aa.

aa....aa: Name of command

bb....bb: RDAREA name

S: Invalidates the corresponding RDAREA processing and resumes processing.

Action

Specify the correct RDAREA name and re-execute the command. If you need to correct the pattern character string of the RDAREA batch specification, see the manual HiRDB Version 9 Command Reference to determine how to specify a correct pattern character string, and then re-execute the command.

Alternatively, re-execute the command without the RDAREA that is not able to be processed. For details about the RDAREAs that can be processed by HiRDB command aa....aa, see the manual HiRDB Version 9 Command Reference.

KFPH00142-E L+S

aa....aa command failed due to specified name not found, bb....bb=cc....cc[, server = dd....dd]

Specified RDAREA name, server name, buffer pool name, or table name not found. HiRDB command aa....aa cannot be processed.

aa....aa: Name of command

bb....bb: Invalid specification:

{ RDAREA |server |buffer pool |table }

cc....cc: Name of RDAREA, server, buffer pool, or table

dd....dd: Shared RDAREA runtime server name

This is displayed when an error occurs in a shared RDAREA during execution of the pddbls command.

S: Performs the following processing for cc....cc.

If an RDAREA, invalidates the corresponding RDAREA processing and resumes processing.

If a server, invalidates the server processing resulting in the error and resumes processing.

If a buffer pool, invalidates the corresponding buffer pool processing and resumes processing.

For a table name, processing is interrupted.

O: Specify the correct RDAREA name, server name, buffer pool name, or table name, and then re-execute the command. If multiple RDAREA names are specified and ALL is specified as the second or subsequent RDAREA name, specify ALL by itself, and then re-execute the command.

KFPH00145-E L+S

aa....aa command failed due to HiRDB error, code=bbb[, server = cc....cc]

A HiRDB system error occurred and HiRDB command aa....aa cannot be processed.

aa....aa: Name of command

bbb: Error code:

-4: Memory shortage

-5: Lock error

-6: Lock release error

-8: RDAREA information management block maintenance error

-9: Transaction startup error

-10: Information collection error in HiRDB file system area

-11: Object cache not released

-12: Lock of object cache disabled

-13: Unlock of object cache disabled

cc....cc: Shared RDAREA runtime server name

This is displayed when an error occurs in a shared RDAREA.

S: Terminates processing.

O: Eliminate the cause of the error on the basis of the message output to the message log file and re-execute the command.

When the server name is displayed
Refer to the message output in the message log file, remove the cause of the error from the relevant server, and re-execute the command.

When the pdorbegin -u command is executed
Check that the RDAREA can be released from online reorganization hold.

KFPH00153-E L+S

aa....aa command failed due to RDAREA status invalid, RDAREA=bb....bb

Unable to execute aa....aa command due to an invalid RDAREA status.

aa....aa: Name of command

bb....bb: RDAREA name

S: Cancels the processing on the RDAREA, and continues processing.

O:

Check the RDAREA's status with the pddbls command, correct the status, then re-execute the command.

When shared RDAREAs are used, check the status of the shared RDAREA for each server using the pddbls -m command, and place all shared RDAREAs in the correct status. Then, re-execute the command.

When temporarily changing from online reorganization hold status to reference-possible hold status, the RDAREA cannot hold backups. Use the pdrels command to release the reference-possible hold. In addition, if the pdorchg command has not been executed, use the pdorbegin command; if pdorchg has been executed, use the pdorend command to release the online reorganization hold, and then re-execute the command.

For more information about whether commands can be executed depending on the status of the RDAREA, see Availability of utility or UAP execution depending on RDAREA status in the manual HiRDB Version 9 Command Reference. However, for the pdorbegin command, see RDAREA status transitions in the manual HiRDB Version 9 Command Reference to verify the correct status for the original RDAREA. In the case of a replica RDAREA, verify that the area is on hold and closed.

KFPH00154-E L+S

RDAREA open failed due to not recovered, RDAREA="aa....aa"

RDAREA that was shut down due to an error has not been recovered and could not be opened.

aa....aa: RDAREA name

S: Invalidates the command for this RDAREA and resumes processing.

Action

Eliminate the cause of the RDAREA shutdown error and release its CLOSE status with the pdrels command.

KFPH00155-W L+S

RDAREA status changed, though not recovered, RDAREA="aa....aa"

Even though RDAREA aa....aa that was shut down has not been recovered, its status was changed. Or, the RDAREA status was changed without reflecting difference data in synchronization-hold RDAREA aa....aa.

aa....aa: RDAREA name

S: Resumes processing.

Action

Check the cause of the RDAREA shutdown error and eliminate the cause if it affects operations.

KFPH00156-E L+S

Backup hold canceled due to deadlock occurred, RDAREA = "aa....aa"[, server = bb....bb]

Backup-hold was cancelled because deadlock occurred.

aa....aa: RDAREA name

bb....bb: Shared RDAREA runtime server name

This is displayed when an error occurs in a shared RDAREA.

S: Terminates processing.

O:

If there is an RDAREA that is in reference-possible backup-hold status of the update WAIT mode or that is in updatable backup-hold status, refer to the deadlock information (for a shared RDAREA, the server deadlock information) and find the RDAREA that is securing the lock on the backup-held RDAREA (resource type 0602). Then use the pdrels command to release that RDAREA's held status, and re-execute the pdhold command.

In all other cases, wait a while, and then re-execute the pdhold command. For details on deadlock information, see HiRDB Version 9 System Operation Guide.

KFPH00157-W L+S

Unable to recover without log file because of update in backup hold, RDAREA=aa....aa

RDAREA aa....aa was updated while it was in updatable backup-hold status (WAIT mode). Recovery of the database using this backup requires the unload log file into which were unloaded the system logs from the most recent synchronization point before the backup was made.

aa....aa: RDAREA name

S: Continues processing.

Action

To recover the RDAREA, use the backup file and unload log file.

KFPH00210-I L

Clustering disordered, table id=aa....aa

In the case of a table for which clustering is specified, rows can no longer be stored in the specified segment and the benefits of clustering are beginning to be lost.

aa....aa: Table number

S: Resumes processing.

O: Reorganize the corresponding table.

KFPH00211-I L

RDAREA usage aaa%, RDAREA="bb....bb"cc....cc

The meaning depends on the circumstances:

System definition pd_rdarea_warning_point not specified:

Master directory RDAREA, data directory RDAREA:

No message is output.

Data dictionary RDAREA, user RDAREA, user LOB RDAREA, registry, and registry LOB RDAREAs:

The system started using the segment with relative location aaa% among all the segments of the last file in RDAREA "bb....bb".

System definition pd_rdarea_warning_point specified:

Master directory RDAREA, data directory RDAREA, data dictionary RDAREA, user RDAREA, registry RDAREAs:

The system started using the segment with usage factor aaa% among all the segments in RDAREA "bb....bb". The current number of unused segments is cc....cc.

User LOB RDAREA, registry LOB RDAREAs:

The system started using the segment with relative location aaa% among all the segments in RDAREA "bb....bb". The number of remaining segments that can maintain effective performance is cc....cc.#

#

In the case of a user LOB RDAREA, the highest throughput can be achieved when the database area has not been used through the end. The effective performance indicates the high throughput status. Once a database is used through the end, throughput becomes lower. Therefore, some action such as database reorganization must be taken beforehand.

aaa: One of the following is displayed:

Relative location of the segment being used in the last file in the RDAREA

Segment usage factor in the entire RDAREA

Relative location in the RDAREA of the segment being used

bb....bb: Applicable RDAREA name

cc....cc: Additional information about segment usage factor, dd....dd segments unused (dd....dd: number of remaining segments)

S: Resumes processing.

If there is not enough space to allocate a new segment in this RDAREA but there is some space in existing segments used for addition or updating, the system continues processing using those segments.

This message is displayed again if the indicated segment is used after it was released due to table deletion, reorganization, etc.

P: Contact the HiRDB administrator.

Action

Use the command or utility shown below to check the remaining space in the RDAREA, then take the appropriate action shown in the table.

Command for checking the remaining space:

Database status display command (pddbls)
Specifying the -a option displays the RDAREA usage status. This command can be used for all RDAREAs.

Database condition analysis utility (pddbst)
Analyzes the RDAREA usage status using physical or logical analysis. This utility can be used for data dictionary RDAREAs, user RDAREAs (except temporary table RDAREAs), and LOB RDAREAs.

Action

The table below shows the actions:

RDAREA type
System definition pd_rdarea_warning_point not specified
System definition pd_rdarea_warning_point specified

Master directory RDAREA or data directory RDAREA
No message is output.

Check the usage status of the RDAREA by using the database status display command (pddbls) or check the additional information about segment usage factor displayed in the message.

Extend the RDAREA as required.

The database condition analysis utility (pddbst) is not applicable to this RDAREA. Additionally, this RDAREA cannot be reorganized.

Data dictionary RDAREA

Check the usage status of the RDAREA by using the database status display command (pddbls) or the database condition analysis utility (pddbst).

Depending on the usage status, either reorganize the table in units of RDAREAs or tables, or expand the RDAREA.

Check the usage status of the RDAREA by using the database status display command (pddbls) or the database condition analysis utility (pddbst) or check the additional information about segment usage factor displayed in the message.

Depending on the usage status, either reorganize the table in units of RDAREAs or tables, or expand the RDAREA.

User RDAREA (non-temporary table RDAREA)

Check the usage status of the RDAREA by using the database status display command (pddbls) or the database condition analysis utility (pddbst).

Depending on the usage status, either reorganize the table in units of RDAREAs or tables, or expand the RDAREA.

Check the usage status of the RDAREA by using the database status display command (pddbls) or the database condition analysis utility (pddbst) or check the additional information about segment usage factor displayed in the message.

Reorganize the tables in units of RDAREAs or tables according to the usage status. Or, extend the RDAREA.

User RDAREA (temporary table RDAREA)
Expand the RDAREA or add an RDAREA, depending on the situation.

LOB RDAREA

Check the usage status of the RDAREA by using the database status display command (pddbls) or the database condition analysis utility (pddbst).

Reorganize the RDAREA in units of user LOB RDAREAs or tables according to the usage status. Or, extend the RDAREA.

Check the usage status of the RDAREA by using the database status display command (pddbls) or the database condition analysis utility (pddbst) or check the additional information about segment usage factor displayed in the message.

Reorganize the RDAREA in units of user LOB RDAREAs or tables according to the usage status. Or, extend the RDAREA.

List RDAREA
Take the corrective actions described in Space shortage in a list RDAREA under RDAREA space shortage in the HiRDB Version 9 System Operation Guide.

KFPH00212-I L

Table should be reorganized, RDAREA="aa....aa", AUTHID=bb....bb, TABLE=cc....cc

A table needs to be reorganized.

aa....aa: RDAREA name

bb....bb: Authorization identifier

cc....cc: Table identifier

S: Resumes processing.

Action

Reorganize the table with the database reorganization utility (pdrorg). The size of the RDAREA must be increased in the following cases:

This message is issued frequently for tables in the same RDAREA.

This message is issued during or immediately after table reorganization.

KFPH00213-W L

All segments in RDAREA "aa....aa" allocated

An attempt was made to allocate a new segment for a table or index, but all segments in RDAREA aa....aa are in use.
This message is output for data dictionary RDAREAs, data dictionary LOB RDAREAs, user RDAREAs, and user LOB RDAREAs. Furthermore, this message is output once per RDAREA after the server has started, and the next event is released from warning message output status.

HiRDB server startup

RDAREA hold release

RDAREA open by operation command

RDAREA expansion

aa....aa: RDAREA name

S: Continues processing.

Even if the RDAREA indicated in this message is too small, and new segments cannot be allocated, if there are any existing empty segments among those added or changed, those segments are used, and processing continues.

Furthermore, if the segments referred to in this message are released when a table is dropped or reorganized, and then the same segments are used later, this message is re-displayed.

Action

See the actions of the KFPH00211-I message.

KFPH00306-E L

RDAREA "aa....aa" hold due to bb....bb

RDAREA aa....aa was placed on error shutdown status for reason bb....bb.
For an in-memory RDAREA, this results in a buffer error.

aa....aa: RDAREA name

bb....bb: Reason for shutting down the RDAREA:

LIST RDAREA error:

An error was detected in a list RDAREA.

error occurred in log less utility:

An error was detected during processing of a utility that does not collect log information, so the RDAREA was shut down.

error occurred in log less uap:

Error was detected during processing of a UAP that does not collect log information, so the RDAREA was shut down.

error occurred in table of RECOVERY NO option at BLOB column:

The RECOVERY NO option was set in the BLOB column, so the RDAREA was shut down.

i/o error occurred:

An I/O error occurred.

open error occurred:

An open error occurred.

page corrupted:

Internal conflict was detected on a page.

rollback failed:

Rollback failed.

time stamp invalid:

Time stamp mismatch was detected on a page.

object ID invalid:

Object ID mismatch was detected on a page.

S: In the case of input from the RDAREA (with the exception of log application site processing when the database recovery utility, rerun, rollback, or Real Time SAN Replication with the log-only synchronous method is being used), terminates processing and rolls back; in all other cases, continues processing.

Action

For an in-memory RDAREA, perform the error recovery steps in Troubleshooting in the manual HiRDB Version 9 Batch Job Accelerator. Otherwise, take the following action:

LIST RDAREA error:

This error is output when HiRDB is started forcibly without recovering a list RDAREA that had been placed on error shutdown status. Reinitialize the list RDAREA, then use the pdrels command to release its shutdown status, then resume the operation.

error occurred in log less utility:

Recover the RDAREA as follows:

When recovering an RDAREA to the state it was in when a backup of the database was made:
Use the pdclose command to close the RDAREA to be recovered, and then use the database recovery utility to recover the RDAREA. Next, use the pdrels -o command to release the shutdown and open the RDAREA, and then resume the operation.

When recovering an RDAREA to it's initial state without using the database recovery utility:
Use the pdclose command to close the RDAREA to be recovered, and then use the database structure modification utility to re-initialize the RDAREA. Next, use the pdrels -o command to release the shutdown and open the RDAREA, and then restore the initial data back into the table and resume the operation.

For details about how to operate in no-log mode, see the HiRDB Version 9 System Operation Guide.

error occurred in log less uap:

Recover the RDAREA as follows:

When recovering an RDAREA to the state it was in when a backup of the database was made:
Use the pdclose command to close the RDAREA to be recovered, and then use the database recovery utility to recover the RDAREA. Next, use the pdrels -o command to release the shutdown and open the RDAREA, and then resume the operation.

When recovering an RDAREA to it's initial state without using the database recovery utility:
Use the PURGE TABLE statement to delete the row data from all the tables updated by the UAP, and then use the pdrels command to release the shutdown. Next, restore the initial data back into the table and resume the operation.

For details about how to operate in no-log mode, see the HiRDB Version 9 System Operation Guide.

error occurred in table of RECOVERY NO option at BLOB column:

Recover the RDAREA as follows:

When recovering an RDAREA to the state it was in when a backup of the database was made:
Use the pdclose command to close the RDAREA to be recovered, and then use the database recovery utility to recover the RDAREA. Next, use the pdrels -o command to release the shutdown and open the RDAREA, and then resume the operation.

When recovering an RDAREA to it's initial state without using the database recovery utility:
Use the PURGE TABLE statement to delete the row data from the tables containing LOB columns in the tables in the RDAREA that was shut down, and then use the pdrels command to release the shutdown. Next, restore the initial data back into the table and resume the operation.

For details about how to operate in no-log mode, see the HiRDB Version 9 System Operation Guide.

i/o error occurred:

Refer to the KFPH22003-E or KFPH23100-E message that is output immediately before this error and correct the I/O error. Use the database recovery utility to recover the RDAREA, then use the pdrels command to release the shutdown, then resume the operation.

open error occurred:

Refer to the KFPH22003-E or KFPH23100-E message that is output immediately before this error and correct the open error. Use the database recovery utility to recover the RDAREA, then use the pdrels command to release the shutdown, then resume the operation.

time stamp invalid:

Contact the customer support center. Save the simple dump that is output under %PDDIR%\spool. Use the database recovery utility to recover the RDAREA, then use the pdrels command to release the shutdown status, then resume the operation.

Other cases:

RDAREA recovery may have failed; check for the following:

The RDAREA had been placed on error shutdown status earlier, but has not been recovered; or, the RDAREA was released forcibly from error shutdown status and was used after the database recovery utility failed.

HiRDB has been started forcibly.

Status or log files were initialized after HiRDB was terminated forcibly or terminated abnormally, and then HiRDB was restarted and used.

When the RDAREA was recovered from a backup earlier, at least one RDAREA related to the recovered RDAREA was not recovered from the backup.

Backup was restored and HiRDB was restarted after HiRDB had been terminated forcibly or terminated abnormally.

If any of the above is applicable, use the database recovery utility to recover the RDAREA, then use the pdrels command to release the shutdown status, then resume the operation.

If none of the above is applicable, contact the customer support center. Save the simple dump that is output under %PDDIR%\spool. Use the database recovery utility to recover the RDAREA, then use the pdrels command to release the shutdown status, then resume the operation.

Log application site using Real Time SAN Replication with the log-only synchronous method

The log application is disabled. Refer to the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide, and take corrective action.

KFPH00307-E L

RDAREA "aa....aa" HELD(CMD) due to bb....bb

RDAREA "aa....aa" was shut down for reason bb....bb.

aa....aa: RDAREA name

bb....bb: Reason for shutting down the RDAREA:

time stamp invalid:

Time stamp mismatch was detected on a page.

i/o error occurred:

An I/O error occurred.

open error occurred:

An open error occurred.

object ID invalid:

Object ID mismatch was detected on a page.

page corrupted:

Page corruption was detected.

data unfinished:

A falsification prevented table in reload-not-completed data status was detected.

S: Shuts down and rolls back the applicable RDAREA.

Action

time stamp invalid:

Contact the customer support center. Save the simple dump that is output under %PDDIR%\spool. If the KFPH00306-E message has not been output for the applicable RDAREA, its shutdown status can be released with the pdrels command and the operation can be resumed. If the KFPH00306-E message has been output, the RDAREA must be recovered; take the action indicated by the KFPH00306-E message.

i/o error occurred:

If the KFPH00306-E message has not been output for the applicable RDAREA, refer to the KFPH22003-E or KFPH23100-E message that is output immediately before this error, and correct the I/O error. Then use the pdrels command to release the shutdown status, then resume the operation.

If the KFPH00306-E message has been output, the RDAREA must be recovered; take the action indicated by the KFPH00306-E message.

open error occurred:

If the KFPH00306-E message has been output for the applicable RDAREA, the RDAREA must be recovered. Take the action indicated by the KFPH00306-E message.

If the KFPH00306-E message has not been output for the applicable RDAREA, refer to the KFPH22003-E or KFPH23100-E message that is output immediately before this error, and correct the open error. Then use the pdrels command to release the shutdown status, then resume the operation.

data unfinished:

A falsification prevented table in reload-not-completed data status is in the applicable RDAREA. Use the database reorganization utility (pdrorg) to completely reload the falsification prevented table in reload-not-completed data status. Then, use the pdrels command to release the shutdown status and resume work.

Other cases:

RDAREA recovery may have failed; check for the following:

The RDAREA had been placed on error shutdown status earlier, but has not been recovered; or, the RDAREA was released forcibly from error shutdown status and was used after the database recovery utility failed.

HiRDB has been started forcibly.

Status or log files were initialized after HiRDB was terminated forcibly or terminated abnormally, and then HiRDB was restarted and used.

When the RDAREA was recovered from a backup earlier, at least one RDAREA related to the recovered RDAREA was not recovered from the backup.

If any of the above is applicable, use the database recovery utility to recover the RDAREA, then use the pdrels command to release the shutdown status, then resume the operation.

If none of the above items is applicable, contact the customer support center. Save the simple dump that is output under %PDDIR%\spool. If the KFPH00306-E message has been output for the applicable RDAREA, the RDAREA must be recovered. Take the action indicated by the KFPH00306-E message. If the KFPH00306-E message has not been output, the shutdown status can be released with the pdrels command and the operation can be resumed.

KFPH00308-E L

Page corrupted, RDAREA = "aa....aa", file name = bb....bb, offset = cc....cc

Page corruption was detected.
For an in-memory RDAREA, page corruption was detected on the in-memory data buffer.

aa....aa: RDAREA name

bb....bb: Name-of-HiRDB-file-system-area\Name-of-HiRDB-file

If the path name of HiRDB file exceeds 131 characters, the last 131 characters of HiRDB file path name are output.

cc....cc: Location relative to the beginning of HiRDB file (shows in decimal the location of the corrupted page)

S: Shuts down this RDAREA and outputs a simple dump file. For an in-memory RDAREA, this results in a buffer error.

O: Contact the HiRDB administrator.

Action

Contact the customer support center. Use the database recovery utility to recover the RDAREA that was shut down. For an in-memory RDAREA, perform the error recovery steps in Troubleshooting in the manual HiRDB Version 9 Batch Job Accelerator.

KFPH00309-E L

DB error inf1=(file=aa....aa, offset=bb....bb, pno=cc....cc, fno=dd)

Outputs maintenance information at the time of a database error.

aa....aa: Name-of-HiRDB-file-system-area\Name-of-HiRDB-file

If the path name of HiRDB file exceeds 131 characters, the last 131 characters of HiRDB file path name are output.

If unclear, ****** is displayed.

bb....bb: Offset from the beginning of HiRDB file page to where the error was detected. (****** is displayed when the file name is unknown)

cc....cc: Page number

dd: File number

S: Continues processing.

Action

Take the action indicated by the abort code in the message KFPH00306-E, KFPH00307-E, KFPH22025-E, KFPH22026-E, KFPH23023-I, or KFPH23040-I that was output after this error.

KFPH00310-E L

DB error inf2=(func=aa....aa, line=bbbbb, RDAREA="cc....cc", RDID=dd....dd, ptype=e, TBLID=ff....ff, IDXID=gg....gg, LISTID=hh....hh, opcode=iiiii, sttype=jj)

Outputs maintenance information at the time of a database error.

aa....aa: Name of the function in which the error was detected

bbbbb: Row number in which the error was detected

cc....cc: RDAREA name (****** is displayed when the RDAREA name is unknown)

dd....dd: RDAREA ID

e: Detected page type:

I: Index

T: Data

D: Directory

L: List

B: LOB

ff....ff: ID of the applicable table (if unknown, ****** is displayed)

gg....gg: ID of the applicable index (if unknown, ****** is displayed)

hh....hh: ID of the applicable list (if unknown, ****** is displayed)

iiiii: Operation code (if unknown, *** is displayed)

jj: Scan type (if unknown, ** is displayed)

S: Continues processing.

Action

Take the actions indicated by the abort code in the KFPH00306-E, KFPH00307-E, KFPH22025-E, KFPH22026-E, KFPH23023-I, or KFPH23040-I message that was output after this error.

KFPH00311-E L

RDAREA "aa....aa" held in Real_Time_SAN_Reprication backup site, due to bb....bb in Real_Time_SAN_Reprication usually site

At the log application site, RDAREA "aa....aa" was shut down due to reason bb....bb.

aa....aa: RDAREA name

bb....bb: Reason for shutdown

log less utility executed:

At the transaction execution site, a utility was executed either in no-log mode or in pre-update log acquisition mode.

log less uap executed:

At the transaction execution site, a UAP was executed in no-log mode.

table of RECOVERY NO/PARTIAL option at BLOB column is changed:

At the transaction execution site, a table with a BLOB column was updated with either the RECOVERY NO or RECOVERY PARTIAL option.

database structure modification utility executed:

At the transaction execution site, the database structure modification utility (pdmod) was executed.

This reason code is output when one of the following facilities is used on the RDAREA undergoing system log application processing:

RDAREA expansion (expand rdarea statement)

RDAREA re-initialization (initialize rdarea statement)

RDAREA deletion (remove rdarea statement)

RDAREA move (move rdarea statement)

RDAREA attribute modification (alter rdarea statement)

held:

The RDAREA at the transaction execution site was shut down due to an error.

S: Continues processing.

Action

The log application is disabled. Refer to the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide, and take corrective action.

KFPH00312-E L

RDAREA "aa....aa" HELD(CMD) in Real_Time_SAN_Reprication backup site, due to bb....bb in Real_Time_SAN_Reprication usually site

At the log application site, RDAREA "aa....aa" was shut down due to reason bb....bb.

aa....aa: RDAREA name

bb....bb: Reason for shutdown

HELD(CMD):

A command shutdown was performed at the transaction execution site.

S: Continues processing.

Action

If a KFPH00311-E message is not output on the RDAREA in question, take corrective action by referring to the KFPH00307-E message that is output at the transaction execution site. If a KFPH00311-E message is output, take corrective action according to the KFPH00311-E message.

KFPH00313-E L

Time stamp invalidity information, (header value=aa....aa, footer value=bb....bb)

Outputs maintenance information when a time stamp inconsistency is found in a page.

aa....aa: Page header time stamp acquisition value

bb....bb: Page footer time stamp acquisition value

S: Continues processing.

Action

Take corrective action according to the KFPH00306-E, KFPH00307-E, KFPH22025-E, or KFPH22026-E message or the abort code that is output following this message.

KFPH00372-I L

RDAREA "aa....aa" not recovered from hold status

RDAREA that was shut down due to an error has not been recovered.

aa....aa: RDAREA name

S: Resumes processing.

Action

Recover the RDAREA and release its SHUTDOWN status.

KFPH20001-E L

Invalid HiRDB ID for database, HiRDB ID=aaaa, database initialize HiRDB ID=bbbb

Identifier aaaa of the started HiRDB differs from identifier bbbb of HiRDB whose database was initialized.

aaaa: Identifier of HiRDB that was started

bbbb: Identifier of HiRDB that was initialized

S: Terminates abnormally.

Action

Re-execute after correcting HiRDB identifier specified in the pd_system_id operand of the system common definition to the following HiRDB identifier:

Identifier of HiRDB whose database was initialized

Or, execute the database initialization utility.

KFPH20003-E L

Server aa....aa initialization failes, function=bb....bb,return code=cccc

When server aa....aa was started, bb....bb resulted in error cccc.

aa....aa: Server name

bb....bb: Function resulting in the error

cccc: Return code

S: Terminates server processing.

O: Contact the HiRDB administrator.

Action

Take action appropriate to the return code:

bb....bb
cccc
Action

malloc
--
There is insufficient process private area. Take the following actions to be sure more than enough memory is available:

Reduce the number of concurrently executing processes.

Increase the swap area.

Add real memory.

p_f_dbh_buf_defmk
-150
In the system common definition, the pdbuffer operand is invalid. Correct the pdbuffer operand.

Other than the above
Refer to the message output before this message was output, eliminate the cause of the error, and then restart the server. If no message was output, contact the customer support center.

p_f_dbh_hba_mmap_copy
-100
The process for acquiring HiRDB database environment information file from the running system failed. Refer to the message output to the running system, eliminate the cause of the error, and then restart the standby HiRDB. If no message was output, contact the customer support center.

-110
-120
The rcp command from the running system failed, a time-out occurred in the running HiRDB, or startup of the running system failed. Refer to the message output to the running system, eliminate the cause of the error, and then restart the standby HiRDB. If no message was output, contact the customer support center.

-140
The rsh command to the running system failed. Set up the environment to enable execution of a remote shell, and then restart the standby HiRDB.

Other than the above
Refer to the message output to the running system, eliminate the cause of the error, and then restart the standby HiRDB. If no message was output, contact the customer support center.

p_f_dbh_dint_rblk_set
-160

While the rapid system switchover facility was being used, the running HiRDB executed the database structure modification utility, but the standby HiRDB did not restart. Therefore, system switching failed. Restart the standby HiRDB.

While the standby less switchover facility was being used, the database structure modification utility was executed, but after the standby status of the alternate portion was cancelled, it did not return to standby status. Or, the database structure modification utility was executed during alternating, but the normal BES unit did not restart. Therefore, system switching failed. Normally terminate, and then restart HiRDB/Parallel Server.

-161

While the rapid system switchover facility was being used, the master directory RDAREA was updated, and then the dictionary server was independently normally terminated and restarted. However, system switchover failed because the standby HiRDB did not restart.

While the rapid system switchover facility was being used, the master dictionary RDAREA was updated, and then the dictionary server was independently normally terminated and restarted. However, after the standby status of the alternate portion was cancelled, it did not return to standby status. Or, the master directory RDAREA was updated during alternating, and then the dictionary server was independently normally terminated and restarted. However, system switchover failed because the normal BES unit did not restart. Normally terminate, and then restart HiRDB/Parallel Server.

-162

While the rapid system switchover facility was being used, HiRDB system definition was modified, and then the running system server was independently normally terminated and restarted. However, system switchover failed because the standby HiRDB did not restart. Restart the standby HiRDB.

While the rapid system switchover facility was being used, HiRDB system definition was modified, and then the normal BES unit was independently normally terminated and restarted. However, after the standby status of the alternate portion was cancelled, it did not return to standby status. Or, HiRDB system definition was updated during alternating, and then the alternate BES unit was independently normally terminated and restarted. However, system switchover failed because the normal BES unit did not restart. Normally terminate, and then restart HiRDB/Parallel Server.

Other than the above
Refer to the message output before this message was output, eliminate the cause of the error, and then restart HiRDB. If no message was output, contact the customer support center.

pdi_omm_mget
-143
-147
(1) From the following server definitions, increase the value of the appropriate server specification.

pd_sds_shmpool_size (single server definition)

pd_bes_shmpool_size (back-end server definition)

pd_dic_shmpool_size (dictionary server definition)

(2) If the above definitions are omitted, specify the following system common definition values:

pd_assurance_table_no operand
At least 102 + the number of tables using the free space reusage facility#

pd_assurance_index_no operand
Single server:
(130 + number of defined indexes#) 1.2 or more
Parallel server:
(number of defined indexes#) 1.2 or more

#: For details about the number of tables and the number of defined indexes, see the manual HiRDB Version 9 System Definition.
(3) If the error occurred at the startup of a user server (executed by specifying the -s option with the pdstart command) that is not a back-end server using the standby-less system switchover (effects distributed) facility, and the unit terminated abnormally, specify server in the pd_shmpool_control operand in the system common definition, and then restart the unit.

Other than the above
Refer to the message output before this message was output, eliminate the cause of the error, and then restart the server. If no message was output, contact the customer support center.

pdi_omm_getseg
-147
If the error occurred at the startup of a user server (executed by specifying the -s option with the pdstart command) that is not a back-end server using the standby-less system switchover (effects distributed) facility, and the unit terminated abnormally, specify server in the pd_shmpool_control operand in the system common definition, and then restart the unit.

Other than the above
Refer to the message output before this message was output, eliminate the cause of the error, and then restart the server. If no message was output, contact the customer support center.

Other than the above
--
Refer to the message output before this message was output, eliminate the cause of the error, and then restart the server. If no message was output, contact the customer support center.

Legend:

--: Not applicable

KFPH20004-E L

Server aa....aa termination failed, function=bb....bb, return code=cccc

When server aa....aa was terminated, bb....bb resulted in error cccc.

aa....aa: Server name

bb....bb: Function resulting in the error

cccc: Return code

S: Terminates server termination processing.

O: Contact the HiRDB administrator.

Action

Refer to the message that was output before this message to eliminate the cause of the error, then restart the server. If no message was output before this message, contact the customer support center.

KFPH20005-E L

Failed to aa....aa 1st file in MASTER DIRECTORY, return code=bbbb

Processing aa....aa on the first HiRDB file in the master directory RDAREA failed.

aa....aa: Processing:

close: Close processing for the first file in the master directory RDAREA

open: Open processing for the first file in the master directory RDAREA

read: Loading from the first file in the master directory RDAREA

bbbb: Return code

S: Cancels HiRDB startup processing and terminates abnormally.

O: Contact the HiRDB administrator.

Action

See 5.1 Error codes returned from HiRDB file system access requests, eliminate the cause of the error, and then re-execute HiRDB.

KFPH20006-W L

Unable to use work HiRDB file system area, return code=bbbbb, HiRDB file system area name=aa....aa

HiRDB file system area aa....aa specified as a work table file cannot be used.

aa....aa: Name of HiRDB file system area

If the name of HiRDB file system area exceeds 117 characters, the last 117 characters of HiRDB file system area name are output.

bbbbb: Return code

S: Resumes processing.

O: Contact the HiRDB administrator.

Action

During execution of database initialization utility:

If the database initialization utility terminated normally, see 5.1 Error codes returned from HiRDB file system access requests, eliminate the cause of the error, and then re-execute the database initialization utility.

During server startup:

See 5.1 Error codes returned from HiRDB file system access requests, eliminate the cause of the error, and then restart the server if necessary.

KFPH20007-W L

Work HiRDB file system area not specified expansion, HiRDB file system area name = aa....aa

Secondary allocation has not been specified for HiRDB file system area aa....aa, specified as a work table file.

aa....aa: Name of HiRDB file system area

If the name of HiRDB file system area exceeds 117 characters, the last 117 characters of HiRDB file system area name are output.

S: Resumes processing.

O: Contact the HiRDB administrator.

Action

During execution of database initialization utility:

If the KFPA11959-E message is output during execution of the database initialization utility, specify a HiRDB file system area for which a secondary allocation is specified, then re-execute the database initialization utility.

During server startup:

Specify a HiRDB file system area for which a secondary allocation is specified, then restart the server if necessary.

KFPH20008-W L

No work HiRDB file system area

There is no HiRDB system file area available for a work table file.

S: Resumes processing.

O: Contact the HiRDB administrator.

Action

During execution of database initialization utility:

If the pdwork operand was not specified in the dictionary server definition or single server definition and the database initialization utility does not terminate normally, specify a HiRDB file system area and re-execute the database initialization utility.

If the pdwork operand is specified in the dictionary server definition or single server definition and the database initialization utility does not terminate normally, refer to the KFPH20006-W message that was output before this message to eliminate the cause of the error, then re-execute the database initialization utility.

During server startup:

If the pdwork operand was not specified in the server definition, specify HiRDB file system area if necessary, then restart the server.

If the pdwork operand is specified in the server definition, refer to the KFPH20006-W message that was output before this message to eliminate the cause of the error, then restart the server if necessary.

KFPH20009-W L

Duplicate work HiRDB file system area aa....aa

HiRDB file system area specified as a work table file has already been specified.

aa....aa: Name of the duplicate HiRDB file system area

If the name of HiRDB file system area exceeds 117 characters, the last 117 characters of HiRDB file system area name are output.

S: Ignores the name of HiRDB file system area that was specified more than once and resumes processing.

O: Contact the HiRDB administrator.

Action

During execution of database initialization utility:

If the database initialization utility does not terminate normally, correct the name of HiRDB file system area for storing the work table in the pdwork operand of the dictionary server definition or single server definition so that it is not duplicated, then restart the database initialization utility.

During server startup:

Correct the name of HiRDB file system area for storing the work table in the pdwork operand of the server definition so that it is not duplicated, then restart the server.

KFPH20010-W L

Number of work HiRDB file system area exceeds 16

The number of HiRDB file system areas specified for work table files exceeds the maximum (16).

S: Ignores all but the first 16 HiRDB file system area names and resumes processing.

O: Contact the HiRDB administrator.

Action

During execution of database initialization utility:

If the database initialization utility does not terminate normally, correct the number of HiRDB file system area names for storing work tables in the pdwork operand of the dictionary server definition or single server definition to 16 or less, then re-execute the database initialization utility.

During server startup:

Correct the number of HiRDB file system area names for storing work tables in the pdwork operand of the server definition to 16 or less, then restart the server.

KFPH20011-E L

Incompatible character code set for database, character code set=aa....aa, database initialize character code set=bb....bb

Character codes type aa....aa of the started file does not match character codes type bb....bb of the initialized HiRDB.

aa....aa: Character codes type of the started HiRDB:

bb....bb: Character codes type of the initialized HiRDB

CHINESE: EUC Chinese kanji codes

LANG-C: One-byte character codes

SJIS: Shift JIS codes

UJIS: EUC Japanese kanji code

UTF-8: Unicode

CHINESE-GB18030: Chinese character encoding GB18030

*******: Invalid character code

S: Terminates processing.

Action

In UNIX, this message may be output if $PDDIR/lib is not assigned in addition to the environment variable SHLIB_PATH (in Solaris or Linux, LD_LIBRARY_PATH; in AIX, LIBPATH). Revise the environment variable, and restart HiRDB.

For character codes type aa....aa:

Execute the Database Load Utility to regenerate the database.

For character codes type bb....bb:

In UNIX, use the pdsetup -d command to delete the HiRDB system under the HiRDB directory from the OS, and then re-execute the pdsetup -c command. For details about the pdsetup command, see the manual HiRDB Version 9 Command Reference. In Windows, execute the pdntenv -c command. For details about the pdntenv command, see the manual HiRDB Version 9 Command Reference.

If the activated HiRDB character code type aa....aa is *******:

An internal conflict was detected. Contact the customer support center.

If the character code type bb....bb is *******:

Either the database is invalid or the master directory RDAREA is corrupted. Either re-create the database by executing the database initialization utility or, if the master directory RDAREA is corrupted, recover it by using the database recovery utility.

KFPH20012-E L

Incompatible HiRDB version for database, HiRDB version=aaaaa, database version=bb....bb

HiRDB indicated version is invalid.

The version of HiRDB system that created the database is newer than the version of HiRDB system being used. Therefore, the database cannot be accessed.

The database cannot be transferred from the version of HiRDB that created it to the version of HiRDB that is being used.

aaaaa: Version of HiRDB that was activated

bb....bb: Internal information that shows the database version

S:

Single-unit configuration using HiRDB/Single Server or HiRDB/Parallel Server:

Terminates abnormally with an abort code PsadsA8.

Multiple-unit configuration using HiRDB/Parallel Server:

The unit containing the dictionary server terminates abnormally with an abort code PsadsA8. Other units also are forced to terminate.

Action

Take one of the following actions:

To make the database version equal to aa....aa, use the pdstart -i command to activate HiRDB system. After a KFPS05201-Q message is output, execute the Database Initialization Utility (pdinit).

To use the database in version bb....bb of HiRDB, restore the old version of HiRDB (for details, see HiRDB Version 9 Installation and Design Guide).

KFPH20013-E L

Incompatible database format with HiRDB, database data model=64-bit, HiRDB data model=32-bit

A database created by a 64-bit-mode HiRDB cannot be accessed by a 32-bit-mode HiRDB.

You cannot migrate from a 64-bit-mode HiRDB to a 32-bit-mode HiRDB.

S: Terminates abnormally with abort code PsadsA8.

Action

Set HiRDB to the 64-bit mode. For the migration method, see HiRDB Version 9 Installation and Design Guide.

KFPH20015-I L

Copying HiRDB database environment information files necessary for server aa....aa initialization from online unit

HiRDB database environment information files necessary for server aa....aa initialization are being acquired from the executing unit.

aa....aa: Server name

S: Continues processing

KFPH20016-E L

Overflow Error occurred by size calculation of memory, server aa....aa

An overflow occurred during the calculation of memory size.

aa....aa: Server name (or ****** if the server name is unknown)

S: Terminates abnormally.

Action

aa....aa is ******:

Revise the system definition so that the result of the I/O server algorithm for the shared memory algorithm used by the unit controller is less than 2³¹ - 1 for the 32-bit mode, or less than 2⁶³ - 1 for the 64-bit mode. For I/O server algorithms, see Shared memory algorithm used by unit controller in HiRDB memory requirements in the manual HiRDB Version 9 Installation and Design Guide.

aa....aa is a server name:

Revise the system definition so that the result of the respective algorithm below is less than 2³¹ - 1 for the 32-bit mode, or less than 2⁶³ - 1 for the 64-bit mode:

HiRDB/Single Server: Shared memory algorithm used by a single server

HiRDB/Parallel Server: Shared memory algorithm used by the server on which the error occurred

For the respective algorithm, see the manual HiRDB Version 9 Installation and Design Guide.

KFPH21001-E L

Error occurred at aa....aa code=bbbb on cc....cc

When server cc....cc was started, error aa....aa with code bbbb occurred.

aa....aa: Error detail:

{ Process Communication |Get Work Area
|Define pd_rdarea_list_no_wrn_pnt
|Get Control Area(rerun ctrl)
|Call hbuf_ucbint| Call adm_complete
|Call p_f_pls_call_by_timing
|Get Environment| Get Control Area| Get Log Area
|Init. SQA | Init. DBH | Init. DIC | Call plugin(start process)
|Call plugin(terminate process) | Call adm_rerun_end }

bbbb: Error code (displays -1 when aa....aa is Define pd_rdarea_list_no_wrn_pnt)

cc....cc: Server name (if acquisition of the server failed, ******** is displayed)

S: Terminates server process activation processing.

O: Contact the HiRDB administrator.

Action

Process Communication displayed as aa....aa:

See 4.1 Detail codes for RPC-related errors in order to take appropriate action on the basis of the displayed code (bbbb).

aa....aa is Get Work Area or Get Log Area:

Increase the size of the process private area by one of the following methods, then re-execute:

Reduce the number of processes that execute concurrently.

Increase the swap size.

Increase the real memory.

aa....aa is Define pd_rdarea_list_no_wrn_pnt:

Reset the pd_rdarea_list_no_wrn_pnt operand in the system definition to a value within the permissible range and restart HiRDB.

Other:

Refer to the message that was output before this message to eliminate the cause of the error, then restart the server. If no message was output, contact the customer support center.

KFPH22001-E L

Invalid DIRECTORY data in RDAREA "aa....aa", reason code=b

A contradiction was detected in the RDAREA control information for RDAREA "aa....aa".

aa....aa: RDAREA name

b: Reason code

S: Terminates abnormally, shuts down the corresponding RDAREA, and invalidates the processing.

Action

Check the RDAREA for an operation error based on the reason code. If there is an operation error, recover the RDAREA, and then retry the processing. If there is no operation error and no corresponding cause, contact the customer support center.

Reason code
Cause
Action

1
2
3
4
9
There is a contradiction in a segment of the corresponding RDAREA or the page management information.
One of the following might have occurred:

The RDAREA was not recovered after an error shutdown (logless shutdown) when an abnormality was detected during execution of a UAP or utility in no-log mode.

The RDAREA was not recovered after an error shutdown (logless shutdown) when an abnormality was detected during execution of the UAP or utility when NO is specified in the RECOVERY option for a BLOB column.

The RDAREA was recovered to a backup state in which some of the HiRDB files that make up the RDAREA are different.

Recover the RDAREA.

To recover to the point when the database backup was made:

Recover the corresponding RDAREA using the backup.

To recover the RDAREA to it's initial state without using the backup:

Use the pdclose command to close the RDAREA to be recovered, and then the database structure modification utility (pdmod) to re-initialize the RDAREA. Next, use the pdrels -o command to release the shutdown and open the RDAREA, and then restore the initial data back into the table.

For details about operations in no-log mode and how to recover an RDAREA, see the HiRDB Version 9 System Operation Guide.

5
6
7
The corresponding RDAREA does not match the information in a system RDAREA (master directory RDAREA or dictionary RDAREA, for example).
Only some of the related RDAREAs might have been recovered using backups made before or after the database structure modification utility (pdmod) or definition SQL statement was executed.
Another possibility is that a related RDAREA might have been recovered from a backup made at a different time.
Use the backups to recover to the same point when a backup was made of the related RDAREAs.
For details about RDAREAs that need to be backed up at the same time, see the HiRDB Version 9 System Operation Guide.

Note

If Real Time SAN Replication with the log-only synchronous method is being used, refer to the HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide, take corrective action, and perform system log application processing.

KFPH22002-E L

Insufficient memory on PROCESS, size = aa....aa

A memory shortage occurred in the process private area.

aa....aa: Size (in bytes) of the area that was to be allocated

S: Terminates abnormally.

Action

Check the memory size estimate for an error, allocate adequate memory, and re-execute.

KFPH22003-E L

HiRDB file "aa....aa" failed, return code=bb....bb, RDAREA="cc....cc", file=dd....dd

"aa....aa" for HiRDB file dd....dd terminated with return code bb....bb.

aa....aa: HiRDB file system function:

{ open |close |lseek |read |write |fstat | creat | sttfs | sttdk }

bb....bb: Return code

cc....cc: RDAREA name:

*MASTER*: Master directory RDAREA

dd....dd: Name-of-HiRDB-file-system-area\Name-of-HiRDB-file

If the path name of HiRDB file exceeds 122 characters, the last 122 characters of HiRDB file path name are output.

S:

HiRDB file comprising the master directory RDAREA:

Cancels processing.

Other HiRDB file:

Shuts down the corresponding RDAREA and resumes processing.

Action

See 5.1 Error codes returned from HiRDB file system access requests, eliminate the cause of the error, and then re-execute. In the case of a master directory RDAREA error, start HiRDB with the pdstart -r command and recover the master directory RDAREA with the database recovery utility.

If Real Time SAN Replication with the log-only synchronous method is being used, it is possible that the database structure modification utility (pdmod) was executed on the transaction execution site. If that is the case, refer to the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide, take corrective action, and perform system log application processing.

KFPH22004-W L

aa....aa reserve Number bb....bb exceeds assurance Number cc....cc, server=dd....dd

The aa....aa reserve number bb....bb exceeds the value cc....cc specified in the operand. The server that generated it is dd....dd.

aa....aa: {Table | Index}

bb....bb: Reserve number of aa....aa

cc....cc: Specified value of pd_assurance_table_no operand or pd_assurance_index_no operand

dd....dd: Server name

S: Continues processing.

Action

After this message is output, if the server does not start due to a shared memory pool insufficiency, take the following action:

shmpool_size operand omitted:

Specify a value of bb....bb or higher in the pd_assurance_table_no operand or pd_assurance_index_no operand, and re-execute.

shmpool_size operand specified:

Increase the value assigned to the shmpool_size operand, and re-execute the UAP.

KFPH22005-E L

Number of aa....aa exceeds limit bb....bb, current=cc....cc, server=dd....dd

There are more entities (cc....cc) than the maximum (bb....bb) that was specified by the user in definition aa....aa. The name of the server is dd....dd.

aa....aa: Specified operand:

{ pd_max_rdarea_no |pd_max_file_no | pd_max_tmp_table_rdarea_no }

bb....bb: Maximum value specified in aa....aa

cc....cc: Number of entities

dd....dd: Server name

S: Cancels startup or recovery processing.

O: Contact the HiRDB administrator.

Action

If the number of existing RDAREAs exceeds the maximum, increase the value of the pd_max_rdarea_no operand in the system common definition and re-execute (when the value of the pd_max_rdarea_no operand is increased, the size of the status file must be reviewed).

If the number of existing RDAREA component files exceeds the maximum, increase the value of the pd_max_file_no operand in the system common definition, and then retry the operation.

If the number of existing temporary table RDAREAs exceeds the maximum, increase the value of the pd_max_tmp_table_rdarea_no operand in the system common definition, and then retry the operation.

KFPH22006-E L

UNIX file "aa....aa" failed, return code=bb....bb, file=cc....cc

"aa....aa" for internal work file cc....cc terminated with return code bb....bb.

aa....aa: HiRDB file system function:

{ open|close|lseek|read|write }

bb....bb: Return code

cc....cc: Name of the internal work file:

If the work file path name exceeds 131 characters, HiRDB directory name is changed to %PDDIR% for output.

S: Cancels processing.

Action

See 4.2 Detail codes for system-related errors to eliminate the cause of the error, and re-execute. If the cause of the error cannot be identified, contact the customer support center.

KFPH22007-E L

HiRDB System "aa....aa" failed, return code=bb....bb

Function "aa....aa" of the single server (HiRDB/Single Server) or system manager (HiRDB/Parallel Server) terminated with return code bb....bb.

aa....aa: HiRDB system facility

bb....bb: Return code

S: Cancels processing.

Action

See 4.2 Detail codes for system-related errors to eliminate the cause of the error, and re-execute. If the cause of the error cannot be identified, contact the customer support center.

KFPH22008-E L

SORT program error occurred, code=aa....aa

An error occurred during sorting.

aa....aa: Error code

S: Cancels processing.

O: Contact the HiRDB administrator.

Action

Take corrective action according to the error code:

Error code | Action
-202 | Memory shortage. Reduce the size of the work buffer specified in the sort operand.
-290 | Size of the work buffer is insufficient. Reduce the size of the work buffer specified in the sort operand.
-210 and -230 | An I/O error occurred. It is possible that the capacity of the sort work disk is insufficient. If there is a capacity shortage, specify a disk with large enough capacity in the sort operand, and execute the processing.

If the error cannot be resolved, acquire the sortdump, SORTIODUMP, and SORTDMP2 that are output to C:\Windows (in UNIX, /tmp or /usr/tmp), and contact the customer support center.

KFPH22009-E L

Unknown server name found in system, server=aa....aa, RDAREA="bb....bb"

Server name aa....aa was not found in the server definition. The invalid server name was found in RDAREA "bb....bb".

aa....aa: Server name

bb....bb: RDAREA name

S: Cancels processing

O: Contact the HiRDB administrator.

Action

Correct the server type with the pdstart -t command in the system common definition.

KFPH22010-E L

System call error occurred, func="aa....aa", errno=bb....bb

A system call error occurred.

aa....aa: System call name (**** is displayed if the system call cannot be identified)

bb....bb: Error code

S: If rerun or rollback was underway, resumes processing; otherwise, terminates abnormally.

Action

Refer to errno.h or the applicable OS manual to check the meaning of the error code, eliminate the cause of the error, then re-execute.

KFPH22011-E L

System call error occurred, func="system", cmd="aa....aa", code=bb....bb, inf="cc....cc"

A command executed by a system function resulted in an error.

aa....aa: Command name

bb....bb: Shell or command termination code

cc....cc: Command error output information

S: Terminates abnormally.

Action

Using the error output information and the shell or command termination code, refer to the OS documentation, resolve the error, and re-execute the command.

In Windows, if "****" is indicated in "cc....cc", resolve the error based on the contents of one of the following files, and re-execute the command:

%PDDIR%\spool\pdrshs1.log

%PDDIR%\spool\pdrshs2.log

KFPH22012-W L

Ignore number of aa....aa, assumed limit bb....bb, server=cc....cc

Operand aa....aa of HiRDB system definition was changed, but the previous specification value bb....bb has been assumed since HiRDB restarted. The target server is cc....cc.

aa....aa: Changed operand

{ pd_max_rdarea_no|pd_inner_replica_control }

bb....bb: Specification value before the operand was changed

cc....cc: HiRDB server name

S: Processing continues. The changed values of these operands take effect at the next HiRDB normal startup.

KFPH22013-E L

RPC "aa....aa" failed, return code=bb....bb, server=cc....cc

If cc....cc is ********, the RPC function aa....aa that was issued when the unit started terminated with error code bb....bb.
If cc....cc is something other than ********, the RPC function aa....aa that was issued from server cc....cc terminated with error code bb....bb.

aa....aa: RPC function

bb....bb: Error code

cc....cc: Server identifier

For an RPC error when the unit starts, ******** is displayed.

S: Terminates processing.

Action

If this message is displayed while a back-end server or unit is starting, and the dictionary server is not running, start the dictionary server, and then retry the operation. Otherwise, eliminate the cause of the error based on 4.1 Detail codes for RPC-related errors, and then retry the operation.

KFPH22014-E L

RDAREA "aa....aa" not found in dictionary server

RDAREA "aa....aa" that is required for the dictionary server cannot be found.

aa....aa: RDAREA name

*masterdirectory*: Master directory

*datadirectory*: Data directory

*datadictionary*: Data dictionary

S: Terminates abnormally.

Action

Specify the pdstart statement for defining the dictionary server in the system common definition so that it matches the correct configuration. If the RDAREA is damaged, recover the data and re-execute.

If Real Time SAN Replication with the log-only synchronous method is being used, refer to the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide, take corrective action, and perform system log application processing.

KFPH22015-E L

HiRDB file system area aa....aa not found, RDAREA="bb....bb"

HiRDB file system area aa....aa for RDAREA "bb....bb" cannot be found in the system.

aa....aa: Name of HiRDB file system area

If the path name of HiRDB file system area exceeds 117 characters, the last 117 characters of HiRDB file system area path name are output.

bb....bb: RDAREA name

S: Resumes processing.

Action

Create HiRDB file system area in which the error occurred in order to recover the RDAREA, then reopen the RDAREA.

If Real Time SAN Replication with the log-only synchronous method is being used, refer to the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide, take corrective action, and perform system log application processing.

KFPH22016-E L

MASTER DIRECTORY RDAREA was already used

The master directory is already being used by another HiRDB system.

S: Terminates abnormally.

O: Contact the HiRDB administrator.

Action

HiRDB systems that use the same name for the first HiRDB file in the master directory RDAREA of the system common definition cannot be started concurrently. Check the system common definition and restart.

KFPH22017-I L

Table should be reorganized, RDAREA="aa....aa", AUTHID=bb....bb, TABLE=cc....cc because disordered LOB DIRECTORY

Management information items in the LOB RDAREA are fragmented.

aa....aa: RDAREA name

bb....bb: Authorization identifier

cc....cc: Table identifier

S: Resumes processing.

Action

RDAREA is a user LOB RDAREA:

Because retrieval performance for the LOB data may deteriorate, reorganize the user LOB RDAREA whose name is displayed in the message.

RDAREA is a data dictionary LOB RDAREA:

Reorganize the dictionary table for the stored procedure and the stored function.

If affected RDAREA is a registry LOB RDAREA:

Reorganize the registry table.

KFPH22018-W L

Status file "aa....aa" failed, return code=bb....bb, server=cc....cc

"aa....aa" for the status file of server cc....cc terminated with return code bb....bb.

aa....aa: File access facility

{ alloc |dealloc |read |write }

bb....bb: Error code

cc....cc: Server identifier

S: Makes preliminary queries to the dictionary server about processing that uses the status file and resumes processing. Furthermore, because HiRDB queries the dictionary server, the performance of startup processing is less efficient than when the status file is used.

Action

Normalize the status file for future operation; see 4.2 Detail codes for system-related errors to eliminate the cause of the error.

If the cause cannot be located, contact the customer support center.

KFPH22019-I L

Information type=aa....aa, detail="bb....bb", code=cc....cc

An event of type aa....aa, detail "bb....bb", and return code cc....cc occurred.

aa....aa: Information type

bb....bb: Internal information

cc....cc: Internal code

S: Resumes processing because the error can be handled by the system.

KFPH22020-W L

Server aa....aa waiting until dictionary server start

Because the dictionary server is required for starting back-end server aa....aa, HiRDB system is waiting until the dictionary server is started.

aa....aa: Server identifier

S: Monitors the status of the dictionary server.

During dictionary server startup:

Resumes processing

When startup cannot be checked within the appropriate amount of time:

Resumes processing without checking dictionary server startup.

Action

Start the dictionary server or a unit that contains the dictionary server.

If a network error can be assumed, eliminate the cause of the error.

KFPH22021-W L

Number of index exceeds reserved number, current reserved number=aa....aa, server=bb....bb

The number of indexes defined has exceeded the reserved number. The currently reserved number of indexes is aa....aa, and this condition occurred at server bb....bb.

aa....aa: Currently reserved number of indexes

bb....bb: Server name

S: Resumes processing. Once this message is output, the following operational benefits might not be obtained, depending on the index:

Performance improvement realized by making index management information resident in memory

Acquisition of statistical information on indexes

Suppression of output of duplicated messages

Preferential allocation of unused pages in used segments after free pages have been released from indexes

Action

Take one of the following actions:

If a KFPH22004-W or KFPH22035-I message is output when the target server is activated, take corrective action based on the message.

If a KFPH22004-W or KFPH22035-I message is not output when the target server is activated, and if the three operational benefits shown in (S) are required, take the following action according to the specification given in the pd_sysdef_default_option operand, and then restart HiRDB:
If the pd_sysdef_default_option operand is omitted, or is set to recommendable:
Specify a value greater than aa....aa (the currently reserved number of indexes) in the pd_assurance_index_no operand of the system common definition.
Either v6compatible or v7compatible specified in the pd_sysdef_default_option operand:
If the number of indexes required between startup and termination of HiRDB is greater than 1.2 times the number of indexes available at HiRDB startup time, set the operand pd_assurance_index_no in the system common definition to the sum of the current number of indexes and the number of indexes to be defined before HiRDB is started normally next time. If aa....aa (the currently reserved number of indexes) already exceeds the value specified in the pd_assurance_index_no operand, the number of indexes reserved represents an automatically increased value; in this case, specify a value greater than aa....aa (the currently reserved number of indexes) in the pd_assurance_index_no operand.

KFPH22022-E L

RDAREA information build failed, reason code=Time out.

A timeout occurred while acquiring RDAREA information during the following:

Startup processing for a back-end server

Unit startup processing in an environment where the standby-less system switchover (effects distributed) facility is being applied

The logging of RDAREA information is taking time either because the dictionary server is not activated or the dictionary server has a high load.

S: Terminates abnormally.

Action

Take one of the following actions:

If the dictionary server is not activated, activate the dictionary server, and then activate this server or unit.

If the dictionary server has a high load, activate this server or unit after the load on the dictionary server has decreased.

KFPH22023-W L

Using resource for "aa....aa" reached bb....bb%, cc....cc

bb....bb% of "aa....aa" is now in use.

aa....aa: Resource type:

rdarea-list-no

Number of lists that can be created at a server

bb....bb: Warning value percentage

cc....cc: Additional information

This information is output in the following format:

number-of-lists-created-at-server / number-of-lists-that-can-be-created-at-server, server=server-name

S: Continues processing.

Action

Delete unneeded lists or add a list RDAREA.

KFPH22024-I L

Extension completed in RDAREA "aa....aa", FILE "bb....bb", ccccc(dd....dd) segments created

The size of HiRDB file "bb....bb" in RDAREA "aa....aa" has been increased by ccccc segments. The total number of segments is dd....dd.

aa....aa: RDAREA name

bb....bb: Name-of-HiRDB-file-system-area\Name-of-HiRDB-file

If the path name of HiRDB file exceeds 112 characters, the last 112 characters of HiRDB file path name are output.

ccccc: Number of added segments

dd....dd: Total number of segments

S: Continues processing.

KFPH22025-E L

Error occurred while Extension, RDAREA "aa....aa", FILE "bb....bb", reason code ccccc

An error occurred while automatically extending HiRBD file "bb....bb" in RDAREA "aa....aa". The reason code is ccccc.

aa....aa: RDAREA name

bb....bb: Name-of-HiRDB-file-system-area\Name-of-HiRDB-file

If the path name of HiRDB file exceeds 121 characters, the last 121 characters of HiRDB file path name are output.

ccccc: Reason code

S: Continues processing.

Action

Take one of the following corrective actions:

Reason code -1544:

Take one of the following actions depending on the contents of the KFPO00107-E message that was output immediately before this message:

If errno is 27 (EFBIG) or 28 (ENOSPC):
The disk that contains the HiRDB file system area used by the RDAREA is full. Eliminate the cause of the error based on the actions indicated in -1535 in 5.1 Error codes returned from HiRDB file system access requests and the actions corresponding to the errno in message KFPO00107-E.

Other than above:
See 5.1 Error codes returned from HiRDB file system access requests and eliminate the cause of the error.

Reason code 303:

If the database recovery utility was executed, execute it again.

If the database recovery utility was not executed, continue the transaction without change.

If the KFPH22025-E message is output repeatedly, contact the customer support center.

Reason code other than above:

See 5.1 Error codes returned from HiRDB file system access requests and eliminate the cause of the error.

KFPH22026-E L

Auto extend function suppressed, RDAREA "aa....aa", FILE "bb....bb", reason code ccccc

The automatic extension function for HiRDB file "bb....bb" in RDAREA "aa....aa" was suppressed. The reason code is ccccc.

aa....aa: RDAREA name

bb....bb: Name-of-HiRDB-file-system-area\Name-of-HiRDB-file

If the path name of HiRDB file exceeds 119 characters, the last 119 characters of HiRDB file path name are output.

ccccc: Reason code

S: The automatic extension function for the applicable RDAREA is suppressed until one of the following triggers:

HiRDB activation

Execution of a command to release RDAREA shutdown

Execution of a command to open the RDAREA

Execution of the database structure modification utility for reinitialization or extension of the RDAREA

Action

Correct the error by referring to the error code and release suppression of the RDAREA automatic extension function.

Reason code
Action

-1556
Take one of the following actions:

Combine the extents of the HiRDB file system areas containing the HiRDB file in question.

Use the database structure modification utility to expand the RDAREA.
If Real Time SAN Replication with the log-only synchronous method is being used, also perform system log application processing.

-1544
Take one of the following actions depending on the contents of the KFPO00107-E that was output immediately before this message:

If errno is 27 (EFBIG) or 28 (ENOSPC):
The disk that contains the HiRDB file system area used by the RDAREA is full. Eliminate the cause of the error based on the actions indicated in -1535 in 5.1 Error codes returned from HiRDB file system access requests and the actions corresponding to the errno in message KFPO00107-E.

Other than above:
See 5.1 Error codes returned from HiRDB file system access requests and eliminate the cause of the error.

1
Execute the pdrels command on the RDAREA.

303
If the database recovery utility was executed, execute it again.
If the database recovery utility was not executed, reset the suppression state of the RDAREA automatic extension facility, and continue the transaction without change.
If the KFPH22026-E message is output repeatedly, contact the customer support center.

Other
Refer to 5.1 Error codes returned from HiRDB file system access requests to resolve the error.

KFPH22027-E L

Number of aa....aa exceeds limit bb....bb,current=cc....cc,server=dd....dd

The number of inner replica groups exceeds value bb....bb specified by operand aa....aa in the system definition. The number of inner replica groups is cc....cc, and the source HiRDB server is dd....dd.

aa....aa: Name of operand in HiRDB system definition

pd_inner_replica_control

bb....bb: Value of operand aa....aa

cc....cc: Number of current inner replica groups

dd....dd: HiRDB server name

S: Stops HiRDB startup process.

O: Contact the HiRDB administrator.

Action

Specify a value greater than or equal to the current number of inner replica groups in the d_inner_replica_control operand.

If Real Time SAN Replication with the log-only synchronous method is being used, start HiRDB after taking all of the following actions:

Reset the definition provided in Designing system definitions in the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide and in the pd_inner_replica_control operand to the definition information previously used by the system, and then start HiRDB.

Delete all the replica RDAREAs defined in HiRDB, and then stop HiRDB normally.

For details about using Real Time SAN Replication with the log-only synchronous method, refer to the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide.

KFPH22028-E L

Staticizer Option required

HiRDB Staticizer Option is required to use the inner replica facility.

S: Terminates processing.

Action

Install HiRDB Staticizer Option to use the inner replica facility.

KFPH22029-E L

RDAREA aa....aa last file freezed, file=bb....bb fileNO=cc

An automatic extension of the RDAREA could not be specified because the final HiRDB file bb....bb in RDAREA aa....aa, file number cc....cc is in frozen update status.

aa....aa: RDAREA name

bb....bb: Name-of-HiRDB-file-system-area\Name-of-HiRDB-file

If the path name of HiRDB file exceeds 131 characters, the last 131 characters of HiRDB file path name are output.

cc: HiRDB file number

S: Terminates processing.

Action

Extend the RDAREA to increase capacity.

If Real Time SAN Replication with the log-only synchronous method is being used, also perform system log application processing.

KFPH22030-W L

Number of table exceeds reserved number,current reserved number=aa....aa,server=bb....bb,RDAREA="cc....cc",AUTHID="dd....dd",TABLE="ee....ee"

The number of defined tables exceeded the number of reserved tables while processing table "ee....ee" with authorization identifier "dd....dd" for RDAREA "cc....cc" on server bb....bb.
After this error message is output, the free space reusage facility may not be effective on some tables.

aa....aa: Current number of reserved tables

bb....bb: Server name

cc....cc: RDAREA name

dd....dd: Authorization identifier

ee....ee: Table name

S: Continues processing.

Action

Take one of the following actions:

Specify SEGMENT REUSE NO in the ALTER TABLE statement to stop the reuse of free space for tables in the free space reusage facility table that do not require the reuse of free space.

If a KFPH22004-W or KFPH22035-I message is output when the target server is activated, take corrective action based on the message.

If a KFPH22004-W or KFPH22035-I message is not output when the target server is activated, terminate HiRDB, change the value specified in the pd_assurance_table_no operand to a value greater than aa....aa (the currently reserved number of tables), and then restart HiRDB.

KFPH22031-W L

No reuse area,RDAREA="aa....aa",AUTHID="bb....bb",TABLE="cc....cc"

The user executed the free space reusage facility in table "cc....cc" using authorization identifier "bb....bb" in RDAREA "aa....aa", but no free space was found.

aa....aa: RDAREA name

bb....bb: Authorization identifier

cc....cc: Table name

S: Continues processing.

P: Take one of the following actions:

Execute the DELETE command to create free space.

Redefine the segment count by specifying SEGMENT REUSE in the ALTER TABLE statement.

Stop reuse of free space by specifying SEGMENT REUSE NO in the ALTER TABLE statement.

KFPH22032-W L

Processing of SQL skipped,tableID=aa....aa,generation number=bb,server=cc....cc

Definition update processing was skipped because all RDAREAs to be processed in generation number bb, server cc....cc are command held and are in closed status.
For the held RDAREAs indicated by the generation number, the definition information in the RDAREAs has not changed. Therefore, if the database entities are separated from the original RDAREA (not in a paired status with the original), they will not match the data dictionary table and index definition information. If you release the shutdown and use the replica RDAREA in this state, an SQL error will result, or the RDAREA will shut down.

aa....aa: Number of the target table for definition SQL, or the number of the table with a defined target index in definition SQL

Asterisks (********) indicate a table definition (CREATE TABLE).

bb: Generation number

cc....cc: Server name

S: Continues processing.

Action

If the definition SQL terminates normally and this message is output, and if the entities in the replica RDAREA in which processing was skipped are separated from the original RDAREA, recreate the entities in the replica RDAREA before releasing the shutdown, and make sure that the table definition and index definition match the status of the replica RDAREA. For details about the inner replica facility, see the HiRDB Version 9 Staticizer Option Description and User's Guide.

KFPH22033-E L

Not available without specification of aa....aa operand

If a shared RDAREA is used, specify Y for the aa....aa operand.

aa....aa: pd_shared_rdarea_use

S: Interrupts start processing.

O: Contact the HiRDB administrator.

Action

Specify Y in the system common definition pd_shared_rdarea_use operand, and re-execute.

KFPH22034-I L

Table status set to check pending status,tableID=aa....aa, RDAREA="bb....bb", constraint type=ccccccc

Table aa....aa stored in RDAREA "bb....bb" was placed in check pending status.

aa....aa: Table number of the table that was placed in check pending status

bb....bb: Name of the RDAREA storing the table that was placed in check pending status

ccccccc: Type of constraint defined in the table that was placed in check pending status

REF: Reference constraint

CHK: Check constraint

REF, CHK: Reference and check constraints

S: Continues processing.

KFPH22035-I L

aa....aa reserve Number bb....bb exceeds assurance Number cc....cc, server=dd....dd

bb....bb, which is the reserve number of aa....aa, exceeds the value cc....cc specified in the operand. The server generating this error is dd....dd.

aa....aa: {Table|Index}

bb....bb: Reserve number of aa....aa

cc....cc: Specification value in the pd_assurance_table_no or pd_assurance_index_no operand

dd....dd: Server name

S: Continues processing.

Action

If aa....aa is Table:

If the currently defined number of tables is less than or equal to the number of tables reserved, table management information can be made resident in memory; therefore, the free space reusage facility can be used.

If the currently defined number of tables is greater than the number of tables reserved, HiRDB can continue normal operations. However, in this case, the free space reusage facility cannot be used.

To use the free space reusage facility, increase the value specified for the pd_assurance_table_no operand in the system common definition to a value greater than bb....bb, and start HiRDB normally.

If aa....aa is Index:

If the currently defined number of indexes is less than or equal to the number of indexes reserved, index management information is made resident in memory; therefore, the following operational benefits can be expected:

Improved performance by making index management information resident in memory

Acquisition of index-related statistical information

Suppression of duplicate output of messages

Preferential allocation of unused pages in used segments after free pages have been released from indexes

If the currently defined number of indexes is greater than the number of indexes reserved, HiRDB can continue normal operations. However, in this case, the operational benefits listed above cannot be expected.

To use the free space reusage facility, increase the value specified for the pd_assurance_index_no operand in the system common definition to a value greater than bb....bb, and start HiRDB normally.

KFPH22036-E E+L

RDAREA held due to restart, RDAREA = "aa....aa"

Because the HiRDB server restarted during in-memory processing, an error-induced shutdown was performed on the RDAREA aa....aa, which was in DB asynchronous state.

aa....aa: RDAREA name

S: Continues processing.

Action

Refer to Troubleshooting in the manual HiRDB Version 9 Batch Job Accelerator, and recover the RDAREA.

KFPH22037-W L

File usage aaa%(bb....bb/cc....cc), RDAREA "dd....dd", FILE "ee....ee"

The HiRDB file ee....ee of the RDAREA dd....dd was allocated to an area of aaa% or higher of the maximum disk size to which automatic extension can expand the HiRDB file.

aaa: The proportion of the maximum disk size that expands by automatic extension and is used by the automatically-extending HiRDB file.

bb....bb: HiRDB file space that automatically extends (units: KB)

cc....cc: The maximum disk size to which the HiRDB file can automatically extend (units: KB)

dd....dd: RDAREA

ee....ee: HiRDB-file-system-area-name\HiRDB-file-name

If the path name of the HiRDB file exceeds 112 bytes, the last 112 bytes of the HiRDB file path name are output.

S: Continues processing.

Action

The HiRDB file can only automatically extend to a certain point. The limits to which HiRDB files can automatically extend are as follows:

Until the automatically extended space exceeds the free space of the HiRDB file system.

Until the automatically extended space exceeds the combined total free space on the disk and in the HiRDB file system.

Until the HiRDB file exceeds 64 GB

Before the maximum automatic extension of this HiRDB file is reached, do the following.

For a user RDAREA that is not a temporary table RDAREA:

Use the pddbls command (display the condition of the RDAREA), database condition analysis utility (pddbst), or pdfstatfs command (display the condition of the HiRDB file system area) to check the usage conditions of the target RDAREA or the HiRDB file system area, and then perform one of the following actions according to the usage conditions:

Reorganize the RDAREA

Expand the RDAREA

For a temporary table RDAREA:

Perform one of the following actions according to the situation:

Expand the RDAREA

Add an RDAREA

For the applicable procedure, see the HiRDB Version 9 System Operation Guide.

KFPH22038-W L

Extent Count = aa, RDAREA "bb....bb", FILE "cc......cc"

The number of extents of HiRDB file cc....cc of RDAREA bb....bb is equal to or greater than aa.

aa: The extent count of the HiRDB file that undergoes automatic extension.

{20|22|24}

bb....bb: RDAREA name

cc....cc: name-of-HiRDB-file-system-area\name-of-HiRDB-file

If the path name of the HiRDB file exceeds 112 bytes, the last 112 bytes of the HiRDB file path name are output.

S: Continues processing.

Action

Once the maximum number of extents for an HiRDB file (24) is reached, no further automatic extensions are possible. Before this HiRDB file reaches the maximum number of extents, do the following.

For a user RDAREA that is not a temporary table RDAREA:

Use the pddbls command (display the condition of the RDAREA) or database condition analysis utility (pddbst) to check the usage conditions of the RDAREA, and then take one of the following actions according to those usage conditions:

Reorganize the RDAREA

Consolidate the extents in the HiRDB file system area

Expand the RDAREA

For a temporary table RDAREA:

Take one of the following actions according to the situation:

Consolidate the extents in the HiRDB file system area

Expand the RDAREA

Add an RDAREA

For the applicable procedure, see the HiRDB Version 9 System Operation Guide.

KFPH22039-I L

RDAREA information build retry due to RPC error occurred, return code=aa....aa, bb....bb=cc....cc

Because an RPC error occurred when acquiring RDAREA information during back-end server or unit start processing, retry RDAREA information acquisition processing.

aa....aa: Error code

For details, see 4.1 Detail codes for RPC-related errors.

bb....bb: Processing target

server: Back-end server

unit: Unit

cc....cc: Back end server name or unit name

S: Continues processing.

KFPH23001-E L

No "pdbuffer" statements

The pdbuffer operand is missing in the system common definition.

S: Terminates abnormally.

Action

Add the pdbuffer operand to the system common definition.

KFPH23002-E L

Invalid "pdbuffer" statement due to aa....aa bb....bb

Invalid pdbuffer operand was detected.

aa....aa: Cause of error:

duplicate buffer pool name: Buffer pool name is duplicated.

duplicate RDAREA: RDAREA is duplicated.

invalid index name: Index name is invalid.

invalid RDAREA name: The RDAREA name is invalid.

bb....bb: RDAREA name, index name, or buffer pool name

S: Terminates abnormally.

Action

Revise the pdbuffer operand in the system common definition, and restart HiRDB.

KFPH23003-E L

Insufficient memory on PROCESS, size=aa....aa

A memory shortage occurred in the process private area during server startup.

aa....aa: Size (in bytes) of area that was to be allocated

S: Terminates abnormally.

Action

Re-evaluate the number of processes, etc., and restart HiRDB.

KFPH23004-E L

Insufficient memory on DYNAMIC_SHMPOOL for global buffer pool, size=aa....aa

There is not enough shared memory to use a global buffer pool.

aa....aa: Size (in bytes) of area that was to be allocated

S: Terminates abnormally.

Action

Refer to system call=shmget, errno=12, mnemonic=ENOMEM in 4.3 System call return codes to investigate and resolve the error, and take corrective action.

KFPH23005-E L

Failed to allocate global buffer pool, errno=aa

Allocation of global buffer failed.

aa: Error code:

4: Shared memory page fixing failed.

8: Internal HiRDB resource shortage occurred.

16: Number of shared memory segments exceeded the maximum.

20: Memory shortage occurred.

24: Shared memory segment size exceeded the maximum.

28: Number of global buffers exceeded the maximum.

32: Overflow occurred during calculation of shared memory size.

36: Number of shared memory identifiers exceeded the maximum.

S: Terminates abnormally.

Action

Take action based on the error code:

4: An attempt to page-fix shared memory segments failed.

Refer to the event log (in UNIX, syslogfile) of the server on which the error occurred, and take either of the following actions:

If KFPO00107-E "shmctl(ommfixed)" failed errno=1 is output:
See message KFPO00107-E and take the corrective actions described there.

If KFPO00107-E "shmctl(ommfixed)" failed errno=12 is output:
If shared memory segments do not need to be page-fixed, specify free in the pd_dbbuff_attribute operand, or omit specification of the operand.
If you want to page-fix the shared memory segments, take either of the following actions:
Increase the real memory.
Reduce the size of the shared memory by decreasing the number of global buffers or the number of buffer sectors defined in the server where the error occurred.

8: Take either of the following actions:

Other than Windows edition (32-bit mode):

HiRDB can manage up to 16 shared memory segments, but this maximum has been exceeded. Take one of the following actions:

Increase the value specified for the SHMMAX operand in the system common definition or unit control information definition.
In UNIX, use the OS's sam command to set the value of the shmmax parameter (kernel parameter) to a value greater than or equal to the specified value for the SHMMAX operand. After shmmax is modified, the operating system must be rebooted.

Reduce the number of shared memory segments to no more than 16 by decreasing the number of global buffers or buffer sectors defined in the server where the error occurred.

Windows edition (32-bit mode):

The number of shared memory segments that HiRDB can manage has exceeded the maximum value (the value specified in the pd_max_dbbuff_shm_no operand in the system definition). Set the values of the global buffer pool shared memory size, pd_max_dbbuff_shm_no operand, and SHMMAX operand such that the following formula is satisfied:

Global buffer pool shared memory size (in MB) <
value of pd_max_dbbuff_shm_no value of SHMMAX

16: Use the OS's sam command to increase the value of the operating system parameter (kernel parameter) shmseg. After shmseg is modified, the operating system must be rebooted.

20: Refer to system call=shmat, errno=12, mnemonic=ENOMEM in 4.3 System call return codes to investigate and resolve the error, and take corrective action. Note that no action is required if this message is output during termination processing of HiRDB, and processing terminates normally (message KFPS01850-I is output).

If this does not resolve the problem, it is possible that contiguous free space (memory) for allocating global buffer shared memory for processes was not allocated because the value specified in the SHMMAX operand in the system common definition (pdsys) is too large. Take either of the following actions:

Other than Windows edition (32-bit mode):

No.
Operand in the system common definition (pdsys) (abnormal termination status)
Action

pd_dbbuff_modify
pd_jp1_use

1
N, or not specified
--
Recover according to the following steps:

Reduce the value specified in the SHMMAX operand to be the minimum value that satisfies the formula below, and then allocate the global buffer by partitioning the current global buffer shared memory into segments.
(value specified in SHMMAX) 16 (global buffer pool shared memory size)

Use pdstart command to restart HiRDB.

2
Y
Y
Recover according to the following steps:

Set the pd_jp1_use operand to N, and then use the pdstart command to restart HiRDB. If you cannot restart, skip step 2 and proceed to step 3.

Use the pdstop command to terminate HiRDB normally.

Reduce the value specified in the SHMMAX operand to be the minimum value that satisfies the formula in No. 1.

Set the pd_jp1_use operand back to Y, and then use the pdstart command to start HiRDB normally.
Note that, because the pd_jp1_use operand is temporarily set to N, JP1 is not notified of HiRDB events that occur while responding to this error (steps 1 and 2). Therefore, make copies if necessary of the syslogfile or message log files to which HiRDB messages are output. If any of these events require corrective action, check the syslogfile or message log files and take the necessary action.

3
Y
N, or not specified
If this error occurred during normal startup of HiRDB, take the actions in No. 1. Otherwise, change the value specified in the SHMMAX operand, and then perform a forced startup of HiRDB. At that point, the database will need to be recovered. The procedure is as follows:

Reduce the value specified in the SHMMAX operand to the minimum value that satisfies the formula in No.1.

Unload the logs since the logs shown in the last synchronization point completion message (KFPS02183-I).

Use the pdstart -r command to start HiRDB.

Use the pdrstr command to recover the master directory RDAREA to the most recent synchronization point.

Use the pdstop command to terminate HiRDB normally.

Use the command pdstart dbdestroy to perform a forced startup of HiRDB.

Use the pdrstr command to recover the RDAREAs other than the master directory RDAREA to the most recent synchronization point.

Legend:--: Not applicable

Windows edition (32-bit mode):

No.
Operand in the system common definition (pdsys) (abnormal termination status)
Action

pd_dbbuff_modify
pd_jp1_use

1
N, or not specified
--
Recover according to the following steps:

Set a value in the SHMMAX operand that is smaller than the value at the time of abnormal termination, reduce the maximum partition size for the shared memory in a single global buffer.

Set the pd_max_dbbuff_shm_no operand to a value that is greater than or equal to global buffer pool shared memory size value of SHMMAX, and then increase the maximum number of shared memory segments.

Use pdstart command to restart HiRDB.

2
Y
Y
Recover according to the following steps:

Set the pd_jp1_use operand to N, and then use pdstart command to restart HiRDB. If you cannot restart, skip step 2 and proceed to step 3.

Use the pdstop command to terminate HiRDB normally.

Execute steps 1 and 2 in No. 1 above.

Set the pd_jp1_use operand back to Y, and then use the pdstart command to start HiRDB normally.
Note that, because the pd_jp1_use operand is temporarily set to N, JP1 is not notified of HiRDB events that occur while responding to this error (steps 1 and 2). Therefore, make copies if necessary of the syslogfile or message log files to which HiRDB messages are output. If any of these events require corrective action, check the syslogfile or message log files and take the necessary action.

3
Y
N, or not specified
If this error occurred during normal startup of HiRDB, take the actions in No. 1. Otherwise, change the value specified in the SHMMAX operand, and then perform a forced startup of HiRDB. At that point, the database will need to be recovered. The procedure is as follows:

Execute steps 1 and 2 in No. 1 above.

Unload the logs since the logs shown in the last synchronization point completion message (KFPS02183-I).

Use the pdstart -r command to start HiRDB.

Use the pdrstr command to recover the master directory RDAREA to the most recent synchronization point.

Use the pdstop command to terminate HiRDB normally.

Use the command pdstart dbdestroy to perform a forced startup of HiRDB.

Use the pdrstr command to recover the RDAREAs other than the master directory RDAREA to the most recent synchronization point.

Legend:--: Not applicable

24: Take either of the following actions:

In UNIX:
The management area size used by the global buffer shared memory exceeded 16 value of shmmax in the operating system parameters, or exceeded the value specified in the SHMMAX operand value in the system definition. This management area cannot be partitioned using the value of the SHMMAX operand. Therefore, calculate the value of shmmax or the value of the SHMMAX operand in the system definition using the formula below, and then change them to the largest value. The OS's sam command can be used to modify the specified shmmax value. After shmmax is modified, the operating system must be rebooted.

In Windows:
The management area size used by the global buffer shared memory exceeded the value specified in the SHMMAX operand value in the system definition. This management area cannot be partitioned using the value of the SHMMAX operand in the system definition. Therefore, calculate the value of the SHMMAX operand using the formula below, and then change it to the largest value. If this memory size did not exceed the specified SHMMAX operand value, the work file in the HiRDB installation directory might have been deleted while HiRDB was operating. In this case, restart the HiRDB service.

No. | HiRDB type | Value specified in pd_dbbuff_modify operand | Management area size used by the shared memory for one global buffer (MB)
1 | Single Server, or Parallel Server (non-effects distributed environment) | N | A p p 1,024 1,024
2 | Y | A p p 1,024 1,024 + B 1,024
3 | Parallel Server (effects distributed environment) | -- | C p p 1,024 1,024

A: Use the value calculated from Formula 1 in When the standby-less system switchover (effects distributed) facility is not used under Formula for size of shared memory used by global buffers in the HiRDB Version 9 Installation and Design Guide.

B: Use the value calculated from Formula 2 in When the standby-less system switchover (effects distributed) facility is not used under Formula for size of shared memory used by global buffers in the HiRDB Version 9 Installation and Design Guide. Use the following value for the value of a in formula 2:

a = A p p 1,024

C: Use the value calculated from the management region part in When the standby-less system switchover (effects distributed) facility is used under Formula for size of shared memory used by global buffers in the HiRDB Version 9 Installation and Design Guide.

p: In Windows, if fixed is specified in the pd_dbbuff_attribute operand in the system common definition or unit control information definition, use the Windows Large Page page size. Otherwise, use a value of 1.

28: The upper limit on the number of global buffers that can be defined on a server was exceeded. Reduce the number of global buffers defined on this server.

32: Take the following action:

In 32-bit mode:
Overflow occurred during calculation of the shared memory size; reduce the shared memory size to no more than 2³¹ - 1 bytes by decreasing the number of global buffers or the number of buffer sectors defined in the server where the error occurred.

In 64-bit mode:
Overflow occurred during calculation of the shared memory size; reduce the shared memory size to no more than 2⁶³ - 1 bytes by decreasing the number of global buffers or the number of buffer sectors defined in the server where the error occurred.

36: See system call=shmget, errno=28, mnemonic=ENOSPC in 4.3 System call return codes to investigate and resolve the error, and take corrective action.

KFPH23006-E L

Failed to allocate semaphore, errno=aa....aa

Allocation of a semaphore resource failed.

aa....aa: Error cause code:

4: The semaphore count per semaphore identifier exceeded the maximum value of the system.

8: The number of semaphores used by the entire system or the number of semaphore identifiers exceeded the maximum value of the system.

S: Terminates abnormally.

Action

Take the following action according to the error cause code:

4: Set the maximum semaphore count (in Solaris, seminfo_semmsl; in Linux, SEMMSL) per semaphore identifier in the operating system parameters to 64 or more.

8: Take one of the following actions:

Increase the maximum semaphore count in the system (in HP-UX, semmns; in Solaris, seminfo_semmns; and in Linux, SEMMNS).

Increase the maximum semaphore identifier count (in HP-UX, semmni; in Solaris, seminfo_semmni; in Linux, SEMMNI; and in Windows, PDUXPLSEMMAX).

Decrease the specified count of the pdbuffer operand.

Decrease the value of the pd_max_users operand.

KFPH23007-E L

File aa....aa bb....bb error

File access failed.

aa....aa: File name

The file name is displayed by the absolute path. If it exceeds 159 characters, the last 159 characters of the file path name are output.

bb....bb: File access function:

close: Close file

create: Create file

open: Open file

read: Read file

write: Write to file

S: Terminates abnormally.

Action

Take action appropriate to the KFPO00107-E message that was issued immediately before this message.

KFPH23008-W L

No file "pdbufenv"

The pdbufenv file that was created during single server (HiRDB/Single Server) or dictionary server (HiRDB/Parallel Server) startup was not found.

S: Resumes processing.

Action

The system creates the corresponding file according to the pdbuffer operand specification. Therefore, if the buffer structure is different from the previous session and the specification is made so that a buffer is not allocated to the RDAREA subject to recovery during restart, the corresponding RDAREA will be placed on shutdown status. In such a case, recover the RDAREA with the database recovery utility.

KFPH23009-E L

System call error func=aa....aa, errno=bb....bb

A system call error occurred.

aa....aa: Name of system call

bb....bb: Error number set in errno

S: Terminates abnormally.

Action

Check the meaning of the errno (external integer function indicating the error status), refer to errno.h or the applicable OS manual to eliminate the cause of the error, then restart HiRDB.

KFPH23010-E L

Insufficient memory on PROCESS for work I/O buffer, size=aa....aa

Buffer for batch I/O cannot be allocated due to a shortage in the process private area.

aa....aa: Size (in bytes) of area that was to be allocated

S: Terminates processing.

Action

Reduce the number of batch I/O pages and re-execute the database load utility or database reorganization utility.

KFPH23011-W L

Invalid SHMMAX statement due to aa....aa bb....bb

The SHMMAX operand is invalid in the system common definition or unit control information definition.

aa....aa: Cause of error:

out of range: Specified value is outside the permitted range.

no value: Specified value is not a numeric value.

bb....bb: Specified value (up to the first 30 characters)

S: Resumes processing assuming the default value of the SHMMAX operand as the maximum segment size for shared memory.

Action

If the sum of the sizes of global buffer pools in the server exceeds the default value of the SHMMAX operand, multiple shared memory segments are allocated, thereby reducing throughput. Correct the SHMMAX operand.

KFPH23012-E L

No necessary option for "pdbuffer" aa....aa

A required option is missing in the pdbuffer operand specification.

aa....aa: Name of required option

S: Terminates abnormally.

Action

Specify the required option and restart HiRDB.

KFPH23013-W L

Failed to allocate index buffer pool aa....aa due to DATA DICTIONARY search failed SQLCODE=bbbb

A global buffer pool dedicated to indexes cannot be allocated because dictionary retrieval failed.

aa....aa: Name of buffer pool

bbbb: SQL code

S: Resumes processing without creating a global buffer pool dedicated to indexes. If a buffer pool has been defined for index RDAREAs, uses that buffer pool. If there is no such buffer pool definition but a buffer pool has been defined for OTHER (pdbuffer -o specification), uses the defined buffer pool.

Action

If the global buffer pool dedicated to indexes is necessary, take action appropriate to the SQL message issued immediately before this message and restart HiRDB.

KFPH23014-W L

Failed to allocate index buffer pool aa....aa due to no index bb....bb

A global buffer pool dedicated to indexes cannot be allocated, because the index specified in the pdbuffer operand was not found.

aa....aa: Name of buffer pool

bb....bb: Name of index

S: Resumes processing without creating a global buffer pool dedicated to indexes. If a buffer pool has been defined for index RDAREAs, uses that buffer pool. If there is no such buffer pool definition but a buffer pool has been defined for OTHER (pdbuffer -o specification), uses the defined buffer pool.

Action

If the specified index has been deleted, delete the corresponding definition from the pdbuffer operand. If the specified index name is invalid, correct the pdbuffer operand specification and restart HiRDB.

KFPH23015-E L

System error, func "aa....aa", code=bbbbbb

A HiRDB function error occurred.

aa....aa: Function name

bbbbbb: Error code

S: Terminates abnormally.

Action

From the event log (in UNIX, syslogfile) or the message log file, determine if any messages were output before or after this message. If any other messages were output, take action according to those messages. If there are no other messages, find bbbbbb in 4.2 Detail codes for system-related errors, eliminate the cause of the error, and then restart HiRDB. If you cannot determine the cause of the error, contact the customer support center.

KFPH23016-E L

Invalid "pdbuffer" statement due to operand combination error, global buffer pool name=aa....aa

Contradictory operands were specified in the pdbuffer statement.

aa....aa: Name of buffer pool

S: Terminates abnormally.

Action

Mutually exclusive options (-r, -i, -o) were specified in a pdbuffer operand specified in the system common definition. Correct the specification so that the -r, -i, and -o options are specified in a different pdbuffer operand.

KFPH23017-W L

Invalid "pdbuffer" statement due to no RDAREA aa....aa

The RDAREA specified with the -r in the pdbuffer operand cannot be found in HiRDB system.

aa....aa: RDAREA name

S: Resumes processing.

Action

Correct the pdbuffer operand in the system common definition.

KFPH23018-W L

Failed to allocate global buffer pool aa....aa due to page size exceeds buffer size for RDAREA bb....bb

System could not allocate a global buffer pool, because the RDAREA page size was greater than the global buffer size.

aa....aa: Global buffer pool name

bb....bb: RDAREA name

S: Resumes processing without allocating a global buffer pool for this RDAREA.

O: To access this RDAREA, either increase the buffer size specified in the -l option of the pdbuffer statement in the system common definition or delete the -l option, then restart HiRDB.

KFPH23020-E L

Failed to allocate LOB buffer pool aa....aa due to invalid RDAREA type bb....bb

A LOB global buffer is not allocated to areas other than the LOB RDAREA.

aa....aa: Name of the global buffer pool

bb....bb: RDAREA name

S: Terminates abnormally.

Action

Specify the LOB RDAREA in the pdbuffer operand of the system common definition.

KFPH23021-E L

Unmatched global buffer definition(standby=aa....aa,current=bb....bb)

The global buffer definitions in the standby system and running system do not match. This error message is output when all of the following conditions are met:

The running global buffer definition was modified when the standby system was in standby status.

After independently stopping, and then restarting the running system, the running system was switched over to the standby system without restarting.

aa....aa: Maintenance information 1

bb....bb: Maintenance information 2

S: Abnormally terminates.

Action

Restart HiRDB.

KFPH23022-E L

Global buffer pool undefined in standby server,RDAREA="aa....aa" standby unit=bbbb standby server=cc....cc

No global buffers were defined in the RDAREA in the alternate BES.

aa....aa: RDAREA name

bbbb: Unit identifier of the alternate BES unit

cc....cc: Alternate BES name

S: Abnormally terminates.

Action

Allocate the global buffer that the alternate BES uses by specifying the -c option or -o option of the pdbuffer operand. Then, restart HiRDB.

KFPH23023-I L

Unit is down because pd_db_io_error_action=unitdown

When unitdown is specified in the pd_db_io_error_action operand, HiRDB (unit for HiRDB/Parallel Server) abnormally terminates because an RDAREA I/O error occurred.

S: Abnormally terminates.

Action

Eliminate the cause of the I/O error based on the error message KFPH22003-E, KFPH22007-E, or KFPH23100-E that was output before this message.

KFPH23024-I L

pd_db_io_error_action=unitdown is ineffective

When unitdown is specified in the pd_db_io_error_action operand, the error shutdown process is performed on the RDAREA because HiRDB (unit for HiRDB/Parallel Server) abnormally terminated and another I/O error was issued.

S: Continues processing.

KFPH23025-E L

Insufficient memory on PROCESS for work I/O buffer,size=aa....aa

No local buffers for random access could be secured due to insufficient process private area.

aa....aa: Area size attempted to be secured (in kilobytes).

S: Terminates processing.

Action

Reduce the number of buffer sectors for local buffers for random access, and then re-execute pdload or pdrorg.

KFPH23026-E L

Insufficient memory on PROCESS,size=aa....aa

There was insufficient process private area when creating the local buffer environment.

aa....aa: Area size attempted to be secured (in kilobytes).

S: Terminates processing.

Action

Re-evaluate the process count and other values, and then re-execute pdload or pdrorg.

KFPH23027-W L

Undefined global buffer pool with '-c' option,RDAREA="aa....aa"

A global buffer pool with the -c option specification has not been defined.

aa....aa: RDAREA name

S: The RDAREA is placed in closed status, and processing continues.

Action

RDAREAs of units for which the standby-less system switchover (effects distributed) facility applies must have a global buffer assigned with the -c option specified. Specify the -c option with the system common definition pdbuffer operand, and assign global buffers to unallocated RDAREAs.

KFPH23028-W L

Too small '-o' option global buffer size,added RDAREA="aa....aa",global buffer size=bbbbb,page size=ccccc

The buffer size bbbbb of the global buffer specified with the -o option is smaller than the page length ccccc of the added RDAREA "aa....aa".

aa....aa: RDAREA name

bbbbb: Buffer size of global buffer

ccccc: Page length of added RDAREA

S: Continues processing.

O: If the global buffer was assigned to RDAREA "aa....aa" specifying the -o option, use the pdstop command to perform a normal termination or a planned termination of HiRDB, restart HiRDB, and assign the global buffer. If the pdstop -u command is used to terminate the unit, which is then restarted and the global buffers assigned, the buffer size of the global buffers will be different from that of other units specified with the -o option, which may cause the RDAREA to shut down during system switchover.

KFPH23029-E E+L

Number of "pdbuffer" statements exceeds the limit

The number of pdbuffer system definitions exceeded the upper limit.

S: Terminates abnormally.

Action

The upper limit on the number of pdbuffer system definitions is 2,000,000 for HiRDB/Single Server, and 2,147,483,647 for HiRDB/Parallel Server. Reduce the number of pdbuffer system common definition, and restart HiRDB.

KFPH23030-I L

Dynamic update of global buffer information,(server=aa....aa, additional poolno=bb....bb, addtional shmno=cc....cc)

Displays information about the dynamic update of global buffers for each server.

aa....aa: Server identifier

bb....bb: Number of global buffer pools that can be added

cc....cc: Number of shared memory segments that can be added

S: Continues processing.

KFPH23031-E L

The definition related to global buffer pool is disagreement, last time=aa....aa this time=bb....bb, errno=cc

HiRDB could not be restarted after the following operations:

Deleting a global buffer using the pdbuffer operand

Reducing the value of the pd_max_add_dbbuff_no operand

Reducing the value of the pd_max_add_dbbuff_shm_no operand

aa....aa: Information about the previous operation

For each error code, server-specific information about the previous operation is displayed.

4: Sum of the number of global buffers and the number of global buffers that can be added dynamically

8: Sum of the number of index global buffers and the number of global buffers that can be added dynamically

16: Number of shared memory segments that can be added

bb....bb: Information about the current operation

For each error code, server-specific information about the current operation is displayed.

4: Sum of the number of global buffers and the number of global buffers that can be added dynamically

8: Sum of the number of index global buffers and the number of global buffers that can be added dynamically

16: Number of shared memory segments that can be added

cc: Error code

S: Terminates abnormally.

Action

Take action appropriate to the error code:

Error code | Action
4 | Either the pdbuffer operand was added or the value of the pd_max_add_dbbuff_no operand was reduced. Reset the pdbuffer and pd_max_add_dbbuff_no operands to their previous values, and then restart HiRDB.
8 | Either the pdbuffer -i operand was added or the value of the pd_max_add_dbbuff_no operand was reduced. Reset the pdbuffer-i and pd_max_add_dbbuff_no operands to their previous values, and then restart HiRDB.
16 | The value of the pd_max_add_dbbuff_shm_no operand was reduced. Restore the pd_max_add_dbbuff_shm_no operand to its previous value, and then restart HiRDB.

KFPH23032-E L

Overflow error occurred by size calculation of memory

An overflow occurred during memory size calculation.

S: Terminates abnormally.

Action

Take the following steps to ensure the memory size is less than or equal to 2³¹-1 (or 2⁶³-1 in 64-bit mode) bytes:

Reduce the number of global buffers specified in the system common definition

If in-memory data processing is being used, reduce the values of the operand pd_max_resident_rdarea_no (the number of in-memory RDAREAs) and the operand pd_max_resident_rdarea_shm_no (the number of shared memory segments used by in-memory data buffers)

KFPH23033-E L

Status file allocation failed due to exceed the allocate limit size, server=aa....aa, key=bbbb, size=cc....cc

The size of data to be stored in the status file exceeded 2,147,483,647 bytes; on server aa....aa, allocation of status file records failed.

aa....aa: Server identifier

bbbb: Maintenance information

cc....cc: Allocation data size

S: Terminates abnormally.

Action

Change the specified values so that the result of the following formula does not exceed 2,147,483,647:

(16 + (((A 8) 8)) 8) (B + C)

A: Value specified for the pd_max_rdarea_no operand of the system common definition

B: Number of index global buffers defined on the server

C: Value specified for the pd_max_add_dbbuff_no operand in the server definition

KFPH23034-E L

Unable to execute dynamic update of global buffer due to use rapid or standby less system switchover facility

The dynamic update of global buffer facility cannot be used because either the rapid system switchover facility or the standby-less system switchover facility is being used.

S: Terminates abnormally.

Action

Either omit the pd_dbbuff_modify operand from the system common definition or specify N, and restart HiRDB.

KFPH23035-I L

Update page cache limit available, server name=aa....aa, limit=bb....bb

The update buffer volume suppression facility was enabled.

aa....aa: Server name

bb....bb: Upper limit on the total number of update buffers on this server

S: Continues processing.

KFPH23036-I L

Update page cache limit unavailable, server name=aa....aa

The update buffer volume suppression facility was disabled.

aa....aa: Server name

S: Continues processing.

KFPH23037-I L

Changed update page cache limit, server name=aa....aa, limit=bb....bb

The upper limit on the total number of update buffers was changed.

aa....aa: Server name

bb....bb: Upper limit on the total number of update buffers on this server

S: Continues processing.

KFPH23038-E L

Number of commit write use pdreclaim exceeded "pd_max_commit_write_reclaim_no" server name=aa....aa

The number of pdreclaim commands executed simultaneously on the server using commit output exceeds the specification value in the pd_max_commit_write_reclaim_no operand.

aa....aa: Server name

S: Terminates the processing.

O: Re-execute the command after the free page release utility (pdreclaim) has terminated. Alternatively, execute the free page release utility (pdreclaim) without specifying the -p option.

Action

Increase the value assigned to the pd_max_commit_write_reclaim_no operand in the system common definition.

KFPH23040-I L

Unit is down because pd_db_access_error_action=unitdown

The unit shut down because a file access error was detected in the RDAREA while a facility that shuts down the unit when a file access error is detected was enabled. Another possibility is that a file access error with respect to the master directory RDAREA was detected, so the unit shuts down.

S: Terminates abnormally.

Action

Refer to one of the following messages, output immediately before this message: KFPH20005-E, KFPH22003-E, KFPH22007-E, or KFPH23100-E. Then, eliminate the cause of the file access error and restart HiRDB.

KFPH23041-I L

File for pd_db_access_error_action=unitdown "aa....aa" failed, return code=bb....bb

The is the internal file for the shutdown if the file access error facility fails to operate.

aa....aa: File operation contents

{create|delete}

bb....bb: Error codes

S: Continues processing.

KFPH23042-E L

Insufficient system resource for access tables,max access TRNGID=aa....aabb....bb TRNBID=aa....aacc....cc tables=dd....dd,current access TRNGID=ee....eeff....ff TRNBID=ee....eegg....gg tables=hh....hh

System resources required for accessing the table are insufficient.
On HiRDB/Parallel Server, only the number of system resources required to access the tables are prepared for each dictionary server and back-end server (system common definition pd_max_access_tables operand value pd_max_users operand value). Whenever a transaction accesses a table, the HiRDB allocates one system resource, and then it releases that system resource when the transaction finishes. Therefore, once a transaction has accessed a table of a value equal to or greater than the pd_max_access_tables operand, there might be a shortage of system resources when a subsquent transaction attempts to access a table.
TRNGID indicates the global identifier of a transaction, and TRNBID indicates the branch identifier of a transaction.

aa....aa: Unit identifier and system identifier of the HiRDB system of the transaction that accessed the most base tables at the time the error was detected

bb....bb: Global transaction number of the transaction that accessed the most base tables at the time the error was detected

cc....cc: Transaction branch number of the transaction that accessed the most base tables at the time the error was detected

dd....dd: Number of base tables accessed by the transaction that accessed the most base tables at the time the error was detected

ee....ee: Unit identifier and system identifier of the HiRDB system of the transaction in which the error was detected

ff....ff: Global transaction number of the transaction in which the error was detected

gg....gg: Transaction branch number of the transaction in which the error was detected

hh....hh: Number of base tables accessed by the transaction in which the error was detected

S: If the error is detected in a user process, the user process terminates abnormally. If the error is detected in a rollback process, the HiRDB system terminates abnormally.

Action

Check whether the dd....dd value in the SQL statement in the transaction indicated by aa....aa, bb....bb, and cc....cc is equal to or less than the largest number assumed for base table accesses. If the dd....dd value is less than the assumed maximum number of base table accesses, set the value of the pd_max_access_tables operand to at least the value of dd....dd or higher. If the dd....dd value is higher than the assumed maximum number of base table accesss, revise the SQL statement so that the dd....dd value is at or below this assumed maximum.

KFPH23045-W L

Unable to fix the shared memory in the real memory,shmid=aa....aa,size=bb....bb

The shared memory segment pages used by the global buffer pool failed to lock. Continue without locking pages.

aa....aa: Shared memory segment identifier

bb....bb: Size of shared memory segment (units: bytes)

S: Continues processing.

Action

If you do not need to page lock the shared memory, take the following actions:

Ignore this message.

If the shared memory is to be page-locked, perform one of the following actions:

Restart Windows. There are times when contiguous space is established in the real memory and page locking succeeds.

After stopping HiRDB, increase real memory and restart HiRDB.

Stop HiRDB, lower the global buffer pool count or the buffer sector count, decrease the size of the shared memory, and then restart HiRDB.

KFPH23046-E E+L

Invalid pd_max_dbbuff_shm_no statement due to aa....aa set value=bbb before value=ccc

HiRDB could not restart because the system definition was changed as follows:

If the pd_dbbuff_modify operand is set to N (do not dynamically update global buffers), the value of the pd_max_dbbuff_shm_no operand was reduced.

If the pd_dbbuff_modify operand is set to Y (dynamically update global buffers), the value of the pd_max_dbbuff_shm_no operand was changed.

aa....aa: Cause of error

low value: The current value is smaller than the value that was specified the last time HiRDB was started.

different value: The current value is different from the value that was specified the last time HiRDB was started.

bbb: Current value

ccc: Value that was specified the last time HiRDB was started

S: Terminates abnormally.

Action

Take the following action:

If the cause of error (aa....aa) is low value:
In the pd_max_dbbuff_shm_no operand, specify a value that is greater than or equal to the value that was specified the last time HiRDB was started, and then restart HiRDB.

If the cause of error (aa....aa) is different value:
Restore the value of the pd_max_dbbuff_shm_no operand to the value before the change, and then restart HiRDB.

KFPH23047-I L

Unit is down because pd_db_hold_action=unitdown

The unit was shut down due to detection of an RDAREA access error, which occurred because the unit shutdown facility was being used when a physical error was detected.

S: Terminates abnormally.

Action

Refer to the error messages output before this one, eliminate the cause of the error shutdown, and restart HiRDB. Error messages output before this one might include KFPH22003-E, KFPH22015-E, KFPH23100-E, and KFPH27007-E.

If it is not possible to eliminate the cause of the error shutdown, change the value of the pd_db_hold_action operand in the system common definition to dbhold, and then restart HiRDB. Because the RDAREA was shut down due to an error, recover the RDAREA if necessary.

KFPH23048-I L

Sum of memory for global buffer pool size=aa....aa, server=bb....bb

On server bb....bb, shared memory of size aa....aa was allocated as a global buffer.
If the standby-less system switchover (effects distributed) facility is used, this message is output per unit, not per server.

aa....aa: Size of shared memory allocated as global buffer (bytes)

bb....bb: For a server, the server name is output. For a unit, ******** is output.

S: Continues processing.

KFPH23049-W L

Sum of memory for global buffer pool too large, server=aa....aa

On server aa....aa, the shared memory allocated as a global buffer exceeded 1.2 GB. HiRDB might not start because the shared memory allocated as a global buffer is too large for the shared memory to be attached.
Note that if the standby-less system switchover (effects distributed) facility is used, this message is output per unit, not per server.

aa....aa: For a server, the server name is output. For a unit, ******** is output.

S: Continues processing.

Action

In Windows in 64-bit mode, and when HiRDB is running in 32-bit emulation mode

Ignore this message. If you want to suppress the output of this message, you can set the pd_shared_memory_report operand in the system definition to N, or use suppression of output messages to the event log (the pdmlgput operand in the system definition).

If this message is output when the HiRDB environment is being created

A list of explanations and actions is provided in the following table:

Explanation
Action

In 32-bit mode Windows, up to 2 GB of memory can be allocated per process. When a process is attached to the shared memory of the global buffer pool, it allocates a process memory area that is the size of the pool. Because it is using memory outside the global buffer pool, there might not be enough free memory when the pool size is greater than 1 GB.
Do not allocate more than 1 GB of shared memory per server as a global buffer pool.

Memory is allocated when a process loads a library, but when multiple libraries are loaded, fragmentation of the memory area can occur. As a result, even when there is enough free memory to attach the process to shared memory, a memory shortage error might occur if the required contiguous area cannot be allocated. This is more likely to occur when plug-ins are used or the system is linked to JP1.
Even when HiRDB starts successfully, depending on the amount of fragmentation of the memory area, memory shortage errors might cause an online unit to shut down, or prevent HiRDB from restarting, or leave HiRDB unable to start.
In the cases listed below, use the SHMMAX operand in the HiRDB system definition and the pd_max_dbbuff_shm_no operand to split the shared memory into smaller-sized segments. For details about these operands, see the manual HiRDB Version 9 System Definition.

A large shared memory is allocated as a global buffer pool.

Plug-ins are used.

The system is linked to JP1 (the pd_jp1_use operand is set to Y).

If this message is output when HiRDB is already running:

Perform the operational checks listed below and check for problems. Note that these operational checks must be repeated if you make changes to definitions that affect the size of the shared memory (including outside the global buffer pool), or start using JP1/Base or a new plug-in. The operational checks are as follows:

Because HiRDB might fail to start if problems occur during these operational checks, make backups and other preparations for recovery. If the pd_dbbuff_modify operand is set to Y, change the value to N temporarily, because when problems occur it will be necessary to perform a forced startup of HiRDB and recover the database.

While the transaction that is updating the database is executing, terminate HiRDB forcibly, restart, and then make sure that the rollback was successfully completed. In HiRDB/Parallel Server, all the back-end servers must be checked.

If HiRDB fails to restart as a result of check 2 above and message KFPH23005-E is output with error code 20, it is not able to operate with the current global buffer allocation. After restarting in accordance with the corrective actions in message KFPH23005-E, it will be necessary to review and, if necessary, revise the allocation of the global buffer.

If problems are discovered when you perform these operational checks, take one of the corrective actions listed below, and then repeat the operational checks.

Change the allocation of the global buffer to reduce the shared memory size.

Reduce the size of shared memory used by HiRDB outside of the global buffer.

Use the SHMMAX operand and the pd_max_dbbuff_shm_no operand to split the shared memory into smaller-sized segments.

KFPH23050-I L

Max of memory for global buffer pool management area size=aa....aa, server=bb....bb

On server bb....bb, the maximum management area size used by the global buffer shared memory is aa....aa.
If the standby-less system switchover (effects distributed) facility is used, this message is output per unit, not per server.

aa....aa: Maximum management area size used by the global buffer shared memory (bytes).

bb....bb: For a server, the server name is output. For a unit, ******** is output.

S: Continues processing

KFPH23051-W L

Maximum-shared-memory-segment-size for global buffer pool too large,server=aa....aa

On server aa....aa, the value specified in the SHMMAX operand exceeds 200 MB (50 MB if the global buffer dynamic update function is used (pd_dbbuff_modify=Y)). HiRDB might not be able to start because the maximum shared memory segment size (the value specified in the SHMMAX operand) is too large and the shared memory cannot be attached.
If the standby-less system switchover (effects distributed) facility is used, this message is output per-unit rather than per-server.

aa....aa: For a server, the server name is output. Forf a unit, ******** is output.

S: Continues processing

Action

In Windows in 64-bit mode, and when HiRDB is running in 32-bit emulation mode

Ignore this message. If you want to suppress the output of this message, you can set the pd_shared_memory_report operand in the system definition to N, or use suppression of output messages to the event log (the pdmlgput operand in the system definition).

If this message is output when the HiRDB environment is being created

Take the following actions:

Under normal conditions:
Omit specification of the SHMMAX operand (the assumed default value is 200) and the pd_max_dbbuff_shm_no operand (the assumed default value is 16).
However, if pd_dbbuff_modify = Y is specified, specify a value less than or equal to 50 in the SHMMAX operand. In the pd_max_dbbuff_shm_no operand, specify a value greater than the result of the following calculation:
amount of shared memory required for global buffer value of SHMMAX operand
To calculate the amount of shared memory required for the global buffer, see Formula for size of shared memory used by global buffers in the HiRDB Version 9 Installation and Design Guide, or check the KFPH23048-I message that was output during HiRDB startup.

If message KFPH23005-E (error code 24) is output when HiRDB starts:
Estimate the management area size used by the global buffer shared memory, and then specify the smallest possible value in the SHMMAX operand. To calculate the amount of shared memory required for the global buffer, see Formula for size of shared memory used by global buffers in the HiRDB Version 9 Installation and Design Guide, or check the KFPH23048-I message that was output during HiRDB startup.
If the management area size used by the global buffer shared memory is greater than 200 MB (50 MB if the global buffer dynamic update funtion is used), revise the value specified in the operand for the global buffer (the pdbuffer operand).
In addition, if the value of the SHMMAX operand changes, re-estimate the number of required resources (size of required shared memory) specified in the pd_max_dbbuff_shm_no operand and the value of the system environment variable PDUXPLSHMMAX.

If this message is output when HiRDB is already running

Take one of the actions indicated below:

Change the allocation of the global buffer to reduce the shared memory size.

Reduce the size of shared memory used by HiRDB outside of the global buffer.

Use the SHMMAX operand and the pd_max_dbbuff_shm_no operand to split the shared memory into smaller-sized segments.

After taking one of these actions, perform the operational checks listed below and check for problems. Note that the operational checks must be repeated if you make changes to definitions that affect the size of the shared memory (including outside the global buffer pool), or start using JP1/Base or a new plug-in. The operational checks are as follows:

Because HiRDB might fail to start if problems occur during these operational checks, make backups and other preparations for recovery. If the pd_dbbuff_modify operand is set to Y, change the value to N temporarily, because when problems occur it will be necessary to perform a forced startup of HiRDB and recover the database.

While the transaction that is updating the database is executing, terminate HiRDB forcibly, restart, and then make sure that the rollback was successfully completed. In HiRDB/Parallel Server, all the back-end servers must be checked.

If HiRDB fails to restart as a result of check 2 above and message KFPH23005-E is output with error code 20, it is not able to operate with the current global buffer allocation. After restarting in accordance with the corrective actions in message KFPH23005-E, it will be necessary to review and, if necessary, revise the allocation of the global buffer.

KFPH23100-E L

HiRDB file aa....aa error, errno=bb....bb, HiRDB file name=cc....cc

A HiRDB file access error occurred.

aa....aa: HiRDB file function:

close: Close HiRDB file

creat: Create HiRDB file

open: Open HiRDB file

read: Read HiRDB file

write: Write to HiRDB file

bb....bb: HiRDB system error code

cc....cc: Name-of-HiRDB-file-system-area\Name-of-HiRDB-file

If the path name of HiRDB file system area exceeds 131 characters, the last 131 characters of HiRDB file system area path name are output.

S: Terminates processing.

Action

Refer to 5.1 Error codes returned from HiRDB file system access requests and eliminate the cause of the error.

If the inner replica facility is used, and aa....aa is write, and bb....bb is -1544:

It is possible that a replica RDAREA is not in command shutdown or closed status and is paired with a volume. This phenomenon can occur when a system in this state executes any of the following:

Definition SQL (For details about definition SQL when using the inner replica facility, see the HiRDB Version 9 Staticizer Option Description and User's Guide)

Integrity check utility (pdconstck)

Update SQL for the relevant RDAREA (INSERT statement, UPDATE statement, DELETE statement, and PURGE TABLE statement)

Utilities for the relevant RDAREA (pdload, pdrorg, pdreclaim, and plug-in utilities)

If this phenomenon occurs, check the status of the volume.

If it is paired
Separate the pair volume, and then use the pdrels command to release the shutdown. If the relevant RDAREA is no longer going to be used, use the pdhold command to put it in command shutdown and closed status.

If it is not paired
If the RDAREA is shut down, recover it with the database recovery utility.

Other than above:

If the RDAREA is shut down, recover it with the database recovery utility.

KFPH23101-E L

DB destruction information, requst=(rdid=aa....aa, pgid=bb....bb, pgno=cc....cc, fno=dd....dd), buff=(pgid=ee....ee, pgno=ff....ff, fno=gg....gg)

Displays maintenance information when a buffer error was detected.

aa....aa: Requested RDAREA ID

bb....bb: Requested table number or index number

cc....cc: Requested page number

dd....dd: Requested file number

ee....ee: Table number or index number in buffer

ff....ff: Page number in buffer

gg....gg: File number in buffer

S: Terminates processing. At this time, the RDAREAs (excluding master directory RDAREAs) might shut down.

Action

Contact the customer support center. If any RDAREAs were shut down, use the database recovery utility to recover them.

If Real Time SAN Replication with the log-only synchronous method is being used and this message is output with respect to a master directory RDAREA at a log application site, it is possible that system log application processing was not performed, even though the database structure modification utility (pdmod) was executed at the transaction execution site. If that is the case, perform system log application processing.

KFPH23201-W L

HiRDB file open retry due to insufficient open resource, code=aaaaa

A resources shortage occurred when a HiRDB file was being opened.

aaaaa: HiRDB system error code

S: Continues processing.

Action

See 5.1 Error codes returned from HiRDB file system access requests and eliminate the cause of the error.

KFPH23202-W L

HiRDB DB read retry due to time stamp invalid, RDAREA name=aa....aa, file name=bb....bb, offset=cc....cc

Reading from the database will be retried because of an invalid page time stamp.

aa....aa: RDAREA name

bb....bb: HiRDB file name

If the name of HiRDB file exceeds 91 characters, the last 91 characters of HiRDB file name are output.

cc....cc: Relative byte position (in decimal) from the beginning of HiRDB file of the page where the invalid time stamp was detected

S: Continues processing.

O: If the RDAREA is shut down immediately after this message is output, contact the customer support center. Save the summary dump that is output under %PDDIR%\spool.

If the RDAREA is not shut down immediately after this message is output, a temporary disk I/O failure has occurred. Examine the disk that holds HiRDB file displayed in the message.

Action

Contact the customer support center. Save the simple dump that is output under %PDDIR%\spool.

KFPH23203-E L

Process wait count unmatch,server name=aa....aa wait buffer count=bb....bb wait process count=cc....cc

A process waiting counter conflict was detected during the default write process.

aa....aa: Server name

bb....bb: number of buffer resources that are being waiting upon

cc....cc: Number of processes waited on by the semaphore

S: Continues processing.

Action

See Facility for acquiring syncpoint output synchronization control information in the HiRDB Version 9 System Operation Guide.

KFPH23204-E L

Process wait count unmatch,process id=aa....aa flag count=bb....bb semaphore count=cc....cc

A process wait count conflict was detected.
For HiRDB/Single Server:
A process wait counter conflict was detected in the single server process.
For HiRDB/Parallel Server:
A process wait counter conflict was detected in the back-end server process or the dictionary server process.

aa....aa: Conflict detection process number

bb....bb: Flag change count

cc....cc: Semaphore operation count

S: Terminates abnormally (shuts down the unit).

Action

See Facility for acquiring syncpoint output synchronization control information in the HiRDB Version 9 System Operation Guide.

KFPH23205-E L

Number of resident RDAREA exceeds "pd_max_resident_rdarea_no", resident RDAREA no=aa....aa, request=bb....bb, server=cc....cc

The number of in-memory RDAREAs exceeded the value of the pd_max_resident_rdarea_no operand.

aa....aa: Number of RDAREAs already allocated in memory

bb....bb: Number of RDAREAs requested to be allocated in memory

cc....cc: Server identifier

S: Terminates processing.

Action

See Amount of memory required during in-memory data processing in the HiRDB Version 9 Installation and Design Guide, and check that no errors were made in the estimation of the required amount of memory.

KFPH23206-E L

Number of shared memory segment for resident RDAREA exceeds "pd_max_resident_rdarea_shm_no", allocate shm no=aa....aa, request=bb....bb, server=cc....cc

The number of shared memory segments for in-memory RDAREA exceeded the value of the pd_max_resident_rdarea_shm_no operand.

aa....aa: Number of shared memory segments that have already been allocated

bb....bb: Number of shared memory segments required for in-memory allocation

cc....cc: Server identifier

S: Terminates processing.

Action

See Amount of memory required during in-memory data processing in the HiRDB Version 9 Installation and Design Guide, and check that no errors were made in the estimation of the required amount of memory.

KFPH23207-E L

Unmatched RDAREA page size RDAREA="aa....aa",memory=bb....bb DB=cc....cc

An RDAREA page length mismatch occurred during in-memory processing.

aa....aa: RDAREA name

bb....bb: Page length of the RDAREA during in-memory allocation

cc....cc: Current RDAREA page length

S: Terminates processing.

Action

Recover the RDAREA from backup at the point when in-memory processing or synchronization was performed, and execute the pdmemdb -k reload command. For details about how to recover in-memory RDAREAs, see Troubleshooting in the manual HiRDB Version 9 Batch Job Accelerator.

KFPH23208-E L

Failed to allocate in-memory data buffer,server=aa....aa, size=bb....bb, reason=cc....cc

Allocation of the in-memory buffer failed.

aa....aa: Server identifier

If the server identifier is unknown, five asterisks (*) are output.

bb....bb: Size of the area that was to be allocated

If the error code is insufficient physical memory, five asterisks (*) are output.

cc....cc: Cause of the error:

page fixed failed: Shared memory page lock failed.

HiRDB segment over: The common memory segment count exceeded the maximum value for HiRDB.

process segment over: The number of shared memory segments that can be added in a process exceeded the maximum value for the OS.

insufficient virtual memory: There is insufficient memory for allocating the in-memory buffer.

insufficient physical memory: The work area is not sufficient for attaching shared memory.

shmmax over: The shared memory segment size exceeded the maximum value.

segment ID over: The number of shared memory identifiers exceeded the maximum value.

S: Terminates processing.

Action

Take one of the following actions according to the cause of the error.

If the cause of the error is page fixed failed:

Refer to the event log (in UNIX, syslogfile) of the server on which the error occurred, and then take one of the following actions:

If KFPO00107-E "shmctl(ommfixed)" failed errno=1 was output
Refer to message KFPO00107-E, take corrective action, and then re-execute the pdmemdb command.

If KFPO00107-E "shmctl(ommfixed)" failed errno=12 was output
If you do not need to page-lock the shared memory, either specify free in the -p operand of the pdmemdb command, or omit the -p option and then re-execute.
If the shared memory is to be page-locked, perform one of the following actions:
- Increase the real memory and then re-execute the pdmemdb command.
- Decrease the RDAREA specified in the pdmemdb command, and then re-execute the command.

If the cause of the error is HiRDB segment over:

The number of shared memory segments that can be used in HiRDB per server is the sum of 16 + pd_max_add_dbbuff_shm_no specification value + pd_max_resident_rdarea_shm_no specification value. Increase the value of the pd_max_resident_rdarea_shm_no operand, and then re-execute the pdmemdb command.

Also, in order to use the shared memory segments effectively, you should exercise caution when gathering together multiple RDAREAs to process in memory. For details about segment allocation, see the manual HiRDB Version 9 Batch Job Accelerator.

If the cause of the error is process segment over or shmmax over:

Revise the algorithm for the required amount of memory. For details about the amount of memory required during in-memory processing, see the HiRDB Version 9 Installation and Design Guide.

In UNIX, also revise the estimation of the OS operating system parameters. For details about estimating operating system parameters, see the HiRDB Version 9 Installation and Design Guide or the OS documentation.

Note that in order to use the shared memory segments effectively, you should exercise caution when gathering together multiple RDAREAs to add to the in-memory. For details about segment allocation, see the manual HiRDB Version 9 Batch Job Accelerator.

If the cause of the error is insufficient virtual memory:

Refer to system call = shmget, errno = 12, mnemonic = ENOMEM in 4.3 System call return codes and take corrective action.

If the cause of the error is insufficient physical memory:

Either decrease the required amount of shared memory by decreasing the number of in-memory RDAREAs, or expand the real memory.

If the cause of the error is segment ID over:

Refer to system call = shmget, errno = 28, and mnemonic = ENOSPC in 4.3 System call return codes, and take corrective action as appropriate.

KFPH23209-E L

Unmatched HiRDB file page number HiRDB file name="aa....aa",memory=bb....bb DB=cc....cc

A HiRDB page count mismatch occurred during in-memory processing.

aa....aa: HiRDB file name

If there are 162 or more characters in the HiRDB file path name, the last 161 characters are output.

bb....bb: Page count during in-memory allocation

cc....cc: Current page count.

S: Terminates processing.

Action

Recover the in-memory RDAREA from backup at the point when in-memory processing or synchronization was performed, and then execute the pdmemdb -k reload command. For details about how to recover in-memory RDAREAs, see Troubleshooting in the manual HiRDB Version 9 Batch Job Accelerator.

KFPH23210-E L

Unmatched HiRDB file number RDAREA="aa....aa",memory=bb....bb DB=cc....cc

A mismatch in the number of RDAREA configuration files occurred during in-memory processing.

aa....aa: RDAREA name

bb....bb: Number of RDAREA configuration files during in-memory allocation

cc....cc: Current number of RDAREA configuration files

S: Terminates processing.

Action

Recover the in-memory RDAREA from backup at the point when in-memory processing or synchronization was performed, and then execute the pdmemdb -k reload command. For details about how to recover in-memory RDAREAs, see Troubleshooting in the manual HiRDB Version 9 Batch Job Accelerator.

KFPH23212-I L

RDAREA "aa....aa" bb....bb end

bb....bb of RDAREA aa....aa was terminated.

aa....aa: RDAREA name

bb....bb: In-memory data processing state

MEMORY_LOAD: Data being is loaded from the RDAREA to the in-memory data buffer

DB_SYNC: Synchronization is being acquired between the RDAREA and in-memory data buffer

S: Continues processing.

KFPH23213-E L

Insufficient memory on PROCESS for in-memory data buffer,size=aa....aa

When the in-memory data buffer was allocated, there was a shortage of process-private memory.

aa....aa: Size of area that was to be allocated

S: Terminates processing.

Action

Re-evaluate the number of processes, and then re-execute the command.

KFPH24003-E L

Invalid "pd_plugin_ixmk_dir" statement, errno=aaaaa, directory or HiRDB file system= bb....bb

An error was detected in the specification of the pd_plugin_ixmk_dir operand in the system definition.

aaaaa: HiRDB file system error code

bb....bb: pd_plugin_ixmk_dir operand specification

If this specification exceeds 120 characters, the last 120 characters are output.

S: Continues processing.

O: Contact the HiRDB administrator.

Action

Terminate HiRDB normally, correct the error by referring to 5.1 Error codes returned from HiRDB file system access requests, then start HiRDB.

In Unix:
If the error code is -1538, either a regular file not in a HiRDB file system area is specified (a regular file system area), or a character special file is specified. In either case, specify either a HiRDB file system area or directory name.

In Windows:
If the error code is -1538, a file not in the HiRDB file system area is specified. If that is the case, specify either a HiRDB file system area or a directory name.

KFPH24004-I L

pd_redo_allpage_put information=(Server=aa....aa,SKIP=bb....bb,APPLY=cc....cc,WRITE=dd....dd,BFPUT=ee....ee)

This displays the internal information related to the database write during full recovery processing of server aa....aa when the pd_redo_allpage_put operand was specified.

aa....aa: Server name

bb....bb: Number of update logs that were not rolled forward, because writing into the database had been completed

cc....cc: Number of update logs that were rolled forward, because writing into the database had not been completed

dd....dd: Number of WRITEs issued during full recovery processing

ee....ee: Internal information

S: Continues processing.

KFPH25000-E L

Error occurred on aa....aa(bbbb), code=ccccc(dd....dd)

An error with error code ccccc occurred in aa....aa(bbbb).

aa....aa: Processing resulting in the error

bbbb: Detail code of the processing resulting in the error

ccccc: Error code

dd....dd: Error detail code

S:

During HiRDB startup: Resumes processing.

During transaction rollback: Terminates processing.

Action

Use the database recovery utility to recover the RDAREA indicated in the KFPH00306-E message (shutdown message) that was output before this message and report the contents of the embedded character to the customer support center.

KFPH25001-E L

Error occurred on aa....aa(bbbb), code=cc(dd....dd)

An error with error code cc occurred in aa....aa(bbbb).

aa....aa: Processing resulting in the error

bbbb: Detail code of the processing resulting in the error

cc: Error code

dd....dd: Error detail code

S: Terminates processing.

Action

Use the database recovery utility to recover the RDAREA indicated in the KFPH00306-E message (shutdown message) that was output before this message and report the contents of the embedded character to the customer support center.

KFPH25002-E C+L

aa....aa wait time over,RDAREA=bb....bb,ccccc=dd....dd

Processing by the free page release utility was suspended because the transaction completion wait time, or the time to execute a search using a holdable cursor, exceeded the specified time.

aa....aa: Reason why the free page release utility was waiting

Transaction: Timeout on transaction completion

Cursor close: Timeout on closing the cursor on a search using a holdable cursor, thereby transaction completion

bb....bb: Name of RDAREA

ccccc: Processing target of the free page release utility

TABLE: Table

INDEX: Index

dd....dd: Name of the processing target of the free page release utility

If ccccc is TABLE, displays the table name

If ccccc is INDEX, displays the index name

S: Terminates processing.

O:

When aa....aa is Transaction:

Re-execute the free page release utility.

If a transaction requires a lengthy access time, re-execute after the transaction has terminated. Alternatively, increase the concurrently executing transaction completion wait time.

When aa....aa is Cursor close:

Re-execute the free page release utility.

If there is a holdable cursor that has been open for a long time, re-execute after the cursor is closed and the transaction has terminated. Alternatively, increase the concurrently executing transaction completion wait time.

KFPH25003-E L

Unusable page accessed,tableID=aa....aa,RDAREA name=bb....bb,file name=cc....cc,code=dd....dd,ee....ee

A page that cannot be used was accessed during operations on the table ID aa....aa, which is defined in RDAREA bb....bb. If WAIT was specified in pd_lock_uncommited_delete_data, HiRDB file areas in excess of the following sizes cannot be used in the RDAREA stored in the table that defines the index.

If the page length is 4096: 32 GB

If the page length is 6144: 48GB

Note that when this message is output once, output is suppressed until one of the following triggers:

HiRDB start time

Execution of the pdopen (RDAREA open) command

aa....aa: table ID

bb....bb: RDAREA name

cc....cc: HiRDB file name

If the path name of HiRDB file exceeds 100 characters, the last 100 characters of the HiRDB file path name are output.

dd....dd: Internal information

ee....ee: Internal information

S: Invalidates this transaction.

Action

Revise the HiRDB file size of the RDAREA that stores the table. For details about the maximum HiRDB file size when WAIT is specified in the pd_lock_uncommited_delete_data operand, see the manual HiRDB Version 9 System Definition. If you have exceeded the maximum size for the RDAREA structure file, use the database structure modification utility (pdmod) to change the configuration so that the maximum size is not exceeded.

KFPH25004-I L

Waiting for transaction completion. RDAREA="aa....aa",bb....bb="cc....cc",TRNGID=dd....ddee....ee,TRNBID=dd....ddff....ff,ACTID=gg....gg,code=hh....hh,iii

The free page release utility is waiting for completion of the transaction displayed in this message.

aa....aa: RDAREA name

bb....bb: Types of processing targets of the free page release utility

TABLE: table

INDEX: index

cc....cc: Identifier of the processing targets of the free page release utility

dd....dd: HiRDB identifier and unit identifier

If the HiRDB identifier and unit identifier cannot be acquired, eight asterisks (*) are displayed.

ee....ee: Global transaction number

If the global transaction number cannot be acquired, eight asterisks (*) are displayed.

ff....ff: Transaction branch number

If the transaction branch number cannot be acquired, eight asterisks (*) are displayed.

gg....gg: User identity sequence number

hh....hh: Waiting for completion

TRAN: Waiting for transaction completion

CURSOR: Waiting for closing of the holdable cursor

iii: Internal information

S: Continues processing.

Action

If a value of 1 or larger was specified in -w when a timeout occurs, wait for the total completion of the transaction output in this message, and execute the free page release utility again. If the value 0 was specified for -w or if the specification was omitted, check whether you can terminate the transaction that the system is waiting for. If you are waiting for a transaction that can be terminated, terminate it. For details, see Free page release utility (pdreclaim) in the manual HiRDB Version 9 Command Reference.

KFPH25100-I L

Index information file assigned, file=aa....aa, index=bb....bb.cc....cc, RDAREA=dd....dd

An index information file was created for the index bb....bb.cc....cc that is stored in the RDAREA dd....dd, with a file name aa....aa.

aa....aa: Name of the index information file

bb....bb: Authorization identifier

cc....cc: Index identifier for the plug-in index

dd....dd: One of the following:

Plug-in index storage RDAREA name, or

Plug-in index storage RDAREA name (replica RDAREA generation number)
When using HiRDB Staticizer Option and the plug-in index storage RDAREA is the replica RDAREA, this message outputs the plug-in index storage original RDAREA name and replica RDAREA generation number.

S: Continues processing.

KFPH25101-E L

Index information file aa....aa error, file name=bb....bb kind=cc....cc index inf=dd....dd errno=ee....ee

Processing aa....aa for the index information file failed when the index information file was being created or updated.

aa....aa: Error type

bb....bb: Name of the index information file

Only the last 100 characters of the file name are output when the length of the index information file name exceeds 100 characters.

cc....cc: Error information

{ 0|1|2 }

dd....dd: Index information

{ 0|1 }

ee....ee: Error code

If the error occurred in HiRDB file system area, HiRDB file system area error code is displayed. For details on errors in a HiRDB file system area, see 5.1 Error codes returned from HiRDB file system access requests. In such a case, the error information displayed in cc....cc is not meaningful.

S: Continues processing if rollback is in progress. Otherwise, invalidates the transaction.

Action

Take actions in the indicated order based on error information and index information.

Error information:

0: Based on the error code (an external integer variable that indicates the condition of the error) and by referring to the errno.h file and the OS manual, check the cause of the error. Take an appropriate action according to the following error cause:

Error cause | Explanation | Action
ENOSPC | The directory holding the index information file is full. | Delete any unneeded files from the directory.

1: The directory holding the index information file is full. Delete any unneeded files from the directory.

2: Records were not read completely. Contact the customer support center.

Index information:

0: Re-execute the UAP.

1: Re-create the index.

KFPH26000-E L

Error occurred on aa....aa(bbbb),code=ccccccc(dddddddd)

An error with error code ccccccc was detected in aa....aa(bbbb).

aa....aa: Processing resulting in the error

bbbb: Detail code of the processing resulting in the error

cccccccc: Error code

dddddddd: Error detail code

S: Terminates abnormally.

Action

Report the contents of the error to the customer support center.

KFPH26001-I L

Information=aa....aa

Displays internal information aa....aa.

aa....aa: Internal information

S: Resumes processing.

Action

If the system terminates abnormally after this message has been output, contact the customer support center.

KFPH26010-I L

Start to assign used page, because pdload used up new pages in RDAREA "aa....aa", table_id="bb....bb"

All new pages for the RDAREA "aa....aa" were used during the data-loading of the table ID "bb....bb". Data is stored in unused free areas.

aa....aa: Name of the RDAREA

bb....bb: Table ID

S: Continues processing.

O: Based on the number of data items stored in the table, review the required RDAREA size. Use the Database Reorganization Utility (pdrorg) to reorganize the table.

KFPH27000-E L+S

System error, func "aa....aa", code=bbbb

A HiRDB system function error occurred.

aa....aa: Name of function

bbbb: Error code

S: Terminates processing.

Action

Function name (aa....aa)
Action by administrator

p_f_dbh_dint_envcp

When the rapid system switchover facility is used:
Resolve the error by referring to message KFPH27028-E, which is output in the standby system unit. Then restart the standby system unit.

When the standby-less system switchover (1:1) facility is used:
Resolve the error by referring to message KFPH27028-E, which is output on the alternate portion to be started in waiting status or on the normal BES unit. Then restart the alternate portion or the normal BES unit in waiting status.

p_f_dbh_buf_envcp

p_f_hba_envcp

Other than above
Refer to 4.2 Detail codes for system-related errors to resolve the error, and then re-execute the function. If you cannot determine the cause of the error, contact the customer support center.

KFPH27002-E S

Message output failed, return code = aaaa, msgno = bb....bb

A message output error occurred.

aaaa: Error code

bb....bb: Message number

S: Terminates processing.

Action

Refer to the system function error code details list, and eliminate the cause of the message output error. If you cannot identify the cause of the error, contact the customer support center. Also, refer to the message number to see which message the system attempted to output, eliminate the cause of the error, and re-execute the command.

KFPH27003-E E+L+S

System call error, func=aa....aa, errno=bbbb

An error has occurred in an operating system function.

aa....aa: Name of system function

bbbb: Value of errno

S: Terminates processing.

Action

Check the description for the errno value in errno.h or the applicable OS documentation to resolve the error, and then re-execute the command.

KFPH27004-E L+S

Work file open failed, aa....aa

A work file open error occurred.

aa....aa: Cause of the error:

errno = bbbb: Error code bbbb was issued

no such file: Specified file was not found

permission denied: The user is not authorized to write data to the directory

S: Terminates processing.

Action

Refer to the file created under %PDDIR%\tmp to eliminate the cause of the error, and re-execute the command.

KFPH27005-E E+L+S

Insufficient memory on PROCESS, size = aa....aa

An attempt to allocate a process private area failed due to a memory shortage.

aa....aa: Size of area that was to be allocated

S: Terminates processing.

O: Re-evaluate the number of processes and re-execute the command.

KFPH27006-E L+S

DATA DICTIONARY RDAREA information get error

An error occurred during collection of information about the data dictionary RDAREA.

S: Terminates processing.

O: Refer to the message log that was output before and after the message to eliminate the cause of the error, and re-execute the command.

KFPH27007-E L

HiRDB file system information get error, code=aaaaa, area=bb....bb

An error occurred during collection of information about a HiRDB file system area.

aaaaa: Error code

bb....bb: Name of HiRDB file system area

If the path name of HiRDB file system area exceeds 117 characters, the last 117 characters of HiRDB file system area path name are output.

S: Invalidates processing on the corresponding RDAREA and resumes processing.

Action

See 5.1 Error codes returned from HiRDB file system access requests, eliminate the cause of the error, and then re-execute the command.

KFPH27008-E L+S

aa....aa command failed due to DATA DICTIONARY RDAREA(bb....bb) status invalid, RDAREA = cc....cc

Because the data dictionary RDAREA bb....bb cannot be referenced, the database operation command aa....aa of the specified RDAREA cc....cc cannot be processed.

aa....aa: Command name

bb....bb: Name of data dictionary RDAREA

cc....cc: RDAREA name (if the RDAREA name cannot be obtained, ***** is displayed)

S: Invalidates processing on the corresponding RDAREA and resumes processing.

O: Correct the status of the data dictionary RDAREA and re-execute the command.

KFPH27009-E L+S

SORT program error occurred, code=aaaa

An error occurred during sort processing.

aaaa: Error code

S: Terminates processing.

Action

Take corrective action according to the error code:

Error code
Action

-202
There is a memory shortage. Reduce the work buffer size specified in the sort operand.

-290
There is a work buffer shortage. Increase the work buffer size specified in the sort operand.

-210
-230
An I/O error occurred. The available capacity on the sort work disk may be insufficient. If the problem is caused by a capacity shortage, specify a disk having sufficient free space in the sort, and execute the processing.

If the error cannot be resolved, acquire the sortdump, SORTIODUMP, and SORTDMP2 that are output to C:\Windows (in UNIX, /tmp or /usr/tmp), and contact the customer support center.

KFPH27010-E L

Unable to send message from aa....aa to bb....bb

During command processing, a communication error occurred between hosts aa....aa and bb....bb.

aa....aa: Send source host name#

bb....bb: Send destination host name#

#: If the system switching facility is being used, the host name of the primary system is indicated.

S: Terminates processing.

Action

If the command is executed while HiRDB is starting, wait until HiRDB has finished starting, and then re-execute the command. Otherwise, take the appropriate action as indicated by the KFPH27000-E message that was output before this message. If the error was not a physical communication error, there might be an inconsistency in the system definitions concerning the relationship between the hosts; check the interhost definitions for the hosts affected by the error, and then retry the operation.

KFPH27011-E L+S

aa....aa command failed due to data dictionary RDAREA (bb....bb) status invalid, buffer pool=cc....cc

Specified buffer pool cc....cc cannot be processed by HiRDB command aa....aa, because HiRDB area for data dictionary bb....bb cannot be referenced.

aa....aa: Command name

bb....bb: Name of data dictionary for RDAREA

cc....cc: Name of buffer pool

S: Name of buffer pool invalidates processing on the corresponding buffer pool area and resumes processing.

Action

If RDAREA for the data dictionary is shut down, eliminate the cause of the error, then re-execute the command. If closed, release close, then re-execute the command.

KFPH27012-I E+L

Usage: pdbufls [-k sts|def|all] [-d] [-x [-y]] [-M]
[{-s server_name[,server_name]...|-a buffer_pool_name[,buffer_pool_name]...}]

Shows how to use the command (pdbufls) to display the status of global buffer pool. This message is displayed when the command option or argument is wrong.

S: Terminates processing

Action

Reenter the command specified correctly.

KFPH27013-I E+L

Usage: pddbchg -q n {-r ORIGINAL_RDAREA[,ORIGINAL_RDAREA...]|-r ALL} [-w]

This message shows the usage of the pddbchg command, which changes the current RDAREA. It is output when a command option or argument is invalid.

S: Terminates processing.

Action

Correct the command format, and then re-execute the command.

KFPH27014-E L+S

No original rdarea named aa....aa[, server = bb....bb]

The specified RDAREA is not the original RDAREA.

aa....aa: RDAREA name

bb....bb: Shared RDAREA runtime server name

This is displayed when an error occurs in the shared RDAREA.

S: Performs one of the following processing actions:

For the pddbchg command, terminates the command without performing any processing on any specified RDAREA.

For the pddbls command, continues processing without performing any processing on the specified RDAREA.

When the -r option of the pdorbegin command is specified
If the RDAREA names are batch-specified, continues processing without performing any processing on the specified RDAREA.
If the RDAREA names are specified directly, terminates the command without performing any processing on any specified RDAREA.

Action

Specify the original RDAREA name and re-execute the command.

KFPH27015-E L+S

aa....aa command failed, RDAREA = bb....bb,code = ccc[, server = dd....dd]

Processing of the pddbchg command could not be performed.

aa....aa: Command name

bb....bb: RDAREA name

ccc: Error code

-30: The specified RDAREA cannot be locked.

-31: The dictionary table and back-end server memory information do not match.

-32: The master directory information cannot be updated.

-33: The dictionary table cannot be updated.

-34: An error occurred in the system function.

dd....dd: Shared RDAREA runtime server name

This is displayed when an error occurs in the shared RDAREA.

S: Terminates processing.

Action

Take the action appropriate for the error code:

-30
Terminate other transactions (if the server name is displayed, other transactions on the server) and re-execute the command. Or, shut down all target RDAREAs inside the inner replica and re-execute the command. Also, if there are RDAREAs shut down through online reorganization hold, the pddbchg command cannot be executed. Release online reorganization hold by executing the pdorbegin command before the pdorchg command and the pdorend command after the pdorchg command, and then re-execute the command.

-31
Check for errors in the system RDAREAs. If there is no error, contact the customer support center.

Other error codes
Check the error message output before this error message, and eliminate the cause of the error. If the server name is displayed, check the message that was output before this message was output, and remove the cause of error from the server. If the cause of the error is unknown, contact the customer support center.

KFPH27016-E L+S

No specified generation RDAREA=aa....aa

No RDAREA of the specified generation could be found.

aa....aa: RDAREA name

S: Terminates processing.

Action

Use the replicate rdarea statement of the database structure modification utility of the specified generation, and then re-execute the command.

KFPH27017-W L+S

replica status changed though MASTER DIRECTORY invalid

The current information on the RDAREA for the master directory is invalid, but the replica status was updated.

S: Continues processing.

KFPH27018-E E+L

pddbchg command not available without Staticizer Option

HiRDB Staticizer Option is required to execute the pddbchg command.

S: Terminates processing.

Action

Check to determine if HiRDB Staticizer Option is being used. Install HiRDB Staticizer Option if necessary.

KFPH27023-E E+L

specified option not available without Staticizer Option

HiRDB Staticizer Option is required for the specified option.

S: Terminates processing.

Action

Check if the environment can be used by HiRDB Staticizer Option. Install HiRDB Staticizer Option if necessary.

KFPH27024-I L+S

HiRDB file freezed, file=aa....aa

HiRDB file aa....aa was put into frozen update status.

aa....aa: HiRDB file name

S: Terminates processing.

KFPH27025-I E+L

Usage:pddbfrz [-d] {-r RDAREA[,RDAREA ...]|-r ALL} [-q generation_number]

This message shows the format of the pddbfrz command. It is output when the command was specified incorrectly.

S: Terminates processing.

Action

Correct the command specification, and then re-execute the command.

KFPH27026-I L+S

HiRDB file freeze skipped, file=aa....aa, reason=bb....bb

Frozen update processing of HiRDB file aa....aa was skipped due to reason bb....bb.

aa....aa: HiRDB file name

bb....bb: Reason code

topfile: This is the first file comprising the RDAREA.

already: The file is already in frozen update status.

plug-in: Plug-in logical files were found.

unused: Nonallocated segments were found.

S: Continues processing.

KFPH27027-E L+S

RDAREA freeze failed, RDAREA=aa....aa

Updating of the specified RDAREA could not be frozen because the RDAREA stores the plug-in index or is an unused RDAREA.

aa....aa: RDAREA name

S: Invalidates processing of the applicable RDAREA, and then processing continues.

Action

Respecify the RDAREA, and then re-execute.

KFPH27028-E E+L

File copy failed, server name = aa....aa, return code = bbbb

When the rapid system switchover facility is used:
Copying of HiRDB database environment information files from the running system server to the standby server failed.

When the standby-less system switchover (1:1) facility is used:
Copying of HiRDB database environment information files from the normal BES unit to the alternate portion, or from the alternate portion to the normal BES unit, failed.

aa....aa: Server name

bbbb: Return code

S: Terminates processing.

Action

Take corrective action according to return code bbbb:

Return code
Cause and action

100
You cannot execute a remote shell in this environment. In an environment using an alias IP address, the following causes are possible:

When the rapid system switchover facility is used:
The host with the alias IP address for the running system unit and the standby system unit may be stopped. If that is the case, activate the server unit that has the alias IP address, and then restart the standby system unit.

When the standby-less system switchover facility is used:
The host with the IP address for the normal BES unit and the alternate portion may be stopped. If that is the case, activate the server unit that has the alias IP address, and then restart either the normal BES unit or the alternate portion.

UNIX edition only
A network failure has occurred. In a system switchover configuration that does not inherit IP addresses, lan_updown is not specified in the server definition statement for the HA monitor. Further, the HA monitor environment setting directory contains network up.down shells named server-id-name.up and server-id-name.down, which are identical to the server identification names specified in the server definition statement for the HA monitor (or the Hitachi Toolkit Extension). This caused a network failure when the system switchover facility was started.
If the system switchover configuration being used does not inherit IP addresses, delete the server-id-name.up and server-id-name.down shells.

101
A time-out occurred. Review the value of the pd_system_complete_wait_time operand. If the rapid system switchover facility is being used, restart the standby system unit. If the standby-less system switchover (1:1) facility is used, restart either the normal BES unit or the alternate portion.

102
Check whether the Hitachi HA Toolkit Extension is being used. If it is not being used, contact the customer support center. If it is being used, take the following action:

If the rapid system switchover facility is used:
An attempt was made to copy HiRDB database environment information files to the standby unit during startup of a secondary system. Check if the running unit started normally.
(1) If the running unit did not start normally:
Check if the Hitachi HA Toolkit Extension process started, and start either the primary system or the secondary system as the running system unit. After the running unit finishes starting, start the standby unit.
(2) If the running unit started normally:
Contact the customer support center.

If the standby-less system switchover facility (1:1) is used:
An attempt was made to copy HiRDB database environment information files from the normal BES unit during startup of the alternate portion in waiting status. Check if the normal BES unit started normally.
(1) If the normal BES unit did not start normally:
Check if the Hitachi HA Toolkit Extension process started, and start the normal BES unit normally, or start the alternate portion as alternating.
If starting the normal BES unit normally:
After the normal BES unit finishes starting, start the alternate portion in waiting status.
If starting the alternate portion as alternating:
After the alternate portion finishes starting, start the normal BES unit in waiting status.
(2) If the normal BES unit started normally:
Contact the customer support center.

Others
Contact the customer support center.

KFPH27030-E L+S

pdhold command required specification of -q option

If the -r ALL or -s option is specified with the pdhold command, the -q option also has to be specified.

S: Terminates processing.

Action

Correct the command format, and then re-execute the command.

KFPH27031-E L+S

Failed to allocate global buffer pool,server=aa....aa,size=bb....bb,errno=cc

Allocation of the global buffer failed.

aa....aa: Server name

bb....bb: Size of the space to be secured (0 is displayed if digit overflowing occurred during the calculation)

cc: Error cause code

S: Terminates processing.

Action

Take the action appropriate for the error cause code, and then re-execute the pdbufmod command.

Error cause code
Error description
Action

4
Page fixing of common memory failed
An attempt to page-fix shared memory segments failed. Refer to the event log (in UNIX, syslogfile) of the server on which the error occurred, and take one of the following actions:

If KFPO00107-E was output with "shmctl(ommfixed)" failed errno=1
See message KFPO00107-E and take the corrective actions described there.

KFPO00107-E was output with "shmctl(ommfixed)" failed errno=12
If shared memory segments do not need to be page-fixed, stop HiRDB normally, specify free in the pd_dbbuff_attribute operand or omit specification of the operand, and then restart HiRDB.
If you want to page-fix the shared memory segments, take either of the following actions:
Increase the real memory.
Reduce the buffer sector count value specified in the pdbufmod command.

8
The common memory segment count exceeded HiRDB maximum.
The number of shared memory segments that can be added per server in HiRDB exceeded the maximum value specified in the pd_max_add_dbbuff_shm_no operand. If in-memory data processing is being used, it exceeds the value 16 + value of pd_max_add_dbbuff_shm_no + value of pd_max_resident_rdarea_shm_no.
Delete any unnecessary global buffers. In addition, define dynamically updated global buffers in the pdbuffer operand. This will decrease the number of common memory segments HiRDB manages.

16
The common memory segment count exceeded the operating system maximum.
The number of common memory segments a process can add exceeded the value of the operating system parameter shmseg in the operating system. Delete any unnecessary global buffers.

20
A memory shortage occurred.
Refer to system call= shmget, errno=12, mnemonic= ENOMEM in 4.3 System call return codes to investigate the cause of the error, and take corrective action.

24
The common memory segment size exceeded the maximum.
Either the common memory size for global buffers exceeded the value of the operating system parameter shmmax in the operating system or the SHMMAX operand value. Decrease the excessive value to decrease the number of buffer sectors in the global buffer.

28
The global buffer count exceeded the maximum.
The maximum number of global buffer pools that can be dynamically added or changed per server (the value specified in the pd_max_add_dbbuff_no operand) has been exceeded. Delete any extraneous global buffer pools, and re-execute the command.

32
Digit overflow occurred during the common memory size calculation.
Decrease the buffer sector count of the global buffer so the common memory size does not exceed 2³¹-1 (2⁶³-1 for the 64-bit mode).

36
The number of common memory identifiers exceeded the maximum.
Refer to system call= shmget, errno=28, mnemonic= ENOSPC in 4.3 System call return codes to investigate the cause of the error, and take corrective action.

KFPH27032-E L+S

Global buffer pool already allocated,global buffer pool name=aa....aa

The global buffers were already allocated.

aa....aa: Global buffer name

S: Terminates processing.

Action

Use the pdbufls -k def command to check the global buffer names already being used. Specify a unique global buffer name and re-execute the pdbufmod command.

KFPH27033-I E+L

Usage: pdbufmod -k {add|del|upd} -a pool name [{-r RDAREA[,RDAREA ....]|-b RDAREA[,RDAREA ....]|-i ID.INDEXNAME|-o}] [-n NUM] [-l SIZE] [-m PRMAX] [-p PRNUM] [-w WRATIO] [-y TRBUFNUM]

Shows how to use the pdbufmod command to dynamically change global buffers. It is output when an invalid command option or argument is used.

S: Terminates processing.

Action

Correct the specification format and re-execute the command.

KFPH27034-E L+S

Unable to execute pdbufmod command, server=aa....aa

The pdbufmod command could not be executed for one of the following reasons:

The rapid system switchover facility was being used

The standby less system switchover facility was being used

The pd_dbbuff_modify operand was omitted or N was specified.

aa....aa: Server name

S: Continues processing.

Action

When using the rapid system switchover facility or the standby less system switchover facility, use the online system configuration modification facility to modify the specification of the pdbuffer operand (change the definition of the global buffer).

When not using the rapid system switchover facility or the standby less system switchover facility, specify Y in the pd_dbbuff_modify operand.

KFPH27035-I E+L

Usage: pdorbegin {-r ORIGINAL_RDAREA[,ORIGINAL_RDAREA...] |-t [AUTHID.]TABLE[-s server[,server...]] [-c CONSTRAINT_TYPE]} [-w LOCK_WAIT_TIME] [-q GENERATION_NUMBER] [-e] [-u]
pdorbegin {-r ORIGINAL_RDAREA[,ORIGINAL_RDAREA...] |-t [AUTHID.]TABLE [-c CONSTRAINT_TYPE]} [-s server[,server...]] [-w LOCK_WAIT_TIME] [-q GENERATION_NUMBER] -u

This is the specification format of the pdorbegin command.

S: Continues processing.

Action

Check the specification format, and then retry the operation.

KFPH27036-I E+L

Usage: pdorchg [-s server[,server....]]

This is the specification format of the pdorchg command.

S: Continues processing.

Action

Check the specification format, and then re-execute.

KFPH27037-I E+L

Usage: pdorend [-s server[,server....]] {[-n RETRY_COUNT] [-w MAX_REFLECT_WAIT_TIME] [-t MAX_TRN_WAIT_TIME] [-m REF_PROCESS_CNT] [-z] | [-f reflection control file] [-p] | [-u]}

This is the specification format of the pdorend command.

S: Continues processing.

Action

Check the specification format, and then re-execute.

KFPH27038-E E+L

Not available without aa....aa option, command = bb....bb

The bb....bb command could not be executed because the aa....aa option was not embedded.

aa....aa: Option name

Staticizer

bb....bb: Command names

{pdorbegin|pdorchg|pdorend}

S: Continues processing.

Action

Embed the option, and then re-execute the command.

KFPH27039-E E+L

Not available without specification of aa....aa operand, command = bb....bb

The bb....bb command could not be executed because the aa....aa operand in the system definition was not specified.

aa....aa: System definition operand name

{pd_inner_replica_control|pd_max_reflect_process_count}

bb....bb: Command names

{pdorbegin|pdorchg|pdorend}

S: Continues processing.

Action

Terminate HiRDB, add the system definition aa....aa operand, restart HiRDB, and then re-execute the command.

KFPH27040-I E+L

Reflection completed, server = aa....aa

Reflection processing completed on the indicated server.

aa....aa: Name of server

S: Continues processing.

KFPH27041-W E+L

Reflection retry, server = aa....aa, count = bb, code = cccc, wait_time = dddd

Retries discrepancies application processing on server aa....aa.

aa....aa: Server name

bb: Retry count

cccc: Reason code

lock: Time-out occurred during the locking procedure.

sync: Time-out occurred in discrepancies application processing after the locking procedure completed.

dddd: Locking wait time (seconds)

S: Continues processing.

O: If discrepancies application processing is repeatedly retried and terminates abnormally, take one of the following actions and re-execute the pdorend command.

Increase the specification value of the -n option.

Increase the specification value of the -w option.

Increase the specification value of the -t option.

If discrepancies application processing terminates abnormally even after taking these actions, reduce the amount of transaction processing and execute the pdorend command.

KFPH27042-W L+S

No held(org) RDAREA, command = aa....aa

There is no RDAREA that can perform updatable online reorganization.

aa....aa: Command name

{pdorchg|pdorend}

S: Terminates processing.

O: Check the operation procedure for updatable online reorganization, and then re-execute the command. For details about how to perform updatable online reorganization, see HiRDB Version 9 Staticizer Option Description and User's Guide.

KFPH27043-E E+L

aa....aa command failed, server = bb....bb, code = ccc

The aa....aa command failed on server bb....bb.

aa....aa: Command name

bb....bb: Server name

ccc: Error code

-50: The maximum wait time of discrepancies application processing elapsed.

-51: The retry count exceeded the specified value.

-52: An error occurred in the pdorend application process.

-53: A communication error occurred.

-54: The applicable server is executing updatable online reorganization.

-55: The execution sequence of updatable online reorganization is incorrect.

-56: It is possible that the pdorchg command has not completed.

-57: The specified option, RDAREA, table, or constraint type is invalid.

S: Terminates processing.

O: Take corrective action according to the error code:

When the error code is -50:

Either increase the value specified for the maximum wait time of discrepancies application processing or reduce the amount of transactions with the replica RDAREA and re-execute the command.

When the error code is -51:

Take one of the following actions, and then re-execute the command:

Increase the value specified for the transaction maximum wait time.

Increase the retry count.

Reduce the amount of transactions with the replica RDAREA.

When the error code is -52:

Take one of the following actions:

If the -u option is not specified in the pdorend command, take action according to the previous error message.

If the -u option is specified in the pdorend command and online reorganization hold of all RDAREAs in the applicable server is released, re-executing this command is not necessary. Use the pddbls command to check the status of the RDAREA. If there is even one RDAREA on the relevant server that is on online reorganization hold, see the description on troubleshooting in the manual HiRDB Version 9 Staticizer Option Description and User's Guide.

When the error code is -54:

Wait for the first pdorend command executed to terminate, and then re-execute the command.

When the error code is -55:

Check the execution sequence of the pdorbegin, pdorchg, and pdorend commands. If the execution sequence is correct, use the pddbls command to check whether the status of the RDAREA is correct.

When the error code is -56:

Check the return code from the pdorchg command. If the system has not normally terminated, use the pdorchg command to normally terminate the system, and then re-execute the pdorend command. If the system has normally terminated, the pddbchg command or the database structure modification utility may be running at the same time as the pdorend command. In this case, re-execute the pdorend command.

When the error code is -57:

When the -u option is not specified
The pdorbegin command cannot be executed because the server containing the RDAREAs to be processed contains an RDAREA or table that has been placed in online reorganization hold. Check the specified RDAREAs or table names.

When the -u option is specified
Specify the option (-r, -t, or -c) and the flag argument (RDAREA, table, or constraint type) that were specified for online reorganization hold, and re-execute the pdorbegin command.
If the -r option is specified, specify any RDAREA among those specified by the -r option that was released during online reorganization hold, and re-execute the pdorbegin command.
If the -t option is specified, specify the table specified in the -t option during online reorganization hold.
If the -c option is specified, specify the constraint type that was specified during online reorganization hold, and re-execute the pdorbegin command.

For other error codes:

Check the message output before this message, eliminate the error cause, and then re-execute the command. If the cause of the error is unclear, contact the customer support center.

KFPH27044-I E+L

aa....aa command started

The aa....aa command started.

aa....aa: Command name

{pdorbegin|pdorchg|pdorend}

S: Continues processing.

KFPH27045-I E+L

aa....aa command ended, return code = bb

The aa....aa command ended.

aa....aa: Command name

{pdorbegin|pdorchg|pdorend}

bb: Return code

0: Normal termination

4: Warning termination

8 and 12: Abnormal termination

S: Terminates processing.

Action

When the return code is not 0, take actions according to the previously output error message.

KFPH27046-E L+S

Refrection management table not found, command = aa....aa

No reflection status management table was found.

aa....aa: Command name

{pdorbegin|pdorchg|pdorend}

S: Terminates processing.

Action

Use the pdorcreate command to create a reflection status management table, and then re-execute command aa....aa.

KFPH27047-E L+S

Reflection management table existed in RDAREA to hold(org), RDAREA = aa....aa

The reflection status management table was found in the RDAREA used for updatable online reorganization.

aa....aa: RDAREA name

S: Terminates processing.

Action

Delete the reflection management status table, and then create a new RDAREA.

KFPH27048-E L

Enter aa....aa command, due to incomplete operation, RDAREA = bb....bb, SERVER = cc....cc

Some operation commands did not complete processing.

aa....aa: Command name {pdorbegin|pdorend}

bb....bb: Original RDAREA name (******** is displayed for the pdorend command)

cc....cc: Server name (******** is displayed for the pdorbegin command)

S: Terminates processing.

Action

Specify the displayed RDAREA or server and re-execute the pdorbegin or pdorend command.

KFPH27049-E L+S

Another RDAREA of the same server already held(org),command = aa....aa,SERVER = bb....bb

This command cannot be executed because another RDAREA on the same server is already in online reorganization hold status.

aa....aa: Command name (pdorbegin)

bb....bb: Server name

S: Terminates processing.

Action

Take the following action to add an RDAREA in updatable online reorganization status on the same server:

When the pdorchg command is not executing
For an RDAREA already in updatable online reorganization hold status, execute the pdorbegin command (-u), release the updatable online reorganization hold status, and re-execute the pdorbegin command.

When the pdorchg command is executing
For an RDAREA already in updatable online reorganization hold status, execute the pdorbegin command (-u), release the updatable online reorganization hold status, use the pddbchg command to change the current RDAREA, and re-execute the pdorbegin command.

For details, see HiRDB Version 9 Staticizer Option Description and User's Guide.

KFPH27050-E L+S

Unable to execute aa....aa command,RDAREA = bb....bb,reason = cc....cc

Cannot execute the aa....aa command for reason cc....cc.

aa....aa: Command name (pdorbegin)

bb....bb: RDAREA name

cc....cc: Reason

invalid RECOVERY type: The column recovery restriction of the RDAREA for storing LOB columns is not ALL.

S: Terminates the server processing the applicable RDAREAs.

Action

If the reason is invalid RECOVERY type, take either of the following actions, and then re-execute the command:

Redefine the RDAREA for LOB column storage as an RDAREA for storing tables that will not be put in online reorganization hold status.

In the table definitions containing a LOB column storage RDAREA, set all column recovery constraints in the LOB column, and execute ALTER TABLE.

KFPH27051-E E+L+S

Number of RDAREA exceeds maximum value

The upper limit on the number of RDAREAs that can be processed has been exceeded.

S: Terminates processing.

Action

The upper limit on the number of RDAREAs that can be processed using the pdorbegin command is 4,096.

With the -r option specified:
Revise the batch specification of RDAREAs specified in the -r option, and then re-execute the command.

With the -t option specified:
Check the total number of tables and related RDAREAs specified in the -t option. Use the pdrdrefls command to check the RDAREAs related to a specified table.
Group the RDAREAs so that the number of RDAREAs to be processed does not exceed 4,096, and then specify the RDAREAs in the -r option and re-execute the command.

KFPH27052-W L+S

Shared RDAREA released hold(org), specified option "-s", server = aa....aa, RDAREA = bb....bb

For a shared RDAREA, specify server aa....aa to release online reorganization hold.

aa....aa: Server name

bb....bb: RDAREA name

S: Continues processing.

Action

Remove the reason why all of the back-end servers cannot be processed in batch, and use the pddbls -m command to check the hold status of the RDAREAs of all back-end servers. Then, release the online reorganization hold of the shared RDAREAs of all back-end servers.

KFPH27053-E E+L+S

Unable to use specified command option aa for bb....bb, command = cc....cc

For bb....bb, command cc....cc, option aa cannot be specified.

aa: Option name

-s

bb....bb: Error cause

shared RDAREA: Shared RDAREA

RDAREA: Non-shared RDAREA

shared table: Shared table on a HiRDB/Parallel Server

cc....cc: RDAREA name

{pdorbegin | pdorchg | pdorend}

S: Terminates processing.

Action

Take the following action to eliminate the cause of the error:

When the error cause is shared RDAREA or RDAREA

When cc....cc is the pdorbegin command
Execute shared RDAREAs and non-shared RDAREAs separately. For shared RDAREAs, execute the command specifying only shared RDAREAs in the -r option. For non-shared RDAREAs, execute the command specifying non-shared RDAREAs in the -r option and drop the -s option. Confirm the information for shared RDAREAs by specifying the -m option of the pddbls command.

When cc....cc is the pdorchg and pdorend commands
Delete the -s option, and re-execute the command.

When the error cause is shared table

Drop the -s option and execute the command.

KFPH27054-E L

Transaction may not determine commit or rollback command=aa....aa

A communication or other error occurred, such that the transaction might not have been completed or rolled back by the system.

aa....aa: Command name

S: Terminates processing.

Action

Check that the transaction of the executed command does not remain using the pdls -d prc and pdls -d trn commands. If the transaction has not completed, cancel it with the pdcancel command and re-execute the command.

KFPH27055-E E+L+S

aa....aa command failed,reason=bb....bb

An error occurred during the execution of aa....aa command.

aa....aa: Command name

bb....bb: Reason

ANALYZE FAILED: An error occurred during analysis of the attached reflection control file.

ANY BES FAILED: An error occurred during processing of one or more back-end servers.

Auth_id INVALID: The default value of an authorization identifier omitted with the -t option is invalid.

SPECIFIED SERVER INVALID: A server not related to a table specified with the -t option was specified with the -s option.

S: Terminates processing.

Action

When bb....bb is Auth_id INVALID: Set or revise the environment variable PDUSER, and re-execute the command.

When bb....bb is SPECIFIED SERVER INVALID: In the -s option, specify the table specified in the -t option of the pdorbegin command or specify the server linked with a referenced table or referencing table of that table, and then re-execute the command. Check the server related to the table using the pdrdrefls command.

When bb....bb is ANY BES FAILED:

When the immediately previous KFPH00132-E message displayed servers not involved in processing:

To continue online reorganization processing, execute one of the following:

Eliminate the cause of the error in the server displayed in the KFPH00132-E message, and re-execute the command.

When online reorganization hold was effected by using the pdorbegin command and specifying the -t option:
If none of the tables specified in the -t option or their referenced tables is a shared table on a HiRDB/Parallel Server, specify the server to be processed in the -s option, and re-execute the command.
If a table specified in the -t option or its referenced table is a shared table on a HiRDB/Parallel Server, re-execute the command without specifying the -s option.

Other than the above:

Take action based on the immediately preceding message that was output, and re-execute the command.

If bb....bb is other than the above: Take action based on the immediately preceding message that was output, and re-execute the command.

KFPH27056-W E+L+S

Warning occurred in reflect service,server=aa....aa

A warning was returned from the pdorend application process.

aa....aa: Server name

S: Continues processing.

Action

Take corrective action according to the KFPT (-W) warning message that is output before this message.

KFPH27058-E L+S

Unable to use specified command option aa for bb....bb, command=cc....cc, RDAREA name="dd....dd"

With command cc....cc, option aa cannot be specified for bb....bb.

aa: Option name

-u

bb....bb: Error cause

resident RDAREA: In-memory RDAREA

cc....cc: Command name

pdhold

dd....dd: RDAREA name

S: Invalidates RDAREA "dd....dd" processing, and continues processing.

Action

Drop the aa option, and re-execute the command.

KFPH27059-I E

Usage: pdmemdb -k {stay|reload|rels|cancel} {-r RDAREA[,RDAREA ...]|-r ALL} [-p {free|fixed}] [-d]

An error was found in the pdmemdb option specification format.

S: Terminates processing.

Action

Revise the option specification and re-execute the command.

KFPH27060-I L+S

RDAREA aa....aa, RDAREA="bb....bb"

aa....aa processing was performed on RDAREA bb....bb.

aa....aa: Type of RDAREA processing

stayed: Adding to in-memory

reloaded: Reloading

released: Releasing in-memory adding

canceled: Canceling the update content of the in-memory buffer

bb....bb: RDAREA name

S: Continues processing.

KFPH27061-W L+S

Resident RDAREA held due to force released, RDAREA = "aa....aa"

Because in-memory allocation was forcibly released, the RDAREA aa....aa error was shut down.

aa....aa: RDAREA name

S: Continues processing.

Action

Take one of the following actions:

See Troubleshooting in the manual HiRDB Version 9 Batch Job Accelerator, and recover the RDAREA.

The RDAREA is allocating in-memory or synchronizing. To restart operations in that state, use the pdrels command to release error shutdown.

KFPH27062-E L+S

"pdmemdb" command failed, RDAREA="aa....aa", reason=bb....bb

The pdmemdb command was executed on the RDAREA aa....aa, but an error caused by bb....bb occurred.

aa....aa: RDAREA name

bb....bb: Cause of the error

INVALID_RDKIND: Invalid RDAREA type (an RDAREA other than the user RDAREA, user LOB RDAREA, or list RDAREA is specified)

INVALID_STATUS: Invalid RDAREA status or in-memory data buffer status

EXIST_PDORRFST: RDAREA that stores the table performing the reflection processing

EXIST_SCHEDULE: SCHEDULE attribute RDAREA

EXIST_SHARED_RDAREA: Shared RDAREA

EXIST_REPLICA_RDAREA: Replica RDAREA

NO_GBUF: No global buffer has been allocated.

S:

For HiRDB/Single Server:

Terminates processing.

For HiRDB/Parallel Server:

If the cause of the error is INVALID_RDKIND, EXIST_PDORRFST, or EXIST_SHARED_RDAREA:
Terminates processing.

If the cause of the error is INVALID_STATUS, EXIST_SCHEDULE, EXIST_REPLICA_RDAREA, or NO_GBUF:
Stops all processing of RDAREAs at the back-end server where the RDAREA aa....aa exists. Continues processing RDAREAs that are at locations besides the back-end server.

Action

Take one of the following actions:

If bb....bb is INVALID_RDKIND, EXIST_SHARED_RDAREA, or EXIST_REPLICA_RDAREA:

Exclude the RDAREA with the error, and re-execute.

If bb....bb is INVALID_STATUS:

Execute the pddbls -M command, check the status of the RDAREA and in-memory data buffers, perform the necessary corrective actions, and then re-execute the command.

If bb....bb is EXIST_PDORRFST:

Take one of the following actions:

Re-execute excluding the RDAREA stored in the table performing reflection processing.

Use the pdorcreate -d command to release the table that performs reflection processing, and then re-execute.

If bb....bb is EXIST_SCHEDULE:

Take one of the following actions:

Use the database structure modification utility to change the RDAREA opening trigger attribute to an attribute other than the SCHEDULE attribute, restart HiRDB, and then re-execute.

When an invalid RDAREA is being alternated and you are using the standby-less system switchover (1:1) facility, reactivate the system, and then re-execute.

Exclude the RDAREA with the error, and then re-execute.

If bb....bb is NO_GBUF:

Take one of the following actions:

Use the pdbufmod -k add command to add a global buffer, and then re-execute.

Restart HiRDB and re-execute with the OTHER buffer allocated.

Exclude the RDAREA with the error, and then re-execute.

KFPH27064-E E

Unable to execute pdmemdb command because of using Real_Time_SAN_Replication, kind=aa....aa

If the Real Time SAN Replication facility aa....aa is being used, the pdmemdb command cannot be executed.

aa....aa: Method of reflecting data to a remote site

sync: All-synchronous method

async: All-asynchronous method

hybrid: Hybrid method

S: Terminates processing.

Action

If in-memory data processing is to be applied, change the system definition so that you are not using the abovementioned data reflection method.

KFPH27065-E E+L

Resident RDAREA held due to HiRDB file error, RDAREA = "aa....aa"

An HiRDB file access error occurred, so an error-induced shutdown was performed on the in-memory RDAREA aa....aa.

aa....aa: RDAREA name

S: Terminates processing.

Action

After taking corrective action according to the error message output directly prior to this message, see Troubleshooting in the manual HiRDB Version 9 Batch Job Accelerator and recover the RDAREA.

KFPH27066-E E

Number of RDAREA exceeded aaaa

The number of RDAREAs specified in the flag argument (after eliminating duplicates) exceeded the maximum value (aaaa).

aaaa: Maximum value

S: Terminates processing.

Action

Decrease the number of RDAREAs specified in the flag argument (after eliminating duplicates) to a value less than or equal to the maximum. For the maximum number of RDAREAs that can be specified, see Specification of RDAREAs in operation commands and utilities in the manual HiRDB Version 9 Command Reference.

KFPH27100-E L+S

Unable to aaaaaa global buffer pool due to bb....bb, RDAREA="cc....cc"

Global buffers could not be added or removed for reason bb....bb.

aaaaaa: Processing content

add: Add

delete: Delete

bb....bb: Reason

invalid RDAREA type: The RDAREA type is invalid.

RDAREA cannot specified: The RDAREA cannot be specified.

cc....cc: RDAREA name

S: Terminates processing.

Action

When the RDAREA type is invalid, an RDAREA other than an RDAREA for LOB is specified in the global buffer for LOB. Specify the correct RDAREA and re-execute the pdbufmod command.

When no RDAREA can be specified, specify an RDAREA in the global buffer for indexes. No RDAREA can be specified in a global buffer for indexes. Re-execute the pdbufmod command without specifying an RDAREA.

KFPH27101-E L+S

Too small buffer size, buffer size=aaaaa,RDAREA="bb....bb", page size=ccccc

The global buffer was not allocated to RDAREA "bb....bb" because the buffer was too small.

aaaaa: Buffer size

bb....bb: RDAREA name

ccccc: RDAREA page length

S: Terminates processing.

Action

The buffer size must be equal to or greater than the RDAREA page length. Allocate a global buffer to meet this condition.

KFPH27102-E L+S

Invalid option is specified, reason code=aa

An invalid combination of pdbufmod command options was found.

aa: Reason code

1: An invalid option was specified in the specified modification type.

10: The -r, -b, -i, or -o option was not specified even though a modification type was added (-k add).

11: Even though the -n option was not specified when adding a modification type (-k add), the -l, -m, -p, -w, or -y option was specified.

12: Even though the -i or -o option was specified when adding a modification type (-k add), the -n option was not specified.

22: Even though the modification type was modified (-k upd), the modified option was not specified. Or, when the concurrent execution maximum prefetch count is 0, only the -p option is specified.

40: The -r option was specified in the global buffer for LOB.

41: The -b option was specified in an RDAREA other than one for the LOB global buffers.

S: Terminates processing.

Action

Specify the correct option and re-execute the pdbufmod command.

KFPH27103-I L+S

Global buffer pool aaaaaaa,global buffer pool name=bb....bb, server=cc....cc

The specified global buffer was added, removed, or modified.

aaaaaaa: Processing content

added: A global buffer was added.

deleted: A global buffer was removed.

updated: A global buffer was updated.

bb....bb: Global buffer name

cc....cc: Server name

S: Terminates processing.

KFPH27104-I L+S

RDAREA "aa....aa" bb....bb,global buffer pool name=cc....cc, server=dd....dd

The specified RDAREA was allocated to or removed from the global buffer.

aa....aa: RDAREA name

bb....bb: Processing content

added: An RDAREA was allocated to a global buffer

deleted: An RDAREA was removed from a global buffer

cc....cc: Global buffer name

dd....dd: Server name

S: Continues processing.

KFPH27105-E L+S

Unable to execute aa....aa command due to command in process

The aa....aa command could not be executed because it is in progress.

aa....aa: Command name (pdbufmod)

S: Terminates processing.

Action

After the command in progress terminates, re-execute the pdbufmod command.

KFPH27106-E L+S

Unable to execute aa....aa commnad due to specified index name not found

The aa....aa command could not be executed because the specified index was not found.

aa....aa: Command name (pdbufmod)

S: Terminates processing.

Action

Specify the correct index name, and then re-execute the pdbufmod command.

KFPH27107-E L+S

aa....aa command failed due to DATA DICTIONARY RDAREA(bb....bb) status invalid, index = cc....cc

The aa....aa command in specified index cc....cc could not be executed because data dictionary RDAREA bb....bb could not be referenced.

aa....aa: Command name (pdbufmod)

bb....bb: Data dictionary RDAREA name

cc....cc: Index name

S: Invalidates this operation and continues processing.

Action

After the data dictionary RDAREA returns to normal status, re-execute the pdbufmod command.

KFPH27108-E L+S

Failed to allocate semaphore

Allocation of a semaphore resource failed.

S: Terminates processing.

Action

Take one of the following actions before re-executing the pdbufmod command:

Increase the maximum (in HP-UX, semmns; in Solaris, seminfo_semmns; and in Linux, SEMMNS) semaphore count in the system.

Increase the maximum (in HP-UX, semmni; in Solaris, seminfo_semmni; in Linux, SEMMNI; and in Windows, PDUXPLSEMMAX) semaphore identifier count.

Delete any unnecessary global buffers.

KFPH27109-E L+S

Unable to add aa....aa global buffer pool due to already allocated, global buffer pool name=bb....bb

An index or -o option global buffer could not be added because the target global buffer was already in use.

aa....aa: Global buffer types

index: Index global buffer

other: Global buffer with the -o option

bb....bb: Global buffer name

S: Terminates processing.

Action

Use the dbufls -k def command to check the global buffers currently in use. Re-execute the command if necessary.

KFPH27110-E L+S

Unable to add global buffer pool due to no RDAREA

A global buffer could not be added because no RDAREA was found to which to allocate the global buffer.

S: Terminates processing.

Action

Use the dbufls -k def command to check for global buffers currently in use. Re-execute the command if necessary.

KFPH27111-E L+S

Unable to delete due to no RDAREA "aa....aa", global buffer pool name=bb....bb

Global buffer bb....bb could not be deleted because RDAREA "aa....aa" was not allocated.

aa....aa: RDAREA name

bb....bb: Global buffer name

S: Terminates processing.

Action

Use the pdbufls -k def command to check for global buffers currently in use. Re-execute the command if necessary.

KFPH27112-E L+S

pdbufmod command failed due to specified name not found, global buffer pool name=aa....aa, server=bb....bb

The pdbufmod command could not be executed because the specified global buffer aa....aa was not defined on server bb....bb.

aa....aa: Global buffer name

bb....bb: Server name

S: Continues processing.

Action

Use the pdbufls -k def command to check for global buffers currently in use. Re-execute the command if necessary.

KFPH27113-E L+S

Unable to execute pdbufmod command due to HiRDB Advanced High Availability not setup

The pdbufmod command could not be executed because HiRDB Advanced High Availability was not set up.

S: Terminates processing.

Action

Set up HiRDB Advanced High Availability, and then re-execute the command.

KFPH27114-E L+S

Unable to delete global buffer pool due to resident RDAREA, RDAREA="aa....aa"

It is not possible to release the global buffer to which the in-memory RDAREA aa....aa was allocated.

aa....aa: RDAREA name

S: Terminates processing.

Action

Use the pdmemdb -k rels command to release in-memory allocation of the RDAREA in question, and then re-execute.

KFPH28001-E L

Insufficient memory on DYNAMIC_SHMPOOL for DB exclusive control, server=aa....aa

For server aa....aa, the shared memory used for exclusive control is insufficient.

aa....aa: Server name

S: Invalidates the transaction.

P:

When NO is specified in the client environment definition PDDBLOG and the transaction is executed to update a shared table:
Consider changing PDDBLOG to YES.

When the transaction involves executing the LOCK statement with the IN EXCLUSIVE MODE specification for multiple shared tables:
Consider reducing the number of shared tables.

When the transaction involves executing in non-shared tables using the UNTIL DISCONNECT specification LOCK statement:
Consider dropping the UNTIL DISCONNECT specification.

Action

The value of the pd_lck_until_disconnect_cnt operand is inappropriate. Revise it by increasing the specified value, and restart HiRDB.

KFPH29005-W L

Unable to check work HiRDB file system area, return code=aa....aa, file system=bb....bb (cc....cc)

An error occurred during a utilization rate check on HiRDB file system area for work tables.

aa....aa: Return code

bb....bb: Name of HiRDB file system area

If the path name of HiRDB file system area exceeds 117 characters, the last 117 characters of HiRDB file system area path name are output.

cc....cc: Server name

S: Continues processing by temporarily skipping checking the utilization rate on the affected HiRDB file system area for work tables. However, the system does not discontinue checking the utilization rate. If the same error persists in utilization rate checks on the same area, the system outputs this error message at the first occurrence of the error, without generating subsequent messages.

O: Notify HiRDB administrator.

Action

See 5.1 Error codes returned from HiRDB file system access requests and eliminate the cause of the error. Utilization rate checks are done on HiRDB file system area for work tables according to the specification made in pd_watch_resource or pdwork_wrn_pnt.

KFPH29006-W L

HiRDB file "aa....aa" information, return code=bbbbb, HiRDB file name=cc....cc

The "aa....aa" processing for HiRDB file cc....cc terminated with error code bbbbb.

aa....aa: Type of HiRDB file processing:

create: HiRDB file creation

delete: HiRDB file deletion

bbbbb: Error code

cc....cc: Name-of-HiRDB-file-system-area\Name-of-HiRDB-file

If the path name of HiRDB file exceeds 148 characters, the last 148 characters of HiRDB file path name are output.

S: Continues processing.

Action

See 5.1 Error codes returned from HiRDB file system access requests and eliminate the cause of the error.

However, if "aa....aa" is create and the error code is -1541, HiRDB file the user tried to create has already been defined. It is possible that the deletion of HiRDB file failed first. In this case, see the KFPH29006-W message issued before this message to check the delete error code for "aa....aa" in 5.1 Error codes returned from HiRDB file system access requests and eliminate the cause of the error.

KFPH29008-I L

Work buffer expanded, server=aa....aa, process ID=bb....bb

The work table buffer size specified in the pd_work_buff_size operand in the system definition was insufficient, but a work table buffer extension was available because the pd_work_buff_expand_limit operand was specified.

aa....aa: Server name

bb....bb: Process ID

S: Continues processing.

Action

Operation premised on availability of the work table buffer extension:

To suppress the outputting of this error message, use the pd_work_table_option operand to specify that message output be suppressed when extending the work table buffer length.

Operation not premised on availability of the work table buffer extension:

Re-evaluate the specification value of the pd_work_buff_size operand so that securing an extension of the work table buffer is not necessary.

Notes

When extending the work table buffer, release the secured extended work table buffer when the work table usage count in the applicable server processes is 0. The work table usage count becomes 0 in the following situations:

When all cursors in use were closed (however, the work table usage count may not become 0 in some internal processes)

When not using a holdable cursor and transactions ended normally or transactions were cancelled

When using a holdable cursor and the UAP is isolated from HiRDB

When using a HiRDB edition other than Linux or Windows and extending the work table buffer, terminate processes, including even resident processes, at the following events to free up memory:

For HiRDB/Single Server:

Terminate single server processes when detaching a UAP from HiRDB.

For HiRDB/Parallel Server:

Terminate the back-end server process or dictionary server process when not using a holdable cursor, when transactions terminate normally, or when transactions are deleted.

When using a holdable cursor, terminate the back-end server process or the dictionary server process when detaching a UAP from HiRDB.

KFPH29009-W L

Unable to expand work buffer due to insufficient memory, server=aa....aa,process ID=bb....bb,size=cc....cc

An attempt to secure a work table buffer extension according to specification of the operand pd_work_buff_expand_limit was made, but it failed because of insufficient process private area.

aa....aa: Server name

bb....bb: Process ID

cc....cc: Total work table buffer size in the applicable process (in kilobytes)

S: Continues processing.

Action

Operation premised on availability of the work table buffer extension:

Reduce the specification value of the pd_work_buff_expand_limit operand to no greater than cc....cc.

Operation not premised on availability of the work table buffer extension:

Do not specify the pd_work_buff_expand_limit operand.

2.5 KFPI messages

KFPI21501-I E

Usage: pdfbkup [-y] [-i] [-r] [-{c|l|f}] HiRDB_file_system_area_name[/file_name] backup_file

Displays the format of the pdfbkup command that saves the specified HiRDB file system in the file.
This message is output when a specified command option or argument is invalid.

S: Terminates processing.

O: Reenter correctly the specified command.

KFPI21502-I E

Usage: pdfrstr [-y] [-q] [-{t|o|r}] backup_file[/file_name] HiRDB_file_system_area_name

Displays the format of the pdfrstr command that stores (restores) The HiRDB file system from a saved file.
This message is output when a specified command option or argument is invalid. However, in the Windows edition, the -q option is disabled, so this message can be ignored. If the -q option is specified, it has no meaning.

S: Terminates processing.

O: Reenter correctly the specified command.

KFPI21503-I E

Usage: pdfls [-[H] [{L|S}] [{t|u}]] HiRDB_file_ system_area_name[/file_name]
pdfls [-x] HiRDB_file_system_area_name [/file_name]

Displays the format of the pdfls command that displays a list of the HiRDB files. This message is output when a specified command option or argument is invalid.

S: Terminates processing.

O: Reenter the command specified correctly.

KFPI21505-I E

Usage: pdfmkfs -n capacity [-l file_count] [-e expand_count] [-i] [-k area_kind] [-s sector_size] [-a] character_special_file pdfmkfs [-r] -n capacity [-l file_count] [-e expand_count] [-i] [-k area_kind] [-a] UNIX_regular_file

Displays the format of the pdfmkfs command that initializes a HiRDB file system area. This message is output when a specified command option or argument is invalid.

S: Terminates processing.

O: Correct the format of the command, and then re-execute it. For details about valid combinations of command options, see the manual HiRDB Version 9 Command Reference.

KFPI21510-E E+L

Backup file open error, file name=aa....aa errno=bbb

Opening of backup file aa....aa failed with error number bbb.

aa....aa: Backup file name

If the name of the backup file exceeds 148 characters, the last 148 characters of the backup file name are output.

bbb: Error number

S: Terminates processing.

O: Refer to the error number and take appropriate action. The following table shows the error numbers and actions.

Error number
Explanation
Action

2
Specified file or directory cannot be found.

Check the specified file or directory and re-execute.

5
I/O error occurred.

Check other message.

Change the file name and re-execute.

11
Specified file is locked by another process.

Wait until the locked process terminates and re-execute.

Change the file name and re-execute.

13
User does not have access privilege to the specified file.

Ask a user who has access privilege to re-execute.

Ask the file owner to modify the access privilege and re-execute.

Change the file name and re-execute.

17
Specified file already exists.

Change the file name and re-execute.

Specify the command with the remove option and re-execute.

20
Directory with the specified path name cannot be found.

Correct the path name specification and re-execute.

21
Specified file is a directory.

Correct the file name specification and re-execute.

23
File table is full.

Terminate unneeded processes and re-execute.

In UNIX, increase the value of nfiles using Kernel Configuration of the sam system command, reconstruct the system, and re-execute the command.

24
Number of open files exceeds the value defined for the system.

28
File system is full.

Delete unneeded files and re-execute.

Other than the above
--

Contact the customer support center.

--: Not applicable

KFPI21511-E E+L

Backup file aa....aa already exist

Backup file aa....aa already exists.

aa....aa: Backup file

If the name of the backup file exceeds 148 characters, the last 148 characters of the backup file name are output.

S: Terminates processing.

O: Specify the -r option. Or, change the backup file name and re-execute.

KFPI21512-W E+L

HiRDB file create error, HiRDB file system area=aa....aa, file name=bb....bb, errno=ccccc

HiRDB file bb....bb cannot be created in HiRDB file system area aa....aa because of error number ccccc.

aa....aa: Name of the HiRDB file system area

If the name of the HiRDB file system area exceeds 114 characters, the last 114 characters of the HiRDB file system area name are output.

bb....bb: HiRDB file name

ccccc: Error code

S: Resumes processing.

O: Check the error number and take appropriate action.

KFPI21513-Q S

HiRDB file system area aa....aa restore from bb....bb. [G:continue, T:terminate]

Asks the operator whether or not data from backup file bb....bb is to be restored to the specified HiRDB file system area aa....aa.

aa....aa: Name of the HiRDB file system area

If the name of the HiRDB file system area exceeds 76 characters, the last 76 characters of the HiRDB file system area name are output.

bb....bb: Backup file name

If the name of the backup file exceeds 76 characters, the last 76 characters of the backup file name are output.

S: Waits for the operator's response.

O: Enter one of the following:

G: Resume processing

T: Terminate processing

KFPI21514-Q S

HiRDB file system area aa....aa backup to bb....bb. [G:continue, T:terminate]

Asks the operator whether or not the specified HiRDB file system area aa....aa is to be saved in backup file bb....bb.

aa....aa: Name of the HiRDB file system area

If the name of the HiRDB file system area exceeds 78 characters, the last 78 characters of the HiRDB file system area name are output.

bb....bb: Backup file name

If the name of the backup file exceeds 78 characters, the last 78 characters of the backup file name are output.

S: Waits for the operator's response.

O: Enter one of the following:

G: Resume processing

T: Terminate processing

KFPI21515-E E+L

Unable to restore because sector size boundary unmatched, file name=aa....aa, HiRDB file record size=bb....bb, HiRDB file system area sector size=cc....cc

HiRDB file aa....aa could not be stored because the record length of the HiRDB file and the sector length of the HiRDB file system area do not match. The record length of the HiRDB file is bb....bb and the sector length of the HiRDB file system area is cc....cc.

aa....aa: HiRDB file name

bb....bb: Record length of the HiRDB file

cc....cc: Sector length of the HiRDB file system area

S: Continues processing.

Action

Initialize the HiRDB file system area specifying the sector length so the record length is a multiple of the sector length, and then re-execute the command.

KFPI21516-E E+L

Unable to aa....aa : Not owner

In UNIX:
The user executing the command is not a superuser or the owner of the HiRDB file system area. Therefore, the user cannot back up, restore, or repair the HiRDB file system area.
In Windows:
The user executing the command is not the owner of the HiRDB file system area. Therefore, the user cannot back up, restore, or repair the HiRDB file system area.

aa....aa: Processing type { "backup"|"restore"|"repair" }

S: Terminates processing.

O: Take the following action:

In UNIX:

Re-execute as a superuser or the owner of the HiRDB file system area.

In Windows:

Re-execute as the owner of the HiRDB file system area.

KFPI21517-W E+L

Unable to backup because I/O error occurred, file name=aa....aa

HiRDB file aa....aa cannot be backed up because an I/O error occurred.

aa....aa: HiRDB file name

S: Terminates processing.

O: Take action appropriate to the error message for the file involved in the backup processing and re-execute the backup or recovery command.

KFPI21518-E E+L

File aa....aa not backup file

Specified file aa....aa is not a backup file.

aa....aa: Backup file name

If the name of the backup file exceeds 148 characters, the last 148 characters of the backup file name are output.

S: Terminates processing.

O: Specify the correct backup file and re-execute the command.

KFPI21519-E E+L

HiRDB file aa....aa not found in backup file

Specified HiRDB file aa....aa was not found in the backup file.

aa....aa: HiRDB file name

S: Terminates processing.

O: Check the name of the HiRDB file or backup file and re-execute the command.

KFPI21527-E E+L

HiRDB file system area aa....aa locked in other process, pid=bb....bb

Indicated HiRDB file system area cannot be initialized because it is being used by another process.

aa....aa: Name of the HiRDB file system area

If the name of the HiRDB file system area exceeds 117 characters, the last 117 characters of the HiRDB file system area name are output.

bb....bb: ID of the process locking the HiRDB file system area

For UNIX HiRDB servers, either the locked process ID or -1 is displayed. For Windows HiRDB servers, -1 is displayed.

When -1 is displayed, it indicates the locked process exists but the process ID could not be fetched.

S: Terminates abnormally.

Action

Take one of the following actions:

Wait for the process using the HiRDB file system area to terminate, and then re-execute.

If HiRDB is running, terminate, and then restart HiRDB. If HiRDB is currently shutting down, wait for other commands manipulating HiRDB files in the HiRDB file system area to terminate, and then re-execute the process.

KFPI21528-E E+L

HiRDB file system area aa....aa locked by other process, PID=bb....bb

HiRDB file system area aa....aa is locked by another process (bb....bb).

aa....aa: Name of the HiRDB file system area

If the name of the HiRDB file system area exceeds 148 characters, the last 148 characters of the HiRDB file system area name are output.

bb....bb: ID of the process locking the HiRDB file system area

For UNIX HiRDB servers, either the locked process ID or -1 is displayed. For Windows HiRDB servers, -1 is displayed.

When -1 is displayed, it indicates the locked process exists but the process ID could not be fetched.

S: Terminates processing.

O: Wait until the process that locked the HiRDB file system area terminates and re-execute.

pdfrstr command:

If HiRDB is operating, stop HiRDB and re-execute the command. When stopping HiRDB, wait for other commands that operate on the HiRDB file system area to be completed, and then re-execute the command.

KFPI21529-W E+L

HiRDB file aa....aa locked by other process, PID=bb....bb

HiRDB file aa....aa cannot be backed up because it is locked by another process (bb....bb).

aa....aa: HiRDB file name

bb....bb: ID of the process locking the HiRDB file system area

For UNIX HiRDB servers, either the locked process ID or -1 is displayed. For Windows HiRDB servers, -1 is displayed.

When -1 is displayed, it indicates the locked process exists but the process ID could not be fetched.

S: Resumes processing.

O: Wait for the process that is locking the HiRDB file to terminate, and then re-execute.

For restoration command:

When HiRDB is operating, stop HiRDB and re-execute the command.

When HiRDB has stopped, wait until another command that is manipulating the HiRDB file terminates and re-execute the command.

For backup command:

Specify the -f option and re-execute the command.

KFPI21530-Q S

HiRDB file system area aa....aa already exist. [G:continue, T:terminate]

Asks the operator whether or not the specified HiRDB file system area is to be initialized.

aa....aa: Name of the HiRDB file system area

If the name of the HiRDB file system area exceeds 117 characters, the last 117 characters of the HiRDB file system area name are output.

S: Waits for the operator's response.

O: Enter one of the following:

G: Resume processing

T: Terminate processing

KFPI21531-E E+L

No more space or partition size over in HiRDB file system area aa....aa

The HiRDB file system area could not be created due to one of the following causes:

If regular files are used, the amount of space specified in the -n option could not be allocated.

If character special files are used in UNIX, or if direct disk access (raw I/O) is used in Windows, the amount of space specified in the -n option exceeds the amount specified for the HiRDB file system area.
If the HDP facility is used, when the specified file was assigned to an actual volume in the DP pool, it became inaccessible due to a problem such as a shortage of space in the DP pool.

The management area size of the HiRDB file system area exceeds the amount of space specified in the -n option.

If a device, such as a DVD-RAM device, was used to handle media with a physical sector length of 2,048 bytes or 4,096 bytes, then the -s option was not specified, or the correct value was not specified.

aa....aa: Name of the HiRDB file system area

If the name of the HiRDB file system area exceeds 117 characters, the last 117 characters of the HiRDB file system area name are output.

S: Terminates processing.

O: Check and, if necessary, revise the following items, and then re-execute the pdfmkfs command.

In UNIX:

If regular files are used, either set the limit value of the system resources for the HiRDB administrator and root user to a value greater than that specified for the -n option, or set it to have no limit.

In AIX, take corrective action according to Notes about the /etc/security/limits file specification values under Estimating AIX OS parameter values in the HiRDB Version 9 Installation and Design Guide.

Reduce the space to be initialized to a size that can be allocated.

Specify an appropriate size character special file.

Delete other files from the OS file system.

If the HDP facility is used, make sure that there is no problem with the DP pool. If a problem has occurred, see the documentation for the HDP facility and take the corrective action specified there.

For the value of the -n option, specify the amount obtained by adding the management area size to the space allocated to the HiRDB file. For details about the management area size, see Size of management area for a HiRDB file system area under pdfmkfs (Initialize HiRDB file system area) in the manual HiRDB Version 9 Command Reference.

For devices, such as DVD-RAM devices, that handle media with a physical sector length of 2,048 bytes or 4,096 bytes, specify the -s option correctly.

In Windows:

Reduce the space to be initialized to a size that can be allocated.

For the value of the -n option, specify the amount obtained by adding the management area size to the space allocated to the HiRDB file. For details about the management area size, see Size of management area for a HiRDB file system area under pdfmkfs (Initialize HiRDB file system area) in the manual HiRDB Version 9 Command Reference.

KFPI21532-E E+L

Unable to initialized : Not owner

In UNIX:

Because the executing user is not the super user or the owner of the HiRDB file system area, the HiRDB file system area cannot be initialized.

In Windows:

Because the executing user is not the owner of the HiRDB file system area, the user cannot initialize the HiRDB file system area.

S: Terminates processing.

O: Take the following action:

In UNIX:

Re-execute the command as the superuser or the owner of the HiRDB file system area.

In Windows:

Re-execute the command as the owner of the HiRDB file system area.

KFPI21533-E E+L

File name aa....aa not found

Specified HiRDB file was not found in the HiRDB file system area.

aa....aa: Name of HiRDB file

S: Terminates processing.

Action

Check the HiRDB file name and re-execute.

KFPI21534-E E+L

Invalid argument for aa operand in bb....bb command

Invalid argument was specified in operand aa of command bb....bb.

aa: Operand name

bb....bb: Command name

S: Terminates processing.

O: Correct the operand argument and re-execute.

KFPI21536-E E+L

Mandatory argument missing

No argument was specified for an operand, or too many arguments were specified.

S: Terminates processing.

O: Correct the operand according to the usage in the message displayed immediately after this message and re-execute.

KFPI21537-E E+L

Invalid operand combination

A required operand is missing or a combination of operands is invalid.

S: Terminates processing.

O: Correct the operand according to the usage in the message displayed immediately after this message and re-execute.

KFPI21538-E E+L

Area_kind aaaa is not supported character_special_file in bb....bb command,HiRDB file system area=cc....cc

HiRDB file system area cc....cc specified in command bb....bb is a character special file. The HiRDB file system area cannot be created in a character special file for usage objective aaaa.

aaaa: Usage objective of the HiRDB file system area

bb....bb: Command name

cc....cc: HiRDB file system area name

If the name of the HiRDB file system area exceeds 117 characters, the last 117 characters of the HiRDB file system area name are output.

S: Terminates processing.

Action

Create the HiRDB file system area in a regular file, or check if the usage objective is correct.

KFPI21547-I E+L

aa....aa command terminated normally

Command aa....aa terminated normally.

aa....aa: Command name: { "pdfbkup"|"pdfrstr"|"pdffsck" | "pdfzeroinit" }

S: Resumes processing.

KFPI21548-W E+L

aa....aa command terminated with warning

Command aa....aa terminated with warning.

aa....aa: Command name: { "pdfbkup"|"pdfrstr"|"pdffsck" | "pdfzeroinit" }

S: Resumes processing.

O: Check the message output before this message. If there is a problem, terminate the processing corresponding to the previous message and re-execute.

KFPI21549-E E+L

aa....aa command terminated with error

Command aa....aa terminated because of an error, or a termination request was received from the user in response to an inquiry by a KFPI21514-Q or KFPI21558-I message.

aa....aa: Command name: { "pdfbkup"|"psfrstr"|"pdffsck" | "pdfzeroinit" }

S: Terminates processing.

O: If the user did not enter Stop, terminate processing on the basis of the message output before this message and re-execute.

KFPI21550-I E

Usage: pdfrm [-I] HiRDB_file_system_area_name/file_name

Displays the format of the pdfrm command that deletes a HiRDB file system. This message is output when a specified command option or argument is invalid.

S: Terminates processing.

O: Reenter the command specified correctly.

KFPI21551-I E

Usage: pdfstatfs [-c|d][-S] HiRDB_file_system_area_name

Displays the format of the pdfstatfs command that displays HiRDB file system area status. This message is output when a specified command option or argument is invalid.

S: Terminates processing.

O: Reenter the command specified correctly.

KFPI21552-Q S

aa....aa:?(y/n)

Asks the operator whether or not HiRDB file aa....aa is to be deleted.

aa....aa: Name of HiRDB file

S: Waits for the operator's response.

O: Enter one of the following:

y: Delete file

n: Do not delete file

KFPI21553-W E+L

File not restored, target HiRDB file was updated after backup, use -r option to force restore, HiRDB file name=aa....aa

A HiRDB file in the backup file has the same name as another file. The HiRDB file was not restored at the restoration destination because it had been updated after being backed up with the pdfbkup command. To force restoration, specify the -r option.

aa....aa: Name of HiRDB file

S: Resumes processing.

O: Check the HiRDB file name. If the HiRDB file must be restored, specify the -r option, then re-execute.

KFPI21554-W E+L

File not restored, HiRDB file already exists, HiRDB file name=aa....aa

The specified file cannot be restored because a file with the same file name already exists in the HiRDB file system area at the restoration destination.

aa....aa: Name of HiRDB file

S: Resumes processing.

O: Check the backup file and restoration destination file. If the file can be restored, specify the -r option and re-execute.

KFPI21555-E E+L

No HiRDB file in HiRDB file system area aa....aa

No HiRDB file was found in HiRDB file system area aa....aa. The pdfls or pdfstatfs command can be used to check whether or not an HiRDB file exists in the HiRDB file system area.

aa....aa: Name of the HiRDB file system area

If the name of the HiRDB file system area exceeds 117 characters, the last 117 characters of the HiRDB file system area name are output.

S: Terminates processing.

O: Check the specified HiRDB file system area and re-execute.

KFPI21556-E E+L

Invalid or too long backup file name aa....aa

The name of the specified backup file contains an invalid character, or the length of the backup file name exceeds the maximum length. For details on how to specify file names, see the HiRDB Version 9 Command Reference.

aa....aa: Backup file name

If the name of the backup file exceeds 148 characters, the last 148 characters of the backup file name are output.

S: Terminates processing.

O: Specify the correct backup file name and re-execute.

KFPI21557-I E

Usage: pdffsck [-c] HiRDB_file_system_area_name

This message shows how to perform an integrity check on the HiRDB file system area or how to use a repair command; it is output when there is an error in a command option or argument.

S: Terminates processing.

O: Revise the command format, and re-execute the command.

KFPI21558-I L+S

HiRDB file system area aa....aa consistent.

There is no integrity error in the specified HiRDB file system area (no repair needed).

aa....aa: HiRDB file system area name

If the HiRDB file system area name is 118 characters or longer, the last 117 characters of the HiRDB file system area name are output.

S: Terminates processing.

KFPI21559-W L+S

HiRDB file system area aa....aa inconsistent.

An integrity error occurred in the specified HiRDB file system area (needs to be repaired).

aa....aa: HiRDB file system area name

If the HiRDB file system area name is 118 characters or longer, the last 117 characters of the HiRDB file system area name are output.

S: Continues processing.

O: The HiRDB file system area is not repaired if the -c option is specified in the pdffsck command. Therefore, re-execute the pdffsck command without specifying the -c option.

KFPI21560-I L+S

HiRDB file system area aa....aa repair complete.

The repair of the specified HiRDB file system area was completed.

aa....aa: HiRDB file system area name

If the HiRDB file system area name is 118 characters or longer, the last 117 characters of the HiRDB file system area name are output.

S: Terminates processing. Waits for a response.

KFPI21561-E L

I/O error occurred, HiRDB file system area aa....aa.

An I/O error occurred in the indicated HiRDB file system area.

aa....aa: HiRDB file system area name

If the HiRDB file system area name is 118 characters or longer, the last 117 characters of the HiRDB file system area name are output,

S: If the operation can be continued, continues processing. If the operation cannot be continued, terminates HiRDB abnormally.

Action

Take action according to the KFPO00107-E message that was output before this message. For details about how to take corrective action after resolving an error in the HiRDB file system area or in a HiRDB file, see the manual HiRDB Version 9 System Operation Guide.

KFPI21562-E L

HiRDB file system area aa....aa access skipped because I/O error had already occurred.

Access to a HiRDB file system area where an I/O error occurred was skipped.

aa....aa: HiRDB file system area name

If the HiRDB file system area name is 118 characters or longer, the last 117 characters of the HiRDB file system area name are output.

S: If the operation can be continued, continues processing. If the operation cannot be continued, terminates HiRDB abnormally.

Action

Take action according to the KFPI21561-E message that was output before this message.

KFPI21570-E E+L

Version unmatch in HiRDB file systemarea aa....aa, version : bbbbbbb

The HiRDB file system area version is newer than the HiRDB version.

aa....aa: Name of the HiRDB file system area

If the name of the HiRDB file system area exceeds 117 characters, only the last 117 characters of the name of the HiRDB file system area are output.

bbbbbbb: Version number of the HiRDB file system area

S: Terminates processing.

Action

Confirm that HiRDB is correctly assembled, and re-execute. Or, confirm that the HiRDB execution path is correct, and re-execute.

KFPI21571-E E+L

HiRDB file system area aa....aa permission denied

In UNIX:

The user does not have access privilege (specified by the chmod OS command) for HiRDB file system area aa....aa.

In Windows:

The user does not have access privilege (specified in the file properties) for HiRDB file system area aa....aa.

aa....aa: Name of the HiRDB file system area

If the name of the HiRDB file system area exceeds 117 characters, only the last 117 characters of the name of the HiRDB file system area are output.

S: Terminates processing.

Action

In UNIX, use the chmod OS command to change the access privilege for the HiRDB file system area. In Windows, use the file properties to change the access privilege, or re-execute the command as a user with the necessary access privilege.

If Real Time SAN replication with the log-only synchronous method is used, and if the pdbkup command is used at a log application site to create a synchronization point dump file for log application processing and a status file for log application processing, execute the command by specifying the -f option. This is necessary because the HiRDB file system area where the target synchronization point dump file for transaction processing and the status file for transaction processing are stored is in a paired status with a transaction site, and the user does not have write privilege for it.

KFPI21572-E E+L

Too many open files on HiRDB file system area aa....aa

The maximum number of files that can be opened in HiRDB file system area aa....aa has already been reached.

aa....aa: Name of the HiRDB file system area

If the name of the HiRDB file system area exceeds 117 characters, only the last 117 characters of the name of the HiRDB file system area are output.

S: Terminates processing.

Action

Take the following action:

In UNIX:

Re-execute after another process has terminated. Or, change the maximum number of files that can be opened (nfiles) with Kernel Configuration of the sam system command, reconstruct the system, then re-execute.

In Windows:

Wait until the other process has terminated, and then re-execute the command.

KFPI21573-E E+L

HiRDB file system area aa....aa not found

Specified HiRDB file system area was not found or the specified HiRDB file system area name is invalid.

aa....aa: Name of the HiRDB file system area

If the name of the HiRDB file system area exceeds 117 characters, only the last 117 characters of the name of the HiRDB file system area are output.

S: Terminates processing.

O: Specify the correct HiRDB file system area name and re-execute.

KFPI21574-E E+L

Invalid or too long HiRDB file system area name aa....aa

The name specified for the HiRDB file system area contains an invalid character.

The name of the HiRDB file system area is too long.

A non-existent directory is specified in the name of the HiRDB file system area specified in the pdfmkfs command.

aa....aa: Name of the HiRDB file system area

If the name of the HiRDB file system area exceeds 117 characters, only the last 117 characters of the name of the HiRDB file system area are output.

For details about the characters that can be specified, see Syntax element conventions and Notes on Windows path names in the manual HiRDB Version 9 Command Reference.

S: Terminates processing.

O: Specify the correct HiRDB file system area name and re-execute.

KFPI21575-E E+L

Invalid file type on aa....aa

Specified file aa....aa is neither a character special file nor a regular file.

aa....aa: Name of the HiRDB file system area

If the name of the HiRDB file system area exceeds 117 characters, only the last 117 characters of the name of the HiRDB file system area are output.

S: Terminates processing.

O: Specify a character special file or regular file and re-execute.

KFPI21576-E E+L

File aa....aa not HiRDB file system area

Specified file aa....aa is not a HiRDB file system area.

aa....aa: Name of specified file

If the name of the specified file exceeds 117 characters, only the last 117 characters of the name of the HiRDB file system area are output.

S: Terminates processing.

O: Specify the correct HiRDB file system area name and re-execute.

KFPI21577-I E+L

pdfzeroinit initialization processing, aa....aa (bb....bb%) complete

aa....aa kilobytes (bb....bb%) of the used space has been initialized.

aa....aa: Size of the used space that has been initialized (KB)

bb....bb: Percentage of the used space that has been initialized (truncated at the decimal point)

S: Continues processing.

KFPI21578-E E+L

Insufficient lock segment for HiRDB file system area

The fcntl system call used for lock processing of the HiRDB file system area exceeded the maximum lock value.

S: Terminates processing.

O: Take the following action:

In UNIX:

Change nflocks with Kernel Configuration of the sam system command, reconstruct the system, then re-execute. Or, re-execute after the other process using the lock has terminated.

In Windows:

Wait until lock processing has terminated, and then re-execute the command.

KFPI21580-E E+L

Control black was destroyed, HiRDB file system area=aa....aa

Management information for a HiRDB file system area has been damaged.

aa....aa: Name of HiRDB file system area

If the name of the HiRDB file system area exceeds 117 characters, only the last 117 characters of the name of the HiRDB file system area are output.

S: Terminates processing.

O: Recover the HiRDB file system area from its backup copy and re-execute.

KFPI21581-E E+L

I/O error occurred, file_name=aa....aa

An I/O error occurred in file aa....aa.

aa....aa: Name of the HiRDB file or name of the backup file

For the HiRDB file name, only the HiRDB file name itself is output, and for the backup file name, the absolute path of the backup file name is output. Moreover, if the name of the file exceeds 148 characters, the last 148 characters are output.

S: Terminates processing.

O: See the error number (errno) displayed in the KFPO00107-E message output before this message and take appropriate action. If no KFPO00107-E message is output, the output destination of the file has a memory shortage.

KFPI21582-E E+L

Insufficient memory on PROCESS, size=aaaaa

A shortage occurred in the process private area.

aaaaa: Requested size (in bytes)

S: Terminates processing.

Action

Terminate an unneeded process and re-execute.

KFPI21583-E E+L

I/O error occured, HiRDB file system : aa....aa

An I/O error occurred in the management area for HiRDB file system area aa....aa.

aa....aa: Name of the HiRDB file system area

If the name of the HiRDB file system area exceeds 117 characters, only the last 117 characters of the name of the HiRDB file system area are output.

S: Terminates processing.

O: Take appropriate action on the basis of the errno displayed in the KFPO00107-E message that was issued before this message.

KFPI21584-E E+L

Specification of aa option required in bb....bb command

Specify the aa option to execute command bb....bb.

aa: Option name

bb....bb: Command name

S: Terminates processing.

Action

Specify option aa, and then re-execute the command.

KFPI21585-E E+L

Control block was destroyed and recovery impossible, HiRDB file system area=aa....aa.

Management information for a HiRDB file system area has been damaged; the area cannot be restored.

aa....aa: HiRDB file system area name

If the HiRDB file system area name is 118 characters or longer, the last 117 characters of the HiRDB file system area name are output.

S: Continues processing.

O: Refer to the section on how to resolve errors in a HiRDB file system area in the manual HiRDB Version 9 System Operation Guide.

KFPI21586-W E+L

Unusable HiRDB file exists.

A HiRDB file that is not referenced by management information for the HiRDB file system area exists.

S: Continues processing.

O: Restore the file by executing the pdffsck command without the -c option.

KFPI21587-I E

Usage: pdfzeroinit HiRDB_file_system_area_name

This message shows the format of the pdfzeroinit command. It is output when the command was specified incorrectly.

S: Terminates processing.

Action

Check the command format and re-execute the command.

KFPI21588-W E

aa....aa HiRDB file exist in HiRDB file system area bb....bb

Initialization of used space was not performed because there are HiRDB files in the HiRDB file system area.

aa....aa: Number of HiRDB files in the HiRDB file system area

bb....bb: Name of the HiRDB file system area

If the name of the HiRDB file system area exceeds 117 characters, only the last 117 characters of the name of the HiRDB file system area are output.

S: Terminates processing.

Action

Execute the pdfstatfs -d command to make sure that there are no HiRDB files in the HiRDB file system area. For details, see the HiRDB Version 9 System Operation Guide.

KFPI21589-I E+L

pdfzeroinit initialization start, HiRDB file system area=aa....aa, size=bb....bb

Initialization of used space in the HiRDB file system area has started.

aa....aa: Name of the HiRDB file system area

If the name of the HiRDB file system area exceeds 117 characters, only the last 117 characters of the name of the HiRDB file system area are output.

bb....bb: Size of the used space to be zero initialized (KB)

S: Continues processing.

KFPI21599-E E+L

Logical inconsistency occurred in aa....aa:bb....bb

An logical inconsistency error has occurred inside of the HiRDB file system.

aa....aa: Error detection information 1

bb....bb: Error detection information 2

S: Terminates processing.

O: Contact the HiRDB administrator.

Action

If KFPO00107-E was output immediately before this message, take the appropriate corrective action for that message. If KFPO00107-E was not output, contact the customer support center.

KFPI21600-E E+L

I/O error occurred, HiRDB file system:aa....aa

An I/O error occurred in HiRDB file system area aa....aa.

aa....aa: Name of the HiRDB file system area

If the name of the HiRDB file system area exceeds 117 characters, only the last 117 characters of the name of the HiRDB file system area are output.

S: Terminates processing.

Action

If KFPO00107-E was output immediately before this message, take the appropriate action based on the indicated errno. If KFPO00107-E was not output immediately before this message, re-execute the command.

KFPI21601-I E

HiRDB file system area aa....aa not initialized, due to no used area

HiRDB file system area aa....aa was not initialized for one of the following reasons:

It is already initialized.

There is no used space.

aa....aa: Name of the HiRDB file system area

If the name of the HiRDB file system area exceeds 117 characters, only the last 117 characters of the name of the HiRDB file system area are output.

S: Continues processing.

2.6 KFPJ messages

KFPJ00001-E A

System call error occurred. [aa....aa code:bb....bb]

An error occurred in a system call function.

aa....aa: Name of the system call function in which the error occurred

bb....bb: Error code returned by the GetLastError function

S: Terminates processing.

Action

Perform shutdown and re-execute. If this error recurs repeatedly, contact the customer support center.

KFPJ00002-E A

An abnormality occurred. [aa....aa Line:bb....bb]

An error occurred during Java application execution.

aa....aa: Name of the source file in which the error occurred

bb....bb: Line number where the error occurred

S: Terminates processing.

Action

Contact the customer support center.

KFPJ00003-E A

Memory became insufficient

A memory shortage occurred during Java application execution.

S: Terminates processing.

Action

Close other application programs and re-execute.

KFPJ00004-E A

Incorrect environment. Re-install.

The operating environment is invalid. Following are possible causes of this problem:

Installation was not terminated correctly.

An environment variable (registry) is invalid.

File does not exist or has been destroyed.

S: Terminates processing.

Action

Re-install the JDBC driver and re-execute.

KFPJ00005-E A

An error occurred during initialization.

An error occurred during initialization.

S: Terminates processing.

Action

If the cause of the definition error cannot be identified, delete the applicable definition file.

KFPJ00201-E A

The directory is invalid.

The directory is invalid. Following are possible causes of this problem:

Directory name specification is invalid

A nonexistent directory was specified

S: Terminates processing.

Action

Specify the correct directory name and re-execute.

KFPJ000202-E A

The numerical data is outside the range.

Numerical data that is not within the specifiable range of values was entered. Following are possible causes of this problem:

Non-numerical data (such as characters) was entered.

A double-byte character was entered.

Numerical data that is not within the specifiable range of values was entered.

S: Terminates processing.

Action

Check the specifiable range of values and re-enter the data.

KFPJ01001-E A

Memory became insufficient. [aa....aa]

A memory shortage occurred during allocation of an area needed for processing.

aa....aa: Maintenance information.

S: Terminates processing.

Action

Terminate other active processing, and then retry the operation. Alternatively, take the corrective action for an insufficient C heap, and then retry the operation.

KFPJ01002-E A

Sequence error occurred. [aa....aa]

The user's sequence of requests to the database was invalid.

aa....aa: Maintenance information

S: Rejects the request from the user.

Action

Check the request sequence to the database.

KFPJ01003-E A

System call error occurred. [aa....aa]

An error occurred in a system call.

aa....aa: Maintenance information

S: Terminates processing.

Action

Re-execute the operation. If this error recurs repeatedly, contact the customer support center.

KFPJ01004-I A

DBMS processing was canceled.

Database processing is being cancelled.

S: Cancels the database processing.

Action

Re-execute as necessary.

KFPJ01005-E A

A data attribute that is not supported was found. [aa....aa]

Specified table column attribute aa....aa cannot be used.

aa....aa: Code (in hexadecimal) of table column attribute that cannot be used.

S: Rejects the request from the user.

Action

Correct the table column attribute and re-execute the user's request. For information on column attribute codes, see the manual on the database at the connection destination.

KFPJ01007-E A

Not support tables containing multivalue columns and array columns.

A table containing a repetition column or array column cannot be used.

S: Rejects the request from the user.

Action

Correct the column attribute and re-execute the user's request.

KFPJ01013-E A

The permission identifier, password or DBMS information specified by the user exceeded 32 bytes.

Authorization identifier, password, or database information specified by the user was longer than 32 bytes.

S: Rejects the request from the user.

Action

Specify the authorization identifier, password, or database information as no more than 32 bytes.

KFPJ01017-E A TYPE4

Invalid table type, index=aa....aa, table type=bb....bb

An argument in the getTables method contains an error in the table type specified in a string type array.

aa....aa: Subscript of a string type array

bb....bb: Value of the specified table type

S: Terminates processing.

Action

Specify the correct table type, and then re-execute the command.

KFPJ01017-E A TYPE2

Incorrect table attribute. [aa....aa]

A table attribute specification is incorrect.

aa....aa: Error code

S: Rejects the request from the user.

Action

Correct the table attributes specification and re-execute. Check the following items, depending on the error code that is output:

If the error code is 1, check that the table attributes are enclosed in single quotation marks (').

If the error code is 2, check whether the specified table attributes are correct.

If the error code is 3, check whether the delimiter used between multiple table attributes is valid.

KFPJ01018-E A

Incorrect input parameter. [aa....aa]

An input parameter is incorrect.

aa....aa: Maintenance information

S: Rejects the request from the user.

Action

Specify the correct input parameter and re-execute.

KFPJ01019-E A

Incorrect output parameter. [aa....aa]

An output parameter is incorrect.

aa....aa: Maintenance information

S: Rejects the request from the user.

Action

Specify the correct output parameter and re-execute.

KFPJ01020-E A

Incorrect version of the DBMS. [aa....aa]

The database version cannot be connected.

aa....aa: Maintenance information

S: Rejects the request from the user.

Action

Contact the system administrator to verify the database version.

KFPJ01021-E A

Incorrect multiple SQL execution. [aa....aa]

The specification for executing multiple SQL statements is incorrect.

aa....aa: Maintenance information

S: Rejects the request from the user.

Action

Correct the specification for executing multiple SQL statements and re-execute.

KFPJ01025-E A

Not prepared to connect to HiRDB. [aa....aa]

The environment for connecting to HiRDB is not ready.

aa....aa: Maintenance information

S: Rejects the request from the user.

Action

Check the application to ensure that an access request is issued after OTS initialization is completed.

KFPJ01060-E A

An XA request error occurred.

An error occurred in an XA request.

S: Rejects the request from the user.

Action

Refer to the manual for the connected database.

KFPJ01070-E A

Object is null. (aa....aa) [function: bb....bb]

No object has been created.

aa....aa: Class name of the object for which the error occurred

bb....bb: Name of the function in which the error occurred

S: Passes jdbInternalException to the calling class.

Action

Create an object and re-execute.

KFPJ01071-E A

Object is not instance of aa....aa. [function: bb....bb]

The object is not an instance of the class specified by the class name.

aa....aa: Class name of the object for which the error occurred

bb....bb: Name of the function in which the error occurred

S: Passes jdbInternalException to the calling class.

Action

Create an instance of an appropriate class and re-execute.

KFPJ01072-E A

Array length is too short. (aa....aa) [function: bb....bb]

The necessary number of array elements has not been generated.

aa....aa: Name of the array in which the error occurred

bb....bb: Name of the function in which the error occurred

S: Passes jdbInternalException to the calling class.

Action

Generate the necessary number of array elements and re-execute.

KFPJ01073-E A

Array is null. (aa....aa) [function: bb....bb]

No array has been generated.

aa....aa: Name of the array in which the error occurred

bb....bb: Name of the function in which the error occurred

S: Passes jdbInternalException to the calling class.

Action

Generate an array and re-execute.

KFPJ01074-W A TYPE4

Warning is occurred. [aaaaaaaaaa]

A warning occurred in the connection destination database.

aaaaaaaaaa: Warning code (warning codes set in logical OR)

0x00000001:

A warning occurred

0x00000002:

A truncated value was received during data retrieval.

0x00000004:

A null value was ignored in the processing of a set function.

0x00000010:

UPDATE and DELETE statements without the WHERE clause were executed.

0x00000080:

A repetition column with a subscript was specified in the SET or DELETE clause of an UPDATE statement, but the update was ignored because the row to be updated does not contain any elements.

0x00000400:

The result of a data operation was a nonexistent date. The result was changed to the last day of the month.

0x00000800:

Either an overflow or a division by zero occurred during execution of an SQL statement. The result of the operation was set as a null value.

0x00001000:

The result of a date operation was a day outside the 00 to 99 range.

S: Continues processing.

Action

Verify the cause of the warning, and take action as necessary.

To resolve a 0x00000002 warning code, review the following specification values:

Value of the property HiRDB_for_Java_MAXBINARYSIZE assigned from the DriverManager class during connection

Value specified in the setMaxBinarySize method of the DataSource class

Value specified in the setMaxBinarySize method of the ConnectionPoolDataSource class

Value specified in the setMaxBinarySize method of the XADataSource class

KFPJ01074-W A TYPE2

A warning is occurred. [aa....aa]

A warning has been issued at the connected database.

aa....aa: Warning code (which is set based on an OR operation)

0x00000001:

A warning has been issued.

0x00000002:

A truncated value was received in a character data search because the embedded variable for receiving the data was too short.

0x00000004:

A null value was ignored in processing a set function.

0x00000008:

The number of columns in the search results does not match the number of embedded variables for receiving those search results.

0x00000010:

An UPDATE or DELETE statement without a WHERE clause was executed.

0x00000040:

A transaction was cancelled implicitly.

0x00000080:

A repetition column with a subscript was specified for the SET or DELETE clause of an UPDATE statement, but the updating was ignored because the row to be updated has no elements in it.

0x00000400:

The result of a date calculation was a nonexistent date, so it was adjusted to the last day of the month.

0x00000800:

Because overflow or division by zero occurred during execution of an SQL statement computation, the computation result was set to the null value.

0x00001000:

In the result of a date calculation, the day portion in the days interval fell outside the range 00 to 99.

S: Sets an SQLWarning.

Action

Take the appropriate action for the particular warning and re-execute.

KFPJ02001-E A

Not found environment definition file. [aa....aa]

The operating environment definition file was not found in the HiRDB directory.

aa....aa: Name of the operating environment definition file

S: Terminates processing.

Action

Create an operating environment definition file in the HiRDB directory.

KFPJ02002-E A

Incorrect environment definition. [aa....aa]

The value of an environment variable that was set in the operating environment definition file was incorrect.

aa....aa: Environment variable name

S: Terminates processing.

Action

Correct the value of the environment variable in the operating environment definition file.

KFPJ02003-E A

Incorrect environment definition. LINE= aa....aa [bb....bb]

One of the following errors was detected:

Syntax of the operating environment definition file was incorrect.

Value of an environment variable that was set in the operating environment definition file is incorrect.

aa....aa: Row in which the error occurred

bb....bb: Definition in which the error occurred

S: Terminates processing.

Action

Correct the operating environment definition file.

KFPJ02004-E A

Not installed.

One of the following errors was detected:

JDBC driver has not been installed.

JDBC driver installation environment is invalid.

S: Cancels processing.

Action

Reinstall the JDBC driver.

KFPJ02005-E A

System call error occurred. [aa....aa]

An error occurred in a system call.

aa....aa: Maintenance information

S: Cancels processing.

Action

If the cause can be determined from the error code (errno), correct the error. If the cause cannot be determined, contact the customer support center.

KFPJ02006-E A

System call error occurred. [aa....aa]

An error occurred in a system call.

aa....aa: Maintenance information

S: Cancels processing.

Action

If the cause can be determined from the error code (errno), correct the error. If the cause cannot be determined, contact the customer support center.

KFPJ02007-E A

Unable to open message file. [aa....aa]

The message log file cannot be opened.

aa....aa: Maintenance information

S: Continues processing. Subsequent outputs of this message consist of the message ID only without the message text.

Action

Because the operation environment has been destroyed, reset the HiRDB environment.

KFPJ02008-E A

System call error occurred during output of aa....aa [bb....bb]

A system call error occurred during message log output.

aa....aa: Name of the message log file

bb....bb: Maintenance information

S: Continues processing.

Action

If this error recurs repeatedly, contact the customer support center.

KFPJ02009-E A

Memory became insufficient. [aa....aa]

A shortage occurred in the memory needed for an operation.

aa....aa: Maintenance information

S: Terminates processing.

Action

Wait a while, then re-execute. If this error recurs repeatedly, contact the customer support center.

KFPJ02010-E A

Incorrect connection database definition. LINE= aa....aa [bb....bb]

One of the following errors was detected:

Syntax of connection destination database definition file is incorrect

A value in the connection destination database definition file is incorrect

aa....aa: Row in which the error occurred

bb....bb: Definition in which the error occurred

S: Terminates processing.

Action

Correct the connection destination database definition file.

KFPJ02011-E A

Not have authority to access the environment definition file. [aa....aa]

There is no access privilege for the operating environment definition file.

aa....aa: Name of the operating environment definition file

S: Terminates processing.

Action

Check whether or not the read privilege has been granted for the operating environment definition file. If not, assign the read privilege. If this error recurs repeatedly, contact the customer support center.

KFPJ02012-E A

Not have authority to access the connection database definition file. [aa....aa]

There is no access privilege for the connection destination database definition file.

aa....aa: Name of the connection destination database definition file

S: Terminates processing.

Action

Check whether or not the read privilege has been granted for the connection destination database definition file. If not, assign the read privilege. If this error recurs repeatedly, contact the customer support center.

KFPJ02013-E A

The database-type-name is duplicated. LINE= aa....aa [bb....bb]

The database type in the connection destination database definition file is duplicated.

aa....aa: Row in which the error occurred

bb....bb: Block name in which the error occurred

S: Terminates processing.

Action

Correct the value in the connection destination database definition file.

KFPJ02014-E A

The database-name is duplicated. LINE= aa....aa [bb....bb]

The database name in the connection destination database definition file is duplicated.

aa....aa: Row in which the error occurred

bb....bb: Block name in which the error occurred

S: Terminates processing.

Action

Correct the value in the connection destination database definition file.

KFPJ02015-E A

The [aa....aa] was not found. [bb....bb]

A required definition was not found in the block of the connection destination database definition file.

aa....aa: Name of the required definition

bb....bb: Block name of the definition

S: Terminates processing.

Action

Use a text editor, etc., to correct the connection destination database definition file.

KFPJ02016-E A

Incorrect Connection-Multi definition. LINE= aa....aa [bb....bb]

One of the following errors was detected:

Syntax of the Connection-Multi definition file is incorrect

A value in the Connection-Multi definition file is incorrect

aa....aa: Row in which the error occurred

bb....bb: Definition in which the error occurred

S: Terminates processing.

Action

Correct the Connection-Multi definition file.

KFPJ02017-E A

Not have authority to access the Connection-Multi file. [aa....aa]

There is no access privilege for the Connection-Multi definition file.

aa....aa: Name of the Connection-Multi definition file

S: Terminates processing.

Action

Check whether or not an access privilege has been granted for the Connection-Multi definition file. If not, assign an access privilege. If this error recurs repeatedly, contact the customer support center.

KFPJ02018-E A

The Connection-Multi-name is duplicated. LINE= aa....aa [bb....bb]

The Connection-Multi name in the Connection-Multi definition file is duplicated.

aa....aa: Row in which the error occurred

bb....bb: Block name in which the error occurred

S: Terminates processing.

Action

Correct the value in the Connection-Multi definition file.

KFPJ02019-E A

The directory was not found. Use the default directory. [aa....aa]

One of the following errors was detected:

The directory that was set in an environment variable in the operating environment definition file was not found or could not be used.

The directory that was set by the user in an environment variable was not found or could not be used.

aa....aa: Environment variable name

S: Ignores the directory specified in the environment variable and uses the default directory.

Action

Take one of the following actions:

Create the directory that was set in the environment variable.

Correct the value of the environment variable in the operating environment definition file.

Correct the value of the environment variable that was set by the user.

Use the environment setup utility to specify the correct directory.

KFPJ02020-E A

The directory was not found. [aa....aa]

One of the following errors was found:

The directory that was set in an environment variable in the operating environment definition file was not found or could not be used.

The directory that was set by the user in an environment variable was not found or could not be used.

aa....aa: Environment variable name

S: Terminates processing.

Action

Take one of the following actions:

Create the directory that was set in the environment variable.

Correct the value of the environment variable in the operating environment definition file.

Correct the value of the environment variable that was set by the user.

KFPJ04099-E A

Error occurred. (aa....aa)[bb....bb][cc....cc][dd....dd][ee....ee]

An error occurred.

aa....aa: Message ID

bb....bb: Message's variable information 0

cc....cc: Message's variable information 1

dd....dd: Message's variable information 2

ee....ee: Message's variable information 3

S: Terminates processing.

Action

Contact the customer support center.

KFPJ20002-E A TYPE4

Statement closed.

Processing cannot be accepted because the Statement instance is already closed.

S: Terminates processing.

Action

Re-create the Statement instance, and then re-execute the command.

KFPJ20002-E A TYPE2

Statement is closed.

Processing cannot be accepted because the Statement instance is already closed.

S: Passes SQLException to the calling class.

Action

Re-create the Statement instance and re-execute.

KFPJ20003-E A TYPE4

Failed character convert.

An error occurred during Unicode conversion of character data.

S: Terminates processing.

Action

Review the following specification values:

ENCODELANG value of the property specified during database connection

ENCODELANG value of the URL specified during database connection

setEncodeLang value of the connection information setup method

KFPJ20003-E A TYPE2

Failed character convert.

An error occurred during Unicode conversion of character data.

S: Passes SQLException to the calling class.

Action

The problem may be in the character string conversion library of the Java execution environment. Check that the Java execution environment, including the JDK version, is correct.

KFPJ20004-E A TYPE4

Unable to read java.io.Reader or java.io.InputStream

Unable to read from the java.io.Reader java.io.InputStream specified in the following methods for the PreparedStatement interface:

setAsciiStream

setCharacterStream

setUnicodeStream

setBinaryStream

S: Terminates processing.

Action

Review the specified java.io.Reader or java.io.InputStream.

KFPJ20004-E A TYPE2

Unable to read stream.

Reading from the input stream failed.

S: Passes SQLException to the calling class.

Action

Check the contents of the input stream specified by the setXXX method of the PreparedStatement class.

KFPJ20005-E A

Unable to write stream.

Writing to the output stream failed.

S: Passes SQLException to the calling class.

Action

Because a memory shortage may have occurred, close other applications and re-execute the UAP.

KFPJ20006-E A TYPE4

Connection closed

Processing cannot be accepted because the Connection instance is already closed.

S: Terminates processing.

Action

Re-create the Connection instance, and then re-execute the command.

KFPJ20006-E A TYPE2

Connection is closed.

Processing cannot be accepted because the Connection instance is already closed.

S: Passes SQLException to the calling class.

Action

Re-create the Connection instance and re-execute.

KFPJ20007-E A

Number format exception.

Because the data obtained from the database is not numerics, the data cannot be obtained with the getXXX method of the ResultSet class that was used.

S: Passes SQLException to the calling class.

Action

Use a getXXX method of the ResultSet class that corresponds to the data type.

KFPJ20008-E A

Set number is overflow to server.

Overflow occurred during conversion into the format at the mainframe of data specified by the setDouble method of the PreparedStatement class.

S: Passes SQLException to the calling class.

Action

Check the contents of the data specified by the setDouble method of the PreparedStatement class.

KFPJ20009-E A TYPE4

Not support method, method=aa....aa

Method aa....aa is unavailable, because it is not supported.

aa....aa: Method name

S: Terminates processing.

Action

Revise the UAP so that method aa....aa is not called.

KFPJ20009-E A TYPE2

Not support method. METHOD:aa....aa

Method aa....aa cannot be used.
aa....aa: Method name

S: Passes SQLException to the calling class.

Action

Correct so that the indicated method is not called.

KFPJ20010-E A TYPE4

Unable to execute batch SQL returned ResultSet or out parameters, SQL="aa....aa"

SQL statement aa....aa cannot be batch-processed, because it returns a result set or an output parameter.

aa....aa: SQL statement

S: Terminates processing.

Action

Review the specified SQL statement.

KFPJ20010-E A TYPE2

Unable to execute BATCH SQL returned ResultSet or OUT parameters. SQL:aa....aa

The aa....aa SQL cannot be executed in the batch mode because it returns a result set or an output parameter.

aa....aa: SQL statement

S: Passes BatchUpdateException to the calling class.

Action

Check the SQL statement.

KFPJ20011-E A TYPE4

Not support fetch direction, direction=aa....aa

Value aa....aa specified in the setFetchDirection method cannot be executed, because it is not supported. (Fetch directions other than ResultSet.FETCH_FORWARD cannot be used.)

aa....aa: Literal defined in the ResultSet value specified in the setFetchDirection method

{ResultSet.FETCH_REVERSE|ResultSet.FETCH_UNKNOWN}

(if the specified value is not defined in ResultSet, the value specified in the setFetchDirection method)

S: Terminates processing.

Action

Specify ResultSet.FETCH_FORWARD.

KFPJ20011-E A TYPE2

Not support fetch direction. Direction:aa....aa

aa....aa specified by the setFetchDirection method is invalid (a search direction other than ResultSet.FETCH_FORWARD cannot be used).

aa....aa: Value specified by the setFetchDirection method

S: Passes SQLException to the calling class.

Action

Specify ResultSet.FETCH_FORWARD.

KFPJ20012-E A TYPE4

Invalid fetch size, size=aa....aa

Value aa....aa of the argument specified in the setFetchSize method contains one of the following errors:

A negativevalue

If the value specified in the setMaxRows method is 1 or greater, the value specified in the setFetchSize method is greater than that specified in the setMaxRows method.

aa....aa: Value of the argument specified in the setFetchSize method

S: Terminates processing.

Action

Review the contents of the specified argument.

KFPJ20012-E A TYPE2

Invalid fetch size. SIZE:aa....aa

One of the following errors was detected in aa....aa of the argument specified by the setFetchSize method:

The argument is less than 0.

The value specified by the setFetchSize method is greater than the value specified by the setMaxRows method when the latter is greater than 1.

aa....aa: Argument contents specified by the setFetchSize method

S: Passes SQLException to the calling class.

Action

Check the contents of the specified argument.

KFPJ20013-E A

DBAccess version unmatch. VERSION-ID:aa....aa

The version of the database being accessed is obsolete.

aa....aa: Version code of the database being accessed

S: Passes SQLException to the calling class.

Action

Contact the customer support center.

KFPJ20014-E A TYPE4

Invalid "HiRDB_for_Java_SQL_IN_NUM" value, value=aa....aa

The value specified in the HiRDB_for_Java_SQL_IN_NUM property is invalid.

aa....aa: Value specified in HiRDB_for_Java_SQL_IN_NUM

S: Terminates processing.

Action

Review the following values:

Value specified in the HiRDB_for_Java_SQL_IN_NUM property during database connection

Value specified in the connection information setup method setSQLInNum

KFPJ20014-E A TYPE2

Invalid HiRDB_for_Java_SQL_IN_NUM. VALUE:aa....aa

The contents of the HiRDB_for_Java_SQL_IN_NUM property are invalid.

aa....aa: Contents specified for HiRDB_for_Java_SQL_IN_NUM

S: Throws an SQLException.

Action

Revise the following specified values:

Value specified for the HiRDB_for_Java_SQL_IN_NUM property during database connection

Value specified for the HiRDB_for_Java_SQL_IN_NUM system property during Java startup

Value specified for the setSQLInNum method to set connection information

KFPJ20015-E A TYPE4

Invalid "HiRDB_for_Java_SQL_OUT_NUM" value", value=aa....aa

The value specified in the HiRDB_for_Java_SQL_OUT_NUM property is invalid.

aa....aa: Value specified in HiRDB_for_Java_SQL_OUT_NUM

S: Terminates processing.

Action

Review the following values:

Value specified in the HiRDB_for_Java_SQL_OUT_NUM property during database connection

Value specified in the connection information setup method setSQLOutNum

KFPJ20015-E A TYPE2

Invalid HiRDB_for_Java_SQL_OUT_NUM. VALUE:aa....aa

The contents of the HiRDB_for_Java_SQL_OUT_NUM property are invalid.

aa....aa: Contents specified for HiRDB_for_Java_SQL_OUT_NUM

S: Throws an SQLException.

Action

Revise the following specified values:

Value specified for the HiRDB_for_Java_SQL_OUT_NUM property during database connection

Value specified for the HiRDB_for_Java_SQL_OUT_NUM system property during Java startup

Value specified for the setSQLOutNum method to set connection information

KFPJ20016-E A TYPE4

Invalid "HiRDB_for_Java_SQLWARNING_LEVEL" value, value="aa....aa"

The value specified in the HiRDB_for_Java_SQLWARNING_LEVEL property is invalid.

aa....aa: Value specified in HiRDB_for_Java_SQLWARNING_LEVEL

S: Terminates processing.

Action

Review the following values:

Value specified in the HiRDB_for_Java_SQLWARNING_LEVEL property during database connection

Value specified in the connection information setup method setSQLWarningLevel

KFPJ20016-E A TYPE2

Invalid HiRDB_for_Java_SQLWARNING_LEVEL. VALUE:aa....aa

The contents of the HiRDB_for_Java_SQLWARNING_LEVEL property are invalid.

aa....aa: Contents specified for HiRDB_for_Java_SQLWARNING_LEVEL

S: Throws an SQLException.

Action

Revise the following specified values:

Value specified for the HiRDB_for_Java_SQLWARNING_LEVEL property during database connection

Value specified for the setSQLWarningLevel method to set connection information

KFPJ20017-E A

Invalid HiRDB_for_Java_CLEAR_ENV VALUE:aa....aa

The contents of the HiRDB_for_Java_CLEAR_ENV property are invalid.

aa....aa: Contents specified for HiRDB_for_Java_CLEAR_ENV

S: Throws an SQLException.

Action

Revise the following specified values:

Value specified for the HiRDB_for_Java_CLEAR_ENV property during database connection

Value specified for CLEAR_ENV in the URL

Value specified for the setClear_Env method to set connection information

KFPJ20018-E A

aa....aa closed

Processing cannot be performed because instance aa....aa is closed.

aa....aa: {XAConnection|PooledConnection}

S: Terminates processing.

Action

Re-create the aa....aa instance, and then re-execute the command.

KFPJ20020-E A

java.io.InputStream or java.io.Reader already closed

The java.io.InputStream or the java.io.Reader is closed.

S: Terminates processing.

Action

Review the processing.

KFPJ20021-E A

Unable to use locator.reason aa....aa closed

The locator facility is unavailable because the Connection, Statement, or ResultSet instance is closed.

aa....aa: Class name

S: Terminates processing.

Action

Investigate the cause of an instance of class aa....aa closing, and review the processing.

KFPJ20022-E A

Unable to get unwrapped object,class=aa....aa

The object of the class specified in the unwrap method of the Wrapper interface could not be acquired.

aa....aa: Fully-specified name of the class specified as an argument to the unwrap method

S: Terminates processing.

P: After consulting Classes that can be specified in unwrap under Wrapper interface in the HiRDB Version 9 UAP Development Guide, specify an appropriate class.

KFPJ20023-E A

Unable to use Blob after free.

This object cannot be used because the free method has been called.

S: Terminates processing.

P: Check the location where the free method is called.

KFPJ20024-E A

Invalid directory aa....aa specified by PDTAAPINFPATH,reason=bb....bb

The output directory for the access path information file is invalid.

aa....aa: Specified directory path name

bb....bb: Cause of error

INVALID PATH: Path name is invalid

PERMISSION DENIED: Write privileges not granted

S: Terminates processing.

O:

When bb....bb is INVALID PATH:

Specify the path name of a directory that exists, and then retry the operation.

When bb....bb is PERMISSION DENIED:

Acquire the appropriate access privileges to the directory, and then retry the operation.

KFPJ20025-E A

File access failed,file=aa....aa,reason=bb....bb,method=cc....cc

An error occurred during file access.

aa....aa: Path name of the file for which the error occurred

bb....bb: Exception string of the java.io.IOException that occurred

cc....cc: Class and method in which the error occurred

S: Terminates processing.

O: Identify the cause of the error from the exception trace log, eliminate the cause of the error, and then retry the operation.

KFPJ20101-E A TYPE4

Unable to register Driver

Registration of the JDBC driver in the driver manager failed.

S: Terminates processing.

Action

The problem may be in the Java execution environment. Make sure the JRE version is correct.

KFPJ20101-E A TYPE2

Unable to register driver.

Registration into the driver manager failed.

S: Passes SQLException to the calling class.

Action

The problem may be in the JDBC interface library of the Java execution environment. Check that the Java execution environment, including the JDK version, is correct.

KFPJ20102-E A

Invalid protocol name.

The protocol name specified by the URL is invalid.

S: Passes SQLException to the calling class.

Action

Check the protocol name specified by the URL.

KFPJ20103-E A

Invalid subprotocol name.

The subprotocol name specified by the URL is invalid.

S: Passes SQLException to the calling class.

Action

Check the subprotocol name specified by the URL.

KFPJ20104-E A

Invalid host name.

The host name specified by the URL is invalid.

S: Passes SQLException to the calling class.

Action

Check the host name specified by the URL.

KFPJ20105-E A

Invalid port number.

The port number specified by the URL is invalid.

S: Passes SQLException to the calling class.

Action

Check the port number specified by the URL.

KFPJ20106-E A

Invalid DB.

The database type specified by the URL is invalid.

S: Passes SQLException to the calling class.

Action

Check the database type specified by the URL.

KFPJ20107-E A

Invalid DBID.

The additional connection information specified by the URL is invalid.

S: Passes SQLException to the calling class.

Action

Revise the additional connection information specified by the URL.

KFPJ20108-E A

Invalid DBENV.

The database definition information specified by the URL is invalid.

S: Passes SQLException to the calling class.

Action

Check the connection database definition information specified by the URL.

KFPJ20202-E A

Not support LangID. LangID:aa....aa

The language passed from the HiRDB client is not supported.
aa....aa: Language name

S: Passes SQLException to the calling class.

Action

Check the HiRDB client's language.

KFPJ20204-E A

Active statement over:

The number of statements that can be opened concurrently has exceeded the maximum.

S: Passes SQLException to the calling class.

Action

Close the instance of the Statement or ResultSet being used and re-execute.

KFPJ20205-E A TYPE4

Unable to use "aa....aa" method in XA connection

Method aa....aa being connected to XA is unavailable.

aa....aa: Method name

S: Terminates processing.

Action

Revise the UAP so that it will not call method aa....aa.

KFPJ20205-E A TYPE2

Current Connection is XA mode.
The method is invalid. METHOD:aa....aa

aa....aa method invocation is invalid because the current connection is in the XA mode.

aa....aa: Method name

S: Passes SQLException to the calling class.

Action

Prevent method aa....aa from being invoked.

KFPJ20206-W A TYPE4

Not support TYPE_SCROLL_SENSITIVE ResultSet type.Changed ResultSet type, ResultSet type=aa....aa

An updated, scrollable result set type cannot be used; therefore, the result set type was changed to aa....aa.

aa....aa: Result set type after the change

{TYPE_SCROLL_INSENSITIVE}

S: Continues processing.

KFPJ20206-W A TYPE2

Not support TYPE_SCROLL_SENSITIVE ResultSet type. Changed ResultSet type:aa....aa

An updated, scrollable result set type cannot be used; therefore, the result set type was changed to aa....aa.

aa....aa: Results set type after the change

S: Sets SQLWarning.

KFPJ20207-W A TYPE4

Not support CONCUR_UPDATABLE ResultSet concurrency.
Changed ResultSet concurrency, ResultSet concurrency=aa....aa

Updatable result sets are unavailable; therefore, the result set was changed to the parallel processing type of result set aa....aa.

aa....aa: Parallel processing type of the result set after the change

{CONCUR_READ_ONLY}

S: Continues processing.

KFPJ20207-W A TYPE2

Not support CONCUR_UPDATABLE ResultSet concurrency.
Changed ResultSet concurrency:aa....aa

Because an updatable results set could not be used, it was changed to results set aa....aa.

aa....aa: Results set after the change

S: Sets SQLWarning.

KFPJ20208-E A TYPE4

Invalid ResultSet type, type=aa....aa

The value aa....aa of the scroll type of the specified result set is an invalid scroll type not defined in ResultSet.

aa....aa: Value of the scroll type of the specified result set

S: Terminates processing.

Action

Review the scroll type of the result set.

KFPJ20208-E A TYPE2

Invalid ResultSet type. TYPE:aa....aa

Scroll type aa....aa of the specified results set is invalid.

aa....aa: Scroll type of the results set

S: Passes SQLException to the calling class.

Action

Check the scroll type of the results set.

KFPJ20209-E A TYPE4

Invalid ResultSet concurrency, concurrency=aa....aa

The value aa....aa of the parallel processing type of the specified result set is an invalid parallel processing type not defined in ResultSet.

aa....aa: Value of the parallel processing type of the specified result set

S: Terminates processing.

Action

Review the parallel processing type of the result set.

KFPJ20209-E A TYPE2

Invalid ResultSet concurrency. CONCURRENCY:aa....aa

Parallel processing type aa....aa of the specified results set is invalid.

aa....aa: Parallel processing type of the results set

S: Passes SQLException to the calling class.

Action

Check the parallel processing type of the results set.

KFPJ20210-E A TYPE4

Invalid escape syntax,code=aaaa

The specified SQL escape clause is invalid.

aaaa: Reason code

Reason code | Explanation
0001 | The escape clause contains a left curly bracket ({) and a keyword (d, t, ts, escape, oj, call, or fn), but there is no right curly bracket (}).
0002 | There is no procedure name after the call in the escape clause.
0003 | There is no space between the call and the procedure name in the escape clause.
0004 | There is no closing parentheses ()) following the call-procedure-name( specification in the escape clause.
0005 | ?=call is specified in the escape clause. This format is not supported by HiRDB.
0006 | No argument is specified after LOCATE in the escape clause.
0007 | An invalid function number was specified after LOCATE in the escape clause.
0008 | No argument is specified after LTRIM or RTRIM in the escape clause.

S: Terminates processing.

Action

Specify the correct escape clause.

KFPJ20210-E A TYPE2

Invalid Escape Syntax.

The specified SQL escape clause is invalid.

S: Passes SQLException to the calling class.

Action

Specify the correct SQL statement.

KFPJ20211-E A

No user Id.

An authorization identifier is not specified.

S: Passes SQLException to the calling class.

Action

Specify an authorization identifier.

KFPJ20212-E A TYPE4

Invalid aa....aa value, value="bb....bb"

The connection information specified in aa....aa is invalid.

aa....aa:

When the getConnection method of the DriverManager class is used

URL, or a user property specification

When a setXXX method of the DataSource, ConnectionPoolDataSource, or XADataSource class is used to set connection information

Name of the setXXX method

(Other than above)

System property specification

bb....bb: Value specified in aa....aa

S: Terminates processing.

Action

Review the connection information specified in aa....aa.

KFPJ20212-E A TYPE2

Invalid aa....aa. value:bb....bb

The connection information specified in aa....aa is invalid.

aa....aa:

When the getConnection method of the DriverManager class is used

URL, or a user property specification

When a setXXX method of the DataSource, ConnectionPoolDataSource, or XADataSource class is used to set connection information

Name of the setXXX method

bb....bb: Value specified in aa....aa.

S: Loads SQLException.

Action

Review the connection information specified in aa....aa.

KFPJ20213-E A

Invalid ResultSet holdability aa....aa

The value of retention facility aa....aa of the specified result set is an invalid retention facility not defined in the ResultSet class.

aa....aa: Value of the retention facility of the specified result set

S: Terminates processing.

Action

Review the value of the retention facility of the result set.

KFPJ20301-E A

Not support cancel.

Asynchronous cancellation cannot be used in the currently connected database.

S: Passes SQLException to the calling class.

Action

Do not use asynchronous cancellation.

KFPJ20302-E A TYPE4

Invalid max rows value, value=aa....aa

A negative value cannot be assigned to the maximum row search count specified in the setMaxRows method.

aa....aa: Value of the maximum row search count specified in the setMaxRows method

S: Terminates processing.

Action

Review the maximum row search count specified in the setMaxRows method.

KFPJ20302-E A TYPE2

Invalid max rows. MAX ROWS:aa....aa

The maximum number of rows to be searched, as specified by setMaxRows, is invalid.

aa....aa: Specification in setMaxRows of the maximum number of rows to be searched

S: Passes SQLException to the calling class.

Action

Check the value of the maximum number of rows to be searched.

KFPJ20303-E A TYPE4

Invalid SQL statement

The specified SQL statement is either a null value or a character string with a zero length.

S: Terminates processing.

Action

Specify the SQL statement correctly.

KFPJ20303-E A TYPE2

Invalid SQL statement.

The specified SQL statement is either a null value or a character string with a zero length.

S: Passes SQLException to the calling class.

Action

Specify the SQL statement correctly.

KFPJ20304-E A TYPE4

Invalid query timeout value, value=aa....aa

A negative value cannot be assigned to the timeout value specified in the setQueryTimeout method.

aa....aa: Timeout value specified in the setQueryTimeout method

S: Terminates processing.

Action

Review the timeout value specified in the setQueryTimeout method.

KFPJ20304-E A TYPE2

Unable to set timeout.

Setting of a timeout value failed.

S: Passes SQLException to the calling class.

Action

Check the timeout value.

KFPJ20305-E A TYPE4

Invalid max field size, size=aa....aa

A negative value cannot be assigned to the maximum field length specified in the setMaxFieldSize method.

aa....aa: Value of the maximum field length specified in the setMaxFieldSize method

S: Terminates processing.

Action

Review the value of the maximum field length specified in the setMaxFieldSize method.

KFPJ20305-E A TYPE2

Unable to set max field size.

Setting of the maximum field size failed.

S: Passes SQLException to the calling class.

Action

Check the maximum field size.

KFPJ20306-E A

Unable to perform executeQuery this SQL

This SQL statement cannot be executed in executeQuery.

S: Terminates processing.

P: In executeQuery, specify an SQL statement that returns a result set.

KFPJ20307-E A

Unable to perform executeUpdate this SQL

This SQL statement cannot be executed in executeUpdate.

S: Terminates processing.

P: In executeUpdate, specify an SQL statement that does not return a result set.

KFPJ20309-E A

Number of registration exceeded max entry

The number of batches registered exceeds the maximum limit: 2,147,483,647.

S: Terminates processing.

Action

Limit the number of batches registered to 2,147,483,647 or less.

KFPJ20401-E A

Not support boolean(SQL BIT) parameter.

A Boolean-type (SQL BIT type) parameter cannot be used.

S: Passes SQLException to the calling class.

Action

Do not use a Boolean-type (SQL BIT type) parameter.

KFPJ20402-E A

Not support byte(SQL TINYINT) parameter.

A byte-type (SQL TINYINT type) parameter cannot be used.

S: Passes SQLException to the calling class.

Action

Do not use a byte-type (SQL TINYINT type) parameter.

KFPJ20403-E A

Not support long(SQL BIGINT) parameter.

A long-type (SQL BIGINT type) parameter cannot be used.

S: Passes SQLException to the calling class.

Action

Do not use a long-type (SQL BIGINT type) parameter.

KFPJ20405-E A

Not support Object parameter.

An object-type parameter cannot be used.

S: Passes SQLException to the calling class.

Action

Do not use an object-type parameter.

KFPJ20406-E A

Not support Ref(SQL REF) parameter.

A ref-type (SQL REF type) parameter cannot be used.

S: Passes SQLException to the calling class.

Action

Do not use a ref-type (SQL REF type) parameter.

KFPJ20407-E A

Not support Array(SQL ARRAY) parameter.

An array-type (SQL ARRAY type) parameter cannot be used.

S: Passes SQLException to the calling class.

Action

Do not use an array-type (SQL ARRAY type) parameter.

KFPJ20408-E A

Not support NULL parameter for SQL STRUCT.

A NULL parameter cannot be used for the SQL STRUCT type.

S: Passes SQLException to the calling class.

Action

Do not use a NULL parameter for the SQL STRUCT type.

KFPJ20410-E A TYPE4

Not support this SQL type, type=aa....aa

A parameter of a data type for which the SQL type code defined in java.sql.Types is aa....aa cannot be assigned.

aa....aa: Literal defined in java.sql.Types having a specified SQL type code value

{java.sql.Types.ARRAY|java.sql.Types.BIGINT|java.sql.Types.BIT|java.sql.Types.BLOB|java.sql.Types.BOOLEAN|java.sql.Types.CLOB|java.sql.Types.DATALINK|java.sql.Types.DISTINCT|java.sql.Types.JAVA_OBJECT|java.sql.Types.NULL|java.sql.Types.OTHER|java.sql.Types.REF|java.sql.Types.STRUCT|java.sql.Types.TINYINT}

If the specified value is other than these SQL type code values, the specified SQL type code value.

S: Terminates processing.

Action

Do not specify aa....aa in an SQL type code.

KFPJ20410-E A TYPE2

Not support this SQL type. TYPE:aa....aa

A parameter of data type aa....aa cannot be set.

aa....aa: Data type

S: Passes SQLException to the calling class.

Action

Do not set a parameter of data type aa....aa.

KFPJ20411-E A TYPE4

Not set parameter, index=aa....aa

The aa....aath parameter has not been set.

aa....aa: Parameter's number

S: Terminates processing.

Action

Set the aa....aath parameter.

KFPJ20411-E A TYPE2

Not set parameter. INDEX:aa....aa

The aa....aath parameter has not been set.

aa....aa: Parameter's column number

S: Passes SQLException to the calling class.

Action

Set the aa....aath parameter.

KFPJ20412-E A TYPE4

Invalid parameter, code=aa(bb....bb)

A parameter is invalid.
The table below gives the reason code and option information:

Reason code | Option information | Meaning
01 | invalid length | A negative value cannot be assigned to a stream specified in the argument.

aa: Reason code {01}

bb....bb: Option information {invalid length}

S: Terminates processing.

Action

Review the value specified for this parameter, based on the option information given for the reason code.

KFPJ20412-E A TYPE2

Invalid parameter.

A parameter is invalid.

S: Passes SQLException to the calling class.

Action

Check the parameter.

KFPJ20413-E A TYPE4

Invalid parameter index, index=aa....aa

The value of the parameter index is invalid.

aa....aa: Value of the parameter index

S: Terminates processing.

Action

Review the value of the parameter index.

KFPJ20413-E A TYPE2

Invalid parameter index. INDEX:aa....aa

A parameter index is invalid.

aa....aa: Parameter index

S: Passes SQLException to the calling class.

Action

Check the parameter index.

KFPJ20414-E A

Not set parameter for batch.

No parameter for batch execution was specified in the invocation of the addBatch method.

S: Passes SQLException to the calling class.

Action

Correct so that the addBatch method is invoked after a batch execution parameter is set by the setXXX method.

KFPJ20415-E A

Not support Blob(SQL BLOB) parameter.

A blob-type (SQL BLOB type) parameter cannot be used.

S: Passes SQLException to the calling class.

Action

Do not use a blob-type (SQL BLOB type) parameter.

KFPJ20416-E A

Not support Clob(SQL CLOB) parameter.

A Clob-type (SQL CLOB type) parameter cannot be used.

S: Passes SQLException to the calling class.

Action

Do not use a clob-type (SQL CLOB type) parameter.

KFPJ20417-E A TYPE4

Unable to convert object to SQL type, object="aa....aa", SQL type="bb....bb"

The object aa....aa specified in the setObject method cannot be converted to a data type whose SQL type code defined in java.sql.Types is bb....bb.

aa....aa: Name of the specified object

Outputs one of the following character strings:

Byte

Short

Integer

Long

Float

Double

BigDecimal

Boolean

String

byte[]

Date

Time

Timestamp

Array

Blob

Clob

Ref

Struct

If these objects are not applicable, outputs the character string that is output to x.getClass().getName() (where x denotes the object specified in the setObject method).

bb....bb: Literal defined in java.sql.Types having a specified SQL type code value.

Outputs one of the following character strings:

java.sql.Types.ARRAY

java.sql.Types.BIGINT

java.sql.Types.BINARY

java.sql.Types.BIT

java.sql.Types.BLOB

java.sql.Types.BOOLEAN

java.sql.Types.CHAR

java.sql.Types.CLOB

java.sql.Types.DATALINK

java.sql.Types.DATE

java.sql.Types.DECIMAL

java.sql.Types.DISTINCT

java.sql.Types.DOUBLE

java.sql.Types.FLOAT

java.sql.Types.INTEGER

java.sql.Types.JAVA_OBJECT

java.sql.Types.LONGVARBINARY

java.sql.Types.LONGVARCHAR

java.sql.Types.NULL

java.sql.Types.NUMERIC

java.sql.Types.OTHER

java.sql.Types.REAL

java.sql.Types.REF

java.sql.Types.SMALLINT

java.sql.Types.STRUCT

java.sql.Types.TIME

java.sql.Types.TIMESTAMP

java.sql.Types.TINYINT

java.sql.Types.VARBINARY

java.sql.Types.VARCHAR

unidentified type#1

SQL code value#2

#1: If an SQL type code value is not specified in the setObject method, the SQL type code value is unidentified type.

#2: If the specified value is other than the SQL type code values listed in the table, the SQL type code is the specified SQL code value.

S: Terminates processing.

Action

Specify a convertible SQL type, or specify an object associated with the SQL type.

KFPJ20417-E A TYPE2

Model of the JAVA_OBJECT is not able to be transformed to SQL type.

JAVA_OBJECT cannot be transformed to the specified SQL type.

S: Passes SQLException to the calling class.

Action

Specify a transformable SQL type, or specify a JAVA_OBJECT that corresponds to the SQL type.

KFPJ20418-E A

Invalid object type of value of an array parameter.

The object type of the value specified in the repetition column parameter is invalid.

S: Throws an SQLException.

Action

Specify an SQL type that can be converted. Or, specify the JAVA_OBJECT that corresponds to the SQL type.

KFPJ20419-E A

Invalid precision of value of an array parameter.

The precision of the value specified in the repetition column parameter is invalid.

S: Throws an SQLException.

Action

Correct the precision of the value.

KFPJ20420-E A

Invalid value of an array parameter.

The value specified in the repetition column parameter is invalid.

S: Throws an SQLException.

Action

Correct the value.

KFPJ20421-E A

When determining precision or scale of value specified to be an array parameter, the arithmetic operation exception occurred.

Changing the precision or scale of value of the value specified in the repetition column parameter caused an arithmetic operation exception.

S: Throws an SQLException.

Action

Correct the value.

KFPJ20422-E A

When get data from array object, a throw of the java.sql.SQLException was carried out. TraceInfo = aa....aa

When data was obtained from an array object, a java.sql.SQLException was thrown.

aa....aa: Stack trace

S: Throws an SQLException.

Action

Determine the cause from the stack trace, and take appropriate action.

KFPJ20423-E A

Value of getBaseType method in Array object and object type of getArray method in Array object is not agreement.

The array element type returned by the array object is not in agreement with the format of the array element object.

S: Throws an SQLException.

Action

Make the array element type returned by the array object agree with the format of the array element object.

KFPJ20424-E A

Value of getBaseType method in Array object is not support.

The array element type returned by the array object is not supported.

S: Throws an SQLException.

Action

Use an array element type that is supported.

KFPJ20425-E A

Specified column is not an array column, so a getArray method of ResultSet class cannot be used.

The specified column is not a repetition column, so the getArray method of the ResultSet class cannot be used.

S: Throws an SQLException.

Action

Specify a getXXX method of the ResultSet class that is appropriate for the column's data type.

KFPJ20426-E A

Invalid number of index.

The index specified by java.sql.Array.getArray or java.sql.Array.getResultSet is invalid.

S: Throws an SQLException.

Action

Correct the index specified by java.sql.Array.getArray or java.sql.Array.getResultSet.

KFPJ20427-E A

Invalid number of start position.

The value of the start position specified by java.sql.Blob.getBytes or java.sql.Blob.position is invalid.

S: Throws an SQLException.

Action

Correct the start position specified by java.sql.Blob.getBytes or java.sql.Blob.position.

KFPJ20428-E A

Invalid number of length.

The value specified by java.sql.Blob.getBytes for the length of the operation is invalid.

S: Throws an SQLException.

Action

Correct the value specified by java.sql.Blob.getBytes for the length of the operation.

KFPJ20429-E A

Max length over of pattern data.

The size specified by java.sql.Blob.position of the byte array to be retrieved exceeds the maximum value.

S: Throws an SQLException.

Action

Correct the size specified by java.sql.Blob.position of the byte array to be retrieved.

KFPJ20430-E A TYPE4

Unable to adapt data to table definition

The number of digits in the integer portion of the specified data is greater than the number of digits in the integer portion of the table definition; therefore, the data cannot be converted to the data type in the table definition.

S: Throws an SQLException.

Action

Review the specified data.

KFPJ20430-E A TYPE2

Unable to adapt data to table definition

The number of digits in the integer portion of the specified data is greater than the number of digits in the integer portion of the table definition; therefore, the data cannot be converted to the data type in the table definition.

S: Terminates processing.

Action

Review the specified data.

KFPJ20431-E A TYPE4

Invalid data beside the range of table definition or unable to adapt, data type=aa....aa, parameter index=bb....bb

The data has a value outside the range of the conversion destination data type, or it is in a nonconvertible format.

aa....aa: Conversion destination data type

If the processing involves a conversion to the data type of the corresponding ? parameter, one of the following HiRDB data types:

{BINARY|BLOB|CHAR|DATE|DECIMAL|FLOAT|INTEGER|MCHAR|MVARCHAR|NCHAR|NVARCHAR|REAL|SMALLINT|TIME|TIMESTAMP|VARCHAR}

If the processing involves a conversion to the SQL data type of the JDBC driver specified in the setObject method, one of the following literals defined in java.sql.Types:

{java.sql.Types.BIGINT|java.sql.Types.DATE|java.sql.Types.DECIMAL|java.sql.Types.DOUBLE|java.sql.Types.FLOAT|java.sql.Types.INTEGER|java.sql.Types.NUMERIC|java.sql.Types.REAL|java.sql.Types.SMALLINT|java.sql.Types.TIME|java.sql.Types.TIMESTAMP|java.sql.Types.TINYINT}

bb....bb: Specified parameter index

S: Terminates processing.

Action

Review the data.

KFPJ20431-E A TYPE2

Data is the value besides the range of a column attribute or the form which cannot be used. DataType:aa....aa

The value of the data is outside the range for the column attribute or is in a format that cannot be used.

aa....aa: Table definition attribute

S: Throws an SQLException.

Action

Revise the data.

KFPJ20432-E A

Not support this parameter type, type=aa....aa, index=bb....bb

This setXXX method cannot be used on the data type of the ? parameter associated with the specified parameter index.

aa....aa: Data type of the parameter (HiRDB data type)

{BINARY|BLOB|CHAR|DATE|DECIMAL|FLOAT|INTEGER|MCHAR|MVARCHAR|NCHAR|NVARCHAR|REAL|SMALLINT|TIME|TIMESTAMP|VARCHAR}

bb....bb: Specified parameter index

S: Terminates processing.

Action

Use a setXXX method compatible with the data type of the parameter.

KFPJ20501-E A

CallableStatement is closed.

Processing cannot be accepted because the CallableStatement instance is already closed.

S: Passes SQLException to the calling class.

Action

Re-create the CallableStatement instance and re-execute.

KFPJ20502-E A TYPE4

Unable to get data, parameter index=aa....aa, data type=bb....bb

The specified ? parameter data cannot be obtained using the getXXX method of the CallableStatement class.

aa....aa: Parameter number

bb....bb: Parameter data type (HiRDB data type)

{ BINARY | BLOB | CHAR | DATE | DECIMAL | FLOAT | INTEGER | MCHAR

| MVARCHAR | NCHAR | NVARCHAR | REAL | SMALLINT | TIME | TIMESTAMP | VARCHAR }

S: Terminates processing.

P: Specify a getXXX method of the CallableStatement class that corresponds to the ? parameter data type.

KFPJ20502-E A TYPE2

Unable to get data aa....aa

The specified column data cannot be obtained using a getXXX method of the CallableStatement class.

aa....aa: Specified column data

S: Passes SQLException to the calling class.

Action

Specify a getXXX method of the CallableStatement class that corresponds to the column data type.

KFPJ20503-E A

Invalid number of get scale.

The contents of scale specified by the getBigDecimal method of the CallableStatement class are invalid.

S: Passes SQLException to the calling class.

Action

Check the contents of scale.

KFPJ20504-E A

Invalid parameter index. INDEX:aa....aa

A parameter index is invalid.

aa....aa: Parameter index

S: Passes SQLException to the calling class.

Action

Check the parameter index.

KFPJ20505-E A

Attribute that designated it with IN and OUT differs.

The IN parameter specified in the INOUT parameter has an attribute different from the OUT parameter.

S: Passes SQLException to the calling class.

Action

Check the attributes. Make sure the java.sql.Types specified in the registerOutParameter method has the same type as the type specified as an argument of setXXX.

KFPJ20506-E A

Output attribute is not able to acquire information because it does not exist in a parameter.

The information cannot be acquired because there is no parameter in which OUT is specified.

S: Passes SQLException to the calling class.

Action

Check the following:

Whether or not there is a parameter with OUT specified in the Java stored procedure that is to be executed; if a parameter with OUT specified is needed, add it and re-create the Java stored procedure.

Whether or not the Java stored procedure to be executed is the correct one; if necessary, correct the UAP so that the intended Java stored procedure will be executed.

Executing the clearParameters method clears the parameter information at the time of execution. Make sure the clearParameters method is not executed after the execution of the execute method and before the execution of the getXXX method.

KFPJ20507-E A

Invalid parameter name, name=aa....aa

An invalid parameter name was specified by the setXXX method, getXXX method, or registerOutParameter method of the CallableStatement class.

aa....aa: Specified parameter name

S: Terminates processing.

P: Revise the specified parameter name.

KFPJ20508-E A

Invalid scale, scale=aa....aa

The specified scale value is invalid.

aa....aa: Specified scale value

S: Terminates processing.

P: Revise the specified scale value.

KFPJ20509-E A

Unable to use this method for parameter, index=aa....aa, parameter=bb....bb

It is not possible to use this method to set or acquire the specified parameter.

aa....aa: Parameter index

bb....bb: Parameter type {IN | OUT}

S: Terminates processing.

P: Do not call the getXXX method or the registerOutParameter method for the IN parameter, or the setXXX method for the OUT parameter.

KFPJ20601-E A TYPE4

Invalid column name, column name="aa....aa"

The column name specified in the getXXX method of the ResultSet class is invalid.

aa....aa: Column name

S: Terminates processing.

Action

Review the specified column name.

KFPJ20601-E A TYPE2

Unable to get number of result columns.

A column name specified by the getXXX method of the ResultSet class is invalid.

S: Passes SQLException to the calling class.

Action

Check the column names.

KFPJ20604-E A

Unable to get data string.

The specified column data cannot be obtained using the getString method of the ResultSet class.

S: Passes SQLException to the calling class.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20605-E A TYPE4

Unable to get data by "getBoolean" method, column index=aa....aa, data type=bb....bb

Data for the specified column cannot be acquired using the getBoolean method of the ResultSet class.

aa....aa: Column number

bb....bb: Data type of the column (HiRDB data type)

{BINARY|BLOB|DATE|TIME|TIMESTAMP}

S: Terminates processing.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20605-E A TYPE2

Unable to get data boolean.

The specified column data cannot be obtained using the getBoolean method of the ResultSet class.

S: Passes SQLException to the calling class.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20606-E A TYPE4

Unable to get data by "getByte" method, column index=aa....aa, data type=bb....bb

The specified column data cannot be obtained using the getByte method of the ResultSet class.

aa....aa: Column number

bb....bb: Data type of the column (HiRDB data type)

{BINARY|BLOB|CHAR|DATE|DECIMAL|FLOAT|INTEGER|MCHAR|MVARCHAR|NCHAR|NVARCHAR|REAL|SMALLINT|TIME|TIMESTAMP|VARCHAR}

S: Terminates processing.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20606-E A TYPE2

Unable to get data byte.

The specified column data cannot be obtained using the getByte method of the ResultSet class.

S: Passes SQLException to the calling class.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20607-E A TYPE4

Unable to get data by "getShort" method, column index=aa....aa, data type=bb....bb

The specified column data cannot be obtained using the getShort method of the ResultSet class.

aa....aa: Column number

bb....bb: Data type of the column (HiRDB data type)

{BINARY|BLOB|CHAR|DATE|DECIMAL|FLOAT|INTEGER|MCHAR|MVARCHAR|NCHAR|NVARCHAR|REAL|TIME|TIMESTAMP|VARCHAR}

S: Terminates processing.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20607-E A TYPE2

Unable to get data short.

The specified column data cannot be obtained using the getShort method of the ResultSet class.

S: Passes SQLException to the calling class.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20608-E A TYPE4

Unable to get data by "getInt" method, column index=aa....aa, data type=bb....bb

The specified column data cannot be obtained using the getInt method of the ResultSet class.

aa....aa: Column number

bb....bb: Data type of the column (HiRDB data type)

{BINARY|BLOB|CHAR|DATE|DECIMAL|FLOAT|MCHAR|MVARCHAR|NCHAR|NVARCHAR|REAL|TIME|TIMESTAMP|VARCHAR}

S: Terminates processing.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20608-E A TYPE2

Unable to get data int.

The specified column data cannot be obtained using the getInt method of the ResultSet class.

S: Passes SQLException to the calling class.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20609-E A TYPE4

Unable to get data by "getLong" method, column index=aa....aa, data type=bb....bb

The specified column data cannot be obtained using the getLong method of the ResultSet class.

aa....aa: Column number

bb....bb: Data type of the column (HiRDB data type)

{CHAR|DATE|DECIMAL|FLOAT|MCHAR|MVARCHAR|NCHAR|NVARCHAR|REAL|TIME|TIMESTAMP|VARCHAR}

S: Terminates processing.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20609-E A TYPE2

Unable to get data long.

The specified column data cannot be obtained using the getLong method of the ResultSet class.

S: Passes SQLException to the calling class.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20610-E A TYPE4

Unable to get data by "getFloat" method, column index=aa....aa, data type=bb....bb

The specified column data cannot be obtained using the getFloat method of the ResultSet class.

aa....aa: Column number

bb....bb: Data type of the column (HiRDB data type)

{BINARY|BLOB|CHAR|DATE|MCHAR|MVARCHAR|NCHAR|NVARCHAR|TIME|TIMESTAMP|VARCHAR}

S: Terminates processing.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20610-E A TYPE2

Unable to get data float.

The specified column data cannot be obtained using the getFloat method of the ResultSet class.

S: Passes SQLException to the calling class.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20611-E A TYPE4

Unable to get data by "getDouble" method, column index=aa....aa, data type=bb....bb

The specified column data cannot be obtained using the getDouble method of the ResultSet class.

aa....aa: Column number

bb....bb: Data type of the column (HiRDB data type)

{BINARY|BLOB|CHAR|DATE|MCHAR|MVARCHAR|NCHAR|NVARCHAR|TIME|TIMESTAMP|VARCHAR}

S: Terminates processing.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20611-E A TYPE2

Unable to get data double.

The specified column data cannot be obtained using the getDouble method of the ResultSet class.

S: Passes SQLException to the calling class.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20612-E A TYPE4

Unable to get data by "getBigDecimal" method, column index=aa....aa, data type=bb....bb

The specified column data cannot be obtained using the getBigDecimal method of the ResultSet class.

aa....aa: Column number

bb....bb: Data type of the column (HiRDB data type)

{BINARY|BLOB|CHAR|DATE|MCHAR|MVARCHAR|NCHAR|NVARCHAR|TIME|TIMESTAMP|VARCHAR}

S: Terminates processing.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20612-E A TYPE2

Unable to get data BigDecimal.

The specified column data cannot be obtained using the getBigDecimal method of the ResultSet class.

S: Passes SQLException to the calling class.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20613-E A TYPE4

Unable to get data by "getBytes" method, column index=aa....aa, data type=bb....bb

The specified column data cannot be obtained using the getBytes method of the ResultSet class.

aa....aa: Column number

bb....bb: Data type of the column (HiRDB data type)

{DATE|DECIMAL|FLOAT|INTEGER|REAL|SMALLINT|TIME|TIMESTAMP}

S: Terminates processing.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20613-E A TYPE2

Unable to get data bytes.

The specified column data cannot be obtained using the getBytes method of the ResultSet class.

S: Passes SQLException to the calling class.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20614-E A TYPE4

Unable to get data by "getDate" method, column index=aa....aa, data type=bb....bb

The specified column data cannot be obtained using the getDate method of the ResultSet class.

aa....aa: Column number

bb....bb: Data type of the column (HiRDB data type)

{BINARY|BLOB|DECIMAL|FLOAT|INTEGER|REAL|SMALLINT|TIME}

S: Terminates processing.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20614-E A TYPE2

Unable to get data Date.

The specified column data cannot be obtained using the getDate method of the ResultSet class.

S: Passes SQLException to the calling class.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20615-E A TYPE4

Unable to get data by "getTime" method, column index=aa....aa, data type=bb....bb

The specified column data cannot be obtained using the getTime method of the ResultSet class.

aa....aa: Column number

bb....bb: Data type of the column (HiRDB data type)

{BINARY|BLOB|DATE|DECIMAL|FLOAT|INTEGER|REAL|SMALLINT}

S: Terminates processing.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20615-E A TYPE2

Unable to get data Time.

The specified column data cannot be obtained using the getTime method of the ResultSet class.

S: Passes SQLException to the calling class.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20616-E A TYPE4

Unable to get data by "getTimestamp" method, column index=aa....aa, data type=bb....bb

The specified column data cannot be obtained using the getTimestamp method of the ResultSet class.

aa....aa: Column number

bb....bb: Data type of the column (HiRDB data type)

{BINARY|BLOB|DECIMAL|FLOAT|INTEGER|REAL|SMALLINT|TIME}

S: Terminates processing.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20616-E A TYPE2

Unable to get data Timestamp.

The specified column data cannot be obtained using the getTimestamp method of the ResultSet class.

S: Passes SQLException to the calling class.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20617-E A TYPE4

Unable to get data by "getAsciiStream" method, column index=aa....aa, data type=bb....bb

The specified column data cannot be obtained using the getAsciiStream method of the ResultSet class.

aa....aa: Column number

bb....bb: Data type of the column (HiRDB data type)

{DATE|DECIMAL|FLOAT|INTEGER|REAL|SMALLINT|TIME|TIMESTAMP}

S: Terminates processing.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20617-E A TYPE2

Unable to get ascii stream.

The specified column data cannot be obtained using the getAsciiStream method of the ResultSet class.

S: Passes SQLException to the calling class.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20618-E A

Unable to get unicode stream.

The specified column data cannot be obtained using the getUnicodeStream method of the ResultSet class.

S: Passes SQLException to the calling class.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20619-E A TYPE4

Unable to get data by "getBinaryStream" method, column index=aa....aa, data type=bb....bb

The specified column data cannot be obtained using the getBinaryStream method of the ResultSet class.

aa....aa: Column number

bb....bb: Data type of the column (HiRDB data type)

{CHAR|DATE|DECIMAL|FLOAT|INTEGER|MCHAR|MVARCHAR|NCHAR|NVARCHAR|REAL|SMALLINT|TIME|TIMESTAMP|VARCHAR}

S: Terminates processing.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20619-E A TYPE2

Unable to get binary stream.

The specified column data cannot be obtained using the getBinaryStream method of the ResultSet class.

S: Passes SQLException to the calling class.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20621-E A TYPE4

ResultSet closed

Because the ResultSet instance is already closed, the processing cannot be accepted.
The JDBC driver might have closed the ResultSet instance because the Statement instance was closed.

S: Terminates processing.

Action

Re-create the ResultSet instance and re-execute.

KFPJ20621-E A TYPE2

ResultSet or Statement is closed.

Processing cannot be accepted because the ResultSet or Statement instance is already closed.

S: Passes SQLException to the calling class.

Action

Re-create the ResultSet instance and re-execute.

KFPJ20622-E A TYPE4

Unable to get data by "getCharacterStream" method,column index=aa....aa, data type=bb....bb

The specified column data cannot be obtained using the getCharacterStream method of the ResultSet class.

aa....aa: Column number

bb....bb: Data type of the column (HiRDB data type)

{DATE|DECIMAL|FLOAT|INTEGER|REAL|SMALLINT|TIME|TIMESTAMP}

S: Terminates processing.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20622-E A TYPE2

Unable to get character stream.

The specified column data cannot be obtained using the getCharacterStream method of the ResultSet class.

S: Passes SQLException to the calling class.

Action

Specify a getXXX method of the ResultSet class that corresponds to the column data type.

KFPJ20627-E A TYPE4

Invalid column index, index=aa....aa

The column index specified in the getXXX method of the ResultSet class is invalid.

aa....aa: Column index

S: Terminates processing.

Action

Review the specified column index.

KFPJ20627-E A TYPE2

Invalid number of get column index.

The index or column name specification by the getXXX method of the ResultSet class is invalid.

S: Passes SQLException to the calling class.

Action

Check the name of the index or column.

KFPJ20629-E A TYPE4

Invalid scale, scale=aa....aa

The scale specified by the getBigDecimal method of the ResultSet class is invalid.

aa....aa: Value of specified scale

S: Terminates processing.

Action

Check the scale.

KFPJ20629-E A TYPE2

Invalid number of get scale.

The scale specified by the getBigDecimal method of the ResultSet class is invalid.

S: Passes SQLException to the calling class.

Action

Check the scale.

KFPJ20630-E A TYPE4

Invalid data format for java.sql.Date

Because the data obtained from the database does not match the date data format, data cannot be obtained using the getDate method of the CallableStatement class or ResultSet class used.

S: Terminates processing.

Action

Specify the getXXX method of the CallableStatement class or ResultSet class that matches the data type.

KFPJ20630-E A TYPE2

Date format exception.

Because the data obtained from the database does not match the date data format, data cannot be obtained using the getXXX method of the ResultSet class used.

S: Passes SQLException to the calling class.

Action

Specify a getXXX method of the ResultSet class that matches the data type.

KFPJ20631-E A TYPE4

Invalid data format for java.sql.Time

Because the data obtained from the database does not match the time data format, data cannot be obtained using the getTime method of the CallableStatement class or ResultSet class used.

S: Terminates processing.

Action

Specify the getXXX method of the CallableStatement class or ResultSet class that corresponds to the data type.

KFPJ20631-E A TYPE2

Time format exception.

Because the data obtained from the database does not match the time data format, data cannot be obtained using the getXXX method of the ResultSet class used.

S: Passes SQLException to the calling class.

Action

Specify a getXXX method of the ResultSet class that matches the data type.

KFPJ20632-E A TYPE4

Invalid data format for java.sql.Timestamp

Because the data obtained from the database does not match the timestamp data format, data cannot be obtained using the getTimestamp method of the CallableStatement class or ResultSet class used.

S: Terminates processing.

Action

Specify the getXXX method of the CallableStatement class or ResultSet class that corresponds to the data type.

KFPJ20632-E A TYPE2

Timestamp format exception.

Because the data obtained from the database does not match the timestamp data format, data cannot be obtained using the getXXX method of the ResultSet class used.

S: Passes SQLException to the calling class.

Action

Specify a getXXX method of the ResultSet class that matches the data type.

KFPJ20633-E A TYPE4

Unable to scroll cursor due to current ResultSet type TYPE_FORWARD_ONLY

Because the result set type of this ResultSet object is TYPE_FORWARD_ONLY, it is not amenable to scrolling.

S: Terminates processing.

Action

Specify a ResultSet object having a result set type compatible with scrolling operations.

KFPJ20633-E A TYPE2

Current ResultSet is TYPE_FORWARD_ONLY. The method is invalid. METHOD:aa....aa

Because the current results set is only for the forward direction, the invocation of method aa....aa is invalid.

aa....aa: Method name

S: Passes SQLException to the calling class.

Action

Do not invoke method aa....aa.

KFPJ20634-E A

Not support CONCUR_UPDATABLE ResultSet concurrency. The method is invalid. METHOD:aa....aa

Because an updatable results set could not be used, the invocation of method aa....aa is invalid.

aa....aa: Method name

S: Passes SQLException to the calling class.

Action

Do not invoke method aa....aa.

KFPJ20635-E A TYPE4

Zero specified

A zero is specified in the absolute method.

S: Terminates processing.

Action

Specify a non-zero value.

KFPJ20635-E A TYPE2

Zero is designated to the row.

0 is specified for the row.

S: Passes SQLException to the calling class.

Action

Do not specify 0 for the row.

KFPJ20636-E A TYPE4

Invalid cursor position

The cursor is not in a valid row.

S: Terminates processing.

Action

Place the cursor in a valid row.

KFPJ20636-E A TYPE2

Row that was designated without existing.

An operation was performed on a results set that has no rows.

S: Passes SQLException to the calling class.

Action

Do not perform an operation on a results set that has no rows.

KFPJ20637-E A TYPE4

Unable to get data by "getBlob" method, column index=aa....aa, data type=bb....bb

Data from the specified column cannot be obtained using the ResultSet class getBlob method.

aa....aa: Column number

bb....bb: Data type of the column (HiRDB data type)

{CHAR|DATE|DECIMAL|FLOAT|INTEGER|MCHAR|MVARCHAR|NCHAR|NVARCHAR|REAL|SMALLINT|TIME|TIMESTAMP|VARCHAR}

S: Terminates processing.

Action

Specify a getXXX method of the ResultSet class that is appropriate for the column's data type.

KFPJ20637-E A TYPE2

Unable to get data BLOB.

Data from the specified column cannot be obtained using the ResultSet class getBlob method.

S: Throws an SQLException.

Action

Specify a getXXX method of the ResultSet class that is appropriate for the column's data type.

KFPJ20701-E A

Invalid column index. INDEX:aa....aa

The index specified by the getXXX method of the ResultSetMetaData class is invalid.

aa....aa: Index

S: Passes SQLException to the calling class.

Action

Correct the error by checking the SQLException.

KFPJ21001-E A

Invalid argument.number:aa....aa value:bb....bb method:cc....cc

An invalid argument parameter is specified.

aa....aa: Argument sequence number

bb....bb: Argument value

cc....cc: Method name

S: Terminates processing.

Action

Review the argument parameters.

KFPJ31002-E A TYPE4

Fail to load native library

Loading of the native library failed.
Possible causes are as follows:

There is no native library.

The user does not have privileges to load to the native library.

S: Terminates processing.

P: Contact the customer support center.

KFPJ31002-E A TYPE2

Not found native library.

Loading of the native library failed.

S: Passes SQLException to the calling class.

Action

Check whether the native library is in the system's standard library directory. Note that this message is not output when the 32-bit edition's Type 2 JDBC driver is used in a 64-bit Java environment. If you are in a 64-bit Java environment, use the Type 4 JDBC driver.

KFPJ50001-E A

Argument is null.

The argument specified for the connection information setting method is the null value.

S: Passes SQLException to the calling class.

Action

Check the argument value.

KFPJ50002-E A

Mandatory property no set. PROPERTY:aa....aa

Required connection information aa....aa has not been set.

aa....aa: Connection information

S: Passes SQLException to the calling class.

Action

Set the aa....aa connection information.

KFPJ50003-E A TYPE4

Invalid login timeout value, value=aa....aa

A negative value cannot be assigned to the logon timeout limit specified in the setLoginTimeout method.

aa....aa: Logon timeout limit specified in the setLoginTimeout method

S: Terminates processing.

Action

Review the value of the logon timeout limit specified in the setLoginTimeout method.

KFPJ50003-E A TYPE2

Invalid LoginTimeout. VALUE:aa....aa

Specification value aa....aa for the setLoginTimeout method is invalid.

aa....aa: Specification value for the setLoginTimeout method

S: Passes SQLException to the calling class.

Action

Check the specification value.

KFPJ50004-E A

Invalid NetworkProtocol. VALUE:aa....aa

Specification value aa....aa for the setNetworkProtocol method is invalid.

aa....aa: Specification value for the setNetworkProtocol method

S: Passes SQLException to the calling class.

Action

Check the specification value.

KFPJ50005-E A

Invalid PortNumber. VALUE:aa....aa

Specification value aa....aa for the setPortNumber method is invalid.

aa....aa: Specification value for the setPortNumber method

S: Passes SQLException to the calling class.

Action

Check the specification value.

KFPJ50006-E A

Invalid DatabaseName. VALUE:aa....aa

Specification value aa....aa for the setDatabaseName method is invalid.

aa....aa: Specification value for the setDatabaseName method

S: Passes SQLException to the calling class.

Action

Check the specification value.

KFPJ50007-E A

Invalid DBEnv. VALUE:aa....aa

Specification value aa....aa for the setDBEnv method is invalid.

aa....aa: Specification value for the setDBEnv method

S: Passes SQLException to the calling class.

Action

Check the specification value.

KFPJ50008-E A TYPE4

Invalid character set

Either a null value or a zero-length character string was specified as an argument in the setEncodeLang method.

S: Terminates processing.

Action

Review the value specified in the setEncodeLang method.

KFPJ50008-E A TYPE2

Encoding Lang is null.

Encoding is not specified.

S: Passes SQLException to the calling class.

Action

Check the encoding character string.

KFPJ50009-E A TYPE4

Invalid description value, value="aa....aa"

Value aa....aa specified in the setDescription method is invalid.

aa....aa: Value specified in the setDescription method

S: Terminates processing.

Action

Review the value specified in the setDescription method.

KFPJ50009-E A TYPE2

Invalid Description. VALUE:aa....aa

Value aa....aa specified in the setDescription method is invalid.

aa....aa: Value specified in the setDescription method

S: Throws an SQLException.

Action

Revise the specified value.

KFPJ55001-E A

Current connection is not XA mode. The getXAResource method is invalid.

Because the connection is not in the XA mode, invocation of the getXAResource method is invalid.

S: Passes SQLException to the calling class.

Action

Do not invoke the getXAResource method.

KFPJ55002-E A

Current NetworkProtocol is not NativeLibrary mode. The getXAResource method is invalid.

Because the connection type is not native library connection, invocation of the getXAResource method is invalid.

S: Passes SQLException to the calling class.

Action

Change the connection type to native library connection.

KFPJ56001-E A

XA session is closed.

XA processing cannot be accepted because the XA session is closed.

S: Passes XAException to the calling class.

Action

Re-create an XAConnection instance, obtain the XAResource instance again using the getXAResource method, and re-execute.

KFPJ56002-E A

XID is null.

The XID argument is the null value.

S: Passes XAException to the calling class.

Action

Check the XID argument value.

KFPJ70001-I A

SQL process is canceled.

SQL processing has been cancelled.

S: Passes SQLException to the calling class.

KFPJ70002-E A TYPE4

Object not active due to termination of transaction

The transaction was terminated (including an internal rollback); this object is nullified.

S: Terminates processing.

Action

When it occurs during operations on a ResultSet object:

Repeat the operations that created the relevant ResultSet object.

When it occurs during operations on a BLOB object:

Repeat the operations that created the ResultSet obtained from the relevant BLOB object.

When it occurs in the getXXX method of the CallableStatement class:

Re-execute the SQL statement for the relevant CallableStatement object, and then re-execute the getXXX method.

If the statement object is set to be invalidated when the transaction is committed, it invalidates the pre-processing of the PreparedStatement object or CallableStatement object. Create the PreparedStatement object or CallableStatement object, and then execute the SQL statement.

KFPJ70002-E A TYPE2

Transaction is completed.

Processing cannot be accepted because the transaction has already been committed or rolled back.

S: Passes SQLException to the calling class.

Action

Close the ResultSet instance and re-execute.

KFPJ70003-E A TYPE4

Unsupported SQL type appeared in SQL, type:aaa, number:bbbbb

The SQL execution results include a data type not supported by the JDBC driver.

aaa: Invalid data code (decimal)

bbbbb: Ordinal number of parameters, beginning with 1

S: Terminates processing.

Action

Review the SQL and the data type in the table to be searched.

For details about the correspondence between data types and about data codes that cannot be used, see the section on the length of data codes and data that are assigned in an SQL descriptor area in the manual HiRDB Version 9 UAP Development Guide.

KFPJ70003-E A TYPE2

Not support SQL type exist in result. TYPE:aa....aa

The SQL execution results include an unusable data type.

aa....aa: Unusable data type

S: Passes SQLException to the calling class.

Action

Check the SQL and the data types in the table to be retrieved.

KFPJ80001-E A

Server version incompatible, server version=aa....aa, client version=bb....bb

The version of the HiRDB server is invalid.
Use HiRDB server version 08-00 or later.

aa....aa: HiRDB server version

bb....bb: HiRDB client version

S: Terminates processing.

Action

Verify that the HiRDB server version is 08-00 or later, and then re-execute the command.

KFPJ80002-E A

BINARY/BLOB data truncated

The retrieval data length of a BINARY or BLOB column exceeds the following specification values:

Value of the HiRDB_for_Java_MAXBINARYSIZE property assigned at connection time from the DriverManager class

Value specified in the setMaxBinarySize method of the DataSource class

Value specified in the setMaxBinarySize method of the ConnectionPoolDataSource class

Value specified in the setMaxBinarySize method of the XADataSource class

S: Terminates processing.

Action

Review the specification values.

If truncation of the retrieval data in the BINARY or BLOB column does not cause a problem, set the following specification values to FALSE:

Value of the HiRDB_for_Java_LONGVARBINARY_TRUNCERROR property assigned at connection time from the DriverManager class

Value specified in the setLONGVARBINARY_TruncError method of the DataSource class

Value specified in the setLONGVARBINARY_TruncError method of the ConnectionPoolDataSource class

Value specified in the setLONGVARBINARY_TruncError method of the XADataSource class

KFPJ80003-E A

Unable to use XA interface for XDM/RD E2

The XA interface cannot be used when using the XDM/RD E2 connection facility.

S: Terminates processing.

Action

Do not use the XA interface when using the XDM/RD E2 connection facility.

KFPJ80100-E A

Current connection closed. "getXAResource" method invalid

Not connected to the database. The getXAResource method call is invalid.

S: Terminates processing.

Action

Re-create the XAConnection instance, re-acquire the XAResource instance by means of the getXAResource method, and continue the processing.

KFPJ80101-E A

Incorrect OpenString,reason=aaaaaaa

The assigned open character string value contains an error.

aaaaaaa: Reason code

STR_OVR:

The character string is longer than 256 bytes.

FRM_ERR:

The format of the character string is invalid.

S: Terminates processing.

Action

For details about using open character strings, see the manual HiRDB Version 9 UAP Development Guide.

KFPJ80102-E A

Error occurred in XAResource, method=aa....aa, reason=bb....bb, code=cc....cc

An XAResource interface error occurred.

aa....aa: Method name of the XAResource interface that produced the error

bb....bb: Character string that indicates the type of error

SVR PROC:

An error occurred on the HiRDB server during transaction termination processing.

SQL ERR:

An error occurred during SQL processing.

RPC CALL:

An error occurred during communication execution.

TRN CMIT:

An error occurred on the HiRDB server during transaction recovery (commit) processing.

TRN ROLB:

An error occurred on the HiRDB server during transaction recovery (rollback) processing.

TRN WAIT:

An error occurred on the HiRDB server during monitoring of the termination of transaction recovery processing.

TRN RCV:

An error occurred on the HiRDB server during acquisition of information about unterminated transactions.

TXA DRIV:

An error occurred in the JDBC driver.

cc....cc: Code indicating the cause of the error

S: Terminates processing.

Action

Take action according to the code indicating the cause of the error.

Error type character string
Error cause code
Meaning
Action

SVR PROC
-902
An improper rollback occurred.
Contact the customer support center.

SQL ERR
SQL code
See the explanation for the applicable SQL code.
Refer to the explanation for the applicable SQL code.

RPC CALL
-2404
A memory shortage occurred.
Possible causes: network error, or server not being activated. Check the network or server status.

-2406
-2418
A network error occurred.

-2407
Timeout occurred during send/receive.

-2410
-2411
-2414
-2415
HiRDB server not activated.

-2412
-2413
-2432
HiRDB server being shut down.

-2416
System error occurred on HiRDB server.

-2417
Memory shortage occurred on HiRDB server.

-2420
Activating the HiRDB server.

-2431
Maximum number of users who can be connected to HiRDB exceeded.

TRN CMIT
TRN ROLB
TRN WAIT
TRN RCV
-4
Invalid inter-host communications.
Possible cause: server not being activated. Check the server status.

-6
Improper rollback occurred.
Contact the customer support center.

-7
No applicable transaction found on HiRDB.
The applicable transaction was terminated independently by HiRDB. Check the status of the transaction in the OLTP system.

100
Connection destination HiRDB is a standby system unit.
Review the client environment variable PDHOST specified in the OLTP system. Make sure the connection destination is the host name of a running system unit. However, note that if the version of the HiRDB client is 06-02/A or earlier, this code can be output if the running system unit is waiting as a standby system unit. If this is the case, update the HiRDB client to version 06-02/B or later.

TXA DRIV
-1
Not connected to a HiRDB server.
It is possible that the program has not performed processing to connect to the HiRDB, or started a transaction in a disconnected state. Check the program.

-2
Thread interrupt exception occurred.
Check the program to make sure it is not executing the Thread.Interrupt method.

KFPJ99001-E A TYPE4

Internal Error occurred,inf1=aa....aa, inf2=bb....bb

An internal system error occurred in the JDBC driver.

aa....aa: Maintenance information

bb....bb: Maintenance information 2

S: Terminates processing.

Action

Check whether an exception or error has occurred by referring to the standard output or the standard error output from the Java Virtual Machine (JVM), which is output to the file specified in the pd_java_stdout_file operand. If no exception or error occurred, contact the customer support center.

KFPJ99001-E A TYPE2

DBA Internal Error. Return Code = aa....aa, Detail code = bb....bb, Message = cc....cc

An internal error occurred during the database access session.

aa....aa: Return code from the database access session

bb....bb: Detailed code from the database access session

cc....cc: Message from the database access session

S: Passes SQLException to the calling class.

Action

Contact the customer support center.

2.7 KFPK messages

KFPK00001-E E+L

aaaaaaaa: file not found, file_kind:bb....bb file_name:cc....cc

Specified file or temporary file created by a utility was not found. Or, specified directory does not contain an analyzable file.

aaaaaaaa: Utility:

Pdstedit: Statistics analysis utility

bb....bb: File type

control file: Control statements file

sort data file: Work file for sorting

unload log file: Unload log file

cc....cc: File name or directory name

S: Terminates processing.

O: Take one of the following actions, depending on the file type:

unload log file or control file:

Check the command name and reenter the command. If file_name is a directory name, check the files under the directory and reenter the command.

sort data file:

Check if the temporary file automatically created by the utility was deleted by mistake.

KFPK00002-E D+E+L

aa....aa: file open failed, file_kind:bb....bb, file_name:cc....cc, errno=dd....dd

Specified file or temporary file created by a utility cannot be opened.

aa....aa: Utility:

Pddbst: Database condition analysis utility

Pdstedit: Statistics analysis utility

bb....bb: File:

control file: Control statements file

edit work file: Work file

sort data file: Work file for sorting

unload log file: Unload log file

DAT file: DAT-format file

predict csv file: CSV output file

cc....cc: File name

dd....dd: errno returned from the open system call

S: Message is output to standard error:

Terminates processing.

Message is output to the error message dialog:

Redisplays the screen immediately before the error occurred.

O: Statistics analysis utility:

Based on errno, check errno.h and the manual for the operating system in use to eliminate the cause of the error, and then re-execute the command.

If *** is indicated in errno, check the cause of the error based on the preceding error message.

Database condition analysis utility:

Based on errno, check errno.h and the manual for the operating system in use to eliminate the cause of the error, and then re-execute the command.

KFPK00003-E D+E+L

aa....aa: file close failed, file_kind:bb....bb, file_name:cc....cc, errno=dd....dd

A file cannot be closed.

aa....aa: Utility

Pddbst: Database condition analysis utility

Pdstedit: Statistics analysis utility

bb....bb: File

control file: Control statements file

edit work file: Work file

sort data file: Work file for sorting

unload log file: Unload log file

predict csv file: CSV output file

cc....cc: File name

dd....dd: errno returned from the close system call

S: Message is output to standard error:

Terminates processing.

Message is output to the error message dialog:

Redisplays the screen immediately before the error occurred.

O: Statistics analysis utility:

Based on errno, check errno.h and the manual for the operating system in use to eliminate the cause of the error, and then re-execute the command.

If *** is indicated in errno, check the cause of the error based on the preceding error message.

Database condition analysis utility:

Based on errno, check errno.h and the manual for the operating system in use to eliminate the cause of the error, and then re-execute the command.

KFPK00004-E D+E+L

aa....aa: I/O error, cause:bb....bb, file_name:cc....cc, errno=dd....dd

An I/O error occurred.

aa....aa: Utility:

Pddbst: Database condition analysis utility

Pdstedit: Statistics analysis utility

bb....bb: Type of system call that caused the error

LSEEK: lseek system call

READ: read system call

WRITE: write system call

cc....cc: File name

dd....dd: errno returned from the system call

S:

Message is output to standard error:
Terminates processing.

Message is output to the error message dialog:
Redisplays the screen immediately before the error occurred.

O:

Statistics analysis utility:
Based on errno, check errno.h and the manual for the operating system in use to eliminate the cause of the error, and then re-execute the command.
If *** is indicated in errno, check the cause of the error based on the preceding error message.

Database condition analysis utility:
Based on errno, check errno.h and the manual for the operating system in use to eliminate the cause of the error, and then re-execute the command.

KFPK00005-E D+E+L

aa....aa: system call error, func=bb....bb, errno=cc....cc

A system call (function) error occurred.

aa....aa: Utility:

Pddbst: Database condition analysis utility

Pdstedit: Statistics analysis utility

bb....bb: Name of system call resulting in the error

cc....cc: errno returned from the system call

S:

Message is output to standard error:
Terminates processing.

Message is output to the error message dialog:
Redisplays the screen immediately before the error occurred.

O: Check the meaning of the error number (errno: external integer variable indicating the error status), refer to errno.h and the applicable OS manual to eliminate the cause of the error, then re-execute the command.

KFPK00006-E D+E+L

aa....aa: unrecovable error, func=bb....bb, errno=ccc

An unrecoverable error occurred.

aa....aa: Utility:

Pddbst: Database condition analysis utility

Pdstedit: Statistics analysis utility

bb....bb: Type of system call that caused the error

CLOSEDIR: closedir system call

CREATE: create or open system call

DELETE: unlink system call

OPENDIR: opendir system call

READDIR: readdir system call

ccc: errno returned from the system call

S:

Message is output to standard error:
Terminates processing.

Message is output to the error message dialog:
Redisplays the screen immediately before the error occurred.

O: Check the meaning of the error number (errno: external integer variable indicating the error status), refer to errno.h and the manual describing the applicable function to eliminate the cause of the error, and then re-execute the command. When the error number is ***, check for the cause based on the error message previously output. If a control statement file is specified and bb....bb is CREATE, review the path name specified in the control statement.

KFPK00007-W E

aa....aa error occurred in log element file, server_name:bb....bb file_name:cc....cc system A/B:d reason=(eee,fffff)

An error occurred in the system log file.

aa....aa: Processing resulting in the error:

Close: Close processing

Open: Open processing

Read: Read processing

bb....bb: Server name corresponding to the file group

cc....cc: File group name

d: System in which the error occurred

eee: Reason code

fffff: Detail code

S: If the error was not in a log file of the other system, the HiRDB system resumes processing by using the log file in the other system.

O: Take action appropriate to the reason code:

Reason code
Explanation
Action

-40
-41
-42
-43
I/O error occurred.
Find the detail code corresponding to the error code in Section 5.1 Error codes returned from HiRDB file system access requests to eliminate the cause of the error.

-50
-51
-52
-53
File contents are invalid.
Determine which of the following caused the message to be output, eliminate the cause of the error, and re-execute the command:

The current group was specified.

An unused file group was specified after initialization.

Non-system log file group was specified.

The log file has been damaged (check whether the log file definition was changed or initialized or whether the status was changed erroneously).

The detail code consists of system maintenance information.

KFPK00008-E E

aa....aa error occurred in log element file, server_name:bb....bb file_name:cc....cc system A/B:d reason=(eee,fffff)

An error occurred in the system log file.

aa....aa: Processing resulting in the error:

Close: Close processing

Open: Open processing

Read: Read processing

bb....bb: Server name corresponding to the file group

cc....cc: File group name

d: System in which the error occurred

eee: Reason code

fffff: Detail code

S: Terminates processing.

O: Take action appropriate to the reason code:

Reason code
Explanation
Action

-40
-41
-42
-43
I/O error occurred.
Find the detail code corresponding to the error code in Section 5.1 Error codes returned from HiRDB file system access requests to eliminate the cause of the error.

-50
-51
-52
-53
File contents are invalid.
The log file may have been damaged (check whether the log file definition was changed or initialized or whether the status was changed erroneously).
The detail code consists of system maintenance information.

KFPK00009-E E

aaaaa error occurred, file=bb....bb

A file I/O error occurred.

aaaaa: Process that caused the error:

Open: An error occurred on an open process

Read: An error occurred on a read process

Close: An error occurred on a close process

bb....bb: File name

S: Terminates processing.

O: Refer to the error message output immediately after this message to eliminate the error cause, and then re-execute the command.

KFPK00010-E E

File I/O error occurred, reason=aa....aa, func=bb....bb, errno=cc....cc, (dd....dd)

An error occurred when inputting or outputting a file.

aa....aa: Error cause

Invalid-parameter: The combination of specified parameters is invalid.

Invalid-permission: The user does not have access permission for the file.

Invalid-device: The file entry type (attribute) is invalid. A directory name might be specified where a file name must be specified (or the converse). In UNIX, a character special file might be assigned to a file on which a character special file cannot be used.

File-format: The file formats are different. It is possible that the specified file name is incorrect, or the file format specified on the command line or in the control statement does not match the file contents.

Invalid-file: The specified file was not created correctly.

File-lock: The file is being used by another user. The file name specified in the command line or control statement might be in use by another job. In UNIX, there might be a shortage of file locking resources for an OS kernel parameter.

No-file: Cannot find the file.

For Invalid-device, when the entry type of the specified file can be identified, the device type is displayed with the entry type in parentheses. In UNIX, the content is the same as the entry for the mode displayed by the operating system's ls -l command.

bb....bb: Name of the system function where an error occurred

If the operating system detected the error, the system function name

If the HiRDB file system detected the error, the HiRDB file system function name beginning with p_f_ios

If other than the above, ***

cc....cc: Error code

If the operating system detected the error, the error number (errno: foreign reference variable that shows the error status) returned by the system function name

If the error was detected by the HiRDB file system, the HiRDB file system error code (for details on HiRDB file system error codes, see 5.1 Error codes returned from HiRDB file system access requests)

If an error cause other than the above, 0

dd....dd: Troubleshooting information (source file name and row number that detected the error). This information is used by the customer support center.

S: Terminates processing.

O: From the error cause, function name, and error code, check errno.h, the manual for the operating system in use, and 5.1 Error codes returned from HiRDB file system access requests to eliminate the cause of the error, and re-execute.

KFPK00011-E E

HiRDB file aa....aa error, errno=bb....bb, HiRDB file name=cc....cc

An error occurred when accessing a HiRDB file.

aa....aa: Process where the access error occurred

open: An open process of a HiRDB file

read: A read process from a HiRDB file

close: A close process of a HiRDB file

bb....bb: Error code of the HiRDB file system

cc....cc: HiRDB file name

S: Terminates processing.

O:

When bb....bb is error code -1562, the applicable HiRDB file system area may not be the UTL type. Check if the HiRDB file system area specified in the input is the correct type.

When bb....bb is an error code other than -1562, see 5.1 Error codes returned from HiRDB file system access requests to eliminate the error cause, and then re-execute.

KFPK00012-E E+L

aa....aa: file already exist, file_kind=bb....bb, file_name=cc....cc

Temporary work file created by the utility already exists.

aa....aa: Utility type

Pdstedit: Statistics analysis utility

bb....bb: File type

sort data file: Temporary work file

cc....cc: File name

S: Terminates processing.

O: Make sure that the same command is not executing concurrently, delete file cc....cc, and then re-execute the command.

KFPK00013-E D+E+L

aa....aa: system call error, func=bb....bb, file_name=cc....cc, errno=dd....dd

Error occurred with the system call (function) That accesses the file.

aa....aa: Utility type

Pdstedit: Statistics analysis utility

Pddbst: Database condition analysis utility

bb....bb: Name of system call causing the error

cc....cc: File name

dd....dd: Error number set in errno

S: When output to standard error, this message terminates processing. When output to a message dialog, the display returns to the screen displayed before the error occurred.

O: Check the error number (errno: external integer variable expressing the error status), see the documentation that describes errno.h and the applicable functions to eliminate the cause of the error, and then re-execute the command.

KFPK00050-E D+E+L

aa....aa: insufficient memory, size=bb....bb

A memory shortage occurred.

aa....aa: Utility:

Pddbst: Database condition analysis utility

Pdstedit: Statistics analysis utility

bb....bb: Size (in bytes) of area that was to be allocated

S:

Message is output to standard error:
Terminates processing.

Message is output to the error message dialog:
Redisplays the screen immediately before the error occurred.

O: Check for a process that uses a large amount of memory:

When there is a process using a large amount of memory:

Wait for the process to terminate, and then re-execute the command.

When there is no process using a large amount of memory:

Use one of the following methods to prepare sufficient memory:

Reduce the number of simultaneously executing processes.

Increase the size of the swap area.

Increase the memory.

KFPK00100-E D+E+L

aa....aa: interface error, func:bb....bb, return code=cccc

An interface error occurred between program functions.

aa....aa: Utility:

Pddbst: Database condition analysis utility

Pdstedit: Statistics analysis utility

bb....bb: Name of function that returned an invalid code

cccc: Detail code

S:

Message is output to standard error:
Terminates processing.

Message is output to the error message dialog:
Redisplays the screen immediately before the error occurred.

O: Contact the HiRDB administrator.

Action

Contact the customer support center.

KFPK00200-I E

Usage: pdstedit [-k edit_item[,edit_item]...]
[-m interval][-t [start_time][,end_time]]
[-u uap_name[,uap_name]...]
[-x host_name[,host_name]...]
[-s server_name[,server_name]...]
[-o dat_dir[-e ext_fmt[,ext_fmt]]][-i unload_log][-w work_dir]
[-d control_file][-b]

Following is a description of how to use the Statistics analysis utility (pdstedit):

-b: Specifies that the title bar is to be displayed for a DAT-format file.

-d: Specifies the name of the control statements file.

-e: Specifies the value of the extended format specification.

-i: Specifies the unload file or unload file storage directory.

-k: Specifies the types of statistical analysis information (more than one information type can be specified).

-m: Specifies the editing interval in minutes (up to 1440 can be specified).

-o: Specifies the name of the DAT-format file output destination directory.

-s: Specifies the server names (a maximum of 32 server names can be specified).

-t: Specifies the editing startup time and end time (the start time and end time cannot both be omitted).

-u: Specifies the UAP names (a maximum of 16 UAP names can be specified).

-x: Specifies the host names (a maximum of 32 host names can be specified).

-w: Specifies the name of the directory under which work files are to be created.

S: Terminates processing.

O: Check the pdstedit parameters for any errors.

KFPK00201-E E+L

aa....aa: invalid parameter

An invalid parameter was specified in the utility activation command. This message is displayed because an invalid option was specified:

aa....aa: Utility:

Pddbst: Database condition analysis utility

Pdstedit: Statistics analysis utility

S: Terminates processing.

O: Check for errors in each utility's runtime input parameters.

KFPK00202-E E+L

aa....aa: invalid combination of options

A combination of utility activation command options is invalid. Or, the combination of the options and the control statement is invalid.

aa....aa: Utility:

Pddbst: Database condition analysis utility

Pdstedit: Statistics analysis utility

S: Terminates processing.

O: Check for errors in the specification of each utility's runtime parameters (command line and control statements).

KFPK00203-E E+L

aa....aa: invalid bb option

Option bb is invalid in a utility activation command.
This message is displayed in one of the following cases:

No key is specified in the option.

Specified key format is invalid in the option.

The key specified in the option exceeds the repetitions limit.

The key specified in the option exceeds the limit.

The -G option was specified in an environment where the HiRDB Staticizer Option cannot be used.

Although not using the facility for predicting reorganization time (Y specified in the system definition pd_rorg_predict operand), the -e, -k pred, -m, -R, -c, or -v option was specified.

The pattern character string of the RDAREA batch specification includes a percent sign (%).

The pattern character string specified in the option consists of only asterisks (*).

aa....aa: Utility:

Pddbst: Database condition analysis utility

Pdstedit: Statistics analysis utility

b: Name of invalid option

S: Terminates processing.

O: Check each utility activation command for parameters that were entered incorrectly. If you need to correct the pattern character string of the RDAREA batch specification, see the manual HiRDB Version 9 Command Reference to determine how to specify a correct pattern character string, and then re-execute the command.

KFPK00204-E L+E

Invalid attribute exists in Control file, line=aa....aa

An invalid value was detected in line aa....aa of the control statement file specified in the -v option.

aa....aa: Control statement line number

S: Throws an SQLException.

O:

pddbst execution:

When executing the facility for predicting reorganization time (when -k pred is specified), check the control statement specification and correct the error. Then, re-execute pddbst.

If other than the above and the -v option is specified, delete the -v option and re-execute.

HiRDB CM execution:

Contact the HiRDB administrator.

Action

If this message is output during the execution of HiRDB CM, contact the customer support center.

KFPK00205-E E+L

Length of unload log file name exceeds bytes

Invalid file name was specified for the statistics analysis utility (pdstedit).

S: Terminates processing.

O: Check the parameters of the utility activation commands for errors.

KFPK00206-E E+L

aaaaaaaa: invalid directory name, kind=bb....bb

The name of a file creation directory specified in a utility activation command is invalid for one of the following reasons:

Specified directory was not found.

The command executor does not have write privilege for the specified directory.

The directory with the specified name does not have the directory attribute.

Specified directory name exceeds 128 bytes.

aaaaaaaa: Utility:

Pdstedit: Statistics analysis utility

bb....bb: Directory:

DAT data file: DAT format file creation

sort data file: Work file for sorting

S: Terminates processing.

O: Check for errors in the specification of each utility's runtime input parameters.

KFPK00207-E E

aaaaaa: unable to assume user id

For the reasons indicated below, the default for the authorization identifier cannot be assumed:

The PDUSER environment variable is undefined.

The authorization identifier or password defined in the PDUSER environment variable exceeds the maximum length.

In the authorization identifier or password defined in the PDUSER environment variable, double quotation marks (") are not paired.

An authorization identifier is not specified in the PDUSER environment variable.

aaaaaa: Utility:

Pddbst: Database condition analysis utility

S: Terminates processing.

O:

If the -u option is omitted when the command is executed, make sure the correct authorization identifier or password is specified in the PDUSER environment variable, and then re-execute the command.

When the Windows edition is being used and the -u option is omitted, check that the authorization identifier and password specified at the command prompt are not enclosed in single quotation marks (').

Example of correct specification:

PDUSER="root"/"root"

When specifying an authorization identifier or password in the client environment definition (hirdb.ini), enclose it in single quotation marks (').

Example of correct specification: PDUSER='"root"/"root"'

KFPK00208-E E

Invalid attribute exists in Base value file, line=aa....aa

One of the following errors occurred in line aa....aa of the standard value definition file specified in the -c option.

Invalid standard value item name

Invalid analysis specification

Invalid specification value descriptor or invalid range

aa....aa: Control statement line number

S: Terminates processing.

O: Check the contents of the standard value definition file, correct the specification error, and re-execute.

KFPK00210-E E

Number of RDAREA exceeded aaaa

The number of RDAREAs specified in flag arguments (excluding duplicates) exceeds the maximum value (aaaa).

aaaa: Maximum value

S: Terminates processing.

Action

Make sure that the number of RDAREAs specified in flag arguments (excluding duplicates) is at or below the maximum value. For the maximum number of RDAREAs that can be specified, see Specification of RDAREAs in operation commands and utilities in the manual HiRDB Version 9 Command Reference.

KFPK00250-W E

Invalid unload log file, file_name:aa....aa

An error was detected in the input file for the statistics analysis utility (pdstedit command).

When the input of the statistics input unload file specified for the statistics analysis utility is a file name:

A file of the specified file's type is not subject to analysis.

The specified file is not an unload statistics log file or unload log file

A pipe file was specified, but the file contained data other than an unload statistics log file. (UNIX edition only.)

The name of an unload statistics log file obtained in 64-bit mode HiRDB is specified in a 32-bit mode HiRDB.

When the input of the statistics input unload file specified for the statistics analysis utility is a directory name:

A file of file aa....aa's type in the specified directory is not subject to analysis.

The specified file is not an unload statistics log file or unload log file of file aa....aa under the specified directory.

The HiRDB file (aa....aa) in the HiRDB file system area in the specified directory is not an unload log file.

File aa....aa located in the specified directory is an unload statistics log file obtained in a 64-bit mode HiRDB; it cannot be input in a 32-bit mode HiRDB.

When the specified input of the statistics input unload file in the statistics analysis utility is a HiRDB file system area name

No HiRDB file was found in HiRDB file system area aa....aa.

HiRDB file aa....aa in the specified HiRDB file system area is not an unload log file.

HiRDB file aa....aa in the specified HiRDB file system area is being unloaded.

The user does not have read or write privileges to the specified HiRDB file system area.

aa....aa: File name

S: Resumes processing, ignoring the invalid file (does not edit the file).

O: Check the pdstedit command parameters for an error. Alternatively, if the user does not have the necessary privileges to the specified HiRDB file system area, grant the user read or write privileges.

KFPK00251-E E

Invalid log record, record_number:aa....aa

A log record is invalid.

aa....aa: Serial number of log record

S: Terminates processing.

O: Contact the HiRDB administrator.

Action

Check the data in the unload log file or unload statistics log file for any damage.

KFPK00252-E E

Invalid sort data file, cause:aa....aa file_name:bb....bb

A work file for sorting is invalid.

aa....aa: Reason:

corrupt record: Records are corrupted

invalid type: Not a work file for sorting

bb....bb: Invalid work file for sorting

S: Terminates processing.

O: Check that no change was made to the sort work file created internally by the pdstedit.

KFPK00253-E E

Invalid log block, block_number:aa....aa

A log block is invalid.

aa....aa: Serial number of log block

S: Terminates processing.

O: Contact the HiRDB administrator.

Action

Check the data in the unload log file for any damage.

KFPK00254-E E+L

aa....aa : Invalid contents in file, file_kind : bb....bb file_name : cc....cc record_length=dd....dd read_length=ee....ee

The contents of the input file are invalid. The file's contents may have been damaged.

aa....aa: Utility type:

Pdstedit: Statistics analysis utility

bb....bb: File type:

unload log file: Unload log file

unload stj log file: Unload statistics log file

sort data file: I/O file for sorting

cc....cc: File name

dd....dd: Record length that was to be loaded (maintenance information)

ee....ee: Length of the data that was loaded successfully (maintenance information)

S: Terminates processing.

O: Contact the HiRDB administrator.

Action

When the file type is unload log file or unload stj log file:

Check as follows for whether or not the data in the unload file has been damaged:

For data transfer using FTP, check if the data in the unload file has been damaged.

Check if the unload file has been updated illegally.
If the file type is unload log file:
In UNIX:
If the statistics log file (statistics log file named pdstj1 or pdstj2 that was output under $PDDIR/spool before unloading was performed using the OS's cp command or the pdstjacm shell script) before cc....cc was unloaded is available, use a command such as cmp to compare the contents of cc....cc with the contents of the file before unloading to make sure they are identical.
In Windows:
If the statistics log file output before cc....cc was unloaded is available, use the fc command to compare cc....cc and the contents of the file before it was unloaded, and make sure they are identical.
If the file type is unload stj log file:
If cc....cc is an unload log file that was backed up using the pdlogunld command and if there is a subsequent unload file acquired using the pdlogunld command and associated with that file, use the cmp command (in UNIX) or the fc command (in Windows) to compare the contents of the two files, and make sure they are identical.

When the file type is sort data file:

Check as follows for whether or not the I/O file for sorting that is created internally by the statistics analysis utility has been modified inadvertently:

In UNIX:

Check whether or not the files under $PDDIR/tmp or /usr/tmp were deleted or updated illegally during execution of the statistical analysis utility.

In Windows:

Determine whether a file under %PDDIR%\tmp was deleted or improperly updated during execution of the statistical analysis utility.

If none of the above is applicable, contact the customer support center.

KFPK00255-W E

aaaaaaaa:Invalid contents in file, file_kind:bb....bb file_name: cc....cc record_length=dd....dd read_length=ee....ee

The contents of the input file are invalid. The file's contents may have been damaged. Perform editing using the records that had been input before the invalid record was detected.

aaaaaaaa: Utility:

Pdstedit: Statistics analysis utility

bb....bb: File type:

unload log file: Unload log file

unload stj log file: Unload statistics log file

cc....cc: File name

dd....dd: Record length that was to be loaded (maintenance information)

ee....ee: Length of the data that was loaded successfully (maintenance information)

S: Continues processing.

O: Contact the HiRDB administrator. For the acquisition time for the log record that was input successfully, refer to FIRST and LAST in the input log file summary information.

Action

When the file type is unload log file or unload stj log file:

Check as follows for whether or not the data in the unload file has been damaged:

For data transfer using FTP, check if the data was transferred in the binary mode.

Check if the unload file has been updated illegally.

When the file type is unload stj log file:

Check that the disk at the statistics log file's output destination (%PDDIR%\spool) did not become full during acquisition of the statistics log file before unloading of cc....cc.

In UNIX, if the statistics log file (statistics log file named pdstj1 or pdstj2 that was output under $PDDIR/spool before unloading was performed using the OS's cp command or the pdstjacm shell script) before cc....cc was unloaded is available, use the cmp command to compare the contents of cc....cc and the file before it was unloaded, and make sure they are identical.
In Windows, if the statistics log file output before cc....cc was unloaded is available, use the fc command to compare cc....cc and the contents of the file before it was unloaded, and make sure they are identical.

When the file type is unload log file:

If cc....cc is an unload log file that was backed up using the pdlogunld command and if there is a subsequent unload file acquired using the pdlogunld command and associated with that file, use the cmp command (in UNIX) or the fc command (in Windows) to compare the contents of the two files, and make sure they are identical.

If none of the above is applicable, contact the customer support center.

KFPK00300-I E

Pdstedit terminated, return code=aa....aa

Execution of the statistics analysis utility is completed.

aa....aa: Return code:

0: Terminated normally

4: Terminated normally, but a warning message was issued

8: Processing was cancelled due to an error

12: Processing was cancelled due to an interrupt (signal generated)

S: Terminates processing.

O:

4 set as the return code:

Check the cause on the basis of the message with type W that was issued during processing.

8 set as the return code:

Check the cause on the basis of the message with type E that was issued during processing.

KFPK00301-I E

Stdin assumed as input

Processing was performed using the standard input, because the -i option was omitted, or processing was placed on input wait status, because the -i option was omitted. Therefore, the standard input was assumed.

S: Resumes processing.

O: Determine whether or not the processing should be resumed using the standard input. To cancel the processing, terminate the utility with the following methods:

Processing placed on input wait status:
Press the return key again.

Other:
In UNIX, specify a process ID, and enter the kill command.
In Windows, specify a process ID, and enter the pdkill command.

KFPK00400-E E

Sort program error

An error occurred during sort processing.

S: Terminates processing.

O: Refer to the preceding sort processing error message, and investigate the cause of the error. If the cause of the error cannot be identified, contact the HiRDB administrator.

Action

Correct the error and re-execute.

KFPK00901-E E

Unable to make an entry SQL_DB_STATE_ANALYZED

Because the result of condition analysis could not be registered in the database management table, the reorganizing time cannot be predicted for the most recent database condition.

S: Terminates processing.

O: Refer to the message# output before this message and eliminate the cause of the error. Then, re-execute pddbst, and register the result of condition analysis in the database management table.

#: For KFPA11204-E, pdmod must be used to create the RDAREA used by the data dictionary to store the database state analyzed table and the database management table.

KFPK00911-W E

Unable to make an entry SQL_DB_STATE_ANALYZED, RDID=aa....aa, OBJID=bb....bb, code=ccc

The facility for accumulating condition analysis results was executed in a merge analysis; the results could not be merged with the database state analysis table.

aa....aa: RDAREA ID

bb....bb: Table or index ID

ccc: Reason code for merge failure

-10: Table or index deleted during execution of pddbst

Other than above: Multiple pddbst commands executed simultaneously

S: Continues processing.

O: Do not execute multiple pddbst commands simultaneously on the same RDAREA. Also, do not delete a table or index during execution of pddbst.

KFPK00999-E L+E

HiRDB Control Manager interface file I/O error occurred, reason=aa....aa

An error occurred in the file that interfaces with HiRDB CM.

aa....aa: Error cause

PATH_NAME: The file path name is too long.

FILE_OPEN: File open failed.

FILE_WRITE: File write failed.

FILE_CLOSE: File close failed.

S: Terminates processing.

O:

If aa....aa is PATH_NAME, see the HiRDB CM manual, and change the file output destination.

If aa....aa is FILE_OPEN, FILE_WRITE, or FILE_CLOSE, refer to pdlog, the event log, or the KFPK00005-E or KFPK00010-E error message that was output to the event log (in UNIX, syslogfile) to resolve the error.

KFPK05200-E E+L

Invalid format exists in control file, line=aa....aa

The format of line aa....aa in the control statements file specified with the -d option of the statistics analysis utility is incorrect.

aa....aa: Line number resulting in the error during analysis

S: Terminates processing.

P: Correct the indicated line in the control statements file and re-execute the command.

KFPK05201-E E+L

Invalid attribute exists in control file, line=aa....aa

The value of line aa....aa in the control statements file specified with the -d option of the statistics analysis utility is incorrect.

aa....aa: Line number resulting in the error during analysis

S: Terminates processing.

P: Correct the indicated line in the control statements file and re-execute the command.

KFPK05202-E E+L

Line of file_group sentence in control file exceeds the limit

The number of file_group statements in the control statements file specified with the -d option of the statistics analysis utility exceeds the maximum.

S: Terminates processing.

P: Correct the control statements file so that the number of file_group statements specified does not exceed 34 and re-execute the command.

KFPK05203-E E+L

server name specified twice in control file, server_name: aa....aa

The same server name was specified more than once in the control statements file with the -d option of the statistics analysis utility.

aa....aa: Duplicated server name

S: Terminates processing.

P: Correct the control statements file so that the same server name is specified only once and re-execute the command.

KFPK05204-E E+L

Error occurred in log file group, server_name:aa....aa, file_name:bb....bb, reason=(cc....cc, dd....dd)

An error was detected in a log file group specified with a control statement of the statistics analysis utility.

aa....aa: Server name corresponding to the file group

bb....bb: File group name

cc....cc: Reason code

dd....dd: Detail code

S: Terminates processing.

Action

Following are the reason codes and actions:

Reason code
Explanation
Action

-1
Argument is invalid.
Contact the customer support center.

-2
Fatal error or unexpected error occurred.

-30
Error in log file definition analysis function
Refer to the error message output before this message to eliminate the cause of the error. The detail code consists of system maintenance information.

-31
Error in log file definition analysis
Log file definition has been changed incorrectly.
Refer to the detail code to return to the original definition.

Following are the detail codes:

Detail code | Explanation
-1 | File group name in definition is incorrect.
-2 | System A file name in definition is incorrect.
-3 | System B file name in definition is incorrect.
Other | Maintenance information

KFPK05300-I E

No data in log file, record_kind=aaa, reason=bb....bb

The log file that was to be subject to the analyses contained no records.

aaa: Record type:

sop: SQL static optimization information log records

dop: SQL dynamic optimization information log records

pcd: SQL object execution information log records

obj: SQL object transfer information log records

cnc: connect/disconnect information log records

sqh: SQL statement information log records

plg: Plug-in statistical information log records

bb....bb: Reason:

NOOPT:

-d option not specified:

The indicated edit item record was not found in the total analysis log file.

-d option specified:

The indicated edit item record was not found in the total analysis log file.

The server specified in the -s option was not defined in the control statements file specified in the -d option.

HOST:

There was no statistics log record that was output from the host specified in the -x option.

SERVER:

The statistical record output from the server specified in the -s option cannot be found.

UAP:

There was no statistics log record that was output from the UAP specified in the -u option.

TIME:

There was no statistics log record that was output within the edit interval specified in the -t option.

S: Resumes processing.

Action

Check the HiRDB Version 9 Command Reference for the message that is output when there is no edit data for the statistics analysis utility, and take appropriate action.

KFPK10012-E D+E

Transaction start error on aa....aa, func=bb....bb return code=cc....cc

An error occurred during transaction startup processing.

aa....aa: Name of server where the error occurred

bb....bb: Name of processing resulting in the error

cc....cc: Error code

S: Message is output to standard error:

Terminates processing.

Message is output to the error message dialog:

Redisplays the screen immediately before the error occurred.

O: Contact the HiRDB administrator.

Action

See 4. Error Detail Codes to eliminate the cause of the error, then re-execute the command. If the error cannot be corrected, contact the customer support center.

KFPK10013-E D+E

Transaction termination error on aa....aa, func=bb....bb return code=cc....cc

An error occurred during transaction termination processing.

aa....aa: Name of server where the error occurred

bb....bb: Name of processing resulting in the error

cc....cc: Error code

S: Message is output to standard error:

Terminates processing.

Message is output to the error message dialog:

Redisplays the screen immediately before the error occurred.

O: Contact the HiRDB administrator.

Action

See 4. Error Detail Codes to eliminate the cause of the error, then re-execute the command. If the error cannot be corrected, contact the customer support center.

KFPK10014-E D+E

aa....aa lock request failed, name=[bb....bb] "cc....cc"

Locking of a resource failed.

aa....aa: Resource type:

Index: Index

RDAREA: RDAREA

Table: Table

bb....bb: Authorization identifier (displayed only when aa....aa is Index or Table)

cc....cc: Name of resource

S: If the facility for accumulating condition analysis results is being executed and there is another process making exclusive use of the target resource, skips the analysis of the target resource, and continues processing. Information on the RDAREA whose processing is skipped is not accumulated.

Terminates processing in the following cases:

A locking error occurred due to other causes

The database condition analysis facility and the facility for predicting reorganization time are being executed

O: Refer to the message that is output to the message log file, resolve the error, and re-execute the command. If the output message is KFPA11770-I, wait until the other process making exclusive use of the target resource terminates, and then re-execute the command.

KFPK10015-E D+E

Directory access error, server=aa....aa

An error occurred while a directory was being accessed.

aa....aa: Server name

S: Message is output to standard error:

Terminates processing.

Message is output to the error message dialog:

Redisplays the screen immediately before the error occurred.

O: Eliminate the cause of the error on the basis of the message that was output to the log file, then re-execute the command. If the output message is KFPA11815-E, the table definition was modified during execution of the command. If that is the case, re-execute the command when the table definition is not being modified.

KFPK10016-E D+E

Insufficient memory in message buffer pool due to concurrent execution of "pddbst"

A temporary memory shortage occurred in the message storage buffer pool during process allocation when the database condition analysis utility (pddbst) was being executed concurrently.

S: Message is output to standard error:

Terminates processing.

Message is output to the error message dialog:

Redisplays the screen immediately before the error occurred.

O: Re-execute the command after execution of the current command is completed.

Action

If the pdchprc command was used to request services from a server for which the maximum number of startup processes had been set to 0, use the pdchprc command to increase the maximum number of startup processes.

If the pdpfresh command was used to request services from a server that is being refreshed, re-execute the UAP after the pdpfresh command terminates.

If utilities are being executed concurrently, review and, if necessary, revise the maximum number of utilities that can be executed at the same time. To find out the maximum number of utilities that can be executed concurrently, see the manual HiRDB Version 9 Command Reference.

KFPK10017-E D+E

Unable to send message from aa....aa to bb....bb

Data cannot be sent from host aa....aa to host bb....bb because a communication error occurred.

aa....aa: Send source host name#

bb....bb: Send destination host name#

#: If the system switching facility is being used, the host name of the primary system is indicated.

S: Message is output to standard error:

Terminates processing.

Message is output to the error message dialog:

Redisplays the screen immediately before the error occurred.

Action

Take action appropriate to the KFPK10100-E message output before this message. If the error was not a physical communication error, there may be an inconsistency in the system definitions concerning the relationship between the hosts; check the interhost definitions for the hosts affected by the error and re-execute.

KFPK10018-E E

Dynamic load error occurred, shared library=aa....aa

An error occurred in dynamic loading of a shared library required for processing.

aa....aa: Full path name of the shared library

S: Terminates processing.

O: Refer to the preceding KFPK00005-E message.

In UNIX:

Check the following, resolve the error, and re-execute the command:

GUI function used
Check whether X Window System and Hitachi Motif have been installed correctly

GUI function not used
Check whether processing is being executed with output of analysis results to standard output specified

In Windows:

Determine whether processing is being executed with output of analysis results to standard output specified, resolve the error, and re-execute the command.

KFPK10019-E E+D

HiRDB file error, func=aa....aa return code=bb....bb filename=cc....cc

An error that produces error code bb....bb occurred in file access function aa....aa for file cc....cc.

aa....aa: Function name

bb....bb: Error code

cc....cc: HiRDB file name

S: Terminates processing.

Action

Correct the error by referring to 5.1 Error codes returned from HiRDB file system access requests, and then re-execute.

KFPK10020-E D+E

RDAREA "aa....aa" not found

RDAREA "aa....aa" could not be found.
Possible cause:

RDAREA to be processed was deleted while a utility was running.

aa....aa: RDAREA name

S: Terminates processing.

O: When the RDAREA to be processed is deleted while a utility is running, reconstruct the environment so that the utility can be executed, and then re-execute the utility. If the RDAREA cannot be deleted, contact the customer support center.

KFPK10100-E D+E

RPC(system) error, func=aa....aa, return code=bbbbb

An RPC-related error or system-related error occurred.

aa....aa: Name of function resulting in the error

bbbbb: Error detail code

S: Message is output to standard error:

Terminates processing.

Message is output to the error message dialog:

Redisplays the screen immediately before the error occurred.

O: See 4. Error Detail Codes to eliminate the cause of the error and re-execute the command. If the HiRDB administrator cannot handle the error, contact the customer support center.

KFPK10101-E E

Unable to start pddbst

The database condition analysis utility cannot be started for one of the following reasons:

The maximum number of concurrently executable utilities has been reached.

HiRDB is engaged in termination processing.

S: Terminates processing.

O: Eliminate the cause of the error and restart.

KFPK10102-W D+E

Specified value not found in system aa....aa="bb....bb"

One of the following errors occurred:

The specified RDAREA name, table identifier, or index identifier was not found.

No replica RDAREA was found in the generation specified by the -q option.

ALL was specified in the second, or subsequent, position.

A pattern character string of only asterisks (*) was specified.

aa....aa: Identifier:

index: Index

RDAREA: RDAREA

table: Table

bb....bb: Specified identifier

S: Resumes processing.

O: Take one of the following actions:

Check whether the specified name exists in the system, specify the correct name, and then restart.

If multiple RDAREA names are specified and ALL is specified as the second, or subsequent, RDAREA name, specify ALL by itself and re-execute the command.

Specify the correct RDAREA name, not a pattern character string that consists of only asterisks (*), and then re-execute the command.

KFPK10103-W D+E

Unable to get status information
aa....aa="bb....bb" [server=ee....ee]
cc....cc="dd....dd" [server=ff....ff]

Information cannot be collected for the specified RDAREA or table identifier for one of the following reasons:

The server subject to analysis is not active.

The RDAREA subject to analysis is on the following status:

When the RDAREA attribute is INITIAL
The RDAREA is not on one of the following statuses:
Open without shutdown
Open with reference-possible backup hold
Referencing-possible backup-hold
Updatable backup-hold

When the RDAREA attribute is DEFER or SCHEDULE
The RDAREA is not on one of the following statuses:
Open without shutdown
Closed without shutdown
Open with reference-possible backup hold
Closed with reference-possible backup hold
Reference-possible backup hold
Updatable backup-hold

aa....aa: Identifier:

index: Index

RDAREA: RDAREA

table: Table

bb....bb: Specified identifier

cc....cc: Identifier:

index: Index

RDAREA: RDAREA

table: Table

dd....dd: Specified identifier

ee....ee: Server name

ff....ff: Server name

S: Resumes processing.

O: Address the reason that information could not be obtained and restart.

KFPK10104-W D+E

No select privilege for authorization id
aa....aa="bb....bb" [server=ee....ee]
cc....cc="dd....dd" [server=ff....ff]

The user does not have the SELECT privilege for the specified table or index authorization identifier.

aa....aa: Identifier:

index: Index

RDAREA: RDAREA

table: Table

bb....bb: Specified identifier

cc....cc: Identifier:

index: Index

RDAREA: RDAREA

table: Table

dd....dd: Specified identifier

ee....ee: Server name

ff....ff: Server name

S: Resumes processing.

O: Check if the user has the SELECT privilege for the table or index authorization identifier subject to analysis, specify a table or index permitted by the SELECT privilege, then re-execute the command.

KFPK10105-E D+E

Unable to connect to HIRDB, user=aa....aa

Connection with HiRDB cannot be established.

aa....aa: authorization identifier

S:

Message is output to standard error:

Terminates processing.

Message is output to the error message dialog:

Redisplays the screen immediately before the error occurred.

O:

SQL statement-related message issued before this message:

Eliminate the cause of the error indicated by the message and re-execute the command.

No SQL statement-related message issued before this message:

Check if the user has the DBA privilege for the HiRDB system and re-execute the command.

KFPK10106-W D+E

Unable to analyze aa....aa="bb....bb", kind=cc....cc

Cannot analyze the specified RDAREA, table identifier, or index identifier.

aa....aa: Analysis target:

RDAREA: RDAREA name

table: Table identifier

index: Index identifier

bb....bb: Name

cc....cc: Type:

When RDAREA is displayed in aa....aa:

master directory: Master directory RDAREA

data directory: Data directory RDAREA

list: List RDAREA

RDAREA for temporary table: Temporary table RDAREA

other: Others

When table is displayed in aa....aa:

view table: Viewed table

cluster: Table without a cluster key definition

temporary table: Temporary table

other: Other

When index is displayed in aa....aa:

temporary index: Temporary table index

other: Index

S:

Message is output to standard error:
Terminates processing.

Message is output to the error message dialog:
Redisplays the screen immediately before the error occurred.

O: Check if the specified resource is subject to analysis. If it is not subject to analysis, correct the specification and re-execute.

KFPK10107-W D+E

No data
RDAREA="aa....aa" server=bb....bb

Specified RDAREA contains no table or index, so the status cannot be displayed.

aa....aa: RDAREA name

bb....bb: Server name

S:

Message is output to standard error:
Terminates processing.

Message is output to the error message dialog:
Redisplays the screen immediately before the error occurred.

KFPK10108-W D+E

No original RDAREA
RDAREA="aa....aa"

The specified RDAREA is not the original RDAREA. If the facility for predicting reorganization time is used, the target is the original RDAREA.

aa....aa: RDAREA name

S: Continues processing.

O: Check to determine if the specified RDAREA is the original RDAREA. If it is not the original RDAREA, specify the original RDAREA and re-execute. Also, to perform condition analysis of the specified replica RDAREA, delete the -q option and re-execute.

KFPK10200-I E

Usage: pddbst -r rdarea_name [-k logi] [-d [-z]] [-a [-h]] [-q generation_number] [-u user_id[-p password]] [-b] [-v control_file_name] -r rdarea_name[,rdarea_name]... -k phys [-f] [-a [-h]] [-q generation_number] [-u user_id[-p password]] [-b] [-v control_file_name] | -t [auth_id.]table_name [-s] [-d] [-q generation_number] [-u user_id[-p password]] [-b] [-v control_file_name] | -t [auth_id.]table_name -k clus [-q generation_number] [-u user_id[-p password]] [-b] [-v control_file_name] | -i [auth_id.]index_name [-d [-z]] [-q generation_number] [-u user_id[-p password]] [-b] [-v control_file_name] | -r {rdarea_name | ALL} [-k logi] -e predict_level [-I] [-n divided_number] [-w sleep_time,segment_number] [-u user_id[-p password]] [-v control_file_name] | [-r ALL] -k pred [-m] -e predict_level [-R watch_time[,maintenance_extension_time]] [-c base_value_define_file_name] [-v control_file_name] [-u user_id[-p password]]

Displays the format of the pddbst utility.

-u: Specifies an authorization identifier.

-p: Specifies a password. This option must be specified together with the -u option.

-b: Specified to avoid online performance degradation of the application due to execution of pddbst.

-r: Specifies the name of an RDAREA. Specify this to perform analysis in units of RDAREAs. If -k phys is specified, multiple RDAREA names can be specified. If -k pred or -k logi -e is specified, -r all can be specified.

-k: Specifies the analysis type in units of RDAREAs. Specify either logi, phys, clus, or pred. Specify logi and phys in pairs with the -r option. Similarly, specify clus in pairs with the -t option. Specify pred when the facility for predicting reorganization time is used.

-d: Specifies the display of detailed information on a page.

-z: Specifies the display of detailed information about index entries. Specify together with -d.

-q: When a replica RDAREA is found, specifies the generation to be analyzed.

-f: Specifies that HiRDB file information is to be displayed.

-a: Specifies the display in DAT format.

-h: When displaying in DAT format, specifies to output the title bar. Specify together with -a.

-t: Specifies [authorization-identifier.] table-identifier. Specify this to perform analysis in units of tables.

-s: Specifies that the number of stored lines is to be analyzed in units of tables. This option can be specified when the -t option is specified. However, it cannot be specified when the -k option is specified.

-i: Specifies the index identifier. This option is specified to perform analysis in units of indexes. The -r option, the -t option, and the -i option cannot be specified together.

-e: When executing the condition analysis results depository facility or the facility for predicting reorganization time, this specifies the prediction level. Specify together with -k logi or pred.

-m: When -k pred -e 1 is specified, specifies performance of a detail analysis.

-R: Specifies the monitoring time and the maintenance delay time. Specify together with -k pred.

-c: Specifies the name of the standard value definition file. Specify together with -k pred.

-v: If the results of the facility for predicting reorganization time are to be output in CSV format or if the work file used by pddbst is to be output to a file other than %PDDIR%\tmp, specifies a control statement specifying an output destination file.

-I: When accumulating analysis information, specify this option when accumulated information on the RDAREA being analyzed is to be reset.

-n: Specify this option when analysis information is to be accumulated multiple times. For the accumulation of analysis information, this option can be specified if 2 is specified in the -e option.

-w: Specify this option when the accumulation of analysis information is to be executed in the background to transactions. For the accumulation of analysis information, this option can be specified if 2 is specified in the -e option.

S: Terminates processing.

O: Check the database condition analysis utility (pddbst) parameters for any errors.

KFPK10201-W D

No parameter in input area

Nothing is specified in the screen input area.

S: Redisplays the input screen on which the error occurred.

P: Set the appropriate value in the input area and re-execute.

KFPK10202-W D

Length of parameter is too long

The specification in the screen input area exceeds the maximum length.

S: Redisplays the input screen on which the error occurred.

P: Specify the correct value in the input area and re-execute.

KFPK10203-W D

Value of aa....aa is not specified

The specification on the screen is invalid. This message is output in either of the following cases:

Authorization identifier cannot be identified because a period is specified at the beginning of the table or index identifier

Table name or index name cannot be identified because a period is specified at the end of the table or index identifier.

An error was found in the specified generation number.

aa....aa: Item specified incorrectly:

authid: Authorization identifier

table name: Table name

index name: Index name

generation number: Generation number

S: Redisplays the input screen on which the error occurred.

O: Specify the correct value in the input area and re-execute.

KFPK10204-W D

Number of RDAREA names exceeds 128

More than 128 RDAREA names are specified.

S: Redisplays the input screen on which the error occurred.

O: Specify the correct values in the input area and re-execute.

KFPK10250-E D+E

User RDAREA inconsistent with dictionary, aaaaa-bb....bb."cc....cc"

Table or index subject to analysis was found in the dictionary but not in the user RDAREA. An inconsistency was found between the dictionary table and a user RDAREA or a user LOB RDAREA.

aaaaa: Identifier:

table: Table

index: Index

bb....bb: Authorization identifier

cc....cc: Specified identifier

S: Skips processing of the table or index resulting in the error and resumes processing.

O: Make sure the problem is not one of the types indicated below. If none of these potential causes applies, contact the customer support center.

If synchronization was ensured when a master directory RDAREA, a data directory RDAREA, and a data dictionary RDAREA were restored from their backups
In this case, perform restoration by ensuring synchronization. If synchronization was not achieved at the time of backup, unload all databases by using the database reorganization utility, re-initialize the databases, and re-create them.

If the status file was initialized and HiRDB was restarted without terminating HiRDB normally, or if HiRDB was started using the pdstart -dbdestroy command
In this case, re-create the database by re-initializing the database.

If tables and indexes were deleted during execution of the command
In this case, re-execute the command when table or index definitions are not being modified.

KFPK10251-W E

Unable to get status information, cause cluster index incomplete RDAREA="aa....aa"

The system was unable to obtain the correct information because the cluster index specified for analysis has not been created.

aa....aa: RDAREA name

S: Resumes processing.

O: Re-execute the command after creating the cluster index.

KFPK10300-I E

Pddbst started

Execution of the database condition analysis utility has started.

S: Resumes processing.

KFPK10301-I E

Pddbst terminated, return code=aa....aa

Execution of the database condition analysis utility is completed.

aa....aa: Return code:

0: Terminated normally

4: Terminated normally, but a warning message was issued. Or, part of the processing might have been skipped.

8: Processing was cancelled due to an error

S: Terminates processing.

O: If the return code is 4 or 8, refer to the warning or error message that is output to standard error or to the message log file, and resolve the error.

KFPK10311-I E

Applied objects nothing

The result of executing the facility for predicting reorganization time is that no resources require maintenance in the specified day range.

S: Continues processing.

KFPK10312-I E

Number of saved data a few, RDAREA aa....aa

Due to insufficient data for predicting with the facility for predicting reorganization time, prediction processing was skipped. For details on the amount of data required for predicting, see the section on the facility for predicting reorganization time in the manual HiRDB Version 9 Command Reference.

aa....aa: Name of the RDAREA

S: Continues processing.

Action

Execute the condition analysis results depository facility on the RDAREA to be analyzed, and after at least four results have been registered, re-execute.

KFPK10313-I E

No data in SQL_DB_STATE_ANALYZED

None of the data required for predicting using the facility for predicting reorganization time is in the condition analysis table (SQL_DB_STATE_ANALYZED).

S: Continues processing.

Action

Execute pddbst for the RDAREA to be analyzed, and register at least four condition analysis results in the condition analysis table. Then, re-execute.

KFPK10314-I E

aaaaa bb....bb."cc....cc" not found, in dd....dd

During execution of the facility for predicting reorganization time, resources in the RDAREA were deleted.

aaaaa: Resource type in the RDAREA

TABLE: Table

INDEX: Index

bb....bb: Authorization identifier

cc....cc: Table identifier or index identifier

dd....dd: Name of the RDAREA

S: Continues processing.

Action

Register the condition analysis result of the condition analysis results depository facility, and re-execute the facility for predicting reorganization time.

KFPK10315-I E

Unable to predict due to data on same time, RDAREA aa....aa

For the following reason, prediction cannot be made from the analysis information table, and so processing of the prediction target RDAREA was skipped.

Data of the prediction target RDAREA was all collected at the same time (within 1 second).

aa....aa: Name of the RDAREA to be analyzed

S: Continues processing.

Action

Execute the condition analysis results depository facility on the prediction target RDAREA at an appropriate interval (in units of 1 day is recommended), and re-execute the facility for predicting reorganization time.

KFPK10316-I E

Number of saved data a few, RDAREA aa....aa, bb....bb=cc....cc.dd....dd

Prediction processing on a table or index in an RDAREA was skipped, because the amount of data necessary for prediction by the facility for predicting reorganization time was insufficient.

aa....aa: RDAREA name

bb....bb: Analysis type

table: Table

index: Index

cc....cc: Authorization identifier

Displays "(Data dictionary)" in the case of a dictionary table or an index in a dictionary table.

dd....dd: Table identifier or index identifier

S: Continues processing.

Action

Execute the facility for accumulating condition analysis results on the RDAREA storing the table or index that is the object of prediction, register four or more pieces of analysis information, and then re-execute the command.

KFPK10400-E D+E

Sort program error -aa....aa

An error occurred during sorting.

aa....aa: Cause of the error:

destroyed file,file_name: Name of the damaged file

incorrect version: Invalid version

insufficient memory: Insufficient memory

I/O error,file_name: Name of file resulting in the I/O error

logical error (maintenance-code): Logical error

S:

Message is output to standard error:
Terminates processing.

Message is output to the error message dialog:
Redisplays the screen immediately before the error occurred.

O: Check the cause of the error on the basis of the displayed cause, correct the error, then re-execute. In the case of a logical error, contact the customer support center.

KFPK10450-E E

Pddbst must be executed at unit defined as manager

The database condition analysis utility must be executed on the unit where the system manager (MGR) is defined.

S: Terminates processing.

O: Re-execute the utility on the unit where the system manager (MGR) is defined.

KFPK10451-E E

Unable to analyze with -e option, aa....aa

For one of the following reasons, condition analysis result processing with the -e option specification could not be executed:

The system definition pd_rorg_predict operand is not Y.

The data dictionary RDAREA that stores the analysis information table and the database management table does not exist.

The replica RDAREA is specified by the -q option.

aa....aa: {not predict mode 'Y' | not found datadictionary of dbmanagement | on replica RDAREA}

S: Terminates processing.

Action

When using the facility for predicting reorganization time, take the following actions:

Specify Y in the system definition pd_rorg_predict operand, and restart HiRDB. Then, execute the facility for predicting reorganization time.

Use pdmod to create the data dictionary RDAREA to store the analysis information table and the database management table, and then execute the facility for predicting reorganization time.

Remove the specification of the -q option, and execute the facility for predicting reorganization time.

KFPK10999-E D+E

Directory kind=aa....aa, file=bb....bb, line=cc....cc

Outputs information about the directory where an access error occurred.

aa....aa: Directory type

SGMB: Segment-managing directory

bb....bb: Internal information 1 (name of the analyzed file)

cc....cc: Internal information 2 (analyzed row)

S: Terminates processing.

O: Refer to the preceding message, resolve the error, and then re-execute the command.

2.8 KFPL messages

KFPL00607-I L+S

aa....aa load started

Index or LOB data loading started.

aa....aa: Data that started loading

Index: Index

LOB: LOB data

S: Continues processing.

KFPL00608-I L+S

aa....aa load ended

Index or LOB data loading terminated.

aa....aa: Data that finished loading

Index: Index

LOB: LOB data

S: Continues processing.

KFPL00615-I L+S

aa....aa load started, server=bb....bb

Server bb....bb index data loading started.

aa....aa: Data that has started loading

Index: Index

bb....bb: Server name

S: Continues processing.

KFPL00616-I L+S

aa....aa load ended, server=bb....bb

Server bb....bb index data loading terminated.

aa....aa: Data that finished loading

Index: Index

bb....bb: Server name

S: Continues processing.

KFPL00621-I L+S

aa....aa in table bb....bb. cc....cc deleted

Row or LOB data was deleted from table bb....bb.cc....cc.

aa....aa: Type of data that was deleted

Data: Row data

LOB data: LOB data

bb....bb: Authorization identifier

cc....cc: Table identifier

S: Continues processing.

KFPL00622-I L+S

aa....aa in table bb....bb. cc....cc deleted, server=dd....dd

Server dd....dd row or LOB data was deleted from table bb....bb.cc....cc.

aa....aa: Type of data that was deleted

Data: Row data

LOB data: LOB data

bb....bb: Authorization identifier

cc....cc: Table identifier

dd....dd: Server name

S: Continues processing.

KFPL00700-I L+S

Retry reopen aa-time of bb after cc-minute, host=dd....dd, file=ee....ee, reason=ff....ff

Multivolume reopen processing will be performed cc minutes from now. The maximum retries count is bb, and the next retry is number aa. The name of the file is ee....ee, and its host name is dd....dd.

aa: Next retry number

bb: Maximum retries count

cc: Retry interval

dd....dd: Host name

ee....ee: File name

If the length of the file name exceeds 104 characters, the last 104 characters of the file name are output.

ff....ff: Reason for retry:

No-file: File is not set.

Same-file: The same file as before is set

S: Resumes processing.

O: Set the next file during retry processing.

KFPL00701-I L+S

File swapping started, file=aa....aa, reason=bb....bb

Processing has begun on file aa....aa on the second or subsequent volume of a multivolume file.

aa....aa: File name

If the length of the file name exceeds 150 characters, the last 150 characters of the file name are output.

bb....bb: Reason code:

ENOSPC: There is no more space on the device

EOV: End-of-volume was detected

S: Resumes processing.

KFPL00702-I L+S

Pdload started, table=aa....aa.bb....bb, cc....cc, dd....dd

Data loading or file partitioning (creation of the partitioning input data file) has started.

aa....aa: Authorization identifier

bb....bb: Table identifier

cc....cc: Double-byte space conversion level (spacelvl=space-conversion-level)

If the space conversion level is specified in the system common definition pd_space_level operand or the database load utility option statement's spacelvl operand, this displays spacelvl=space-conversion-level. Further, if space conversion processing is not performed, spacelvl=space-conversion-level is not displayed.

dd....dd:

For data loading:

generation=generation-number is displayed. However, this is only valid when the HiRDB Staticizer Option is included.

For file partitioning:

mode=split is displayed.

S: Resumes processing.

KFPL00703-I L+S

aa....aa rows loaded

aa....aa rows were stored.
When data is loaded into a FIX table in which a reserved column is defined, make sure that the number of rows being stored matches the number of rows in the input data file. If they do not match, some data from the input file might be loaded into the reserved column.

aa....aa: Number of rows stored

S: Resumes processing.

KFPL00704-I L+S

Pdload terminated, return code=aa

pdload utility processing is completed.

aa: Return code:

For data loading:

0: Data loading terminated normally.

4: Data loading terminated normally; however, a processing-unrelated warning error occurred or an input data error was detected, and some of the data was not stored.

8: Data loading terminated abnormally. Further, this return code is output even with an input data error, when there is a duplicate key error with the dataerr=rollback operand specified or the -i c option (index batch creation mode) is specified.

For file partitioning (creation of the partitioning input data file):

0: All data in the input data file is output to the partitioning input data file.

4: Normal data in the input data file was output to the partitioning input data file. However, error data was not output to the partitioning input data file.

8: Creation of the partitioning input data file terminated abnormally.

S: Terminates processing.

O:

8 set as the return code:
Refer to the error message that was output to standard error or message log file to eliminate the cause of the error, then re-execute the command. Further, if data loading was executed in no-log mode, and the RDAREA performs a logless shutdown or a duplicate key error is detected during batch index creation, which leads to incompatibility between the tables and the indexes, return the database to its status before the database load utility (pdload) was executed, and then re-execute.

4 set as the return code:
Check for erroneous data by referring to the error information file. If there is any erroneous data, for data loading, re-execute data loading with the corrected data only. For file partitioning, correct the data, and then re-execute the database load utility.

KFPL00705-I L+S

aa....aa rows processing

Row aa....aa is being processed.

aa....aa: Number of rows

S: Resumes processing.

KFPL00706-I L+S

Partial input data file split started, part=a/b

Out of b total execution iterations required to create a partitioning input data file, processing of iteration a has started (in units of 1,024 RDAREAs).

a: Current execution iteration count

b: Total number of iterations to be executed

S: Continues processing.

KFPL00707-I L+S

LOB load started, RDAREA=aa....aa

Data loading of LOB data to the LOB RDAREA aa....aa has started.
The output destination for this message depends on the value specified in the -m option of the utility that was executed. For details about the -m option, see the manual HiRDB Version 9 Command Reference.
The following table indicates the output destinations corresponding to the value specified in the -m option:

Value specified in -m option
Output destination of message

lvl0
Log file (L) and standard output (S)

lvl1
Log file (L)

lvl2
Neither the log file (L) nor standard output (S)
However, the message is output to the work file.

aa....aa: RDAREA name

S: Continues processing.

KFPL00708-I L+S

LOB load ended, RDAREA=aa....aa, return code=bb

Data loading of LOB data to the LOB RDAREA aa....aa has ended with return code bb.
The output destination for this message depends on the value specified in the -m option of the utility that was executed. For details about the -m option, see the manual HiRDB Version 9 Command Reference.
The following table indicates the output destinations corresponding to the value specified in the -m option:

Value specified in -m option
Output destination of message

lvl0
Log file (L) and standard output (S)

lvl1
Log file (L)

lvl2
Neither the log file (L) nor standard output (S)
However, the message is output to the work file.

aa....aa: RDAREA name

bb: Return code

0: Data loading of LOB data terminated normally.

8: Data loading of LOB data terminated abnormally.

S: Continues processing if the return code is 0. Terminates processing if the return code is 8.

O: If the return code is 8, refer to the error message output to standard error output, the message log file, or the error information file, and eliminate the cause of the error. Then, use a LOB intermediate file to re-execute data loading for the LOB RDAREA that had the error or the LOB RDAREA that was not processed.

KFPL00709-I L+S

aa....aa file was created, file=bb....bb

Because specification of an error information file or a LOB intermediate file was omitted, file bb....bb was created.
SQL definition file bb....bb was created.

aa....aa: File type

Error information: Error information file

Lobmid: LOB intermediate file

SQLDef: SQL definition file

bb....bb: Unique file name generated by the system

If the length of the file name exceeds 150 characters, the last 150 characters of the file name are output.

S: Resumes processing.

KFPL00710-I L+S

Index information file assigned, index=aa....aa.bb....bb, RDAREA=cc....cc. file=dd....dd

Index information for RDAREA cc....cc of index aa....aa.bb....bb was output to dd....dd.
The output destination for this message depends on the value specified in the -m option of the utility that was executed. For details about the -m option, see the manual HiRDB Version 9 Command Reference.
The following table indicates the output destinations corresponding to the value specified in the -m option:

Value specified in -m option
Output destination of message

lvl0
Log file (L) and standard output (S)

lvl1
Log file (L)

lvl2
Neither the log file (L) nor standard output (S)
However, the message is output to the work file.

aa....aa: Authorization identifier

bb....bb: Index identifier

cc....cc: RDAREA name

dd....dd: File name

If the length of the file name exceeds the value obtained from the following formula, the last number of characters obtained from the formula are output.

150 - authorization-identifier-length - index-name-length - RDAREA-name-length

S: Resumes processing.

KFPL00711-I L

aa....aa started. table=bb....bb."cc....cc", RDAREA="dd....dd"

The aa....aa process started.
RDAREA dd....dd of table bb....bb."cc....cc" is to be processed.

aa....aa:

pdloadm: pdload control process

pdsds: Single server process

pdbes: Back-end server process

bb....bb: Authorization identifier

cc....cc: Table identifier

dd....dd: RDAREA name

For loading of table unit data, an asterisk (*) is displayed.

S: Continues processing.

KFPL00712-I L+S

aa....aa started, table=bb....bb.cc....cc, server=dd....dd,spacelvl=e, generation=ff

Unload or reload processing has started for table bb....bb.cc....cc at server dd....dd.
spacelvl=e is displayed when a space conversion level is specified in the spacelvl operand of the option statement of the database reorganization utility. spacelvl=e is not displayed if no space conversion is performed by the utility.
When the inner replica facility is being used, generation=ff is displayed.

aa....aa: Executed processing:

{ LOB reload|LOB unload|Reload|Unload }

bb....bb: Authorization identifier

cc....cc: Table identifier

dd....dd: Server name

e: Space conversion level

ff: Generation number

S: Resumes processing.

KFPL00713-I L+S

aa....aa rows bbbbbb, table=cc....cc.dd....dd, server=ee....ee

aa....aa rows of table cc....cc.dd....dd on server ee....ee were unloaded or reloaded.

aa....aa: Number of rows processed

bbbbbb: Executed processing:

{ unloaded|reloaded }

cc....cc: Authorization identifier

dd....dd: Table identifier

ee....ee: Server name

If the -g option is specified with respect to a row-partitioned table, displays the name of the server storing the RDAREA that matches the last partitioning condition in the table definition.

S: Resumes processing.

KFPL00714-I L+S

aa....aa ended, table=bb....bb.cc....cc, server=dd....dd, return code=ee

Unload processing, reload processing, used free page release processing, or used page read processing has terminated for table bb....bb.cc....cc at server dd....dd.

aa....aa: Executed processing:

{ Unload|Reload|LOB unload|LOB reload|Reclaim|Page read }

bb....bb: Authorization identifier

cc....cc: Table identifier

dd....dd: Server name

ee: Return code

S: If the return code is 0 or 4, resumes processing; otherwise, terminates processing.

O: If the return code is neither 0 nor 4, refer to the error message that was output to the message log file to eliminate the cause of the error, then re-execute the command.

KFPL00715-I L+S

Index load started at aa....aa, index=bb....bb."cc....cc", RDAREA=dd....dd, generation=ee

Index loading has started.
When the inner replica facility is being used, generation=ee is displayed.
The output destination for this message depends on the value specified in the -m option of the utility that was executed. For details about the -m option, see the manual HiRDB Version 9 Command Reference.
The following table indicates the output destinations corresponding to the value specified in the -m option:

Value specified in -m option
Output destination of message

lvl0
Log file (L) and standard output (S)

lvl1
Log file (L)

lvl2
Neither the log file (L) nor standard output (S)
However, the message is output to the work file.

aa....aa: Server name

bb....bb: Authorization identifier

cc....cc: Index identifier

dd....dd: RDAREA name

ee: Generation number

S: Resumes processing.

KFPL00716-I L+S

Index load ended at aa....aa, index=bb....bb, RDAREA=cc....cc, return code=dd

Index loading terminated with return code dd.
The output destination for this message depends on the value specified in the -m option of the utility that was executed. For details about the -m option, see the manual HiRDB Version 9 Command Reference.
The following table indicates the output destinations corresponding to the value specified in the -m option:

Value specified in -m option
Output destination of message

lvl0
Log file (L) and standard output (S)

lvl1
Log file (L)

lvl2
Neither the log file (L) nor standard output (S)
However, the message is output to the work file.

aa....aa: Server name

bb....bb: Index identifier

cc....cc: RDAREA name

dd: Return code:

0: Normal termination

8: Abnormal termination

S: Resumes processing.

O: If the processing terminated abnormally, refer to the error message that was displayed before this message to eliminate the cause of the error.

KFPL00717-I L+S

Pdrorg started, func=aaaa

Database reorganization utility processing aaaa has started.

aaaa: Processing:

rorg: Table reorganization

unld: Table unloading

reld: Table reloading

ixmk: Batch index creation

ixrc: Index re-creation

ixor: Index reorganization

rclm: Used free page release processing

bfon: Page read processing

S: Resumes processing.

KFPL00719-I L+S

Pdrorg terminated, return code=aa

Database reorganization utility (pdrorg) processing has terminated.

aa: Return code:

0: Terminated normally.

4: Terminated normally, but a processing-unrelated warning error occurred.

8: Terminated abnormally.

S: Terminates processing.

O: If the return code is neither 0 nor 4, refer to the error message that was output to standard output or message log file to eliminate the cause of the error, then re-execute the command.

KFPL00720-I L+S

aaaaa file bb....bb, server=cc....cc, file=dd....dd

An index information file was deleted.
The output destination for this message depends on the value specified in the -m option of the utility that was executed. For details about the -m option, see the manual HiRDB Version 9 Command Reference.
The following table indicates the output destinations corresponding to the value specified in the -m option:

Value specified in -m option
Output destination of message

lvl0
Log file (L) and standard output (S)

lvl1
Log file (L)

lvl2
Neither the log file (L) nor standard output (S)
However, the message is output to the work file.

aaaaa: Index

bb....bb: deleted

cc....cc: Server name

dd....dd: File name

If the length of the file name exceeds 150 characters, the last 150 characters of the file name are output.

S: Resumes processing.

KFPL00721-I L+S

aa....aa in table bb....bb.cc....cc deleted, RDAREA=dd....dd

Row data or LOB data was deleted from table bb....bb.cc....cc in RDAREA dd....dd.
The output destination for this message depends on the value specified in the -m option of the utility that was executed. For details about the -m option, see the manual HiRDB Version 9 Command Reference.
The following table indicates the output destinations corresponding to the value specified in the -m option:

Value specified in -m option
Output destination of message

lvl0
Log file (L) and standard output (S)

lvl1
Log file (L)

lvl2
Neither the log file (L) nor standard output (S)
However, the message is output to the work file.

aa....aa: Type of data that was deleted:

Data: Row data

LOB data: LOB data

bb....bb: Authorization identifier

cc....cc: Table identifier

dd....dd: RDAREA name

S: Resumes processing.

KFPL00722-I L+S

Unload file output completely, server=aa....aa, file=bb....bb

Output to an unload data file has been completed at server aa....aa.

aa....aa: Server name

bb....bb: Name of unload data file

If the length of the unload data file name exceeds 150 characters, the last 150 characters of the unload data file name are output.

S: Resumes processing.

KFPL00723-I L+S

aa....aa rows bb....bb, table=cc....cc.dd....dd, RDAREA=ee....ee

bb....bb processing for aa....aa rows was executed for RDAREA ee....ee in table cc....cc.dd....dd.
The output destination for this message depends on the value specified in the -m option of the utility that was executed. For details about the -m option, see the manual HiRDB Version 9 Command Reference.
The following table indicates the output destinations corresponding to the value specified in the -m option:

Value specified in -m option
Output destination of message

lvl0
Log file (L) and standard output (S)

lvl1
Log file (L)

lvl2
Neither the log file (L) nor standard output (S)
However, the message is output to the work file.

aa....aa: Number of rows processed

bb....bb: Processing type

{ loaded|unloaded|reloaded }

cc....cc: Authorization identifier

dd....dd: Table identifier

ee....ee: RDAREA name

S: Resumes processing.

KFPL00724-I L+S

Index not created, index=aa....aa.bb....bb, RDAREA=cc....cc

Because index aa....aa.bb....bb in RDAREA cc....cc is only part of a non-partitioned index, the index is left on uncompleted status.
The output destination for this message depends on the value specified in the -m option of the utility that was executed. For details about the -m option, see the manual HiRDB Version 9 Command Reference.
The following table indicates the output destinations corresponding to the value specified in the -m option:

Value specified in -m option
Output destination of message

lvl0
Log file (L) and standard output (S)

lvl1
Log file (L)

lvl2
Neither the log file (L) nor standard output (S)
However, the message is output to the work file.

aa....aa: Authorization identifier

bb....bb: Index identifier

cc....cc: RDAREA name

S: Resumes processing.

O: Create the index using the index information file for the entire index.

KFPL00725-I L+S

Index aa....aa started at bb....bb, index=cc....cc."dd....dd", RDAREA="ee....ee", source=ff....ff, generation=gg

Index information unload processing has started.
When the inner replica facility is being used, generation=gg is displayed.
The output destination for this message depends on the value specified in the -m option of the utility that was executed. For details about the -m option, see the manual HiRDB Version 9 Command Reference.
The following table indicates the output destinations corresponding to the value specified in the -m option:

Value specified in -m option
Output destination of message

lvl0
Log file (L) and standard output (S)

lvl1
Log file (L)

lvl2
Neither the log file (L) nor standard output (S)
However, the message is output to the work file.

aa....aa: unload

bb....bb: Server name

cc....cc: Authorization identifier

dd....dd: Index identifier

ee....ee: RDAREA name

****** is displayed for the RDAREA name in the case of index re-creation by index (idxname statement specified) or in the case of index reorganization.

ff....ff: Data to be unloaded:

row: Table data

key: Index key

gg: Generation number

S: Resumes processing.

KFPL00726-I L+S

Index aa....aa ended at bb....bb, index=cc....cc."dd....dd", RDAREA="ee....ee", return code=ff....ff

Index information unload processing is completed.
The output destination for this message depends on the value specified in the -m option of the utility that was executed. For details about the -m option, see the manual HiRDB Version 9 Command Reference.
The following table indicates the output destinations corresponding to the value specified in the -m option:

Value specified in -m option
Output destination of message

lvl0
Log file (L) and standard output (S)

lvl1
Log file (L)

lvl2
Neither the log file (L) nor standard output (S)
However, the message is output to the work file.

aa....aa: unload

bb....bb: Server name

cc....cc: Authorization identifier

dd....dd: Index identifier

ee....ee: RDAREA name

****** is displayed for the RDAREA name in the case of index re-creation by index (idxname statement specified) or in the case of index reorganization.

ff....ff: Return code (0: normal termination; 8: abnormal termination)

S: Resumes processing.

O: In the case of abnormal termination, check the message that was output before this message, eliminate the cause of the error, then re-execute the command.

KFPL00727-I L+S

aa....aa keys processed, index=bb....bb."cc....cc", RDAREA="dd....dd"

aa....aa plug-in indexes were batch-created.
The output destination for this message depends on the value specified in the -m option of the utility that was executed. For details about the -m option, see the manual HiRDB Version 9 Command Reference.
The following table indicates the output destinations corresponding to the value specified in the -m option:

Value specified in -m option
Output destination of message

lvl0
Log file (L) and standard output (S)

lvl1
Log file (L)

lvl2
Neither the log file (L) nor standard output (S)
However, the message is output to the work file.

aa....aa: Number of records

bb....bb: Authorization identifier

cc....cc: Index identifier

dd....dd: RDAREA name

S: Continues processing.

KFPL00728-I L+S

Index not reorganized, PLUGIN index aa....aa."bb....bb"

Plug-in index aa....aa."bb....bb" is included in the indexes to be reorganized. Because plug-in indexes cannot be reorganized, reorganization processing for the plug-in index was skipped.

aa....aa: Authorization identifier

bb....bb: Index identifier

S: Continues processing.

O: If the plug-in index needs to be re-created, take one of the following actions:

Reorganize the table for which the plug-in index is defined

Re-create the plug-in index

KFPL00732-I L+S

aa....aa started, table=bb....bb.cc....cc, spacelvl=d, generation=ee

Unload or reload processing for table bb....bb.cc....cc has started.
spacelvl=d is displayed when a space conversion level is specified by the spacelvl operand of the option statement of the database reorganization utility. spacelvl=d is not displayed if no space conversion is performed by the utility.
When the inner replica facility is being used, generation=ee is displayed.

aa....aa: Processing that was executed:

{ LOB reload | LOB unload | Reload | Unload }

bb....bb: Authorization identifier

cc....cc: Table identifier

d: Space conversion level

ee: Generation number

S: Resumes processing.

KFPL00733-I L+S

aa....aa rows bb....bb, table=cc....cc.dd....dd

Unload or reload processing for aa....aa rows has started for table cc....cc.dd....dd.

aa....aa: Number of processed rows

bb....bb: Processing type:

unload: Unloading

reload: Reloading

cc....cc: Authorization identifier

dd....dd: Table identifier

S: Resumes processing.

KFPL00734-I L+S

aa....aa ended, table=bb....bb.cc....cc, return code=dd

Unload or reload processing for table bb....bb.cc....cc has terminated.

aa....aa: Processing type:

Unload: Unloading

Reload: Reloading

LOB unload: LOB data unloading

LOB reload: LOB data reloading

bb....bb: Authorization identifier

cc....cc: Table identifier

dd: Return code

S: Return code 0 or 4: Resumes processing.

Return code other than 0 or 4: Terminates processing.

O: Return code other than 0 or 4:

Refer to the error message that was output to the log file to eliminate the cause of the error, then re-execute the command.

KFPL00735-I L+S

Unload file output completed, file=aa....aa

Output processing of an unload data file terminated.

aa....aa: Unload data file name

If the length of the unload data file name exceeds 150 characters, the last 150 characters of the unload data file name are output.

S: Resumes processing.

KFPL00736-I L+S

Pdrorg restarted, at aa....aa,table=bb....bb."cc....cc"dd....dd

The table reorganization process was restarted from aa....aa.

aa....aa: Process type

unload: Unload process

delete: Data deletion process

reload: Reload process

ixrc: Index re-create process

status clear: Status clear process

bb....bb: Authorization identifier

cc....cc: Table identifier

dd....dd: ", server=server-name" is displayed when the -g option is not specified.

S: Continues processing.

KFPL00738-I L+S

Pdpgbfon terminated, return code=aa

Processing of the global buffer residence utility (pdpgbfon) Terminated with return code aa.

aa: Return code

0: Terminated normally (reading into the global buffer completed).

4: A buffer flush occurred (not all pages were read into the global buffer).

8: Terminated abnormally (reading into the global buffer failed).

12: Terminated abnormally (pdrorg could not start, or it terminated abnormally).

S: Terminates processing.

O:

If the return code is 4:

If all table and index pages must be read into the global buffer, consider extending the global buffer. If there is an increase in dummy pages due to reduced data storage efficiency, resulting in an increased volume of used pages, consider releasing free pages or reorganizing the database.

If the return code is 8:

Refer to the message that was output before this message, and eliminate the cause of the error. Then, re-execute.

If the return code is 12:

Execution of pdrorg operating as an extension of pdpgbfon failed. Refer to the message that is output to standard error, the message log file, or the event log (in UNIX, syslogfile), resolve the error that caused abnormal termination of pdrorg, and then re-execute the command. For the system function return values to determine the reason for the execution of pdrorg failing, see the KFPL22000-E message output immediately before this message.

KFPL00739-I L+S

Pdreclaim terminated, return code=aaa

The free page release utility (pdreclaim) process terminated with return code aaa.

aaa: Return code:

0: Normal termination (releasing of used free page is complete)

4: A time-out occurred (now releasing a used free page)

8: Abnormal termination (releasing of used free page failed)

Other values: Abnormal termination (pdrorg cannot be started or pdrorg terminated abnormally).

S: Terminates processing.

O:

When the return code is 4:
Increase the wait time specified with the -w option. Alternatively, wait for the UAP accessing the table in which used free pages are to be released to terminate, and then re-execute.

When the return code is 8:
See the message output before this message to eliminate the cause of the error, and then re-execute.

When the return code is not 0, 4, or 8:
Failed to execute pdrorg when extending pdreclaim. The value returns to the return value of the system function. Refer to the message that is output to standard error, the message log file, or the event log (in UNIX, syslogfile), resolve the error that caused abnormal termination of pdrorg, and then re-execute the pdreclaim command.

KFPL00740-I L+S

Error exists in command line, usage is as follows

An error was detected in the specified command. The command's format is output after this message.

S: Terminates processing.

O: Correct the error in the command and re-execute.

KFPL00750-I L+S

Audit trail aa....aa file load started(b,c,d), file=ee....ee

Data began loading into the audit trail table.
The output destination for this message depends on the value specified in the -m option of the utility that was executed. For details about the -m option, see the manual HiRDB Version 9 Command Reference.
The following table indicates the output destinations corresponding to the value specified in the -m option:

Value specified in -m option
Output destination of message

lvl0
Log file (L) and standard output (S)

lvl1
Log file (L)

lvl2
Neither the log file (L) nor standard output (S)
However, the message is output to the work file.

aa....aa: Generation

b: c (current) or s (other than current)

c: d (waiting for data loading) or - (data loading is complete)

d: h (currently holding) or - (not currently holding)

ee....ee: Absolute path name of the audit trail file

If the length of the file name exceeds 150 characters, the last 150 characters of the file name are output.

S: Continues processing.

KFPL00751-I L+S

Audit trail aa....aa file loaded, file=bb....bb

Data has been loaded into the audit trail table.
The output destination for this message depends on the value specified in the -m option of the utility that was executed. For details about the -m option, see the manual HiRDB Version 9 Command Reference.
The following table indicates the output destinations corresponding to the value specified in the -m option:

Value specified in -m option
Output destination of message

lvl0
Log file (L) and standard output (S)

lvl1
Log file (L)

lvl2
Neither the log file (L) nor standard output (S)
However, the message is output to the work file.

aa....aa: Generation

bb....bb: Absolute path name of the audit trail file

If the length of the file name exceeds 150 characters, the last 150 characters of the file name are output.

S: Continues processing.

KFPL00791-I L+S

Pdparaload started, table=aa....aa."bb....bb"

Parallel loading of table aa....aa."bb....bb" was started.

aa....aa: Authorization identifier

bb....bb: Table identifier

S: Continues processing.

KFPL00792-I L+S

Pdload execution started, table=aa....aa."bb....bb"

RDAREA unit data loading (pdload) of table aa....aa."bb....bb" was started by means of parallel loading.

aa....aa: Authorization identifier

bb....bb: Table identifier

S: Continues processing.

KFPL00793-I L+S

Pdload execution abnormal terminated, table=aa....aa."bb....bb", RDAREA="cc....cc", return code=dd, pdload process id=ee....ee

RDAREA unit data loading (pdload), which was executed by parallel processing, terminated abnormally in the return code dd.
For details about pdload return codes, refer to message KFPL00704-I.

aa....aa: Authorization identifier

bb....bb: Table identifier

cc....cc: RDAREA name

dd: pdload return codes

ee....ee: pdload process ID

S: Continues processing.

O: Take corrective action by following the procedure in the Operation when a command error occurs section under When loading data to a row partitioned table (parallel loading facility) in the HiRDB Version 9 Installation and Design Guide.

KFPL00794-I L+S

Pdparaload terminated, return code=aa

Parallel loading terminated.

aa: Return code

0: Parallel loading terminated normally.

4: Parallel loading terminated normally. However, one or more of the executed RDAREA unit data loads (pdload) terminated with return code 4.

8: Parallel loading terminated abnormally. However, one or more of the executed RDAREA unit data loads (pdload) terminated with return code 8.

S: Terminates processing.

O: When the return code is not 0, take corrective action according to the previously output error message KFPL00793-I. If the KFPL00793-I message was not output, take corrective action according to the previously output error message.

KFPL00800-I L+S

Loading until aa....aath row committed

The loading transaction was completed up to the aa....aath row.

aa....aa: Number of rows from the beginning of the input data file or unload file (number of rows from the beginning is also displayed in the case of re-execution)

S: Continues processing.

KFPL00810-I L+S

aa....aa restart at bb....bbth row

The utility's processing was restarted at the bb....bbth row.

aa....aa: Utility:

Pdload: Database load utility

Pdrorg: Database reorganization utility

bb....bb: Number of rows from the beginning of the input data file or unload file

S: Continues processing.

KFPL00900-I E+L

Error detail, aa....aa

This is error detail information.

aa....aa: Internal error information

S: The higher system that received the message handles it.

KFPL10000-E E+L

Command option '-i s' cannot be specified in this case

For processing tables defined with non-partitioned key indexes processed in units of RDAREAs, -i s (index update mode) cannot be specified as the index creation method.

S: Continues processing.

O: Change the index creation method to -i n (index information output mode) and re-execute the command.

KFPL10001-E E+L

Command option '-r' cannot be used when partitioning condition altered

Processing in units of RDAREAs cannot be specified for unload data file consolidation (-g option specified) because the partitioning condition for a table in the unload data file differs from the partitioning condition of the table to be reloaded.

S: Terminates processing.

Action

To change the table partitioning condition, restore the previous partitioning condition and make a backup of the table. Specify the -g option and unload the file in table units.

After changing the table partitioning condition, specify the -g option and reload the file in table units.

KFPL10002-E E+L

Command option "aa....aa" cannot be specified in this case

If aa....aa is -W:

When the lobunld statement (for unloading LOB data) is specified in the control information file, the -W option cannot be specified.

When the unload statement (uoc) is specified in the control information file, the -W option cannot be specified.

The -W option cannot be specified for a table containing abstract data type columns.

If aa....aa is -k unld:

Unload processing cannot be executed for a table for which a LOB column has been defined, except in the following cases:
For unloading data by specifying the -W option
Both the LOB column structure base table and the LOB data are unloaded at the same time with the -j option specified

The falsification prevented table cannot perform unload processes for which the -W option is not specified.

If aa....aa is -g:

The -g option cannot be specified for the processing of a LOB column structure base table relative to a hash-partitioned table in which a LOB column is defined.

If aa....aa is -j:

When the -j option is specified, the -W option cannot also be specified.

If aa....aa is -kc, -f:

These options cannot be specified for a table that includes an abstract data type.

If aa....aa is -b:

If -k f (default) or -k c is specified, a binary-format input data file cannot be used for a table containing a column of abstract data type for which BLOB is an input parameter.

If aa....aa is -in, -ix:

These options cannot be specified for a table for which a plug-in index is defined.

If aa....aa is -c:

The -c and -W options cannot both be specified for a FIX table.

If aa....aa is -t:

Reloading by schema cannot be executed for an unload data file created by means of unloading by table. Also, if a tblname statement is specified by table, reloading by schema cannot be executed.

If aa....aa is -k:

When using UOC, only rorg or unld can be specified with the -k option.

If aa....aa is -c dic:

When using UOC, -c dic (specified for a dictionary table) cannot be specified.

If aa....aa is -U:

The -U option cannot be specified when data is loaded into one of the following tables:

A table with an abstract data type column

A table with a BINARY type column

A table with a repetition column

A FIX table

aa....aa: {-W|-k unld|-g|-j|-kc|-f|-b|-in|-ix|-c|-t|-k|-c dic|-U}

S: Terminates processing.

O: Take one of the following actions:

If aa....aa is -W:

For the unloading operation, either specify the unload statement or delete the lobunld statement.

To create an unload data file with pdrorg while using a UOC, specify the unload data file in the unload statement. To create an unload data file using a UOC, delete the -W option.

If data loading is being performed, delete the -W option.

If aa....aa is -k unld:

When reorganizing a table, specify -k rorg. For unloading, specify the -W option.

If aa....aa is -g:

Delete the -g option.

If aa....aa is -j:

When unloading both LOB column structure base table data and LOB data simultaneously, delete the -W option. When unloading row data only, delete the -j option.

If aa....aa is -kc, -f:

When specifying a table containing an abstract data type, delete the -kc, -f option.

aa....aa is -b:

Specify the -k v option.

If aa....aa is -in, -ix:

When specifying a table for which a plug-in index is defined, delete the -in, -ix option.

If aa....aa is -c:

Correct the contents of the column structure information file by specifying the -a and -W options for a FIX table.

If aa....aa is -t:

Correct the -t option specification.

If aa....aa is -k:

When using a UOC, specify rorg or unld with the -k option. Also, when not using UOC, delete the unlduoc statement.

If aa....aa is -c dic:

When using a UOC, no process can be performed on the dictionary table. To process the table the user defined, specify -c user. Also, when not using UOC, delete the unlduoc statement.

If aa....aa is -U:

Load data from a pdload unload file. To create the pdload unload file, specify the -W option when you execute the pdrorg, and then unload the data.

KFPL10003-E E+L

Unable to specified command option 'aa....aa' when bb....bb

If bb....bb is ADT column defined:

The aa....aa option cannot be specified because the abstract data type is defined.

If bb....bb is unload_row(uoc):

The aa....aa option cannot be specified because (uoc) is specified in the unload statement.

If bb....bb is INSERT ONLY table:

The aa....aa option cannot be specified in the falsification prevented table.

If bb....bb is ORG status:

The aa....aa option cannot be specified because the RDAREA that stores the table is in online reorganization hold.

aa....aa: {-W|-j|-k rorg|-f|-d}

bb....bb: {ADT column defined|unload_row(uoc)|INSERT ONLY table|ORG status}

S: Terminates processing.

O:

If bb....bb is ADT column defined:

With the -W option, the data to be input from the indicated table to the Database Load Utility (pdload) cannot be created by the Database Reorganization Utility (pdrorg). Therefore, use a UAP to create the data.

With the -j option, delete the -j option and re-execute.

If bb....bb is unload_row(uoc):

-W: Delete the -W option and execute.

-k rorg: Change to -k unld and execute.

-f: Delete the -f option and execute.

If bb....bb is INSERT ONLY table:

Delete the aa....aa option and execute.

If bb....bb is ORG status:

Execute after releasing online reorganization hold or after deleting the aa....aa option.

KFPL10004-E E+L

Unable to specified aa....aa in Control file when bb....bb

If bb....bb is ADT column defined:

aa....aa cannot be specified because an abstract data type is defined.

If bb....bb is INSERT ONLY table:

aa....aa cannot be specified because the table is a falsification prevented table.

If bb....bb is invalid condition:

aa....aa cannot be specified because the specification conditions are different.

If bb....bb is Not divided table:

For non-partitioned tables, the src_work control statement cannot be specified.

If bb....bb is current character code set:

For the current HiRDB default character encoding, the charset operand cannot be specified in the option control statement.

If aa....aa: Control statement information

{tblname | unlduoc |option job | option_row (diverskip) | src_work |option_row(charset)}

If bb....bb: Reason information

{ADT column defined | INSERT ONLY table | invalid condition | Not divided table |current character code set }

S: Terminates processing.

O:

If bb....bb is ADT column defined:

Data cannot be transferred to the indicated table. To transfer data to the indicated table, use a UAP to create data from the source table and then move it to the indicated table.

If bb....bb is INSERT ONLY table:

To port a falsification prevented table, specify the -W option, unload the table, and then use the database load utility (pdload) To port the table. Alternatively, if the aa....aa option cannot be specified for a falsification prevented table, delete the aa....aa option and re-execute.

If bb....bb is invalid condition:

option diverskip=on cannot be specified in the control statement. Remove it, and re-execute, or ensure a condition that can be specified.

If bb....bb is Not divided table:

Creation of the partitioning input data file can be executed for a partitioning table. Check whether the table specified on the command line is a partitioning table.

If bb....bb is current character code set:

The charset operand cannot be specified in the option control statement. Remove it, and then retry the operation, or ensure a condition that can be specified.

KFPL10005-E E+L

Unable to execute aa....aa command by each RDAREA, RDAREA="bb....bb"

Data reloading by RDAREA or reorganization by RDAREA cannot be executed for the following reason:

Although an added RDAREA is the processing target, the rebalancing utility has not been executed on that RDAREA.

aa....aa: Utility:

pdload: Database load utility

pdrorg: Database reorganization utility

bb....bb: RDAREA name

S: Terminates processing.

O: Take one of the following actions:

After execution of the rebalancing utility, execute data reloading by RDAREA or reorganization by RDAREA

Execute data loading by table or reorganization by table

KFPL10006-E E+L

Unable to execute aa....aa command, Table status=bb....bb, RDAREA=cc....cc, table=dd....dd."ee....ee"

When bb....bb is DATA_UNFINISH:

The following utilities cannot be executed because the table is in reload-not-completed data status:

pdload

pdrorg -k {rorg|ixmk|ixrc|ixor}

pdrbal

When bb....bb is completed:

The following utility cannot be executed because table reloading is complete (the table is not in reload-not-completed data status):

pdrorg -k reld

When bb....bb is memory_db:

The following utilities cannot be executed because the table is in an in-memory database:

pdrorg -k {rorg|reld}

pdload

aa....aa: Utility name

pdload: Database load utility

pdrorg: Database reorganization utility

pdrbal: Rebalancing utility

bb....bb: Table status

DATA_UNFINISH: Reload-not-completed data status

completed: Reload is complete

memory_db: In an in-memory database

cc....cc: RDAREA name

dd....dd: Authorization identifier

ee....ee: Table identifier

S: Terminates processing.

Action

When bb....bb is DATA_UNFINISH:

Use the database reorganization utility to reorganize the table, and then re-execute.

bb....bb is completed:

You cannot reregister a row in the applicable table or RDAREA.

When bb....bb is memory_db:

You cannot update the applicable table.

KFPL10007-E E+L

Unable to execute aa....aa command on ORG status, RDAREA="bb....bb", reason=cc....cc

When the RDAREA is in online reorganization hold status, aa....aa could not be executed for reason cc....cc.

aa....aa: Utility name

pdload: Database load utility

pdrorg: Database reorganization utility

pdreclaim: Free page release utility

bb....bb: RDAREA name

cc....cc: Reason

BLOB COLUMN defined: A BLOB column was defined.

INSERT ONLY table: A falsification prevented table.

replica RDAREA: The RDAREA is a replica RDAREA.

current RDAREA: The RDAREA is the current RDAREA.

S: Terminates processing.

Action

After releasing online reorganization shutdown, re-execute.

KFPL11111-E E+L

Time over, no response from utility server, time=(aa....aa, bb....bb)

Because the process did not terminate within the utility run monitoring time specified in the pd_utl_exec_time operand of the system definition or the option statement in the utility, a no-response failure was judged to have occurred.

aa....aa: The value set as the utility run monitoring time (in seconds)

bb....bb: The response wait time for a time-out to occur (in seconds)

S: Abnormally terminates.

O: If the value aa....aa set as the processing time for the utility is not appropriate, change the specified value of the exectime operand in the option statement in the utility (after recovering from an error such as logless shutdown), and then re-execute. If the specified value is appropriate, after recovering from an error such as logless shutdown, re-execute the utility. If a similar error recurs even after re-executing the utility, contact the HiRDB administrator.

Action

If a timeout occurred even though value aa....aa set as the processing time for the utility is appropriate, a no-response error may have occurred. Back up the files in the %PDDIR%\spool\save directory and the %PDDIR%\tmp\command-name YYYYMMDDHHMMSS process-ID.txt file as investigation data and contact the customer support center.

KFPL11724-E E+L

PLUGIN environment definition error, code=aaa

The environment variable is incorrectly specified.

aaa: Error reason code

-30: The storage area for the environment variable is invalid.

-90: The specification value for the environment variable is greater than the maximum length that can be specified.

S: Terminates processing.

O: If the reason code is -90, correct the environment variable specification and re-execute the command.

Action

If the reason code is -30, contact the customer support center.

KFPL13002-E E+L

Row length too long

A value specified in the table definition exceeds the row length that can be processed by a utility.

S: Terminates processing.

O: Consider revising the table definition as follows:

Reduce the number of elements in a repetition column

Reduce the column definition length

KFPL15007-E E+L

Dynamic load error occurred, shared library=aa....aa

An error occurred during dynamic loading of a shared library required for processing.

aa....aa: Absolute pathname of shared library

S: Terminates processing.

O: Refer to the preceding KFPL22000-E message.

In UNIX:

Resolve the error as follows, and then re-execute the command:

If using EasyMT, check its installation for an error.

If not using EasyMT, check the control information file and delete the information about the usage of EasyMT.

In Windows:

Review the control information file.

KFPL15010-E E+L

Invalid environment for aa....aa, reason=bb....bb

The environment required to execute utility aa....aa is invalid.

aa....aa: Name of utility

bb....bb: Reason code:

No-tty: There is no terminal in the execution environment.

S: Terminates processing.

O: Eliminate the cause of the error on the basis of the displayed reason code and re-execute:

No-tty: Specify the identifier and password in the PDUSER environment variable and re-execute without specifying -u in the command line.

KFPL15011-E E+L

No specified Environment variable aa....aa

The aa....aa environment variable has not been set.

aa....aa:

PDDIR: PDDIR environment variable

PDUSER: PDUSER environment variable

S: Terminates processing.

O: Set the PDDIR environment variable or the PDUSER environment variable, and then re-execute.

KFPL15027-E E+L

Unable to execute pdload command without aa....aa privilege

Because the user does not have privilege aa....aa for the table that was to be subject to data loading, the pdload utility could not be executed.

aa....aa: Privilege:

insert: INSERT privilege

delete: DELETE privilege

audit: Audit privilege

S: Terminates processing.

O: After being granted the privilege required during data loading, re-execute the command. When the target table for data loading is the audit trail table, the auditor must execute the command.

KFPL15029-E E+L

Table aa....aa.bb....bb not found in system

The table specified on the command line was not found.
When *all* is displayed for bb....bb, the specified schema has no tables. Or, the tables in the schema were deleted during execution of the utility.
aa....aa: Authorization identifier

bb....bb: Table identifier

S: Terminates processing.

O: Correct the authorization identifier or table identifier specified on the command line and re-execute the command. Also, do not delete the tables during execution of the utility.

KFPL15030-E E+L

Table definition altered (aa....aa/bb....bb)

Definition of a table subject to processing was modified during utility execution.

aa....aa: Internal information

bb....bb: Internal information

S: Terminates processing.

O: Do not modify the tables during execution of the utility; check the table definition and re-execute.

KFPL15031-E E+L

Unable to specify aa....aa table

The following tables cannot be processed by the utility:

Viewed tables

Temporary tables

Tables for which flexible hash partitioning is defined

Matrix-partitioned tables for which flexible hash partitioning is defined on a second dimension partitioning column

aa....aa: Table type

viewed: Viewed table

temporary: Temporary table

flexiblehash: Table for which flexible hash partitioning is defined, or matrix-partitioned table for which flexible hash partitioning is defined on a second dimension partitioning column

S: Terminates processing.

O:

For a viewed table or temporary table specified on the command line:

Change the specified table name to the name of the base table, and then re-execute the command.

For the following tables specified on the command line:

Tables for which flexible hash partitioning is defined

Matrix-partitioned tables for which flexible hash partitioning is defined on a second dimension partitioning column

Because the pdparaload command cannot be executed, load the data another way, such as on a per-table basis.

If the table name is incorrect, specify the correct table name, and then re-execute the command.

KFPL15032-E E+L

Specified constraint aa....aa."bb....bb" not found

The specified constraint name is not defined in HiRDB.

aa....aa: Authorization identifier

bb....bb: Constraint name

S: Terminates processing.

P: Revise the constraint name, and then re-execute the command.

KFPL15034-E E+L

Specified RDAREA aa....aa not found

Specified RDAREA does not contain a table or index to be processed.

aa....aa: RDAREA name

S: Terminates processing.

O: Correct the RDAREA name and re-execute the command.

KFPL15035-E E+L

Only one RDAREA name can be specified

An attempt was made to execute the database load utility (pdload) by specifying multiple RDAREA names, but the corresponding table was not partitioned by values.

S: Terminates processing.

O: Delete the incorrect information from the control information file and re-execute the command.

KFPL15036-E E+L

Specified RDAREA ID not found, ID=aa....aa

The applicable utility (the RDAREA may have been deleted by mistake) cannot be executed because the RDAREA with the RDAREA ID aa....aa was not found.

aa....aa: RDAREA ID (real RDAREA ID)

S: Terminates processing.

O: If the user inadvertently deleted the RDAREA while the utility was executing, create the deleted RDAREA and re-execute the utility. Alternatively, specify the generation number of the RDAREA to be processed and re-execute the utility.

KFPL15037-E E+L

Changed aa....aa, RDAREA "bb....bb"

When aa....aa is current generation:
If the utility was executing without the generation (-q option) specified, the generation of RDAREA "bb....bb" was changed from the current generation.
When aa....aa is inner replica status:
If the utility was executing with the generation (-q option) specified, the replica status of RDAREA "bb....bb" was changed.

aa....aa:

current generation: Current generation

inner replica status: Replica status

bb....bb RDAREA name

S: Terminates processing.

O:

When aa....aa is current generation:
When executing the utility without specifying the generation, do not change the current generation of the RDAREA storing the table that is being executed.
When re-executing the utility without specifying the generation, return the generation of RDAREA aa....aa to the generation from when the utility was executed previously.

When aa....aa is inner replica status:
When executing the utility while specifying the generation, do not change the inner replica status of the RDAREA being executed.

KFPL15040-E E+L

Insufficient memory on PROCESS

A work area shortage occurred.

S: Terminates processing.

O: Check whether there are other processes that use a large amount of memory.

There are processes that use a large amount of memory:

Wait for the associated processes to terminate, then re-execute the command.

There are no processes that use a large amount of memory:

Use one of the following methods to ensure that there is sufficient memory:

Reduce the number of simultaneously executing processes.

Increase the size of the swap area.

Increase the amount of memory.

Note

If this message is displayed during the execution of a plug-in-provided command, the message is output only to the indicated output device type (L).

KFPL15046-E E+L

aaaaaa error occurred, file=bb....bb

A file I/O error occurred.

aaaaaa: Processing resulting in the error:

{ Open|Read|Write|Close|Reopen }

bb....bb: File name

S: Terminates processing (in the case of the Close error, the system may resume processing).

O: Refer to the message that is output after this message to eliminate the cause of the error, then re-execute the command.

KFPL15047-E E+L

File I/O error occurred, reason=aa....aa, func=bb....bb, errno=cc....cc, (dd....dd)

A file I/O error occurred.

aa....aa: Reason for the error:

Date-check:

The creation date of the mounted tape is earlier than the date specified in the validate operand.

Empty-file:

The specified file is empty (0 bytes).

File-format:

The specified format and the actual file format are different. It is possible that the specified file name is invalid, or the file format specified on the command line or in the control statement does not match the contents. Further, for a DAT format input file, if the length of a single row of data exceeds 32 KB, the maxreclen operand must be specified in the source control statement.

File-lock:

The file is being used by another user. The file name specified in the command line or control statement might be in use by another job. In UNIX, there might be a shortage of file locking resources for an OS kernel parameter.

File-sequence:

The multi-volume file sequence was incorrect.

Invalid-device:

The entry type (attribute) of the specified file is invalid. Or, when MTguide is being used, MTguide has not been started. If the system can identify the entry type, it displays one alphabetic character enclosed in parentheses; this character is the same as the entry in the mode output by the OS's ls -l command. It is possible that a directory name was specified in a location that requires a file name (or vice versa), or that a character special file was assigned to a file where a character special file cannot be used.

Invalid-environment:

Because the set value obtained by the uname system call is invalid, a streaming tape device cannot be used. Check that the OS has been installed correctly or that the OS version satisfies the prerequisite conditions of the HiRDB system or related program products.

Invalid-parameter:

The combination of specified parameters is invalid.

Invalid-path:

The path name is invalid.

Invalid-permission:

The specified file version is invalid (access privilege error). It is possible that a file is being used for which an access privilege has not been granted by an HiRDB administrator, or for MT, the write protect may be enabled.

No-data:

The data for the number of data items stored at the synchronization point was not found in the specified file.

No-file:

File to be read was not found or file into which data was to be written has been deleted.

No-space:

There is not enough space in the file to which data is to be written.

In UNIX:
If this error occurs even when there is sufficient disk space, you might not have defined the HiRDB file system area for a large file, or the case falls under OS kernel parameter restrictions. For details about OS kernel parameter restrictions, see Checking and modifying OS parameters in the HiRDB Version 9 Installation and Design Guide.

In Windows:
If this error occurs when there is sufficient disk space, it is possible that the HiRDB file system area is not defined as a large file (2048 MB or greater) in the pd_large_file_use operand.

No swap-file:

There is no unload data file for multivolume (check the file size or specify a multivolume file). If this error occurs during read processing, it is possible that a file is used for which write processing (unloading processing, etc.) did not terminate normally.

Rorg:

When pdrorg was executed, a file was unloaded by specifying -k unld.

Same-file:

The file processed immediately before was specified as a multivolume file. Or, an attempt was made to overwrite a previous volume during multivolume write processing.

Schema-file:

An unload file was used that was created on a per-table rather than a per-schema basis.

Suppress:

The -S option was not specified when unloading.

Unmatch-entry:

An entry in the file header does not match the information in the control information file (the system displays the inconsistent entry name in parentheses).

bb....bb: Name of the system function in which the error occurred

If the operating system detected the error: The system function name

If the HiRDB file system detected the error: The name of the HiRDB system function name beginning with p_f_ios

If other than the above: ***

cc....cc: Error code

If the operating system detected the error, this is the error number (errno: the foreign reference variable that displays the error status) returned by the system function.

If the error is detected by the HiRDB file system, this is the HiRDB file system error code. For details on error codes, see 5.1 Error codes returned from HiRDB file system access requests. The primary error causes and measures to consider are listed below:
-1511: It is possible that the specified file path name violates the file name rules of the HiRDB file system. Area names have a maximum of 117 characters, and file names have a maximum of 30 characters.
-1532: It is possible that the specified file path name is invalid. Correct the file path name. Further, specify only the HiRDB file system name; if it is not specified up to the file name, specify it up to the file name.
-1534: It is possible that the specified file name is the same as a file name in use by another job. Change the file name.
-1535: There is insufficient volume. Further, if the insufficient volume appears immediately after the beginning of processing, consider that the value specified for the file size on the command line or in a control statement may exceed the HiRDB file system restriction. Use the pdfmkfs command to create a large HiRDB file system, or revise the initial volume and incremental volume specified on the command line or in the control statement.
-1538: The pdfmkfs command specifies a file that has not been initialized. Have the pdfmkfs command use an initialized file.
-1540: There is no access privilege to the HiRDB file system name. Have the HiRDB administrator grant an access privilege.
-1562: There is no HiRDB file system initialized by the pdfmkfs -k UTL command. Use the pdfmkfs command with UTL specified in the -k option to specify an initialized file.

If an error cause other than the above: 0.

dd....dd: Troubleshooting information (source file name and number that detected the error). This information is used by the customer support center.

S: Terminates processing.

O: From the error reason, function name, and error code, refer to errno.h, the manual for the operating system in use, and 5.1 Error codes returned from HiRDB file system access requests to eliminate the cause of the error, and re-execute.

KFPL15048-E E+L

File operation was canceled by aa....aa

Multi-volume file exchange was cancelled.

aa....aa: Cause of cancellation:

system: Cancelled by the system.

user: Cancelled by the user.

S: Terminates processing.

O: Re-execute the processing, if necessary.

KFPL15049-I L+S

MT was created at aa....aa

The MT creation date specified in the input data file is YYYY-MM-DD.

aa....aa: Creation date specified in the mounted MT label (in the format YYYY-MM-DD)

Format: YYYY-MM-DD

YYYY: Year

MM: Month

DD: Date

S: Cancels processing if the file was created prior to the date or number of days specified in the validate operand of the control information file; continues processing if the file was created after the date or number of days specified in the operand.

O: If processing is cancelled, mount the MT with the correct creation date and re-execute.

KFPL15050-E E+L

EasyMT error occurred, func=aa....aa, reason=bb....bb

File I/O processing using EasyMT resulted in an error.

aa....aa: Name of function resulting in the error

bb....bb: Error detail information

S: Terminates processing.

O: Based on the error detail information, check the documentation for JP1/Magnetic Tape Access or EasyMT, eliminate the cause of the error, and then re-execute.

KFPL15052-E E+L

Invalid aa....aa statement bb....bb entry in Control file, value=cc....cc, reason=dd....dd

Value cc....cc specified for entry bb....bb of control statement aa....aa in the control information file is invalid.

aa....aa: Control statement type

bb....bb: Entry name

cc....cc: Specified value

dd....dd: Reason code:

Invalid-device: File format is invalid.

Invalid-permission: File permission is invalid.

No-directory: There is no directory.

Pathname-length: The length of the file path name is invalid.

For items omitted from the control information file, the default values are displayed.

S: Terminates processing.

O: Check the corresponding item in the control information file, eliminate the cause of the error, then re-execute.

KFPL15053-E E+L

Length of statement in Control file is over,line=aa....aa

If the control statement specified in the control statement file of the pdparaload command is added to the RDAREA name, the maximum length (1,023 bytes) is exceeded.

aa....aa: Row number error (row number of the control statement in which the error occurred)

S: Terminates processing.

O: Change the file path name so that the maximum file length (1,023 bytes) will not be exceeded even if the control statement that specified the pdparaload control statement file is added to the RDAREA name. Then, re-execute the command. For details about how to specify control statements, see pdparaload in the manual HiRDB Version 9 Command Reference.

KFPL15059-E E+L

aa....aa directory not found

The name specified for an index information file is not a directory.

aa....aa: Directory name specified in the control information file

S: Terminates processing.

O: Correct the directory name in the control information file and re-execute the command.

KFPL15060-E E+L

Invalid file for index information file, file=aa....aa, reason=bb....bb

File aa....aa specified as an index information file is invalid.

aa....aa: Specified file name

If the length of the file name exceeds 134 characters, the last 134 characters of the file name are output.

bb....bb: Reason code:

Duplicated-entry:

When multiple files were specified, the same file was specified more than once.

Invalid-device:

File format is invalid.

Invalid-header:

Header ID is missing.

Invalid-permission:

Specified file permission is invalid.

Invalid-record-length:

When multiple files were specified, some of the files have different record lengths.

No-file:

Specified file was not found.

No-header:

Header is missing.

S: Terminates processing.

O: Refer to the specified index information file and the reason code to eliminate the cause of the error, then re-execute.

KFPL15061-E E+L

Imcomplete record found in index information file, file=aa....aa, reason=bb....bb

Index information file aa....aa contains an invalid record.

aa....aa: Specified file name

If the length of the file name exceeds 118 characters, the last 118 characters of the file name are output.

bb....bb: Reason code:

Tally-length:

Total length of fixed-length records is not a multiple of the record length.

Variable-record:

The length of the data part of a variable-length record is invalid.

S: Terminates processing.

O: Because the index information file is damaged, re-create the index and re-execute.

KFPL15062-E E+L

aa....aa error occurred, func=bb....bb, rc=cc....cc

An error occurred in one of the following processing operations:

Sort processing

Magnetic tape I/O processing

aa....aa: Processing that generated the error

SORT: Sort processing

EasyMT: Magnetic tape I/O processing

bb....bb: Name of function resulting in the error

cc....cc: Return code set by the function resulting in the error

S: Terminates processing.

O: Take the following action:

If aa....aa is SORT:
Refer to 7. Messages Related to Sort Processing, and take corrective action.
Messages related to sort processing are output in the format KBLSnnn-E, where nnn denotes the absolute value of the return code that is output to cc....cc.
The table below summarizes frequently output return codes and the required corrective action:

Return code | Action
-202 | Memory shortage. Reduce the work buffer size specified in the sort operand.
-290 | Work buffer shortage. Increase the work buffer size specified in the sort operand.
-210, -230 | An I/O error occurred. It is possible that the disk space for sort processing is insufficient. If insufficient disk space is the cause of the error, specify a disk with sufficient space in the sort operand, and then re-execute the processing.

If the error cannot be resolved, acquire the sortdump, SORTIODUMP, and SORTDMP2 that are output to C:\Windows (in UNIX, /tmp or /usr/tmp), and contact the customer support center.

If aa....aa is EasyMT:
Contact the customer support center.

KFPL15063-E E+L

aa....aa failed, index=bb....bb, authid=cc....cc, file=dd....dd, RDAREA=ee....ee

An error occurred during processing aa....aa.

aa....aa: Processing:

Check-status: Checking the index status

Commit: Terminating index creation

Load-index: Creating an index

Preparation: Preparing for processing

Purge-index: Deleting an index

Unfinish-index: Processing the incomplete index status

bb....bb: Index identifier

cc....cc: Authorization identifier

dd....dd: File name

If the length of the file name exceeds 52 characters, the last 52 characters of the file name are output.

ee....ee: RDAREA name (if the RDAREA name cannot be identified, **....** is displayed)

S: Terminates processing.

O: Refer to the message that was output before this message to eliminate the cause of the error, and re-execute.

KFPL15064-E E+L

Specified index record file=aa....aa conflicted with command line specification, reason=bb....bb

Specification on command line is in conflict with index information file aa....aa due to bb....bb reason.

aa....aa: File name

If the length of the file name exceeds 95 characters, the last 95 characters of the file name are output.

bb....bb: Reason code:

Invalid-table: Authorization identifier or table identifier is invalid.

S: Terminates processing.

O: Check the specification of the authorization identifier or table identifier on the command line and in the index information file to eliminate the cause of the error, then re-execute.

KFPL15065-E E+L

Index aa....aa on table bb....bb.cc....cc not found in server=dd....dd

Index aa....aa of table bb....bb.cc....cc was not found on server dd....dd.

aa....aa: Index name

bb....bb: Authorization identifier

cc....cc: Table identifier

dd....dd: Server name

S: Terminates processing

O: Correct the server name specified in the control statement or command line, and then re-execute.

KFPL15066-E E+L

Index record in aa....aa not available for bb....bb.cc....cc, reason=dd....dd (system=ee....ee, file=ff....ff)

Index information file aa....aa is not the most recent file for index bb....bb.cc....cc.

aa....aa: File name

If the length of the file name exceeds the value obtained from the following formula, the last number of characters obtained from the formula are output.

Where the reason code is Table-division:

100 - authorization-identifier-length - index-identifier-length

Where the reason code is Unload-time:

97 - authorization-identifier-length - index-identifier-length

bb....bb: Authorization identifier

cc....cc: Index identifier

dd....dd: Reason code:

Table-division:

The number of partitions does not match the actual table partitions.

Unload-time:

The date the index information file was created does not match. ee....ee displays the date the most recent index information file was created (when -i c or n was specified) or the date the index was invalidated (when -i x was specified). ff....ff displays the date the specified index information file was created. Both dates are displayed in the format %Y-%m-%d %H:%M:%S. If reload processing has already been completed, loaded is displayed.

ee....ee: Value in the HiRDB system

ff....ff: Value in index information file

S: Terminates processing.

O: Re-execute specifying the most recent information file, or re-create the index.

KFPL15067-E E+L

Unmatched number of index record file(s)=aa....aa, table division=bb....bb at server=cc....cc, index=dd....dd

The number of index information files specified in the index statements of the control information file does not match the number of table partitions in the server.

aa....aa: Number of index statements specified in the control information file

bb....bb: Number of table partitions in the server

cc....cc: Server identifier

dd....dd: Index name

S: Terminates processing.

O: Specify as many index statements in the control information file as there are table partitions in the server, then re-execute.

KFPL15068-E E+L

Specified index record file=aa....aa conflicted with Control file specification, reason=bb....bb

Information in the control information file contradicts the information in index information file aa....aa in terms of bb....bb.

aa....aa: File name

If the length of the file name exceeds 113 characters, the last 113 characters of the file name are output.

bb....bb: Reason code:

Unload-condition:

The user specified the file into which the non-partitioning index of a partitioned table was unloaded in units of RDAREAs using the control information file, but the file contains the index information file unloaded in units of tables

Invalid-index:

Index name is different.

Invalid-RDAREA:

RDAREA name is different.

Invalid-RDAREA-id:

RDAREA identification number is different.

S: Terminates processing.

O: Check the index information file specified in the index statement of the control information file, eliminate the cause of the error, then re-execute.

KFPL15069-E E+L

Unmatched index records, files=aa....aa,bb....bb

Index information in index information file aa....aa is different from that in index information file bb....bb.

aa....aa: Name of index information file

bb....bb: Name of index information file

If the length of the file name exceeds 85 characters, the last 85 characters of the file name are output.

S: Terminates processing.

O: Correct the control information file and re-execute.

KFPL15070-E E+L

aa....aa failed, status=bb

An error occurred during the aa....aa processing.

aa....aa: Processing:

Check-Status: Index status checking

bb: Status:

1: After the index information file had been created, the table was modified by one of the following means, so the index information file's contents no longer match the table's contents, making the index information file unusable:

By execution of pdload or pdrorg by RDAREA

By reinitialization of an RDAREA storing the index's table (execution of pdmod)

3 or 4: An index has been created.

S: Terminates processing.

O:

When the status is 1:
Create an index based on the index information file created with pdload or pdrorg; or, use pdrorg (-k ixrc) To re-create the index.

When the status is 3 or 4:
Check that the correct index was created.

KFPL15071-E E+L

Unmatched generation number between number "aa" of bb....bb "cc....cc" and number "dd" of command line

Generation number "aa" of bb....bb and generation number "dd" of the -q option (the current generation number when the -q option is not specified) do not match.

aa: Generation number of bb....bb

bb....bb: File type

index-record-file: Index information file

Lobmid-file: LOB middle file

unload-file: Unload data file

cc....cc: The file name of bb....bb

dd: The generation number specified by the -q option (the current generation number if the -q option is not specified)

S: Terminates processing.

O:

If "dd" is correct:
Specify bb....bb created by the generation number specified by the -q option in the control statement, and then re-execute.

If "dd" is incorrect:
Specify in the -q option the generation number that created bb....bb, and then re-execute.

KFPL15101-E E+L

Specified column aa....aa not found

Column name specified in the column structure information file is not found in the names of columns comprising the table.

aa....aa: Column name

S: Terminates processing.

O: Correct the column name in the column structure information file and re-execute the command. Note that neither unneeded tabs nor spaces can be specified in the column structure information file. Accordingly, do not use any unneeded tabs or spaces when specifying the column name.

KFPL15102-E E+L

Column aa....aa is duplicated

A duplicated column name was specified in the column structure information file.

aa....aa: Column name

S: Terminates processing.

O: Delete the duplicate column name from the column structure information file and re-execute the command.

KFPL15199-E E+L

Logical inconsistency occurred in aa....aa, data=bb....bb

Logical inconsistency was detected in a program.

aa....aa: Name of function

bb....bb: Invalid data

S: Terminates processing.

O: Contact the HiRDB administrator.

Action

Contact the customer support center.

KFPL15224-E E+L

Insert error occurred at aa....aaTH row, table=bb....bb.cc....cc

An error occurred during reloading of row aa....aa.

aa....aa: Row number

bb....bb: Authorization identifier

cc....cc: Table identifier

S: Terminates processing.

O: Refer to the message output to the log file before this message to check the cause of the error, and re-execute the command.

KFPL15225-E E+L

Rollback called

Processing was rolled back for the reason indicated in the message log file before this message.

S:

n specified in the -l option:
Terminates abnormally (the database remains on error status)

a or p specified in the -l option:
Terminates processing

O: Eliminate the cause of the rollback by checking the message log file that was output before this message. If n was specified in the -l option, use the backup copy to recover the database to the status it was in before the utility executed.

KFPL15226-E E+L

aa....aa request failed, table=bb....bb.cc....cc, server=dd....dd

An error occurred in a table during processing aa....aa.

aa....aa: Processing:

Scan: Row retrieval

Delete: Row deletion

Insert: Row insertion

LOB delete: LOB data deletion

LOB insert: LOB data insertion

LOB scan: LOB data retrieval

Map purge: Deletion of LOB data definition information

LOB length: Acquisition of LOB data length

bb....bb: Authorization identifier

cc....cc: Table identifier

dd....dd: Server name

S: Terminates processing.

O: Refer to the message that was output to the message log file before this message to eliminate the cause of the error.

KFPL15227-E E+L

Unable to aa....aa without bbbbbb privilege

The aa....aa command cannot be executed because the user does not have table access privilege.

aa....aa: Command

pdrorg: Database reorganization utility

pdreclaim: Free page release utility

pdpgbfon: Global buffer residence utility

bbbbbb: Required access privilege

DBA: DBA privilege

audit: Audit privilege

delete: DELETE privilege

insert: INSERT privilege

select: SELECT privilege

S: Terminates processing.

O: After being granted table access privileges, re-execute the command. When the audit trail table is being processed, the auditor must execute this command.

KFPL15229-E E+L

Unable to get aa....aa information, table=bb....bb."cc....cc"

Definition information aa....aa cannot be obtained due to the message that was output before this message.

aa....aa: Type of definition information:

ADT: Abstract data type information

AUDIT: Audit definition information

cluster: Cluster key information

column: Column information

divide: Partitioning information

gen: Generation number

index: Index information

LOB: LOB information

multidim: Matrix partitioning information

privilege: Access privilege information

rdarea: RDAREA information

schema: Schema information

server: Server information

table: Table information

constraint: Constraint information

bb....bb: Authorization identifier

cc....cc: Table identifier

If a name cannot be determined, HiRDB displays the symbol **....**.

For schema units, HiRDB displays the symbol *all*.

S: Terminates processing.

O: Refer to the message in the log file that was output before this message to eliminate the cause of the error, and re-execute the command.

Note

If this message is displayed during the execution of a plug-in-provided command, the message is output to the indicated output device type (E+L).

KFPL15231-E E+L

cc....cc table aa....aa.bb....bb cannot be specified for table name

The specified table cannot be processed because it is not a permanent base table.

aa....aa: Authorization identifier

bb....bb: Table identifier

cc....cc: Table type

Viewed: Viewed table

Temporary: Temporary table

S: Terminates processing.

O: Review the specified table name, and then re-execute the command after specifying the name of the correct permanent base table.

Note

If this message is displayed during the execution of a plug-in-provided command, the message is output to the indicated output device type (E+L).

KFPL15232-E E+L

Unable to use sequence aa....aa."bb....bb"

You do not have privileges to use the sequence generator aa....aa."bb....bb", so you cannot use it.

aa....aa: Sequence generator authorization identifier

bb....bb: Sequence generator identifier

S: Terminates processing.

O: Use a sequence generator for which you have use privileges.

KFPL15233-E E+L

Unable to get sequence information, sequence=aa....aa."bb....bb"

Definition information about aa....aa."bb....bb" cannot be obtained due to the details described in the message that was output prior to this message.

aa....aa: Sequence generator authorization identifier

bb....bb: Sequence generator identifier

S: Terminates processing.

O: Refer to the preceding message, resolve the error, and then re-execute the command.

KFPL15234-E E+L

Specified RDAREA aa....aa not found, table=bb....bb.cc....cc

RDAREA aa....aa specified in the -r option does not contain table bb....bb.cc....cc.

aa....aa: RDAREA name

bb....bb: Authorization identifier

cc....cc: Table identifier

S: Terminates processing.

O: Correct the RDAREA name and re-execute the command.

KFPL15235-E E+L

Specified sequence aa....aa."bb....bb" not found

There is no sequence generator specified in the column structure information file, the null value information file, o rthe function information file.

aa....aa: Sequence generator authorization identifier

bb....bb: Sequence generator identifier

S: Terminates processing.

O: Re-examine the sequence generator specified in the structure information file, null value information file, or the function information file, and if the name is invalid, specify a correct name and re-execute data loading. In addition, if a sequence generator has not been defined, define the corresponding sequence generator, and then re-execute data loading.

KFPL15240-E E+L

Insufficient memory on PROCESS, size=aa....aa, part=bb....bb, code=cc....cc

A memory shortage occurred.

aa....aa: Size (in bytes) of memory resulting in shortage

However, a negative value is displayed because the size of the target memory exceeds 2 GB.

bb....bb: Part number

cc....cc: Part code

S: Terminates processing.

O: Check whether there are other processes that use a large amount of memory.

There are processes that use a large amount of memory:

Wait for the associated processes to terminate, then re-execute the command.

There are no processes that use a large amount of memory:

Use one of the following methods to ensure that there is sufficient memory:

Reduce the number of simultaneously executing processes.

Increase the size of the swap area.

Increase the amount of memory.

KFPL15246-E E+L

aa....aa error occurred, file=bb....bb

File deletion failed.

aa....aa: Unlink

bb....bb: File name

If the length of the file name exceeds 150 characters, the last 150 characters of the file name are output.

S: Resumes processing.

O: The file is not deleted. Delete the file if it is not needed.

KFPL15281-E E+L

No index on table aa....aa.bb....bb

An index is not defined on the specified table aa....aa.bb....bb; therefore, the following operations cannot be performed: index creation, used free page release processing, or reading data into the global buffer.

aa....aa: Authorization identifier

bb....bb: Table identifier

S: Terminates processing.

O: Check the specified table name, specify the name of a table for which an index has been defined, then re-execute the command.

KFPL15282-E E+L

No LOB column on table aa....aa.bb....bb

LOB processing is disabled because no LOB column is defined in the specified table.

aa....aa: Authorization identifier

bb....bb: Table identifier

S: Terminates processing.

O: Check the specified table name. To process LOB data, specify the name of a table for which a LOB column has been defined, then re-execute the command.

KFPL15283-E E+L

Unable to execute pdrorg command, aa....aa does not support

aa....aa, which is not supported by the current version of the Database Reorganization Utility (pdrorg), cannot be executed. Similarly, pdreclaim and pdpgbfon, which also use pdrorg, cannot be executed.

aa....aa:

ADT column: Abstract data type column

ADT return: Constructor parameter reverse generation function for returning the abstract data type

S: Terminates processing.

O: When ADT return is displayed for aa....aa, unloading with -W specified cannot be executed. To reorganize a table or transfer data to another table, check if unloading without the -W specification might be possible. To reference the unload data from a UAP, use another facility to unload the data or use a UAP to extract the data.

Action

Cancel the execution of the database reorganization utility (pdrorg), the free page release utility (pdreclaim), and the global buffer residence utility (pdpgbfon).

KFPL15284-E E+L

Unable to execute aa....aa, PLUGIN does not support bb....bb function

The function bb....bb is not supplied by the plug-in; the function aa....aa cannot be executed. Or, the function aa....aa cannot be executed because the function bb....bb of the plug-in used by the LOB RDAREA is not supported.

aa....aa: Function for which execution was attempted

ixmk: Batch creation of an index

pdreclaim: Free page release utility

pdpgbfon: Global buffer residence utility

bb....bb: Plug-in-provided function

INDEX_LOAD: Plug-in index batch-created section recovery function

PAGE_FREE: Release used free pages

PAGE_READ: Data read facility to the global buffer

S: Terminates processing.

O: To create a plug-in index, execute the index creation function (-k ixrc). Also, pdpgbfon cannot be processed for a LOB RDAREA. Terminate the command.

KFPL15285-E E+L

Unable to specified aa....aa option, PLUGIN does not support bb....bb function

The function bb....bb is not supplied by the plug-in; the option aa....aa cannot be executed.

aa....aa: Option {-i n: index information output mode}

bb....bb: Implementation function {INDEX_LOAD: Plug-in index batch-created section recovery function}

S: Terminates processing.

O: If aa....aa is -i n, set index creation mode to either -i c (batch index creation mode) or -i s (index update mode).

KFPL15286-E E+L

Column "aa....aa" cannot be specified in bb....bb

Because column "aa....aa" does not support the constructor parameter reverse generation function for returning the BLOB attribute, it cannot be specified for bb....bb.

aa....aa: Column name

bb....bb: Type:

blobtovarchar_row: Row in the blobtovarchar statement

S: Terminates processing.

O: When blobtovarchar_row is displayed for the type, specify an abstract data type whose return value from the constructor parameter reverse generation function is the BLOB type, and re-execute the command.

KFPL15287-E E+L

Unable to convert data, column= aa....aa, line=bb....bb

Data in the bb....bbth row of column aa....aa cannot be converted.
Consider the following causes:

There is more than 32 KB of data in the BLOB-type data that was returned by the constructor reverse generation function, and it has the abstract data type specified by the blobtovarchar statement.

An invalid string was stored in the relevant column.

aa....aa: Column name

bb....bb: Row number

S: Terminates processing.

P: If there is more than 32 KB of data in the BLOB-type data that has the abstract data type specified by the blobtovarchar statement, reduce the data size to no more than 32 KB. Alternatively, check whether any invalid character strings are stored in the relevant column, and if so, correct them.

KFPL15288-E E+L

Unable to data copy, data size=aa....aa, limit=bb....bb, line= cc....cc

BLOB data in the cc....ccth line with data size aa....aa cannot be copied because it is larger than the allocated memory size of bb....bb.

aa....aa: Data size

bb....bb: Allocated memory size

cc....cc: Line number

S: Terminates processing.

O:

If the loblimit operand is specified in the option statement, change the specified value so that it is greater than the data size and re-execute.

If the loblimit operand is not specified in the option statement, specify a value greater than the data size in the loblimit operand in the option statement and re-execute.

KFPL15300-E E+L

Invalid unload file, file=aa....aa

Specified unload data file was not created correctly.

aa....aa: Name of unload data file

If the name of the unload data file exceeds 150 characters, the last 150 characters of the unload data file name are output.

S: Terminates processing.

O: Specify an unload data file that was created correctly during unload processing and re-execute the command.

KFPL15301-E E+L

Unable to reload file by aa....aa, file=bb....bb

Because the specified unload data file was not created in units of tables in a user RDAREA or dictionary RDAREA, data cannot be reloaded in the units specified in the -c option.

aa....aa: Reload unit:

{ user table|dictionary }

bb....bb: Name of unload data file

If the name of the unload data file exceeds 150 characters, the last 150 characters of the unload data file name are output.

S: Terminates processing.

O: If the unload data file was created for each table in a user RDAREA, reload the data in units of tables. If the unload data file was created for tables in a dictionary RDAREA, reload the data in units of dictionary tables.

KFPL15302-E E+L

Invalid aa....aa file, kind=bb....bb, file=cc....cc

The file specified for aa....aa processing contains bb....bb. The file cannot be used because the processing to be executed does not match the file contents.

aa....aa: Processing to be executed

{ lobunld|unload }

bb....bb: Specified file contents:

table: Base table

LOB: LOB data

table (LOB): Base table and LOB data

cc....cc: Name of the unload data file

If the name of the unload data file exceeds 150 characters, the last 150 characters of the unload data file name are output.

S: Terminates processing.

O: Match the processing to be executed with the file contents and re-execute.

lobunld statement executed:
Specify a file to which LOB data was unloaded.

unload statement executed:
Specify a file to which a base table was unloaded. To use a file to which base table and LOB data were unloaded simultaneously, specify the command's -j option.

KFPL15305-E E+L

Table aa....aa.bb....bb not found in unload file, file=cc....cc

Specified table aa....aa.bb....bb was not found in the unload data file.

aa....aa: Authorization identifier

bb....bb: Table identifier

cc....cc: Name of unload data file

If the length of the unload data file name exceeds the value obtained from the following formula, the last number of characters of the unload data file name obtained from the formula are output.

169 - authorization-identifier-length - table-identifier-length

S: Terminates processing.

O: Specify the unload data file containing the table and re-execute the command. Or, if the specified table name is invalid, correct it and re-execute the command.

KFPL15308-E E+L

Number of aa....aa.bb....bb columns not equal to unload file, file=cc....cc

The number of columns in table aa....aa.bb....bb in the unload data file does not match the number of columns in the reload destination table.

aa....aa: Authorization identifier

bb....bb: Table identifier

cc....cc: Name of unload data file

If the length of the unload data file name exceeds the value obtained from the following formula, the last number of characters of the unload data file name obtained from the formula are output.

157 - authorization-identifier-length - table-identifier-length

S: Terminates processing.

O: Create an unload data file for the specified table and re-execute the command.

KFPL15310-E E+L

aa....aa information of bb....bb.cc....cc not equal to unload file, file=dd....dd

Reloading cannot be executed because the definition (partitioning definition or LOB column definition) for table bb....bb.cc....cc in the unload data file does not match the definition of the reload table. LOB cannot be processed if the partitioning definition for the unload data file differs from the reload table definition.

aa....aa: Definition description of the specified table:

Divided: Partitioning definition

LOB: LOB column definition

Divided (LOB): Partitioning definition (LOB process)

bb....bb: Authorization identifier

cc....cc: Table identifier

dd....dd: Name of the unload data file

If the length of the unload data file name exceeds the value obtained from the following formula, the last number of characters of the unload data file name obtained from the formula are output.

147 - authorization-identifier-length - table-identifier-length

S: Terminates processing.

O: Create the unload data file for the specified table and reload.

KFPL15311-E E+L

Table aa....aa.bb....bb definition altered RDAREA information not equal to unload file, file=cc....cc

Table aa....aa.bb....bb cannot be reloaded because the definition of table storage RDAREAs used during reloading does not match the definition used during unloading.

aa....aa: Authorization identifier

bb....bb: Table identifier

cc....cc: Name of the unload data file

If the length of the unload data file name exceeds the value obtained from the following formula, the last number of characters of the unload data file name obtained from the formula are output.

131 - authorization-identifier-length - table-identifier-length

S: Terminates processing.

O: Specify the RDAREAs used during unloading and re-execute the command.

KFPL15312-E L+E

Unable to reload divided method altered

Loading cannot be executed without the -g option specified because the table partitioning method specified for reloading does not match the partitioning method used for unloading. Reloading fails in the following cases when there is a mismatch in the partitioning method specifications:

Reloading from an unpartitioned table or a table partitioned by flexible hash partitioning or FIX hash partitioning to a table with key range partitioning

Reloading from an unpartitioned table or a table partitioned by key range partitioning or flexible hash partitioning to a table with FIX hash partitioning

Reloading from a table partitioned by FIX hash partitioning to a table with FIX hash partitioning when the partitioning conditions have been changed

Reloading from a table partitioned by key range partitioning to a table with key range partitioning when the partitioning conditions have been changed

Data cannot be reloaded between tables partitioned with different partitioning methods during reorganization by RDAREA.

S: Terminates processing.

O: Change the partitioning method; use the following procedure, as applicable:

When the data can be placed in one unload file:
Unload with the -g option specified, modify the table definition, then reload with the -g option specified.

When the data cannot be placed in one unload file:
Unload with the -W option specified, modify the table definition, then use the database load utility to load the data.

KFPL15313-E E+L

Abstract data type definition altered, table=aa....aa."bb....bb", COLUMN="cc....cc", TYPE="dd....dd", attribute=ee....ee

Reloading cannot be executed because the abstract data type definition during unloading differs from the abstract data type definition during reloading. For details, see the KFPL15314-E message.

aa....aa: Authorization identifier

bb....bb: Table identifier

cc....cc: Column name

dd....dd: Abstract data type name

ee....ee: Attribute that is different from the one used during unloading:

TYPE_NAME: Data type name

PLUGIN_ID: Plug-in ID

DEF_ATTR_NUM: Abstract data type attributes count

DEF_ATTR_DTYPE: Attribute data type

DEF_ATTR_DLEN: Attribute definition length

DEF_ATTR: Abstract data type attribute definition

LOB_RDAREA_NUM: Number of LOB column storage RDAREAs

LOB_RDAREA: RDAREA for storing LOB attribute data

LOB_RDAREA_ID1, -2, -3: Attributes 1 to 3 of the LOB column storage RDAREAs

LOB_RDAREA_ID: LOB column storage RDAREA ID

LOB_RDAREA_SERV: Server name where LOB column storage RDAREAs are located

ADT_NUMBER: Abstract data type column definitions count

UNLOAD_TYPE: Abstract data type unload method

FUNC_PARAM_NUM: Function parameters count

FUNC_PARAM_TYPE: Function parameter data type

FUNC_PARAM_LEN: Function parameter data length

S: Terminates processing.

Action

A table whose abstract data type definition has been modified cannot be reloaded. Use a UAP, etc., to transfer the data. Or, set the abstract data type definition to that used during unloading and then reload.

If the plug-in that provides the applicable abstract data type supports the constructor parameter reverse generation function, recover the table from the backup or set the abstract data type definition to that used during unloading and then reload. Then specify the constructor parameter reverse generation function (unld_func statement) in the control information file and unload the table, modify the abstract data type attribute, and then reload the table by specifying the constructor function facility (unld_func statement).

KFPL15314-E L

Unload=aa....aa, Reload=bb....bb, position=cc....cc

Displays detailed information (definition contents during unloading and reloading) for the preceding KFPL15313-E message.

aa....aa: Definition contents during unloading

bb....bb: Definition contents during reloading

cc....cc: Definition position (0 if the position cannot be identified)

The relationships between ee....ee in the KFPL15313-E message and aa....aa, bb....bb, and cc....cc in this message are shown below:

ee....ee in KFPL15313-E
Output aa....aa and bb....bb
Output format
cc....cc

TYPE_NAME
authorization-identifier.abstract-data-type-name
Characters
--

PLUGIN_ID
Plug-in ID
Decimal number

DEF_ATTR_NUM
Attributes count
Decimal number

DEF_ATTR_DTYPE
Attribute data type:

INTEGER

SMALLINT

CHAR

VARCHAR

NCHAR

NVARCHAR

MCHAR

MVARCHAR

FLOAT

SMALLFLT

BLOB

Characters
Definition sequence number of abstract data type attribute definition

DEF_ATTR_DLEN
Attribute definition length
Decimal number

DEF_ATTR
Abstract data type type ID
Decimal number

LOB_RDAREA_NUM
Number of LOB column storage RDAREAs
Decimal number
LOB definition sequence number

LOB_RDAREA
Name of LOB column storage RDAREA
Characters

LOB_RDAREA_ID1
LOB column storage RDAREA definition sequence
Decimal number

LOB_RDAREA_ID2
LOB column storage RDAREA storage sequence
Decimal number

LOB_RDAREA_ID3
ID of table storage RDAREA corresponding to LOB column storage RDAREA
Decimal number

LOB_RDAREA_ID
ID of LOB column storage RDAREA
Decimal number

LOB_RDAREA_SERV
Name of server where LOB column storage RDAREA is located
Characters

ADT_NUMBER
Number of abstract data type columns defined in table
Decimal number
--

UNLOAD_TYPE
Abstract data type unloading and reloading method:

unload_func:

Unloading with unload_func statement specified

reld_func:

Reloading with reld_func statement specified

instance:

Unloading without using unld_func statement or UNLOAD function

Reloading without using reld_func statement or UNLOAD function

unload:

Unloading or reloading with UNLOAD function

Characters

FUNC_PARAM_NUM

aa....aa:

Number of functions specified by unld_func statement

bb....bb:

Number of parameters specified by reld_func statement

Decimal number
Specification sequence of function parameter of reld_func statement

FUNC_PARAM_TYPE
Parameter data type (each data type is the same as DEF_ATTR_DTYPE):

aa....aa:

Data type of value returned by function specified by unld_func statement

bb....bb:

Data type of function parameter specified by reld_func statement

Characters

FUNC_PARAM_LEN
Parameter data size

aa....aa:

Definition length of value returned by function specified by unld_func statement

bb....bb:

Definition length of function parameter specified by reld_func statement

Decimal number

--: Not applicable

S: Terminates processing

O: Refer to the action to be taken for the KFPL15313-E message.

KFPL15315-E E+L

Unable to restart pdrorg, status unmatched, kind=aa....aa

The table reorganization process cannot be restarted because the status of the table does not match.

When aa....aa is option_control:

The option and specified control statement during restart do not match the option and specified control statement when table reorganization failed.

When aa....aa is server:

The table status of the row partitioning among servers table does not match.

When aa....aa is unload_time:

The unload data file specified in the unload statement or lobunld statement during restart and the unload data file specified when table reorganization failed do not match.

When aa....aa is restart_inf:

The re-execution information does not match.

When aa....aa is schema or table_inf:

The table status of each table in the schema is different.

aa....aa: Status type

option_control: Specified option or control statement

server: Status between servers

unload_time: Unload time

restart_inf: Re-execution information

schema: Table status in the schema

table_inf: Table information

S: Terminates processing.

Action

When aa....aa is option_control:

When a different option and control statement is specified, and the table reorganization process is re-executed, specify the option and control statement specified when table reorganization failed.

When aa....aa is server_status or unload_time:

Take one of the following actions:

When one RDAREA is recovered from backup or an RDAREA is initialized, the table reorganization process cannot be restarted. Recover all stored RDAREAs from backup, and then execute the table reorganization process (in this case, no restarting occurs).

When any applicable tables are manipulated before restart, restarting does not occur. Recover the tables from backup.

When a different unload data file is specified, specify the unload data file specified when table reorganization failed.

When actions 1 through 3 are not taken, table reorganization (pdrorg -k rorg) cannot be executed. To forcibly execute table reorganization, specify tblstatus=clear in the option statement, clear the table's status, and then execute.

When aa....aa is restart_inf, schema or table_inf:

When the reload process is performed on the applicable table (a table in the schema), restarting cannot be performed. In this case, execute reloading (pdrorg -k reld) and complete the reload process.

KFPL15316-E E+L

Unable to reload table kind unmatched, kind=aa....aa

An unloaded table cannot be reloaded because the unload file and table to reload are different file types.

When aa....aa is INSERT ONLY table:

The unloaded table cannot be reloaded in either of the following situations:

When the unloaded table is a non-falsification prevented table and the reload destination is a falsification prevented table.

When the unloaded table is a falsification prevented table and the other table (table of another system) at the reload destination is a falsification prevented table.

aa....aa: Table type

INSERT ONLY table: Falsification prevented table

S: Terminates processing.

Action

Specify the correct unload table or table name, and then re-execute.

KFPL15317-E E+L

Table aa....aa.bb....bb not unloaded by cluster key sequence, file=cc....cc

Table aa....aa.bb....bb in the unload data file was not unloaded in the order of cluster key values of the reload destination table.

aa....aa: Authorization identifier

bb....bb: Table identifier

cc....cc: Name of unload data file

If the length of the unload data file name exceeds the value obtained from the following formula, the last number of characters of the unload data file name obtained from the formula are output.

157 - authorization-identifier-length - table-identifier-length

S: Terminates processing.

O: Create the unload data file in the order of cluster key values and re-execute the command.

KFPL15318-E E+L

Cluster information not equal to aa....aa.bb....bb on unload file, file=cc....cc

The cluster key definition for table aa....aa.bb....bb in the unload data file does not match that for the reload destination table.

aa....aa: Authorization identifier

bb....bb: Table identifier

cc....cc: Name of unload data file

If the length of the unload data file name exceeds the value obtained from the following formula, the last number of characters of the unload data file name obtained from the formula are output.

152 - authorization-identifier-length - table-identifier-length

S: Terminates processing.

O: Create the unload data file for the specified table in the order of cluster key values and re-execute the command.

KFPL15319-E E+L

Unable to unload order by physical, table=aa....aa.bb....bb

Because a cluster key has been defined for table aa....aa.bb....bb, the table cannot be reorganized in physical order.

aa....aa: Authorization identifier

bb....bb: Table identifier

S: Terminates processing.

O: Unload the table in the order of cluster key values and re-execute the command.

KFPL15321-E E+L

Index aa....aa not found on table bb....bb.cc....cc

Specified index aa....aa has not been defined for table bb....bb.cc....cc.

aa....aa: Index identifier

bb....bb: Authorization identifier

cc....cc: Table identifier

S: Terminates processing.

O: If the index identifier is invalid, correct it and re-execute the command.

KFPL15322-E E+L

aa....aa key not found on table bb....bb.cc....cc

Key aa....aa is not defined in table bb....bb.cc....cc.

aa....aa:

Cluster: Cluster key

Primary: Primary key

bb....bb: Authorization identifier

cc....cc: Table identifier

S: Terminates processing.

O:

If the specified table name is invalid:
Correct the table name and re-execute the command.

If the specified table name is correct:
Check if key aa....aa is defined in the table. If it is not defined, specify the keys, except for key aa....aa, in the same order as the unloading sequence and re-execute the command.

KFPL15323-E E+L

Unable to unload order by index, index=aa....aa.bb....bb

The index specified in the order of unloading in the unload function contains one of the following errors:

The index has multiple structure columns and descending order was specified:
Because the specified index has multiple structure columns, the index cannot be unloaded in descending order.

A plug-in index was specified:
The specified index is a plug-in index; an unloading operation with an index specification cannot be performed.

An index with a repetition column was specified:
The specified index is an index for a repetition column; an unloading operation with an index specification cannot be performed.

A substructure index was specified:
An unloading operation cannot be performed with a substructure index specification.

aa....aa: Authorization identifier

bb....bb: Index identifier

S: Terminates processing.

O: In the -b option, specify the name of an index that is not one of the following, or specify physical, and then re-execute the command.

An index with an exceptional key value specified

An index that includes a repetition column among the columns comprising the index

A plug-in index

A substructure index

KFPL15327-E E+L

Unable to reload due to DB data compressed in unload file , table=aa....aa. "bb....bb", column="cc....cc", attribute=dd....dd, value=ee....ee

When reloading data using an unload data file containing compressed data, the data could not be reloaded because the compression specification for the table was different at unload time and at reload time.

aa....aa: Authorization identifier

bb....bb: Table identifier

cc....cc: Name of the column where the error was detected

dd....dd: Compression specification for the column where the error was detected

COMPRESSED: Compression specification

partition size: Compression partition size

ee....ee: Value of compression specification in the unload data file for the column where the error was detected

The following table indicates the cause of the error based on the information output in dd....dd and ee....ee.

Information about the column where the error was detected
Cause of error

Compression specification (dd....dd)
Value of compression specification in the unload data file (ee....ee)

COMPRESSED
use (compression is specified)
The compression specifications do not match.
No compression is specified for the table being reloaded.

no use (no compression is specified)
The compression specifications do not match.
No compression is specified for the column in the unload data file.

partition size
Compression partition size
The compression partition sizes do not match.

S: Terminates processing.

O:

If the wrong unload data file was specified:

Specify the unload data file corresponding to the table to be reloaded, and then reload the data.

If you want to reload the data in the specified unload data file:

Make sure that the compression specification of the table to be reloaded matches the compression specification of the table at unload time, and then reload the data.

KFPL15326-E E+L

Unable to unload due to specified index except values, index=aa....aa."bb....bb"

The index aa....aa."bb....bb", specified in the -b option, contains a defined index exclusion value; the index cannot be unloaded.

aa....aa: Authorization identifier

bb....bb: Index identifier

S: Terminates processing.

O: Either specify an index for which an index exclusion value is not defined or omit the specification of the -b option and re-execute the command.

KFPL15331-E E+L

aa....aa not held, RDAREA=bb....bb

RDAREA bb....bb is not in command hold status.

aa....aa: {Data dictionary|USER RDAREA}

bb....bb: RDAREA name

S: Terminates processing.

O: Place the corresponding RDAREA on command shutdown status and re-execute the command.

KFPL15333-E E+L

Data dictionary lock request failed

Data dictionary RDAREA cannot be locked.

S: Terminates processing.

O: Refer to the message that was output before this message to eliminate the cause of the error, and re-execute the command.

KFPL15334-E L

Specified data dictionary table not found in system, table=aa....aa

Specified table aa....aa is not a dictionary table.

aa....aa: Table identifier

S: Terminates processing.

O: Correct the specified table name and re-execute the command.

KFPL15335-E E+L

Specified aa....aa file is many, max=bb....bb

The number of files specified in the unload statement, lobunld statement, or idxname statement exceeds the maximum specifiable value bb....bb.

aa....aa: Incorrect specification:

{ unload|lobunld|idxname }

bb....bb: Maximum number of files that can be specified

S: Terminates processing.

O:

For the unload or lobunld statement
Check the specified table definition and the specification of the unload or lobunld statement, correct the unload or lobunld statement, and re-execute.
If the -g option is not specified, the maximum number of files that can be specified equals the number of partitioned servers. If the -g option is specified, the number is 1.

For the idxname statement
Check the specified table definition and the specification of the idxname statement, correct the idxname statement, and re-execute.
The maximum number of files that can be specified equals the number of indexes defined in the table. If the asterisk (*) is specified in the name operand of the idxname statement, the maximum number of files that can be specified is 1.

KFPL15336-E E+L

Specified aa....aa name bb....bb of cc....cc file not much

The server name specified by the unload or lobunld statement or by the server operand of the idxname statement differs from the server name in the table definition.

aa....aa: server

bb....bb: Specified server name

cc....cc: Processing that was attempted:

{ unload|lobunld|idxname }

S: Terminates processing.

O:

For the unload or lobunld statement
Correct the server name in the unload or lobunld statement, and re-execute.

For the idxname statement
Correct the server name specified by the server operand of the idxname statement, and re-execute.

KFPL15337-E E+L

Specified aa....aa name bb....bb of index file not much

The index information file name or RDAREA name specified in the index information file (index) To be used is different from the name specified in the index definition of the table subject to processing.

aa....aa: Specified name:

{ RDAREA|index }

bb....bb: Index information file name or RDAREA name

S: Terminates processing.

O: Correct the index information file name or RDAREA name in the index information file to be used and re-execute the command.

KFPL15338-E E+L

Specified aa....aa name bb....bb of cc....cc directory not much

The server name for the directory specified in the control information file does not match the information in the table definition subject to processing.

aa....aa: server

bb....bb: Server name

cc....cc: Specified directory type

{ index|sort }

S: Terminates processing.

O: Correct the server name for the directory specified in the control information file and re-execute the command.

KFPL15339-E L

Index file no specified, index=aa....aa.bb....bb, RDAREA=cc....cc

An index information file was not specified for index aa....aa.bb....bb in RDAREA cc....cc.

aa....aa: Authorization identifier

bb....bb: Index identifier

cc....cc: RDAREA name

S: Terminates processing.

O: Specify the index information file for the corresponding RDAREA and re-execute the command.

KFPL15340-E E+L

RDAREA name not specified in index file, index=aa....aa

An RDAREA name was omitted for the index information file to be used.

aa....aa: Specified index identifier

S: Terminates processing.

O: Add the RDAREA name to the index information file and re-execute the command.

KFPL15341-E E+L

Server name not specified in aa....aa

No server name was specified for the directory or file name specified in the control information file.

aa....aa: Invalid specification:

{ unload file (unload file)

| index directory (index directory)

| sort directory (sort directory)

| lobunld file (LOB unload file) }

S: Terminates processing.

O: Specify the server name for the directory or file name specified in the control information file and re-execute the command.

KFPL15342-E E+L

Specified aa....aa directory is too many, max=bb....bb

The number of directories specified in the control information file exceeds the permitted maximum bb....bb.

aa....aa: Type of directory

{ index|sort work }

bb....bb: Permitted maximum

S: Terminates processing.

O: Check the table definition, correct the number of directories, then re-execute the command.

KFPL15343-E E+L

Index file duplicated, index=aa....aa.bb....bb, RDAREA=cc....cc

A duplicated name was specified for the index or RDAREA to be used.

aa....aa: Authorization identifier

bb....bb: Index identifier

cc....cc: RDAREA name

S: Terminates processing.

O: Correct the duplicated name of the index information file or RDAREA to be used and re-execute the command.

KFPL15344-W E+L

Control character found, skip row=aa....aa, table=bb....bb."cc....cc"

A NULL or linefeed character was found in row data; this row was not output.
Row data (character data, national character data, or mixed character data) That contains a NULL or linefeed character cannot be output in DAT format.

aa....aa: Number of lines skipped

bb....bb: Authorization identifier

cc....cc: Table identifier

S: Resumes processing.

O: In the -W option, specify either bin or extdat, and output the file in binary format or extended DAT format.

KFPL15345-E E+L

Unable to execute aa....aa for PLUGIN index bb....bb."cc....cc"

Function aa....aa cannot be executed for plug-in index bb....bb."cc....cc".

aa....aa: Function:

ixor: Index reorganization

pdreclaim: Free page release utility

pdpgbfon: Global buffer residence utility

bb....bb: Authorization identifier

cc....cc: Index identifier

S: Terminates processing.

O: Take one of the following actions:

When aa....aa is ixor:

When you want to reorganize the plug-in index:
Instead of reorganizing the plug-in index, reorganize the table in which the plug-in index is defined or re-create the plug-in index.

When there is no need to reorganize the plug-in index:
Delete the index or idxname statement that specifies the plug-in index, then re-execute index reorganization.

When aa....aa is pdreclaim:

When a plug-in index is specified in the idxname statement of pdreclaim, delete the idxname statement. When releasing a plug-in index used free page, re-create the index (pdrorg -k ixrc).

When aa....aa is pdpgbfon:

Because the plug-in index cannot be processed by pdpgbfon, terminate the command.

KFPL15346-W E+L

Table aa....aa."bb....bb" cc....cc skipped

When cc....cc is reload:
During reloading by schema, because the information for table aa....aa."bb....bb" was not found in the unload data file, the reload process was skipped. Or, when resuming table reorganization, the reloading process was skipped because reloading of table aa....aa."bb....bb" is complete. If the timing of the abnormal termination is such that it occurs before the table status is written as reorganizing, the table status becomes like the initial status. In other words, the status is the same as when reloading has completed, such that the reload processing of the unloaded table is skipped. In this case, specify the relevant table only, with the -t option, and re-execute the reloading (-k reld).

When cc....cc is ixrc:
The index recreation process was skipped because creation of the index for table aa....aa."bb....bb" was complete when table recreation resumed.

aa....aa: Authorization identifier

bb....bb: Table identifier

cc....cc: Process type

reload: Reload process

ixrc: Index reorganization process

S: Continues processing.

KFPL15347-E E+L

Unmatched aa....aa between bb....bb "cc....cc" of RDAREA "dd....dd" and bb....bb "ee....ee" of RDAREA "ff....ff"

aa....aa ("cc....cc") of RDAREA "dd....dd", which is the target when executing the utility, and aa....aa ("ee....ee") of RDAREA "ff....ff" do not match.

aa....aa:

generation number: Generation number

inner replica status: Replica status

bb....bb:

number: Number

status: Status

cc....cc: Generation number

current: Current RDAREA

not current: Other than the current RDAREA

dd....dd: RDAREA name

ee....ee: Generation number

current: Current RDAREA

not current: Other than the current RDAREA

ff....ff: RDAREA name

S: Terminates processing.

O:

When aa....aa is generation number:
If the utility is executed (during current access) without the generation number (using the -q option) specified, use the pddbchg command to match up the generation number of the RDAREA to be processed, and re-execute.

When aa....aa is inner replica status:
If the utility is executed with the generation number (using the -q option) specified, use the pddbchg command to match up all replica statuses of the RDAREA to be processed.

KFPL15348-E E+L

No specified generation RDAREA="aa....aa", generation=bb

No RDAREA "aa....aa" of specified generation bb was found.

aa....aa: RDAREA name (*** is output when no RDAREA of the specified generation was found)

bb: Generation number (if a table or index is dropped while the utility is executing, the generation number cannot be determined, and -1 is output)

S: Terminates processing.

O:

If the specified generation number is correct:

Create a replica RDAREA for the target RDAREA, and then re-execute the utility.

If the specified generation number is in error:

Specify the correct generation number, and then re-execute the utility.

If a definition SQL is executed on a table on which a utility is being executed:

Execute the definition SQL when the utility is not being executed.

KFPL15349-E E+L

aa....aa scan failed, code=bb

A data access error occurred during retrieval of BLOB or BINARY column data.

aa....aa: Attribute of the column that generated the error

LOB: BLOB column

BIN: BINARY column

bb: Error code

4: A data access error occurred during acquisition of BLOB or BINARY data.

12: Updating of a BLOB column or a BINARY column was detected during acquisition of BLOB or BINARY data.

S: Terminates processing.

O:

Error code 4:

Refer to the message that was output to the message log file before this message, resolve the error, and then re-execute the command.

Error code 12:

Make sure that tables subject to unload processing are not being updated, and then re-execute the command.

KFPL15555-E E+L

Few file descriptors, soft limit=aa....aa, hard limit=bb....bb

The input file cannot be partitioned because the physical limit value for files that can be opened or locked by a single process set in the kernel parameters for the OS is too small.

aa....aa: The logical limit (soft limit) for the number of files that can be opened or locked by single processes

bb....bb: The physical limit (hard limit) for the number of files that can be opened or locked by single processes

S: Terminates processing.

O: Raise the physical limit value for files that can be opened or locked by single process set in kernel parameters for the OS. For details about estimating required specification values for HiRDB operations, see Estimating operating system parameters for the OS in the HiRDB Version 9 Installation and Design Guide.

KFPL16300-E E+L

Invalid lobmid file, file=aa....aa

The specified LOB middle file has not been created correctly.

aa....aa: Name of the LOB middle file

If the length of the LOB intermediate file name exceeds 150 characters, the last 150 characters of the LOB intermediate file name are output.

S: Terminates processing.

O: Specify a LOB middle file that was output correctly during creation of the LOB column structure base table and re-execute the command.

KFPL16310-E E+L

Divided information of aa....aa.bb....bb not equal to lobmid file, file=cc....cc

LOB column data loading is disabled because the partitioning definition for table aa....aa.bb....bb in the LOB middle table differs from the partitioning definition for the table for loading the LOB column data.

aa....aa: Authorization identifier

bb....bb: Table identifier

cc....cc: Name of the LOB middle file

If the length of the LOB middle file name exceeds the value obtained from the following formula, the last number of characters of the LOB middle file name obtained from the formula are output.

152 - authorization-identifier-length - table-identifier-length

S: Terminates processing.

O: Use the LOB middle file for the specified table to load the LOB column data.

KFPL16320-E E+L

Unmatched LOB load type "a" in command line with LOB load type "b" of LOBMID file cc....cc

Value "a"specified in the -k option on the command line during LOB creation does not match value "b" specified in the -k option on the command line during creation of the LOB column structure base table.

a: LOB creation type specified in the -k option during LOB creation:

f: Creation of a file for each item of LOB data

c: Creation of a LOB column input file

b: LOB creation type specified in the -k option during creation of the LOB column structure base table:

f: Creation of a file for each item of LOB data

c: Creation of a LOB column input file

cc....cc: Name of LOB middle file

If the length of the LOB middle file name exceeds 66 characters, the last 66 characters of the LOB middle file name are output.

S: Terminates processing.

O: For LOB creation, specify the same LOB creation type in the -k option that was specified for creation of the LOB column structure base table.

KFPL16321-E E+L

Unmatched number of "lobcolumn" statements with aa....aa (number of LOB columns)

The number of lobcolumn statements in the control information file does not match the number of LOB columns.
The number of lobcolumn statements required for creation is aa....aa.

aa....aa: Number of required lobcolumn statements

S: Terminates processing.

O:

LOB creation in units of tables or RDAREAs of LOB column structure base table:
Specify as many lobcolumn statements as there are LOB columns in the table to be created. When a column structure information file is used, specify as many lobcolumn statements as there are LOB columns specified in the column structure information file.

LOB creation in units of LOB RDAREAs:
Specify one lobcolumn statement.

KFPL16322-E E+L

LOB column "aa....aa" not found, table=bb....bb."cc....cc"

Specified LOB column "aa....aa" was not found in the table.

aa....aa: Column name

bb....bb: Authorization identifier

cc....cc: Table identifier

S: Terminates processing.

O: Specify a LOB column name entered in the table definition and re-execute the command.

KFPL16323-E E+L

RDAREA "aa....aa" conflicted with LOB column "bb....bb"

LOB RDAREA "aa....aa" specified in the lobmid control statement contradicts the information about LOB column "bb....bb" specified in the lobcolumn statement.

aa....aa: LOB RDAREA name

bb....bb: Column name

S: Terminates processing.

O: Check the correspondence between the LOB RDAREA name specified in the lobmid control statement and the LOB column name specified in the table definition, then re-execute the command.

KFPL16324-E E+L

Unable to continue LOB load, because of invalid LOB middle file, file=aa....aa

LOB cannot be created due to invalid LOB middle file aa....aa.

LOB middle files obtained by using the same input data file as when LOB column structure base table was created:
The order of the LOB middle files specified during LOB creation is invalid.

LOB middle file obtained by using a different input data file as when LOB column structure base table was created:
LOB middle file specified during LOB creation is invalid.

aa....aa: LOB middle file name

If the length of the LOB middle file name exceeds 140 characters, the last 140 characters of the LOB middle file name are output.

S: Terminates processing.

O:

LOB middle files obtained by using the same input data file as when LOB column structure base table was created:
Specify the LOB middle files in the same orde r as the corresponding input data file lines in the LOB column structure base table, then re-execute the command.

LOB middle file obtained by using a different input data file as when LOB column structure base table was created:
A LOB middle file obtained from a different input data file cannot be specified at the same time. Use a separate control statement to specify a LOB middle file for a different input data file, then execute the command to create its LOB data.

KFPL16325-W E+L

LOBCOLUMN for "aa....aa" ignored, because of not specified LOB column in column structure information file

The lobcolumn statement for "aa....aa" was ignored, because this control statement is for a LOB column that is not specified in the column structure information file (a LOB column that is not specified in the input file for the LOB column structure base table).

aa....aa: Name of the ignored LOB column

S: Ignores the specified lobcolumn statement and resumes processing.

KFPL16326-E E+L

Unable to omit aa....aa in "bb....bb" statement

aa....aa cannot be omitted from statement "bb....bb" that was specified in the control information file.

aa....aa: Omitted information:

column name: Column name

bb....bb: Name of control statement:

lobcolumn: lobcolumn statement

S: Terminates processing.

O: Specify aa....aa in statement "bb....bb" of the control information file and re-execute the command.

KFPL16327-E E+L

Unable to continue LOB load, because invalid column structure information file

LOB data cannot be created due to incorrect information in the column structure information file specified in the -c option.

The LOB column specified during LOB creation is not the one specified in the input data file during LOB column structure base table creation.

S: Terminates processing.

O:

Column structure information file not specified in -c option during LOB column structure base table creation:

Create LOB data by omitting specification of the column structure information file in the -c option during LOB creation and specifying lobcolumn control statements for all LOB columns.

Column structure information file specified in -c option during LOB column structure base table creation:

Check that the column structure information file specified in the -c option for LOB column structure base table creation is the same file specified for LOB creation, specify the corresponding lobcolumn control statement, then re-execute the command.

KFPL16328-W L+S

Unable to check LOB data count, because error data exist in input data file

During LOB column structure base table creation, erroneous data was found in the input data file for the LOB column structure base table. If the -e option was specified, the system cancels data load processing for the LOB column structure base table, in which case the number of LOB data items in the LOB column input file cannot be verified during LOB data creation.

S: Resumes processing.

KFPL17000-E E+L

Unmatched aa....aa DB=bbbbbb, UTL=cccccc

One of the following errors was detected:

The job name associated with the synchronization point information stored in the database does not match the job name specified in the utility control statement.

The index creation method associated with the synchronization point information stored in the database does not match the index creation method used during the execution of the utility.

The utility name associated with the synchronization point information stored in the database does not match the utility that was executed.

aa....aa: Mismatching information type:

job name: Job name

index mode: Index mode

bbbbbb:

job name displayed for aa....aa: The job name stored in the database (L in parentheses indicates pdload; R indicates pdrorg)

index mode displayed for aa....aa: The index creation method stored in the database (value specified in -i option)

cccccc:

job name displayed for aa....aa: The job name specified during utility execution (if *** is displayed, no job name was specified)

index mode displayed for aa....aa: The index creation method specified during utility execution (value specified in -i option)

S: Terminates processing.

O:

job name displayed for aa....aa:
Execute the utility of the abnormally terminated job, then re-execute. If there is no need to re-execute the utility of the abnormally terminated job, specify CLR in the job operand and execute.

index mode displayed for aa....aa:
Re-execute the utility of the abnormally terminated job without modifying the index creation method (-i option). If there is no need to re-execute the utility of the abnormally terminated job, specify CLR in the job operand and execute.

KFPL17001-E E+L

Unload file not available for aa....aa. bb....bb of RDAREA cc....cc, reason=dd....dd (system=ee....ee, file=ff....ff)

The unload data file cannot be used because it is not recent.

aa....aa: Authorization identifier

bb....bb: Table identifier

cc....cc: RDAREA name

dd....dd: Reason (Unload-time: Unload data file creation date)

ee....ee: Date on DB side

ff....ff: Date on unload data file side

S: Terminates processing.

O: Specify a recent unload data file (the last reorganization (-k rorg) executed on the applicable table) and re-execute.

KFPL17010-E E+L

Unmatched row count RDAREA=aa....aa(bb....bb), RDAREA=cc....cc(dd....dd)

The synchronization point rows counts for a row-partitioned table stored in different RDAREAs do not match.

aa....aa: RDAREA name

bb....bb: Rows count

cc....cc: RDAREA name

dd....dd: Rows count

S: Terminates processing.

O: Take one of the following actions:

After executing the utility at the level of the RDAREAs that terminated abnormally, re-execute the utility at the table level.

When re-executing the utility at the RDAREA level is not necessary, specify CLR in the job operand.

When *** is output to the RDAREA, see the KFPL15036-E message output before this message was output.

KFPL20000-E E+L

Internal function (aa....aa) error occurred, code=bbbbb

HiRDB detected an error in the extension of the utility process.

aa....aa: Name of the function where the error was detected

bbbbb: Error detail code

S: Terminates processing.

O: See the error detail code to eliminate the cause of the error, and then re-execute the command. For more information about the error detail code, see 4.1 Detail codes for RPC-related errors, or 4.2 Detail codes for system-related errors. If an error occurs that operators cannot solve, contact the HiRDB administrator. The table below summarizes the most common causes of the error and the required action:

Detail code
Cause
Action

-307
A timeout occurred.
If processing does not terminate within the utility execution monitoring time specified in the pd_utl_exec_time operand or the option statement's exectime operand, take the action indicated in the KFPL11111-E message.

-310
The communication destination unit or server is not running.
If the unit or server specified in the control statement or on the command line has stopped, have the HiRDB administrator start the unit or server. If the unit or server cannot be started, change the name of the unit or server specified in the control statement or on the command line to the name of a running unit or server.

-314
Communication among processes executed by the utility is unavailable.

If the utility's processes were forcibly terminated by the pdcancel command, ignore this message.

It is possible that messages cannot be output to standard output and the communication buffer is full of messages that cannot be output, so that the messages cannot be received. In this case, enable messages to be output to standard output on the monitor where the command was executed.

If the utility's processes are executing in parallel on multiple servers, or if an error occurred in the processes on a server causing processing to be interrupted, such that there are no processes to receive the statements transmitted from processes that are being processed, take action based on the error message that was output from the first server where an error occurred.

-364
An error occurred on the communication destination server.
If the communication destination process was forcibly terminated due to the reason cited in the error message output before this message, take the action indicated in that message.

-5104
The number of concurrently executing utilities has exceeded the maximum.
Take one of the following actions:

If this message is output when XDS is starting up or terminating, start or terminate XDS again, making sure the total number of XDS processes to be started or terminated (the XDS database definition pd_import_export_parallel) does not exceed 64.

If you are executing the utility at the same time as XDS is starting up or terminating, execute the utility after XDS has finished starting up or terminating.

If multiple utilities are executing concurrently, reduce the number of concurrently executing utilities.

If the value of the pd_exec_mode operand in the system common definition is 0, change it to 1.

-5303
HiRDB did not start normally.
Refer to the error message that was output before this message, investigate the cause of the error, and take corrective action. If necessary, re-execute the command.

Action

If the problem is that the unit or server stopped, restart the unit or server. However, if the problem is that a network error caused a temporary stop, HiRDB may automatically restart. In this case, no restart is necessary. For details on when HiRDB automatically restarts, see the HiRDB Version 9 System Operation Guide.

If an error occurs that the HiRDB administrator cannot solve, contact the customer support center.

KFPL20001-E E+L

Insufficient memory in message buffer pool due to concurrent execution of aa....aa

A temporary memory shortage occurred in the message storage buffer pool during process allocation when pdload, pdrorg, pdrbal, or a plug-in-provided command was executed concurrently.

aa....aa: Program name:

{ "pdload"|"pdrorg"|"pdrbal"|"COMMAND" }

S: Terminates processing.

O: Re-execute the command after the current execution of pdload, pdrorg, pdrbal, or the plug-in-provided command is completed.

Action

If the pdchprc command was used to request services from a server for which the maximum number of startup processes had been set to 0, use the pdchprc command to increase the maximum number of startup processes.

If a service was requested from a server being refreshed by the pdpfresh command, re-execute the utility after the pdpfresh command has finished.

If utilities are being executed concurrently, review and, if necessary, revise the maximum number of utilities that can be executed at the same time. To find out the maximum number of utilities that can be executed concurrently, see the manual HiRDB Version 9 Command Reference.

KFPL20003-E E+L

Unable to send message from aa....aa to bb....bb

A communication error occurred between servers aa....aa and bb....bb.

aa....aa: Name of the send source host

bb....bb: Name of the send destination host

S: Terminates processing.

Action

Take action appropriate to the KFPL20000-E or KFPL20100-E message output before this message. If the error was not a physical communication error, there may be an inconsistency in the system definitions concerning the relationship between the hosts; check the interhost definitions for the hosts affected by the error and re-execute.

KFPL20005-E E+L

Server down detected

Abnormal server termination was detected. Or, processing cannot be resumed because the system was switched.

S: Terminates processing.

O: Correct the cause of the abnormal server termination on the basis of error messages that have already been output and re-execute the command. If system switchover occurred during processing, set the host that executes the command so that it can reference and update files needed for command processing, then re-execute.

KFPL20010-E E+L

aa....aa error occurred, code=bbbb

Connection establishment or release with HiRDB failed.

aa....aa: Processing:

{ Connect|Disconnect }

bbbb: Error detail code

S: Terminates processing.

O: See 4.2 Detail codes for system-related errors to eliminate the cause of the error, and re-execute the command.

Note

If this message is displayed during the execution of a plug-in-provided command, the message is output only to the indicated output device type (L).

KFPL20020-E E+L

Transaction (aa....aa) error occurred, code=bbbbb

Transaction startup or settlement failed.

aa....aa: Type of transaction:

{ begin|commit|rollback }

bbbbb: Error detail code

S: Terminates processing.

O: See 4.2 Detail codes for system-related errors to eliminate the cause of the error. If commit or rollback processing, other than during pdrorg unload processing, caused an error, re-execute the command after restoring the database to the status it was in before the utility was executed. If the error cannot be corrected, contact the HiRDB administrator.

Action

Contact the customer support center.

KFPL20041-E E+L

Staticizer Option not setup

The -q option can only be used when the HiRDB Staticizer Option is embedded.

S: Terminates processing.

Action

Embed the HiRDB Staticizer Option, and then re-execute.

KFPL20050-E E+L

Invalid host name

This utility cannot be executed with the specified host name.

S: Terminates processing.

O: Correct the host name on the command line or in the control information file and re-execute the command.

KFPL20051-E E+L

Invalid server name

The server name specified in the control statement or command line is invalid.

S: Terminates processing.

O: Correct the server name specified in the control statement or command line, and then re-execute the command.

KFPL20060-E E+L

Security Audit inactive, status=aa....aa, reason=bbbbb

The security audit facility has stopped, so the history of the utility was not output to the audit trail file.

aa....aa: Run status of the security audit facility

INACTIVE: The security audit facility has stopped.

OTHER: Another error occurred.

bbbbb: Error detail code

S: Continues processing.

O: When it is necessary to fetch an audit trail, take one of the following actions according to the run status of the security audit facility:

INACTIVE: Start the security audit facility.

OTHER: See the Detail codes for the system-related error. For information on system-related errors, see 4.2 Detail codes for system-related errors. If an error occurs that programmers cannot solve, contact the HiRDB administrator.

Action

If an error occurs that the HiRDB administrator cannot solve, contact the customer support center.

KFPL20061-E E+L

Audit trail generation file write error, reason=aaaaa

The history of this utility was not output to the audit trail file because an error occurred during output to the audit trail file.

aaaaa: Error detail code

S: Continues processing.

O: When it is necessary to fetch an audit trail during re-execution of the utility, see the error detail code to eliminate the cause of the error. For information on system-related errors, see 4.2 Detail codes for system-related errors. If an error occurs that programmers cannot solve, contact the HiRDB administrator.

Action

If an error occurs that the HiRDB administrator cannot solve, contact the customer support center.

KFPL20062-E E+L

Audit trail generation file not found, number=aaa

There are no audit trail files for data loading.

aaa: Audit trail file number

S: Terminates processing.

Action

Use the pdls command to check the status of the audit trail file specified in the srcuoc control statement, and once there is an audit trail file waiting for data loading, re-execute the command.

KFPL20090-E E+L

Unable to output message to aa....aa

Messages cannot be output to aa....aa.

aa....aa: Output destination

{ stdout|stderr }

S: Resumes processing.

Action

Refer to the message that was output before this message to determine the cause of the error.

KFPL20091-E L

Unable to output information to report file

Information cannot be output to the processing results file.

S: Continues processing.

Action

For the cause and action to be taken, refer to the message that is output immediately before this message.

KFPL20100-E E+L

Communication (aa....aa) error occurred, code=bbbbb

A communication error occurred.

aa....aa: Type of communication processing

bbbbb: Error detail code

S: Terminates processing.

O:

See 4.1 Detail codes for RPC-related errors and eliminate the cause of the error, then re-execute the command. If an error occurs that the programmer cannot handle, contact the HiRDB administrator.

If aa....aa is p_f_sqa_rcomb_open or p_f_sqa_rcomb_close and the error detail code is 8, there is insufficient memory. In UNIX, if the error detail code is other than 8, an error occurred in combuf communications. If there is insufficient memory, re-estimate the memory. Also, stop any unnecessary processes. In UNIX, if an error occurred in combuf communications, refer to the OS documentation to resolve the error.

If one of the following codes is output, the error may not be a communication error. In that case, take the appropriate action.

-307:

If processing does not terminate within the utility execution monitoring time specified in the pd_utl_exec_time operand or the option statement's exectime operand, take the action indicated in the KFPL11111-E message.

-314:

Communication among processes executed by the utility is unavailable. Consider the following causes.

(1) If the utility's processes were forcibly terminated by the pdcancel command, ignore this message.

(2) It is possible that messages cannot be output to standard output and the communication buffer is full of messages that cannot be output, so that the messages cannot be received. In this case, enable messages to be output to standard output on the monitor where the command was executed.

(3) If the utility's processes are executing in parallel on multiple servers, or if an error occurred in the processes on a server causing processing to be interrupted, such that there are no processes to receive the statements transmitted from processes that are being processed, take action based on the error message that was output from the first server where an error occurred.

-364:

If the communication destination process was forcibly terminated due to the reason cited in the error message output before this message, take the action indicated in that message.

Action

If the error cannot be corrected by the HiRDB administrator, contact the customer support center.

KFPL20200-E E+L

Database access (aa....aa) error occurred, code=b

An error occurred before or after the database was referenced or updated.

aa....aa: Processing resulting in the error

b: Error code:

4: Memory shortage

8: I/O error

S: Terminates processing.

O:

If the error code is 4:
Allocate enough memory to the process and re-execute the command.

If the error code is 8:
Refer to the message that is output to standard error or to the message log file, resolve the error, and then re-execute the command.

KFPL21000-E E+L

PLUGIN function error occurred, operation=aa....aa, code=bb....bb, line=cc....cc

An error occurred in a plug-in function.

aa....aa: Operation name

bb....bb: The return code received from the plug-in function

cc....cc: Row number of the data in which the error occurred

S: Terminates processing.

O: Correct the cause of the error by referring to the preceding error message and re-execute the command.

KFPL21111-E E+L

Unable to make parameter, operation=aa....aa, code=bb....bb, line=cc....cc

Unable to generate the argument to be passed to the constructor function.

aa....aa: Parameter generation processing type

bb....bb: Return code from the parameter generation function

cc....cc: Line number at which the error occurred

S: Terminates processing.

O:

Correct the cause of the error by referring to the preceding error message and re-execute the command.

When data-loading using a binary-format input data file, if the preceding error message is KFPA11930-E (insufficient memory) and the allocation area size is different from the input parameter size, the problem is an invalid input data file format. In this case, review the input data file.

KFPL21112-E E+L

ADT operation error, operation=aa....aa, code=bb....bb

An error occurred during abstract data type operation aa....aa.

aa....aa: Operation function name

bb....bb: Operation code

S: Terminates processing.

O: Correct the error by referring to the error message that was output immediately before this message, and re-execute the command. If no error message has been output, contact the customer support center.

KFPL22000-E E+L

System call error, func=aa....aa, errno=bbb

A system call (function) error occurred.

aa....aa: Name of system call (function)

bbb: Error number set in errno

S: Terminates processing.

O:

Check the meaning of the error number (errno: external integer variable indicating the error status), refer to errno.h and to the applicable OS manual to eliminate the cause of the error, then re-execute the command.

If errno = 0, eliminate the cause of the error by referring to the KFPL22001-E message output before this message, and re-execute the command.

In addition, this message is sometimes output when one of the following occurs while XDS is starting up. If this is the case, ignore the message.

The XDS process was terminated by the pdxdsstop -f command or the pdstop -f command.

The XDS process was terminated using the kill command or similar means.

Database import terminated abnormally.

The XDS process terminated abnormally.

In some cases, messages are not output to standard output device during the execution of a plug-in-provided command.

KFPL22001-E E+L

aa....aa

Displays information about an error that occurred during a system call. If the OS's system log facility does not support Japanese character codes, messages may not be output correctly to the system log. In such a case, refer to the HiRDB message log.

aa....aa: Error information

S: Terminates processing.

O: Correct the error by referring to the error information, and re-execute the command.

KFPL22222-I L+S

Max row length=aa....aa

The maximum row length of the unload data file output in the DAT format is aa....aa bytes.

aa....aa: Maximum row length

S: Continues processing.

O: If the output unload data file will be the input to pdload and the maximum row length displayed in this message is 32 KB or more, specify the maximum row length in the maxreclen operand of the source statement.

KFPL22223-I L+S

Delete row count=aa....aa, table=bb....bb. "cc....cc", file=dd....dd

aa....aa rows were not output to the unload data file because a UOC issued a deletion request during the unload processing of table bb....bb."cc....cc".
The output destination for this message depends on the value specified in the -m option of the utility that was executed. For details about the -m option, see the manual HiRDB Version 9 Command Reference.
The following table indicates the output destinations corresponding to the value specified in the -m option:

Value specified in -m option
Output destination of message

lvl0
Log file (L) and standard output (S)

lvl1
Log file (L)

lvl2
Neither the log file (L) nor standard output (S)
However, the message is output to the work file.

aa....aa: The number of rows for which a deletion request was issued

bb....bb: Authorization identifier

cc....cc: Table identifier

dd....dd: Unload data file name

If the name of the unload data file exceeds 101 characters, the last 101 characters of the unload data file name are output.

S: Continues processing.

KFPL23000-E E+L

Error occurred on server=aa....aa

An error occurred at the server.

aa....aa: Server name

S: Terminates processing.

O: Refer to the error message that was output immediately before this message to eliminate the cause of the error, and re-execute the command. If the processing is being executed in the no-log mode, re-execute after restoring the database to the status it was in before the utility was executed.

KFPL23001-E E+L

Server aa....aa not running

A server is not active.

aa....aa: Server name

S: Terminates processing.

O: Activate the server indicated in the message and re-execute the command.

KFPL23100-E E+L

HiRDB file aa....aa error, errno=bb....bb, HiRDB file name=cc....cc

A HiRDB file access error occurred.

aa....aa: HiRDB file function:

close: HiRDB file close processing

open: HiRDB file open processing

read: HiRDB file read processing

write: HiRDB file write processing

reopen: Opening of HiRDB file or the second or subsequent volume of a multivolume file

bb....bb: HiRDB system error code

cc....cc: Name of the HiRDB file

If the length of the HiRDB file name exceeds 150 characters, the last 150 characters of the HiRDB file name are output.

S: Terminates processing.

Action

See 5.1 Error codes returned from HiRDB file system access requests to eliminate the cause of the error.

KFPL23201-W E+L

Skip load process,audit trail aa....aa file status=(b,c,d),file=ee....ee

Data loading was skipped because the specified audit trail file is not on hold, and not waiting for data loading. If the param operand of the srcuoc statement specifies all audit trail files, and no audit trail file can be loaded, this message applies to all audit trail files.

aa....aa: Generation

b: c (current) or s (not current)

c: d (waiting for data loading) or - (data loading is complete)

d: h (currently on hold) or - (not currently on hold)

ee....ee: Audit trail file name displayed by the absolute path name

If the length of the file name exceeds 144 characters, the last 144 characters of the file name are output.

S: Continues processing.

When data loading resumes, after data loading of the audit trail file is skipped and message KFPL23201-W is output, the return code of pdload will be as follows.

Number of audit trail files loaded into the audit trail table | Value specified in the param operand of the srcuoc statement
file=audit trail file name | file=all
mode=normal | mode=force | mode=normal
1 or more | 0 | 0 | 0
0 | 4 | 4 | 4

Legend:

0: Terminates normally with return code 0.

4: Terminates with a warning and return code 4.

Note: If an error occurs during data loading due to some other cause, it terminates abnormally with return code 8.

Action

Use the pdls command to check the name and file status of the specified audit trail file.

If the file name is incorrect, correct it and re-execute the command.

If the specified audit trail file data has been loaded, normally no action is required. If data needs to be loaded, you can specify force in the mode operand to the srcuoc statement and re-execute if necessary.

Note that when data loading is executed with file=all specified in the param operand to the srcuoc statement, it is not necessary to recover the audit trail table and reload the data, because the audit trail file data will have been loaded.

KFPL23202-E E+L

Error occurred at change audit trail aa....aa file status, file=bb....bb, reason=ccccc

The data loaded status of the audit trail file cannot be changed.

aa....aa: Generation

bb....bb: Audit trail file name displayed by the absolute path name

If the length of the file name exceeds 128 characters, the last 128 characters of the file name are output.

ccccc: Error code

S: Terminates processing.

Action

The data from the specified audit trail file has already been registered to the audit trail table. If an error occurs and this audit trail file is again loaded with data, the data is duplicated, therefore deletion of data using the pdaudrm -f command is recommended. To understand why the status of the audit trail file could not be changed, see the error detail code on the message that was output, and eliminate the cause of the error. For details on error detail codes, see 4. Error Detail Codes.

KFPL23203-E E+L

Table aa....aa.bb....bb cc....cc table

Table aa....aa.bb....bb specified an audit trail data registration UOC even though it is not an audit trail table. Or, this table did not specify an audit trail data registration UOC even though it is an audit trail table.

aa....aa: Authorization identifier

bb....bb: Table identifier

cc....cc: Table type

not audit: Non-audit trail table

audit: Audit trail table

S: Terminates processing.

Action

Specify an audit trail data registration UOC for audit trail tables, and then re-execute the command without specifying an audit trail data registration UOC for non-audit trail tables.

KFPL23204-E E+L

Invalid audit trail generation file status, file=aa....aa, generation=bbb

Because the previously executed data load of an audit trail file terminated abnormally, the data load log in the audit trail table does not match the status of the audit trail file.

aa....aa: Name of the audit trail file for which data loading was attempted

If the length of the file name exceeds 150 characters, the last 150 characters of the file name are output.

bbb: Invalid audit trail file generation number (last three characters of the audit trail file name)

S: Terminates processing.

O: Take one of the following actions:

If the facility for automatically loading audit trail table data is not being used:

In the param operand of the srcuoc control statement, specify only the audit trail file corresponding to the generation number (bbb) output in this message, and then execute data loading for the audit trail table.

Audit trail file data was not loaded because of abnormal termination; therefore, load that data into the audit trail table if it is necessary to do so.

Re-execute data loading on the audit trail file (aa....aa) on which loading was previously attempted.

If the facility for automatically loading audit trail table data is being used:

See Actions to take when an error occurs while the facility for automatic loading is being used, in the HiRDB Version 9 System Operation Guide.

KFPL23500-E E+L

RDAREA aa....aa bb....bb

RDAREA is in hold status (error shutdown, logless shutdown, reference-possible backup hold, or updatable backup hold), close status, frozen update status, or online reorganization hold status.

aa....aa: RDAREA name

bb....bb: Status of the RDAREA

held: Held

closed: Closed

freezed: Frozen

ORG: Online reorganization hold

S: Terminates processing.

O:

Other than online reorganization hold

RDAREA opening attribute set to INITIAL
Place the RDAREA in open, shutdown release, command shutdown, referrable shutdown, or frozen update release status and then re-execute the command.

RDAREA opening attribute set to DEFER or SCHEDULE
Release the RDAREA from shutdown status, place it in referencing-permitted shutdown status or frozen update release status, and then re-execute the command.

Online reorganization hold

Release online reorganization hold and re-execute the command.

KFPL24000-E E+L

Unable to specify configuration file

A column structure information file cannot be specified using a binary-format input data file.

S: Terminates processing.

O: Match the attribute of the input data column of the binary-format input data file with the attribute of the column data of the table so that a column structure information file need not be specified, then re-execute the command.

KFPL24001-E E+L

Unable to specify null-information file

A null value information file or a function information file cannot be specified for inputting a DAT-format input data file.

S: Terminates processing.

O: Specify the null value for inputting the DAT-format input data file, delete the specification for the null value information file or function information file, and then re-execute the command.

KFPL24100-E E+L

Unable to convert data, column=aa....aa

A data type of the input data file specified in the column structure information file cannot be converted to the data type of the data in column aa....aa of the table.

aa....aa: Column name

S: Terminates processing.

O: Correct any problems found in the data types specified in the column structure information file, and then re-execute the command.

KFPL24101-E E+L

Unable to specify filedir, column=aa....aa

The filedir operand cannot be specified in column aa....aa in the column structure information file due to one of the following reasons:

The column is not an XML-type column.

f is not specified in the -K option.

aa....aa: Column name

S: Terminates processing.

O:

If the column is not an XML-type column:

Delete the filedir operand.

If the column is an XML-type column:

If you specify a file path in order to load parameter attribute data from an individual file, specify f in the -K option.

If you are directly processing data from input data files, delete the filedir operand.

KFPL24102-E E+L

Unable to specify sequence,column="aa....aa"

The sequence generator cannot be specified in column aa....aa in the column structure information file for one of the following reasons:

Sequence generator data could not be converted to column data.

The specified column is a repetition column.

aa....aa: Column name

S: Terminates processing.

O: Specify a sequence generator in a column for which this specification is possible, and then re-execute the command.

KFPL24150-E E+L

No aa....aa on table

Neither table nor index was defined, but an index information file or work directory for sorting was specified. Or, LOB was not defined in the table, but information about a LOB input file or LOB middle file was specified.

aa....aa: One of the following:

index: Index information

LOB: LOB column

S: Terminates processing.

O: Delete unnecessary information from the control information file. Or, check the name of the table subject to processing for an error and re-execute the command.

KFPL24151-E E+L

Cannot omit aa....aa name

Name aa....aa cannot be omitted for a file for a table partitioned by values.

aa....aa: Missing name:

RDAREA: RDAREA name

server: Server name

S: Terminates processing.

O: Specify the name of the RDAREA or server that is to use the file or directory and re-execute the command.

KFPL24152-E E+L

Index aa....aa not found, table=bb....bb.cc....cc

Index aa....aa has not been defined for table bb....bb.cc....cc.

aa....aa: Index identifier (when name=* is specified in the idxname statement, *** is output when there is no target index in the table)

bb....bb: Authorization identifier

cc....cc: Table identifier

S: Terminates processing.

O: Correct the index name specified in the control information file and re-execute the command. When *** is output to the index identifier, check if an index exists in the table.

KFPL24153-E E+L

Index aa....aa not found in RDAREA bb....bb

Index aa....aa was not found in RDAREA bb....bb.

aa....aa: Index identifier

bb....bb: RDAREA name

S: Terminates processing.

O: Correct the RDAREA name specified in the control information file and re-execute the command.

KFPL24154-E E+L

Unnecessary aa....aa directory specified

A work file for index information or sorting was specified for a server for which no index has been defined.

aa....aa: Type of directory{ { index|sort work }

S: Terminates processing.

O: Correct the server name for the directory specified in the control information file and re-execute the command.

KFPL24155-E E+L

Function aa....aa."bb....bb" not found, column="cc....cc"

The function "bb....bb" cannot be found in the abstract data type of the column "cc....cc". Following are the possible causes of this problem:

The function specified in the column structure file (with the same name and parameter) is not defined.

The return value of the function specified in the column structure file is not the abstract data type of the column.

If you are using the XML type, the function specified in the column structure information file is not consistent with the value specified in the -G option.

aa....aa: Authorization identifier

bb....bb: Function name

cc....cc: Column name

S: Terminates processing.

O: Specify the correct function information in the column structure information file, and then re-execute the command. In addition, if you are using the XML type, specify the function corresponding to the value specified in the -G option in the column structure information file, as follows:

In the case of -G xml: the XMLPARSE function

In the case of -G esisb: the XML function

KFPL24156-E E+L

Required function not specified

The constructor function necessary for generating a value to be stored in a column of the abstract data type is not specified. Or, the constructor parameter reverse generation function for reverse-generating a data value of the abstract data type is not specified. Following are possible causes of this problem:

The indicated function is not one in which a constructor function is plug-in-implemented.

If a column structure information file was omitted, either a function with the same name as the data type name is not defined as an abstract data type, or multiple functions with the same name are defined.

A column of abstract data type for which a function is not defined has been found.

unld_func statement is not specified in the control information file.

S: Terminates processing.

O:

Specify in the column structure information file a plug-in-implemented constructor function that generates the values to be stored in a column of the abstract data type, and then re-execute the command.

Alternatively, specify a constructor parameter reverse generation function that reverse generates abstract data type data values to the control information file, and then re-execute the command.

KFPL24157-E E+L

Function aa....aa."bb....bb" not found, type=cc....cc,"dd....dd", kind=ee....ee

Function "bb....bb" specified by ee....ee is not defined in abstract data type "dd....dd".

aa....aa: Authorization identifier of the function

bb....bb: Function name

cc....cc: Authorization identifier of the abstract data type

dd....dd: Abstract data type name

ee....ee: Type:

{ unld_func|reld_func }

S: Terminates processing.

O: Specify the correct function by referring to the manual for the applicable plug-in of the abstract data type, and re-execute.

KFPL24158-E E+L

Specified type not found in this table, type=aa....aa."bb....bb"

Abstract data type aa....aa."bb....bb" specified by the type operand of the unld_func statement in the control information file is not defined in this table.

aa....aa: Authorization identifier of the abstract data type

bb....bb: Abstract data type name

S: Terminates processing.

O: Specify an abstract data type name defined in the table and re-execute.

KFPL24159-E E+L

Function_row missing in Control file, column="aa....aa"

An unld_func statement corresponding to the abstract data type defined in column "aa....aa" is not specified in the control information file.

aa....aa: Column name

S: Terminates processing.

O: Specify a constructor parameter reverse generation function in the unld_func statement in the control information file by referring to the manual for the plug-in that provides the abstract data type defined in the applicable column, and re-execute. If the constructor parameter reverse generation function is not implemented by the plug-in or if the -j option is specified, delete this option and re-execute.

KFPL24500-E E+L

Unable to continue pdload because of invalid aa....aa length, line=bb....bb

A negative value was detected in the length section for the length of variable-length data in the binary-format input data file or in an effective element count for a repetition column. Or, the length of the input data exceeded the area reserved by maxreclen.

aa....aa: Data type

{ VARCHAR|NVARCHAR|MVARCHAR|BINARY|BLOB|ARRAY }

bb....bb: Line number

S: Terminates processing.

O:

Determine whether an invalid length is specified in the length section for the length of variable-length data or in the effective element count storage area for a repetition column. Also determine whether there is an error in column data in the binary-format input file. If an error is found, correct the contents of the file and then re-execute the command.

Or, if the length of the input data is greater than the value specified by maxreclen, check the maximum length of the input data, specify a value greater than the maximum length in maxreclen, and then re-execute.

KFPL24509-E E+L

Insert error occurred, line=aa....aa

An error occurred during data storage processing for line aa....aa.

aa....aa: Line number

S: Terminates processing.

O: Correct the cause of the error by referring to the preceding error message and re-execute the command.

Note when re-executing:

If the KFPL15225-E message (rollback) is output concurrently with this message, re-execute from the first row. If the KFPL15225-E message is not output, specify the -r option, and then re-execute from the row output to this message.

KFPL24510-E E+L

Error data detected, process stopped, error code=aa

An error was detected in the input data during execution of the pdload utility. Processing is terminated.

aa: Logical error number

For logical error numbers and their descriptions, see the HiRDB Version 9 Command Reference.

S: Terminates processing.

O:

Data loading:
Correct the data in the row number indicated in the KFPL24509-E message that was displayed together with this message.
If a KFPL15225-E message is displayed, all database storage processing is cancelled (rolled back). Therefore, the command is re-executed to store data from the beginning of the input file. If this command was executed in the no-log mode, the database needs to be restored from its backup.
If a KFPL15225-E message is not displayed, the storage of the data immediately preceding the error was completed (committed); therefore, the command is re-executed to store the data at and following the revised data (by using the -r option).

File partitioning (creation of the partitioning input data file):
See the error message output to the error information file, correct the relevant data, and re-execute the command.

KFPL24990-E E+L

Only one aa....aa can be specified in Control file

aa....aa can be specified only once in a control information file.

aa....aa: Type:

source_row: source statement row

mtguide_row: mtguide statement row

emtdef_row: emtdef statement row

input_file: Input file

unload_file: Unload file

tblname_row: tblname row

lobmid_row: lobmid statement row

lobdata_row: lobdata statement row

idxname_row: idxname statement row

array_row: array statement row

option_row: option statement row

report_row: report statement row

blobtovarchar_row: blobtovarchar statement row

execstop_row: execstop statement row

extdat_row: extdat statement row

src_work_row: src_work statement row

fixtext_option_row: fixtext_option statement row

constraint_row: constraint statement row

S: Terminates processing.

O: Take one of the following actions, as appropriate to the displayed type:

If source_row, mtguide_row, emtdef_row, lobmid_row, lob_data_row, array_row, or blobtovarchar_row is displayed:
Change the source row, mtguide row, emtdef row, lobmid row, lobdata row, array row, or blobtovarchar row in the control information file to one row each, and then re-execute the command.

If input_file is displayed:
When specifying EasyMT information, specify only one input data file, and then re-execute the command.

If unload_file is displayed:
When specifying EasyMT information, specify only one unload data file, and then re-execute the command.

If idxname_row is displayed:
Delete all idxname statements except in rows in which (*) is specified in the name operand, and re-execute the command.

If tblname_row or fixtext_option_row is displayed:
Specify one tblname or fixtext_option statement and re-execute the command.

If option_row, report_row, execstop_row, extdat_row, src_work_row, or constraint_row is displayed:
Specify one option, report, execstop, extdat, src_work, or constraint_row statement in the control information file and re-execute the command.

KFPL24991-E E+L

Specified aa....aa conflicted with command line specification

Information specified in the control information file contradicts the information specified on the command line, as shown below:

Database load utility:

The srcuoc statement was specified when using a binary format file to load data into a table with an abstract data type column.

-f easymt was not specified on the command line, but EasyMT information or the validate operand was specified in the control statement.

-f easymt was specified on the command line, but file input by a UOC was specified in the control statement.

-k c was not specified on the command line, but the lobcolumn statement was specified.

The vv option was specified in the type option of the array statement for control statements even when a fixed-length data-format file was specified.

The fv option was specified in the type option of the array statement for control statements even when a DAT format file was specified.

The srcuoc statement was specified in the control statement even when -k d was specified on the command line.

The job operand was specified in the option statement in the control statement even when -l n, -k f, -k v, or -k c was specified on the command line.

nowait=yes was specified in the option statement when the -n option or -I s was not specified on the command line.

The extdat statement was specified, even though no DAT format file was specified.

The null_string operand was specified in the option statement, even though no DAT format file was specified.

The enclose_del operand was specified in the option statement for an input data file that is not in the fixed-size data format.

Although the -b option was specified on the command line, the src_work statement was specified (if a binary format input data file, the partitioning input data file cannot be created).

The srcendian operand was specified in the option statement in the control statement, even though, on the command line, -W and -b were not specified together or -U was not specified.

Two or more input data files were specified in the source statement in the control statement, even though -W, -b, and -w were all specified on the command line.

The host name of the utility special unit was specified in the source statement in the control statement, even though -W, -b, and -w were all specified on the command line.

An RDAREA name was specified in the source statement in the control statement, even though -W, -b, and -w were all specified on the command line.

The charset operand was specified in the option statement in the control statement, even though an extended DAT format or fixed-length data format file was not specified.

Database reorganization utility:

-f easymt was not specified on the command line, but EasyMT information was specified in the control statement.

-f hirdb was not specified on the command line, but the HiRDB file information was specified in the control statement.

-k reld was specified on the command line, but fileno=ADD was specified in the control statement.

-k reld -c dic was specified on the command line, but the tblname control statement was specified.

-k reld was specified on the command line, but the lobunld and tblname control statements were specified.

The idxname statement was specified in the control statement even when -k ixrc was not specified on the command line.

The job operand was specified in the option statement in the control statement even when -l n, -k unld, -k ixrc, -k ixor, -k ixmk, -c dic, or -t all (reorganization by schema) was specified on the command line.

The lobunld statement was specified, even though the -j option was specified in the command line.

Although -W extdat was specified on the command line, multiple unload file names were specified in the unload statement.

The unldenq operand is specified in the option statement, but -k unld is not specified in the command line.

The charset operand was specified in the option statement in the control statement, even though neither -W extdat or -W fixtext was specified on the command line.

Free page release utility or global buffer residence utility:

The idxname statement cannot be specified when the target resource is a table, when processing a dictionary table, or when processing at the schema level.

aa....aa: Type:

array_row: array statement

easymt_information: EasyMT information

emtdef_row: emtdef statement

extdat_row: extdat statement

fileno: File sequence number

hirdb_information: HiRDB file information

idxname_row: idxname statement

lobcolumn_row: lobcolumn statement

lobunld_row: lobunld statement

option_row(charset): option statement charset operand

option_row(enclose_del): option statement enclose_del operand

option_row(job): option statement job operand

option_row(nowait): option statement nowait operand

option_row(null_string): null_string operand in the option statement

option_row(srcendian): option statement srcendian operand

option_row(tblstatus): tblstatus operand in the option statement

option_row(unldenq): option statement unldenq operand

src_work_row: src_work statement

srcuoc_row: srcuoc statement

tblname_row: tblname statement

unload_row: unload statement

S: Terminates processing.

O:

aa....aa is array_row:

Specify either ff or fv if the input data file is a fixed-length data format file and re-execute the command. Or specify either ff or vv if the input data file is a DAT format file and re-execute the command.

aa....aa is easymt_information or emtdef_row:

EasyMT used:
Add the -f easymt specification to the command line and re-execute the command.

EasyMT not used:
Delete the EasyMT information from the source row, the validate operand, or the emtdef row from the control information file and re-execute the command.

aa....aa is extdat_row:

The extdat statement is valid only for DAT format files, so when processing fixed-size data format or binary format files, delete the extdat statement, and then re-execute.

aa....aa is fileno:

For -k reld specified, correct the specification of fileno=ADD and re-execute the command.

aa....aa is hirdb_information:

To use a HiRDB file system as the unload file, specify -f hirdb on the command line and re-execute the command. Otherwise, delete the HiRDB file information from the control file and re-execute the command.

aa....aa is idxname_row:

For the database reorganization utility:
To re-create indexes by index, specify -k ixrc and re-execute the command.

For the free page release utility or global buffer residence utility:
Specify the idxname statement when releasing a specific index, an RDAREA, or free pages on which only a server is using an index; or when reading data into the global buffer.

aa....aa is lobcolumn_row:

To use a LOB column input file, specify -k c on the command line and re-execute the command. Otherwise, delete the lobcolumn statement from the control file and re-execute the command.

aa....aa is lobunld_row(charset):

For the database load utility
Prepare the input data file in extended DAT format or fixed-length data format.

For the database reorganization utility
Specify the -W extdat or -W fixtext option on the command line.

aa....aa is option_row(enclose_del):

Specify the -a option when the input data file is a fixed-size data format file. For input data files in other formats, delete the enclose_del operand.

aa....aa is option_row(job):

For pdload
When the job operand is specified in the option statement, re-execute the command without specifying -l n, -k f, -k v, or -k c.

For pdrorg
When the job operand is specified in the option statement, re-execute the command without specifying -l n, -k unld, -k ixrc, -k ixor, -k ixmk, or -c dic.

aa....aa is option_row(nowait):

To execute a NOWAIT search concurrently with pdload, omit the -n option or specify -i s. If the NOWAIT search is not to be executed concurrently with pdload, specify nowait=no in the option statement.

aa....aa is option_row(null_string):

When the null_string operand is specified using the option statement, it is valid only when in the DAT format. For the binary format or fixed-size data format, delete the null_string operand of the option statement.

aa....aa is option_row(srcendian):

If the srcendian operand is specified in the option statement, specify both the -W and -b options, or the -U option, and then re-execute the command.

aa....aa is option_row(tblstatus):

The tblstatus operand in the option statement can be specified only with -k rorg. Therefore, either delete the tblstatus operand or change to -k rorg.

aa....aa is option_row (unldenq):

The unldenq operand of the option statement can be specified only with -k unld. Therefore, either delete the unldenq operand or change it to -k unld.

aa....aa is src_work_row:

If the input data file is composed of all columns in fixed length binary format, it is handled as a fixed length data format input data file, and a partitioning input data file can be created. If there are also variable length columns, consider either performing data loading in table units or partitioning the input data file.

aa....aa is srcuoc_row:

When -k d is specified
Change the specification so that UOC is not used.

When -W, -b, and -w are all specified
Change the source statement in the control statement as follows:
Only one input data file is specified
The host name of the utility special unit is not specified
The RDAREA name is not specified

aa....aa is tblname_row:

A dictionary table or a table in which a LOB column is defined cannot be reloaded to another table. Check the option on the command line or the tblname statement, correct it, then re-execute the command.

aa....aa is unload_row:

If extdat is specified in the -W option, specify a single unload file name and re-execute.

KFPL24992-E E+L

Specified aa....aa conflicted with Control file specification

One of the following contradictions was found in the control information file:

This is a multivolume file, but Mtguide is not to be used according to the specified information.

The mtguide or emtdef statement is not specified at the beginning of the control information file.

A control statement not necessary for creating a LOB column only is specified.

A UOC is declared, but the srcuoc or source statement is missing.

Processing in units of tables is specified for a table containing a LOB column, but an attempt was made to process the LOB column in units of RDAREAs.

A control statement is specified that is not needed for creation of the LOB column structure base table only. Or, a control statement needed for LOB creation is missing.

Because the input data file is a binary-format file, the specification of the array data format for a column of variable-length data type is invalid.

An idxname and an index statement are both specified.

An unld_func or reld_func statement is specified for an abstract data type with the LOB attribute even when the -j option is not specified.

The unld_func and reld_func statements are not specified as a pair even when -k rorg is specified.

The job operand of the option statement is specified at the same time as the lobunld statement.

An RDAREA name is specified in the source statement even when nowait=yes is specified in the option statement.

The lobunld statement was not specified when using a UOC (when the unld_uoc statement is specified).

(UOC) was specified in the unload statement when using a UOC (when the unld_uoc statement is not specified).

(uoc) or UOC information was specified in the unload statement when not using a UOC (when unld_uoc statement is not specified).

HiRDB information or EasyMT information was specified when (uoc) is specified in the unload statement.

Y was specified in the fixrow operand in the unld_uoc statement for a non-FIX table.

When creating the partitioning input data file (when the src_work statement is specified), the RDAREA name or the report statement is specified in the source statement. Or, the source statement is not specified.

aa....aa: Conflicting contents:

multi_volume: Volume names

mtguide_row: mtguide statement

emtdef_row: emtdef statement

srcuoc_row: srcuoc statement

idxwork_row: idxwork statement

index_row: index statement

sort_row: sort statement

lobmid_row: lobmid statement

source_row: source statement

lobcolumn_row: lobcolumn statement

array_row: array statement

idxname_row: idxname statement

func: unld_func or reld_func statement

option_row(job): option statement job operand

option_row(nowait): option statement nowait operand

lobunld_row: lobunld statement

unload_row(hirdb): HiRDB information in the unload statement

unload_row(EASYMT): EasyMT information in the unload statement

unld_uoc_row: fixrow in the unld_uoc statement

lobunld_row(uoc): (uoc) or UOC information in the unload statement

src_work_row: src_work statement

S: Terminates processing.

O: Take action appropriate to the displayed information and re-execute the command:

multi_volume:

To specify a multivolume, specify mtguide use.

mtguide_row or emtdef_row:

Specify the mtguide or emtdef statement after the source or unload statement.

srcuoc_row:

Specify the source statement or delete the srcuoc statement.

lobmid_row:

Delete the RDAREA name in the lobmid statement. Or, add the RDAREA name in the source statement.

source_row:

Specify the srcuoc statement. Alternatively, specify the file name in the source statement.

lobcolumn_row:

To create only a LOB column structure base table, delete the lobcolumn statement.

To create LOB data, add the lobdata statement.

array_row:

Revise the specification of the array data format.

idxname_row:

To re-create indexes by index-storage RDAREA, delete the idxname statement. To re-create indexes by index, delete the index statement.

In the case of pdreclaim and pdpgbfon, either limit operands to the name operand or avoid mixing an idxname statement that has a server operand specification with an idxname statement that has an rdarea operand specification.

func:

If the unld_func and reld_func statements are not specified as a pair in -k rorg, specify them as a pair.

To specify an unld_func or reld_func statement for an abstract data type with the LOB attribute, specify the -j option concurrently.

option_row(job):

To perform data loading or reloading with synchronization point setting specified, delete the lobunld statement.

option_row(nowait):

To execute a NOWAIT search concurrently with pdload, do not specify an RDAREA name in the source statement. If the NOWAIT search is not to be executed concurrently with pdload, specify nowait=no in the option statement.

lobunld_row:

When using UOC (when specifying the unlduoc statement), the lobunld statement cannot be specified, so delete it.

unload_row(uoc):

When not using UOC (when not specifying the unlduoc statement), delete the unload statement (uoc) or the UOC information.

lobunld_row(hirdb):

Delete the HiRDB information.

lobunld_row(ESAYMT):

Delete the EasyMT specification.

unld_uoc_row(fixrow):

Delete the fixrow specification.

src_work_row:

Delete the RDAREA name specification or the report statement from the source statement. Also, if the source statement is not specified, specify the source statement.

Other:

Delete all the control statements that are not related to LOB creation.

KFPL24993-E E+L

Invalid absolute pathname, file=aa....aa

The absolute path of file aa....aa exceeded the permitted maximum length of 1,023. This error may occur in the following cases:

The length of the absolute path exceeded the maximum value of 1,023, including the directory name for the LOB input file specified in the lobdata statement and the name of the LOB column input file specified in the lobcolumn statement in the control information file.

The absolute path of the LOB column input file specified in the lobcolumn statement of the control information file exceeded the maximum length of 1,023.

aa....aa: Name of LOB column input file specified in lobcolumn statement

If the length of the LOB input file name exceeds 150 characters, the last 150 characters of the LOB input file name are output.

S: Terminates processing.

O: Check the control information file for the directory name for the LOB input file specified in the lobdata statement and the name of the LOB column input file specified in the lobcolumn statement and correct any error. If the specified information is correct, move the LOB column input file to a location where the absolute path length does not exceed 1023, specify that absolute path in the control statement, then re-execute the command.

KFPL24999-E E+L

aa....aa invalid

The specified -u option value or the authorization identifier or password specified in an environment variable was invalid during utility execution. Or, the password entered as a response to an input request message was invalid.

aa....aa: Information resulting in the error:

Auth_id: Authorization identifier

Password: Password

S: Terminates processing.

O:

Auth_id displayed:
Check the -u option on the command line, or correct the PDUSER environment variable and re-execute the command.

Password displayed:
Correct the PDUSER environment variable and re-execute the command. Or, if the password was entered in response to the input request message, re-execute the command by entering the correct password.

Note on specifying an authorization identifier or a password (Windows edition only):
When omitting the -u option, make sure the character string specifying an authorization identifier or password in the command prompt is not enclosed in single quotation marks (').
Example of correct specification: -u "root"/"root"
When specifying an authorization identifier or password in a client environment definition (hirdb.ini), enclose it in single quotation marks (').
Example of correct specification: PDUSER='"root"/"root"'

KFPL25000-E E+L

Invalid format exists in command line

The format of the command line is invalid for the utility.

S: Terminates processing.

O: Correct the command line and re-execute the command.

KFPL25001-E E+L

Invalid attribute exists in command line

An invalid value for the utility was specified on the command line. This message is also displayed when an identifier that uses national characters is specified while the LANG environment variable is not set correctly.

S: Terminates processing.

O: Take one of the following actions:

In UNIX:

Correct the command line and re-execute the command

Use character codes of the type specified in the LANG environment variable in pdsetup and re-execute the command.

In Windows:

Revise the command line, and re-execute the command.

If the LANG environment variable is defined, remove the LANG environment variable and re-execute the command. To remove the LANG environment variable, execute the following command at the command prompt:
set LANG=

KFPL25002-E E+L

Inconsistent specification in command line

Mutually exclusive options were specified on the command line for the utility.

S: Terminates processing.

O: Correct the command line and re-execute the command.

KFPL25003-E E+L

Mandatory specification missing in command line

A required option was omitted from the command line for the utility.

S: Terminates processing.

O: Specify the required information on the command line and re-execute the command.

KFPL25004-E E+L

Invalid format exists in Control file, line=aa....aa

The format of line aa....aa in the control information file for the utility is invalid.

aa....aa: Line number of erroneous line

S: Terminates processing.

O: Correct the indicated line in the control information file and re-execute the command.

KFPL25005-E E+L

Invalid attribute exists in Control file, line=aa....aa

An invalid value was specified on line aa....aa in the control information file for the utility.

aa....aa: Line number of line containing invalid value

S: Terminates processing.

O: Correct the indicated line in the control information file and re-execute the command.

KFPL25006-E E+L

Mandatory specification missing in Control file, line=aa....aa

A required item was omitted from line aa....aa in the control information file for the utility.

aa....aa: Line number of erroneous line

S: Terminates processing.

O: Specify the required item on the indicated line in the control information file and re-execute the command.

KFPL25007-E E+L

Duplicate attribute aa....aa exists in Control file

aa....aa was duplicated in the control information file for the utility.

aa....aa: Duplicated information in the control information file

S: Terminates processing.

O: Correct the duplicated information in the control information file and re-execute the command.

KFPL25009-E E+L

Mandatory specification does not exist in Control file

A control statement required in a control information file for the database load utility (pdload) was not specified.

The source statement was not specified when data was loaded.

During LOB loading, either the lobmid or the lobdata statement was not specified.

S: Terminates processing.

O: In the control information file, specify the source, lobmid, or lobdata statement, and then re-execute the command.

KFPL25010-E E+L

HiRDB aa....aa interface error occurred, code=bb, file=cc....cc[, contents='dd....dd'x]

An interface error occurred between HiRDB Dataextractor, DataStage, or XDS and the database load utility (pdload). ", contents='dd....dd'x" is output only if code=2.

aa....aa: Function type

Dataextractor: HiRDB Dataextractor or DataStage

export: XDS

bb: Maintenance code

1:

The file specified by the file operand in the extractorinf clause is not FIFO.

2:

The content of the file specified by the file operand in the extractorinf clause is not COMPLETED (an error may also occur when there is a newline or other character after COMPLETED).

cc....cc: Maintenance information 1

The file name specified by the file operand in the extractorinf clause (if the length of the file name exceeds the maximum character length, only the end of the file name, up to the maximum number of characters, is output).

dd....dd: Maintenance information 2

This is the content (displayed in hexadecimal numbers) of the file specified by the file operand in the extractorinf clause. x is displayed when nothing is specified to the file.

S: Terminates processing.

O:

aa....aa is Dataextractor:

When an error occurs in the HiRDB Dataextractor or DataStage:
See the message output by HiRDB Dataextractor or DataStage, and then take appropriate action.

When HiRDB Dataextractor or DataStage was cancelled:
Ignore this message.

Other:
Contact the customer support center.

aa....aa is export:

This message is sometimes output under the circumstances listed below. If this is the case, you can safely ignore the message.

The XDS process was terminated by the pdxdsstop -f command or the pdstop -f command

The XDS process was terminated using the kill command or similar means

Database export terminated abnormally

The XDS process terminated abnormally

If the message is output in circumstances other than the above, contact the customer support center.

KFPL25011-E E+L

Invalid option specified in command line, option=aa

Invalid option aa is specified in the command line of a utility.

aa: Option name

If more than one invalid option is specified in the command line of a utility, the first invalid option is displayed.

S: Terminates processing.

O: Delete option aa or specify a valid option, and then re-execute the command.

The -K and -G options cannot be specified for tables with no XML-type columns defined. Delete these options.

KFPL25012-E E+L

Invalid option value specified in command line, option=aa

The value of option aa, specified in the command line of a utility, is invalid.

aa: Option name

S: Terminates processing.

O: Revise the value specified in option aa, and then re-execute the command.

KFPL25013-E E

Inconsistent specification in command line, option=aa, bb

The command line for a utility to be executed contains mutually exclusive options aa and bb.

aa: Option name

bb: Option name

S: Terminates processing.

O: Delete either option aa or option bb, and then re-execute the command.

-b and -K:

If a binary format file, or the pdload unload file output by pdrorg, is specified as the input data file, you cannot specify f in the -K option. Delete the -K option, or change it to match the format of the input data file.

-W and -G:

If a pdload unload file output by pdrorg is specified as the input file, you cannot specify xml in the -G option. Delete the -G option, or change it to match the format of the input data file.

KFPL25040-E E+L

Cannot allocate communication buffer, size=aaaaa, code=b

Communication buffer cannot be allocated.

aaaaa: Communication buffer size to be allocated

b: Reason code:

4: Area shortage

8: Protocol error

S: Terminates processing.

O: Take the following action:

In UNIX:

Wait until another process using a large amount of the user space terminates and re-execute the command.

If row partitioning among servers is performed and commands are executed by table, consider whether commands can be executed by RDAREA instead. The necessary buffer size is reduced to the reciprocal of the number of servers.

In Windows:

Wait until another process using a large amount of the user space terminates and re-execute the command.

If commands are executed by table, consider whether commands can be executed by RDAREA instead. The necessary buffer size is reduced to the reciprocal of the number of servers.

Action

Reduce the value of pd_utl_buff_size (length of communication buffer for utility) in the system common definition.

KFPL25100-E E+L

Column name missing in configuration file

No column name with the NOT NULL constraint has been specified in the column structure information file. Or, no column name has been specified.

S: Terminates processing.

O: Specify the required column names in the column structure information file and re-execute the command.

KFPL25101-E E+L

Invalid format existed in dataload file

The format of an input data file is invalid.

S: Terminates processing.

O: Correct the information in the input data file and re-execute the command.

KFPL25102-E E+L

Invalid attribute in configuration/null-information file, line=aaaaa

The column structure information file, null value information file, or function information file contains erroneous information.

aaaaa: Row number where erroneous information was detected

S: Terminates processing.

O: Correct the information in the column structure information file, null value information file, or function information file, and then re-execute the command.

KFPL25103-E E+L

Unable to specify reserved column to configuration/null-information file, file=aa....aa, line=bb....bb

A reserved column cannot be specified in a column structure information file, null value information file, or function information file.

aa....aa: Name of the erroneous column structure information file, null value information file, or function information file

If the length of the file name exceeds 130 characters, only the last 130 characters of the file name are output.

bb....bb: Line number where the reserved column is specified

S: Terminates processing.

O: Delete the specification of the reserved column from the column structure information file, null value information file, or function information file, and then re-execute the command. If data for the reserved column appears in the input file, delete the data as well.

KFPL25200-E E+L

Unable to get utility definition

The system common definition could not be read, so default values were assumed for the environment.

S: Resumes processing.

Action

Check the contents of the system common definition file the next time the default values are changed for the utility execution environment.

KFPL25210-E E+L

aa....aa must be executed at unit defined as manager

aa....aa should be executed at the unit where the system manager is defined.

aa....aa: Utility or command for which execution was attempted

pdload: Database Load Utility

pdrorg: Database reorganization utility (including pdreclaim and pdpgbfon)

COMMAND: Plug-in-provided command

pdrbal: Rebalancing utility

S: Terminates processing.

O: Log in the remote unit where the system manager (MGR) is defined and re-execute the command.

KFPL25211-E E+L

Cannot specify input file at manager

The server specified for an input data file was not any of the following:

Front-end server

Back-end server

Dictionary server

S: Terminates processing.

O: Change the location of the input data file and re-execute the command.

KFPL25212-E E+L

Default value length too long, column="aa....aa"

Because the column name statement in the column structure information file was omitted, the default was specified for storage in column "aa....aa", but the default could not be stored because the default is longer than the applicable column.

aa....aa: Column name

S: Terminates processing.

O: Either specify the column name statement of the column structure information file or change the length of the applicable column in the table definition so the default can be stored, and then re-execute.

KFPL25213-E E+L

Unable to execute aa....aa command due to check pending status, table=bb....bb."cc....cc"

Utility aa....aa cannot be executed because table bb....bb."cc....cc" is in check pending status.

aa....aa: Utility name

bb....bb: Authorization identifier

cc....cc: Table identifier

S: Terminates processing.

Action

Execute the integrity check utility to confirm that there is no row data with a constraint violation. After the check pending status of the table is released, re-execute the utility.

KFPL25214-E E+L

Unable to get sequence number,sequence=aa....aa."bb....bb"

It is not possible to acquire the sequence number of the sequence generator aa....aa."bb....bb" for the following reason:

An attempt was made to acquire a sequence number from a sequence generator, but the range in which acquisition is possible was exceeded.

aa....aa: Sequence generator authorization identifier

bb....bb: Sequence generator identifier

S: Terminates processing.

O: Use the database condition analysis utility to reference the current value of the sequence generator, and check the sequence generator definition. Then take corrective action, such as by changing the acquisition range or cycle specifications of the sequence number, and re-execute.

KFPL25222-W E+L

Unable to output aa....aa file, reason=bb....bb

An input data error was detected. However, data cannot be output to the error information file or the partitioning input data file for the reasons indicated in bb....bb.
Regardless of how many times data could not be output to the error data file or the partitioning input data file, the message is output only once.

aa....aa: File type

error data: Error data file

error information: Error information file

divided: Partitioning input data file

bb....bb: Reason code

ROW LENGTH:

The row length of the error data exceeds 32 KB or it exceeds the value specified in the maxreclen operand of the source statement.

UNIQUE_ERROR:

Although a duplicate key value error was detected in the index for which unique key or primary key was specified, a shortage of error data file edit buffers occurred.

PLUGIN_ERROR:

Although an error was detected by a plug-in supplied function, an error data file edit buffer shortage occurred.

INSUFFICIENT MEMORY:

The area for editing the dump image list to be output to the error information file could not be allocated due to a memory shortage.

S: Resumes processing.

O:

Error data file:

Although some data was output to the error information file, other data was not output to the error data file. Therefore, search the relevant data not from the error data file but from the input data file, and correct it.

If the buffer size is insufficient, for the next data loading, specify a sufficiently large error data file edit buffer size in the errwork operand. Even if the error is detected, the data is output to the error data file.

Error information file:

Because a dump image list is not output to the error information file, refer to the error message that is output to the error information file, retrieve the applicable error data from the input data file, and revise the data.

Partitioning input data file:

Specify the maximum row length in the maxreclen operand, and re-execute.

KFPL25225-E E+L

Incompatible file format, file=aa....aa

The aa....aa file was output in a prior version, so it is not compatible.

aa....aa: File name

If the file name exceeds the maximum character length, then the maximum number of characters are output as counted from the end of the file name.

S: Terminates processing.

Action

Action during importing (pdload):

Because the table transfer unload file is not backwards compatible, a table cannot be transferred during export and import.

Transfer the table using a different means, such as the database reorganization utility and database load utility.

KFPL25226-E E+L

Error occurred in aa....aa library function call, reason=bb....bb, inf=cc....cc

An error occurred in the processing of a compression library function call.
If this message is displayed during the execution of a command provided by a plug-in, the message is output only to the indicated output device type (L).

aa....aa: Processing type

compressed: Compression

bb....bb: Reason for error

LIBRARY LOAD FAILURE:
The compression library failed to load.

INSUFFICIENT MEMORY:
A memory shortage occurred during processing of the data compression function.

cc....cc: When the reason for error is LIBRARY LOAD FAILURE, "********" is displayed.

When the reason for error is INSUFFICIENT MEMORY, it displays the size of the area that was to be allocated (in bytes). If the size of the area cannot be determined, "********" is displayed.

S: Terminates processing.

O:

If bb....bb is LIBRARY LOAD FAILURE:

Ask the HiRDB administrator whether your environment is configured to use the data compression function.

If bb....bb is INSUFFICIENT MEMORY:

Re-execute. If this error occurs again, contact the HiRDB administrator.

Action

If bb....bb is LIBRARY LOAD FAILURE:

Check whether the compression library has been installed correctly.

If bb....bb is INSUFFICIENT MEMORY:

Reduce the number of concurrently executing processes to ensure that sufficient memory is available.

KFPL25338-E E+L

Invalid RDAREA id found in unload file, RDAREA id=aa....aa, file=bb....bb

The RDAREA for storing the unloaded rows is different from the RDAREA for storing the rows to be reloaded.

aa....aa: Name of unloaded RDAREA

bb....bb: Name of unload data file

If the length of the unload data file name exceeds 143 characters, the last 143 characters of the unload data file name are output.

S: Terminates processing.

O:

RDAREA name specified in the -r option:

Specify the unload data file containing the rows of the corresponding RDAREA and re-execute the command.

-r option omitted:

Specify the correct unload data file and re-execute the command. Or, restore the corresponding table, specify reorganization processing (-k rorg), then re-execute the command.

-g option specified:

Because row data that cannot be stored is in the unload file, refer to the table definition before change, add to the partitioning condition an RDAREA in which rows can be stored, and change the table definition. Then specify reload processing (-k reld) and re-execute the command.

KFPL25339-E E+L

Unable to get aa....aa information from unload file, file=bb....bb

Information aa....aa is not found in the unload data file. Therefore, the data cannot be reloaded.

aa....aa: Type of information:

column: Column information

dictionary: Dictionary information

divide: Partitioning information

hash: Hash partitioning information

index: Index information

index rdarea: Information about index storage RDAREA

LOB: LOB information

ADT: Abstract data type

multidim: Matrix partitioning information

bb....bb: Name of unload data file

If the length of the unload data file name exceeds 148 characters, the last 148 characters of the unload data file name are output.

S: Terminates processing.

O: Refer to the message in the message log file that was output before this message to eliminate the cause of the error, then re-execute the command.

KFPL25340-E E+L

aa....aa information not exists on unload file, file=bb....bb

Because information aa....aa was not found in the unload data file, data cannot be reloaded.

aa....aa: Type of information:

Column: Column information

Dictionary: Dictionary information

Divide: Partitioning information

Hash: Hash partitioning information

Index: Index information

Index rdarea: Information about index storage RDAREA

LOB: LOB information

ADT: Abstract data type

multidim: Matrix partitioning information

bb....bb: Name of unload data file

If the length of the unload data file name exceeds 150 characters, the last 150 characters of the unload data file name are output.

S: Terminates processing.

O: Specify the correct unload data file and re-execute the command.

KFPL25341-E E+L

aa....aa lock request failed, id=bb....bb

Locking resource aa....aa failed.

aa....aa: Name of resource

bb....bb: Resource ID

S: Terminates processing.

O: Re-execute the command after the user processing currently occupying the corresponding resource has terminated.

KFPL25342-E L

Invalid EOF found in unload file, file=aa....aa

Indicated unload data file is invalid.

aa....aa: Name of unload data file

If the length of the unload data file name exceeds 150 characters, the last 150 characters of the unload data file name are output.

S: Terminates processing.

O: Specify the correct unload data file and re-execute the command.

KFPL25343-E E+L

Different column information in unload file, table=aa....aa.bb....bb

Because the table definition in the unload data file is different from the table definition in the table to be reloaded, the table cannot be reloaded.

aa....aa: Authorization identifier

bb....bb: Table identifier

S: Terminates processing.

O: Unload the corresponding table (-k unld) and re-execute the command. Or, reorganize the database (-k rorg).

KFPL25344-E L

Insufficient index file, index=aa....aa.bb....bb

Specified index information files are not sufficient for index aa....aa.bb....bb.

aa....aa: Authorization identifier

bb....bb: Index identifier

S: Terminates processing.

O: Specify the remaining index information files and re-execute the command.

KFPL25347-E E+L

No specified aa....aa in Control file

No unload data file, LOB data unload file, or index information file was specified. Or, no LOB column input file was specified for a LOB column that was specified in the input data file for the LOB column structure base table.

aa....aa: Type of required file:

{ index (index information file)

| unload (unload data file)

| unload (lobunld) (unload data file or LOB data unload file)

| lobcolumn (LOB column input file) }

S: Terminates processing.

O: Take one of the following actions:

Specify an unload data file, LOB data unload file, or index information file and re-execute the command.

Specify all the LOB column input files for the LOB columns that were specified in the input data file for the LOB column structure base table.

To re-create the index (-k ixrc), specify an idxname or index statement and re-execute the command.

KFPL25352-E E+L

Insufficient unload file, table=aa....aa.bb....bb, server=cc....cc

No unload data file was specified for server cc....cc.

aa....aa: Authorization identifier

bb....bb: Table identifier

cc....cc: Server name

S: Terminates processing.

O: Specify an unload data file and re-execute the command.

KFPL25353-E E+L

Incompatible byte order between unload and reload system

Reloading cannot be executed because the byte order of the unloaded system differs from the byte order of the system to be reloaded.

S: Terminates processing.

O: Unload/reload objects between systems that support the same byte order.

KFPL25354-E E+L

Incompatible character code set, HiRDB=aa....aa, unload file=bb....bb

The character codes of the unload file do not match the character codes of the reload destination HiRDB.
The character code type of the table transfer unload file does not match the character code type of the import destination HiRDB.

aa....aa: HiRDB character code type:

CHINESE: EUC Chinese kanji codes

LANG-C: One-byte character codes

SJIS: Shift JIS codes

UJIS: EUC Japanese kanji code

UTF-8: Unicode (UTF-8)

bb....bb: Character code type for the unload data file:

CHINESE: EUC Chinese kanji codes

LANG-C: One-byte character codes

SJIS: Shift JIS codes

UJIS: EUC Japanese kanji code

UTF-8: Unicode (UTF-8)

S: Terminates processing.

O: Unload and reload objects only between systems that support the same character code types.

Also, import and export only between systems that support the same character code types. However, note that during import, if -w csetnck is specified in the pdload option, the table data in the table transfer unload file will be stored in the database as-is, so the values of the stored table data cannot be guaranteed.

KFPL25355-E E+L

More than aa....aa bytes in bb....bb

The row length exceeds the maximum length after conversion to DAT format or fixed length data format.

aa....aa: Maximum length

bb....bb: Row length

S: Terminates processing.

Action

If necessary, change the format specification to binary format (-W bin) and re-execute.

KFPL25356-E E+L

Incompatible unload file version

The specified unload data file cannot be used because the version differs from that of the current HiRDB.

S: Terminates processing.

O: Check that the correct unload data file is specified. If the wrong unload data file is specified, specify the correct unload file and re-execute.

Action

The specified unload data file cannot be reloaded because it was created by a version of HiRDB that is older than the current HiRDB version. If necessary, specify an unload data file that was output by the current HiRDB version and re-execute.

KFPL25357-E E+L

Invalid LOB data, RDAREA="aa....aa"

LOB data is invalid.

aa....aa: LOB storage RDAREA name

S: Terminates processing.

O:

For pdrorg:

During execution in table units:
Reinitialize the LOB data storage RDAREA defined for the table to be processed, specify only lobunld in the control statement, then reload the data in table units.

During execution in RDAREA units:
Reinitialize the output LOB RDAREA, specify only lobunld in the control statement, then reload the data in RDAREA units.

For pdload:

In creation mode:
Reinitialize the LOB RDAREA to be processed and load the LOB data. The RDAREA to be reinitialize is the same as for pdrorg.

In add mode:
Back up the table and LOB RDAREA and reload the data. Do not update the table and LOB RDAREA with the UAP until they have been backed up.

KFPL25358-E E+L

Invalid LOB data, RDAREA=aa....aa, line=bb....bb

Row bb....bb of LOB data could not be stored in user LOB RDAREA aa....aa.
Possible reasons:

Another attempt to load data into a LOB column was made even though data loading to the LOB column is complete.

An attempt to load data (including reloading) was made to a user LOB RDAREA that is in DB disrupted status.

aa....aa: User LOB RDAREA name

bb....bb: Number of rows in which errors were detected

S: Terminates processing.

O:

Correct the user LOB RDAREA name or the LOB middle file name, and then re-execute.

Restore the user RDAREA or user LOB RDAREA from the stored backup, and then re-execute.

KFPL25359-E E+L

Unable to reload table or unload file due to aa....aa defined

A row cannot be re-registered in another table because a LOB column is defined in that table or in the table in the unload data file.

aa....aa: LOB column

S: Terminates processing.

O: An unloaded table or row cannot be re-registered in a table in which a LOB column is defined. Create another table with the database load utility or a UAP.

KFPL25360-E E+L

aa option not specified when bb option specified

Option bb is specified, but no option aa is specified.

aa: Option name

bb: Option name

S: Terminates processing.

O: Check the combination of options, and then re-execute the command.

KFPL25361-E E+L

Lock time out error occurred, RDAREA=aa....aa

A lock wait timeout occurred during lock processing on RDAREA aa....aa.

aa....aa: Name of the RDAREA subject to lock processing

S: Terminates processing.

O:

Wait until the processing using the RDAREA terminates, and then re-execute the command.

Either increase the value specified with the -w option (increasing lock wait time) or increase the value specified with the -n option (increasing the retry count), and then re-execute the command.

KFPL25700-I L+S

UOC information, message=aa....aa, code=bb

A message output request was received from the UOC.

aa....aa: Output message requested from UOC

bb: UOC's return code

S: If UOC's return code is 4, resumes processing; otherwise, terminates processing.

O: If processing was cancelled, check the message output by the UOC, eliminate the cause of the error, then re-execute the command.

KFPL25710-E E+L

Invalid value in UOC interface area, code=aa, line=bb....bb

Invalid value was set by UOC in the UOC interface area.

aa: Error detail code:

10: The address of the data edited by the UOC was not set.

20: For a binary input data file, the length of the data edited by the UOC did not match the table definition. For an extended DAT format input data file, the length of data edited by the UOC is set to a negative value.

30: No return code or an invalid return code was set by the UOC.

40: Data was updated beyond the data length in the input buffer used to store data input from the utility. Or, the UOC interface area was damaged.

50: There was no linefeed character at the end of the DAT-format input data file. In the case of a binary input data file with -W specified that is output by the database reorganization utility, the input data contains BLOB data.

51: The variable length character string type or large object data type is invalid.

52: The sign part of the packed format data is invalid.

53: The packed data value or specified range of packed data in the packed format is invalid.

54: The actual length of the repetition column does not match the returned data.

55: The number of times the repetition column is repeated is invalid.

56: The null value flag of the repetition column is invalid.

57: The null value setting in a NOT NULL column is invalid.

60: The value of the store flag is invalid.

70: The parameter of the audit trail data registration UOC is invalid.

bb....bb: Number of row where the error occurred

This is the state when the row number is 0, an error occurs during the UOC start process and no lines were processed.

S: Terminates processing. However, abnormally terminates processing when the error detail code is 40.

O: Reevaluate the content set in the UOC interface area, correct the program, and then re-execute the command.

KFPL25999-W E+L

Unable to make an entry SQL_DB_MANAGEMENT, RDID=aa....aa, reason=bb....bb

The result of condition analysis could not be registered in the database management table. Therefore, if only one table or one index is stored in the RDAREA with RDAREA ID aa....aa,# an error may occur in the RDAREA estimated obsolescence time prediction shown by the facility for predicting reorganization time (the obsolescence prediction time is late).
If multiple RDAREAs are to be processed, a message is output only for the first RDAREA where an error was detected.
#: If multiple tables or indexes are stored in a single RDAREA, the RDAREA estimated obsolescence time prediction cannot reference the database management table because, even if some of the tables or indexes in the RDAREA are reorganized, not all of the RDAREA is reorganized, so it is not reflected in the prediction.

aa....aa: RDAREA ID

bb....bb: Error cause

MEMORY: Insufficient memory.

CONNECT: HiRDB connection failed.

ACCESS: Database management table could not be accessed.

HOLD: Access not possible due to command hold.

SQL_ERR: Database management table could not be modified.

MESSAGE_SEND: Communication error.

S: Continues processing.

O:

See the error message# that was output before this message and eliminate the cause of the error, then re-execute pddbst. Then, when the result of pddbst execution is reflected in the database management table and the facility for predicting reorganization time is executed, the prediction precision increases. If multiple tables or indexes are defined in a single RDAREA, re-execution is not necessary. Also, even without re-execution, the prediction error can be minimized by executing the condition analysis results depository facility every day.

If the RDAREA estimated obsolescence time prediction is already displayed and most of the reorganization time can be divided, determine the prediction time to be that already displayed in the RDAREA estimated obsolescence time prediction of the previous several days.

#: With KFPA11204-E, the data dictionary RDAREA that stores the analysis information table and the database management table must be created using pdmod.

KFPL26339-E E+L

Unable to get aa....aa information from lobmid file, file=bb....bb

aa....aa information cannot be acquired from the LOB middle file.

aa....aa: Information type:

column: Column information

LOB: LOB information

bb....bb: LOB middle file name

If the length of the LOB intermediate file name exceeds 150 characters, the last 150 characters of the LOB intermediate file name are output.

S: Terminates processing.

O: Referring to the error message that was output before this message, eliminate the cause of the error, and then re-execute the command.

KFPL26340-E E+L

aa....aa information not exists on lobmid file, file=bb....bb

LOB column data cannot be loaded because aa....aa information does not exist in the LOB middle file.

aa....aa: Information type:

Column: Column information

LOB: LOB information

bb....bb: LOB middle file name

If the length of the LOB intermediate file name exceeds 150 characters, the last 150 characters of the LOB intermediate file name are output.

S: Terminates processing.

O: Specify the correct LOB middle file and re-execute the command.

KFPL26342-E E+L

Invalid EOF found in lobmid file, file=aa....aa

LOB middle file is invalid.

aa....aa: LOB middle file name

If the length of the LOB intermediate file name exceeds 150 characters, the last 150 characters of the LOB intermediate file name are output.

S: Terminates processing.

O: Specify the correct LOB middle file and re-execute the command.

KFPL27100-E E+L

Unable to get UOC aa....aa information, name=bb....bb, errno=ccc

The system was unable to obtain the following UOC information:

library: UOC storage library

function: UOC function

aa....aa: Type of UOC information:

library: Shared library name

function: Function name

bb....bb: Name of UOC information

ccc: Error number set in errno

S: Terminates processing.

O: Check errno.h and the OS manual for the details of errno (external integer variable indicating the error status) To determine the cause of the error and correct the name specified in the control information file. Or, check the specified library to make sure that it is a shared library and that access permission has been granted, then re-execute the command. If errno = 0, correct the error by referring to the KFPL22001-E message that was output immediately before this message, and re-execute the command.

KFPL27500-E L

aa....aa wait time over,bbbbb=cc....cc."dd....dd",RDAREA=ee....ee

During processing to release free pages, processing was canceled because the time spent waiting for the transaction to finish, or the time spent waiting for a search using holdable cursor to execute, exceeded the waiting time specified in the -w option.

aa....aa: {Transaction|Cursor close}

bbbbb: {INDEX|TABLE}

cc....cc: Authorization identifier of the index or table

dd....dd: {index identifier|table identifier}

ee....ee: RDAREA name

S: Terminates processing.

O: If you want to continue to release free pages, take the following actions, and then re-execute pdreclaim.

If aa....aa is Transaction:

Take either of the following actions:

Wait for the UAP of the large object transaction to terminate, and then retry the operation.

Re-execute with a longer waiting time specified in the -w option.

If aa....aa is Cursor close:

Take either of the following actions:

Close the holdable cursor that has been open for the longest time, terminate the transaction, and then retry the operation.

Re-execute with a longer waiting time specified in the -w option.

KFPL28000-E E+L

Internal error occurred, code=aaa(bb....bb)

An internal error occurred.

aaa: Maintenance code (the following table shows maintenance codes and their meanings)

bb....bb: Maintenance information (the following table shows maintenance information)

S: Terminates processing.

O: Execute this command using the version of HiRDB assumed by the plug-in provided by the command or a newer version.

Because the HiRDB version does not match the version assumed by the plug-in, upgrade the HiRDB version. If the versions match, contact the customer support center.

Following is a list of maintenance codes and maintenance information:

Maintenance code
Explanation
Maintenance information

1
Invalid execution command line format
--

2
Required option not specified in execution command line
--

100
Duplicate control statements, shown in maintenance information, in control information file
Control statement

101
Plug-in type (index statement) not specified in control information file
--

102
Conflicting plug-in type (index statement) specifications in control information file
--

104
Invalid type format for error row number, shown in maintenance information, specified in control information file
Information type and error row number:

Information type:
library_name: Library name
function_name: Function name
option_string: Option character string
mode_kind: Mode type
lock_kind: Lock type
table_access_kind: Table access type

105
Number of modecheck statements in the control information file greater than the maximum limit
--

107
Invalid error row number format, shown in maintenance information in control information file
Error-causing row number

108
Required items (func statement and func_type statement) not found in control information file
--

109
Input error on control information file shown in maintenance information
Name of control information file

200
Specified external routine name not registered

Detail code:

1: Library name

2: Plug-in function

201
Not a utility timing
Timing code for specified external routine

--: Not applicable

KFPL28002-E E+L

Invalid HiRDB connect aa....aa

Either the environment variable PDUSER is not specified, or the authorization identifier or the password specified in the environment variable PDUSER is invalid.

aa....aa: Error type

user_id: HiRDB connection authorization identifier

password: HiRDB connection password

S: Terminates processing.

O:

Correct the contents of the environment variable PDUSER and re-execute the command.

Correct specification: PDUSER="root"/"root"

When specifying an authorization identifier or password in a client environment definition (hirdb.ini), enclose it in single quotation marks (').

Example of correct specification: PDUSER='"root"/"root"'

KFPL28101-E E+L

Table aa....aa."bb....bb" not found

The table to be processed, aa....aa."bb....bb", is not found.

aa....aa: Authorization identifier

bb....bb: Table identifier

S: Terminates processing.

O: Review and revise the authorization identifier and the table identifier for the table to be processed and re-execute the command.

KFPL28102-E E+L

Index aa....aa."bb....bb" not found

The index to be processed, aa....aa."bb....bb", is not found.

aa....aa: Authorization identifier

bb....bb: Index identifier

S: Terminates processing.

O: Review and revise the authorization identifier and the index identifier for the index to be processed and re-execute the command.

KFPL28103-E E+L

Column "aa....aa" not found in table bb....bb."cc....cc"

The column name "aa....aa" is not found in the table bb....bb."cc....cc".

aa....aa: Column name

bb....bb: Authorization identifier

cc....cc: Table identifier

S: Terminates processing.

O: Correct the column name and re-execute the command.

KFPL28104-E E+L

Privilege not satisfy

The command cannot be executed because the user does not have the requisite privilege.

S: Terminates processing.

O: Check if the current privilege is valid. If it is invalid, change it, and re-execute the command. If the current privilege is the valid one, ask the HiRDB administrator or the owner of the table to grant the privilege for the indicated table, and then re-execute the command.

Action

If a programmer asks to be granted a privilege and his or her request is proper, the requested privilege should be assigned.

KFPL28105-E E+L

Column "aa....aa" not ADT

The column name "aa....aa" is not an abstract data type (ADT).

aa....aa: Column name

S: Terminates processing.

O: Specify a column of abstract data type and re-execute the command.

KFPL28108-E E+L

PLUGIN not defined in column "aa....aa"

A plug-in is not defined for the specified column name "aa....aa".

aa....aa: Column name

S: Terminates processing.

O: Change the type of the column to a type defined by a plug-in and re-execute the command.

KFPL28109-E E+L

PLUGIN not defined in index "aa....aa"

The index "aa....aa" is not a plug-in index.

aa....aa: Index identifier

S: Terminates processing.

O: Change the name of the index to be executed to a plug-in index name and re-execute the command.

KFPL28900-I L

Pdplgexe started, generation=aa

Execution of the Plug-in Execution Utility (pdplgexe) has started.
generation=aa is displayed when using the inner replica facility.

aa: Generation number

S: Resumes processing.

KFPL28901-I L

Pdplgexe terminated, return code=aa

Execution of the Plug-in Execution Utility (pdplgexe) has terminated.

aa: Return code

0: Normal termination

8: An error occurred in the plug-in function

12: An error occurred in a function other than the plug-in function

S: Terminates processing.

O: For a non-0 return code, correct the cause of the error by referring to the error message that was output to either standard output device or the message log file and re-execute the command.

KFPL28904-I L+S

Transaction commit

The transaction was committed.

S: Resumes processing.

KFPL28905-E E+L

Transaction rollback

The transaction was rolled back due to the reason indicated in the message log file that was output prior to this message.

S: Terminates processing.

O: Correct the cause of the roll back by reviewing the message log file that was output prior to this message.

KFPL30000-I R

aa....aa name=bb....bb

Displays the beginning of the message for the data that was to be inserted in RDAREA bb....bb.

aa....aa:

Server: Server name

RDAREA: RDAREA name

bb....bb: Identifier

S: Outputs the information message to the error information file and terminates processing.

KFPL30001-I R

Rows successfully loaded=aa....aa

aa....aa rows of data were loaded successfully.

aa....aa: Number of rows

S: Outputs the information message to the error information file and terminates processing.

KFPL30002-I R

aa....aa rows outputed, RDAREA=bb....bb

Data stored in RDAREA bb....bb yields aa....aa rows output.

aa....aa: Row count

bb....bb: RDAREA name

S: Outputs an information message to the error information file and terminates processing.

KFPL31001-E R

Invalid input data byte, line=aa....aa, column=bb....bb[, element=cc....cc]

The input data length indicated by line=aa....aa, column=bb....bb (element cc....cc for a repetition column if element= is output) is invalid.

aa....aa: Line number

bb....bb: Column number

Because this indicates the position from the beginning of the data in the input data file, the displayed value includes columns and constructor function arguments that are designated for skipping by the skipdata statement.

cc....cc: Element number

S: Outputs the error message to the error information file.

O: Correct the data on the indicated line of the input data file.

KFPL31002-E R

Invalid pack format value, line=aa....aa, column=bb....bb[, element=cc....cc]

The packed format data indicated by line=aa....aa, column=bb....bb (element cc....cc for a repetition column if element= is output) is invalid.

aa....aa: Line number

bb....bb: Column number

Because this indicates the position from the beginning of the data in the input data file, the displayed value includes columns and constructor function arguments that are designated for skipping by the skipdata statement.

cc....cc: Element number

S: Outputs an error message to the error information file.

O: Correct the packed format data of the indicated line number in the input data file.

KFPL31003-E R

Invalid varchar length, line=aa....aa, column=bb....bb[, element=cc....cc]

The length of the variable-length data (VARCHAR, NVARCHAR, MVARCHAR, BINARY) indicated by line=aa....aa, column=bb....bb (if element is output, repetition column element cc....cc) exceeds the column definition length used during table definition; or the -z option is omitted when storing variable-length data with a zero length.

aa....aa: Line number

bb....bb: Column number

Because this indicates the position from the beginning of the data in the input data file, the displayed value includes columns and constructor function arguments that are designated for skipping by the skipdata statement.

cc....cc: Element number

S: Outputs an error message to the error information file.

O: Correct the data of the indicated line number in the input data file.

KFPL31004-E R

Data conversion error occurred, line=aa....aa, column=bb....bb[, element=cc....cc]

An error occurred during the conversion processing of the input data indicated by line=aa....aa, column=bb....bb (element cc....cc for a repetition column if element= is output).
Consider the following causes:

The data in the input file is incorrect.

The specification of the charset operand of the option control statement does not match the character encoding of the input data file.

aa....aa: Line number

bb....bb: Column number

Because this indicates the position from the beginning of the data in the input data file, the displayed value includes columns and constructor function arguments that are designated for skipping by the skipdata statement.

cc....cc: Element number

S: Outputs an error message to the error information file.

P: Correct the data on the indicated line number in the input data file. Alternatively, revise the specification of the charset operand of the option control statement.

KFPL31005-E R

Number of columns in input file not equal to table columns, line=aa....aa

The number of input data rows at line aa....aa does not match the number of rows to be stored.

aa....aa: Line number

S: Outputs the error message to the error information file.

P: Correct the data of the relevant row number in the input data file.

If the data includes (00)₁₆, this appears as a space when viewed in a text editor, so that the data can be viewed correctly. However, HiRDB considers (00)₁₆ to represent the end of data, and it may handle it as a column count mismatch. Check the data contents using a binary editor.

If the data loading target is a FIX table in which a reserved column has been defined, and there is reserved column data in the input data file, delete the reserved column data from the input data file.

KFPL31006-E R

Invalid null value, line=aa....aa, column=bb....bb

Invalid null value was specified for the input data on line aa....aa, column bb....bb.

aa....aa: Line number

bb....bb: Column number

Because this indicates the position from the beginning of the data in the input data file, the displayed value includes columns and constructor function arguments that are designated for skipping by the skipdata statement.

S: Outputs the error message to the error information file.

O: Correct the data on the indicated line of the input data file.

KFPL31007-E R

Invalid input record for cluster key sequence, line=aa....aa

The input records at line aa....aa are not sorted in order of cluster key values.

aa....aa: Line number

S: Outputs the error message to the error information file.

O: Correct the data on the indicated line of the input data file.

If it is difficult to rearrange the data in cluster key order, the data can be stored without checking the order by specifying the -x option. However, with this storage method, there is no cluster key benefit.

KFPL31008-E R

Key duplication error occurred, line=aa....aa[bb....bb]

The input data key values in line=aa....aa are duplicate. If the message No output for error data is displayed, the work buffer for the creation of an error data file is too small.

aa....aa: Line number

bb....bb: (No output for error data)

S: Resumes processing after outputting an error message to the error information file.

O: Correct the data associated with the indicated line number in the input data file and re-execute the command. If a message No output for error data is output, error data is not output to the error data file. This problem can be resolved by specifying a large enough size for the work buffer for the creation of an error data file and by re-executing the command.

KFPL31009-E R

Invalid partitioning key value, line=aa....aa

Input data contains a column value at line aa....aa that does not satisfy the partitioning storage condition for a table to be created.

aa....aa: Line number

S: Outputs the error message to the error information file.

O: Correct the data on the indicated line of the input data file.

KFPL31010-E R

Invalid row length, line=aa....aa

The length is invalid of the row data in row number aa....aa in the input file.

Binary-format file:
The row length or column offset is invalid in the binary-format file output by pdrorg.

Fixed-size data format file:
Data cannot be input at the row length specified in the column structure information file.

aa....aa: Row number

S: Outputs the error message to the error information file and terminates processing.

O:

Binary-format file:
Correct the row length or column offset in the row data.

Fixed-size data format file:
Correct the column structure information file so that the column information matches the input data length.

In either file format, the intended file may not be specified as the input file; in such a case, specify the correct file and re-execute the command.

KFPL31011-E R

Invalid LOB format, line=aa....aa, column=bb....bb

Specification was invalid for LOB column line = aa....aa, column = bb....bb.

Length of the LOB input file name specified in the input file for the LOB column structure base table was invalid.

LOB data length specified in the LOB column input file was invalid.

Invalid EOF was detected when acquiring 4-byte LOB data from the LOB column input file or when acquiring the specified LOB data.

aa....aa: Row number

Row number in the input data file. When a LOB column input file is used, this is the number of the data item in the LOB column input file that resulted in the error.

bb....bb: Column number

Because this indicates the position from the beginning of the data in the input data file, the displayed value includes columns and constructor function arguments that are designated for skipping by the skipdata statement.

S: Outputs information to the error information file and terminates processing.

O:

Separate file is provided for each item of LOB data:
Check that the length of the LOB input file name corresponding to the row number in the input data file for the LOB column structure base table is greater than 0 and not greater than 1023. If the length is invalid, correct it. If the length of the file name is correct, change the specification to the absolute path name.
When EasyMT is being used, check that the length of the file name is greater than 0 and not greater than 17. If the length is invalid, correct it.

LOB column input file is provided:
Check that the length of the LOB data in the LOB column input file corresponding to the row number in the input data file for the LOB column structure base table is greater than 0 and not greater than the defined length and that the specified LOB data exists. If there is an error, correct it.

KFPL31012-E R

Specified LOB file not found, line=aa....aa

LOB input file specified in line aa....aa cannot be found.

aa....aa: Line number

S: Outputs the message to the error information file and terminates processing.

O: Check that the LOB input file is on the specified path.

KFPL31013-E R

LOB data too long, line=aa....aa

Length of the LOB data for row aa....aa specified in the table definition was greater than the defined LOB column length.

Separate file is provided for each item of LOB data:

The LOB input file data specified for row aa....aa of the input data file for the LOB column structure base table exceeded the defined length.

LOB column input file is provided:

LOB data in the LOB column input file corresponding to row aa....aa of the input data file for the LOB column structure base table exceeded the defined length.

aa....aa: Row number

Row number in the input data file. When a LOB column input file is used, this is the number of the data item in the LOB column input file that resulted in the error.

S: Outputs information to the error information file and terminates processing.

O:

Separate file is provided for each item of LOB data:
Correct the LOB input file for the indicated row that was specified in the input data file for the LOB column structure base table.

LOB column input file is provided:
Correct the LOB data for the indicated row in the LOB column input file.

KFPL31014-E R

LOBMID file conflicted with LOB data file, line=aa....aa

Information specified for the LOB column structure base table obtained from the LOB middle file (LOBMID file) contradicts the information specified for the LOB column input file:

NULL was specified for the LOB column structure base table, but data with a length of at least 1 byte was specified for the LOB column input file.

Default value was specified for the LOB column structure base table, but data with a length of at least 1 byte was specified for the LOB column input file.

aa....aa: Row number

Row number in the input data file

S: Outputs information to the error information file and terminates processing.

O: Check the specifications for the LOB column at the row number of the input data file of the LOB column structure base table, correct the LOB data at the row number of the LOB column input file that resulted in the error, then re-execute the command.

KFPL31015-E R

Unmatched LOB data count, line=aa....aa

The number of data items of the input data file of the LOB column structure base table does not match aa....aa the number of LOB data data items in the LOB column input file.

aa....aa: Row number

Data number that resulted in the error in the LOB column input file

S: Outputs the error message to the error information file.

O: To use a LOB column input file, as many data items are required in the LOB column input file as there are rows in the input data file for the LOB column structure base table. Check the KFPL00703-I message for the number of data items created during creation of the LOB column structure base table and compare that number with the data number displayed in this message. Make sure that the number of data items in the input data file for the LOB column structure base table matches the number of LOB data items in the LOB column input file, then re-execute the command.

KFPL31016-E R

Invalid parameter, line=aa....aa, column=bb....bb, code=cc [dd....dd]

The input parameter for the constructor function that generates the values to be stored in a column of abstract data type is invalid. If the message No output for error data is displayed, the data length for the last line of data in the input data file is too short.

aa....aa: Line number

bb....bb: Column number

Because this indicates the position from the beginning of the data in the input data file, the displayed value includes columns and constructor function arguments that are designated for skipping by the skipdata statement.

cc: Logical error number

For the logical error numbers, see the HiRDB Version 9 Command Reference.

dd....dd: (No output for error data)

S: Resumes processing after outputting an error message to the error information file.

O:

By referring to the logical error details, correct the indicated data in the input data file that was specified as an input parameter for the function and re-execute the command.

If the message No output for error data is displayed, not all error data has been output to the error data file. This problem can be resolved by correcting the data in the last line of the input data file and re-executing the command.

KFPL31017-E R

Specified LOB file permission denied, line=aa....aa

The user does not have the access privilege to the LOB input file specified in row aa....aa of the data.

aa....aa: Row number

S: Outputs the error message to the error information file, and then continues processing.

O: To enable the HiRDB administrator to read the file, grant the access privilege to the LOB input file.

KFPL31018-E R

PLUGIN function error occurred, line=aa....aa, reason="bb....bb", column="cc....cc" [dd....dd]

The value to be stored in a column of abstract data type, using a plug-in-provided function, is invalid. If the message No output for error data is displayed, the work buffer for the creation of an error data file is too small.

aa....aa: Line number

bb....bb: Description of the error detected by a plug-in-provided function

cc....cc: Column name

dd....dd: (No output for error data)

S: Resumes processing after outputting an error message to the error information file.

O: Correct the indicated data in the input data file by referring to the error message.

If the message No output for error data is displayed, error data is not output to the error data file. This problem can be resolved by specifying a large enough size for the work buffer for the creation of an error data file and by re-executing the command.

KFPL31019-E R

Invalid number of element, line=aa....aa, column=bb....bb

The specification of the element count for the repetition column in line=aa....aa, column=bb....bb contains an error.

aa....aa: Line number

bb....bb: Column number

Because this indicates the position from the beginning of the data in the input data file, the displayed value includes columns and constructor function arguments that are designated for skipping by the skipdata statement.

S: Resumes processing after outputting an error message to the error information file.

O: Determine whether the element count for the repetition column is correct. In addition, check whether the column data in the input data file is error-free. If the element count is invalid or the column data contains an error, correct the file contents and re-execute the command.

KFPL31020-E R

Invalid enclose character detected, line=aa....aa, offset=bb....bb

An invalid enclosed character was detected at byte bb....bb from the beginning of line aa....aa in the data.

aa....aa: Row number

bb....bb: Position where the invalid enclosed character was detected

S: Outputs the error message to the error information file, and then terminates processing.

O: For an input data file in the extended DAT format, specify two consecutive values when handling the same value as the enclosed character with data.

KFPL31021-E R

Invalid file path format, line=aa....aa, column=bb....bb

The specification format for the input file in column bb....bb of row aa....aa is invalid.
The file name length, which is a combination of the path name specified in the column structure information file and the path name in the input data file, is invalid.

aa....aa: Row number

bb....bb: Column number

The column number indicates the position from the first data item in the input data file. Therefore, it indicates a value that contains the number of arguments in a column or constructor function that are not input by means of a skipdata statement.

S: Outputs an error message to the error information file.

P:

When preparing a file by data item for XML-type parameter attributes, make sure that the length of the file name, which is a combination of the path name specified in the column structure information file and the path name in the input data file, is greater than 0 but less than or equal to 1,023. If there are any errors, correct them.

If the length of the file name is valid, correct the format of the absolute path specification.

KFPL31022-E R

Specified file not found, line=aa....aa, column=bb....bb

No files are specified in column bb....bb of row aa....aa.

aa....aa: Row number

bb....bb: Column number

The column number indicates the position from the first data in the input data file. Therefore, it indicates a value that contains the number of arguments in a column or constructor function that are not to be input with skipdata.

S: Outputs an error message to the error information file.

P: Check whether the specified input file exists in the specified path.

KFPL31023-E R

File data too long, line=aa....aa, column=bb....bb

The data length of the file specified in column bb....bb of row aa....aa exceeds the defined length specified for table definitions.

aa....aa: Row number

bb....bb: Column number

The column number indicates the position from the first data in the input data file. Therefore, it indicates a value that contains the number of arguments in a column or constructor function that are not to be input with skipdata.

S: Outputs an error message to the error information file.

P: Correct the file that was specified in the input file.

KFPL31024-E R

Specified file permission denied, line=aa....aa, column=bb....bb

You do not have access privileges to the file specified in the data in column bb....bb of the aa....aa row.

aa....aa: Row number

bb....bb: Column number

The column number indicates the position from the first data in the input data file. Therefore, it indicates a value that contains the number of arguments in a column or constructor function that are not to be input with skipdata.

S: Outputs an error message to the error information file, and continues processing.

P: Grant administrative access privileges for the file so that it can be read.

KFPL31090-E R

Input data too long, line=aa....aa, column=bb....bb [,element=cc....cc]

The input data length of line=aa....aa, column=bb....bb (if an element has been output, the repetition column element cc....cc) exceeds the defined column length for the table definitions.

For data loading:
The error data and handling data are not stored.

For file partitioning:
However, data is not output to the divided-input data file.

aa....aa: Row number

bb....bb: Column number

cc....cc: Element number

S: Outputs an error message to the error information file, and continues processing.

O: Correct the data that exceeded the definition length, and then re-execute pdload.

KFPL31090-W R

Input data too long, line=aa....aa, column=bb....bb[,element=cc....cc]

The length of the input data in line=aa....aa, column=bb....bb (and repetition column element cc....cc if element is displayed) exceeds the column definition length at the time the table was defined.

For data loading:
The data is stored by truncating the data portion that exceeds the defined length.

For file partitioning (creation of a partitioning input data file):
The data is output to the partitioning input data file.

aa....aa: Line number

bb....bb: Column number

cc....cc: Element number

S: Outputs an error message to the error information file and continues processing.

O: Check whether any problems resulted from truncating the data portion that exceeds the defined length. If there is a problem, modify the data that exceeds the defined length, and then re-execute pdload.

KFPL33000- L+S

Pdrbal started, table=aa....aa."bb....bb", execmode=cc....cc

Rebalancing of table aa....aa."bb....bb" has begun.

aa....aa: Authorization identifier

bb....bb: Table identifier

cc....cc: Operation mode:

share: Shared mode

exclusive: Exclusive mode

S: Continues processing.

KFPL33001- L+S

Pdrbal terminated, return code=aa

The pdrbal processing terminated with return code aa.

aa: Return code.

0: Normal termination (all data was rebalanced)

4: Normal termination (some data was not rebalanced)

8: Abnormal termination

S: Terminates processing.

O:

Return code is 4:
Re-execute pdrbal.

Return code is 8:
Correct the error by referring to the error message that is output to standard output or the message log file, and re-execute pdrbal.

KFPL33002- L+S

Report file aa....aa assigned

Processing results file aa....aa has been created.

aa....aa: Processing results file name

If the length of the execution result file name exceeds 129 characters, the last 129 characters of the execution result file name are output.

S: Continues processing.

KFPL33003-l L+S

Activation of dictionary information completed, status=aa....aa

Dictionary information was activated.

aa....aa: Dictionary information activation timing:

START:

At the time of rebalancing startup:

If an error occurs after this message has been output, the execution status of pdrbal is rebalancing.

END:

At the time of rebalancing termination:

If an error occurs after this message has been output, rebalancing has been completed, and it is not necessary to re-execute pdrbal.

S: Continues processing.

KFPL33004- L+S

aa....aa rows bb....bb, table=cc....cc."dd....dd"

aa....aa rows were processed during rebalancing of table cc....cc."dd....dd".

aa....aa: Number of rows

bb....bb:

processing: Processed

cc....cc: Authorization identifier

dd....dd: Table identifier

S: Continues processing.

KFPL33005- L+S

Pdrbal stopped at execstop, table=aa....aa."bb....bb"

Rebalancing of table aa....aa."bb....bb" was halted by specification of the execstop statement.

aa....aa: Authorization identifier

bb....bb: Table identifier

S: Terminates processing.

KFPL33500-E E+L

Unable to specify "aa....aa" in this case

Cannot specify the following control statements in the control information file when "aa....aa" is specified in the command line:

"aa....aa" is -k share or -k exclusive:

index statement

idxwork statement

sort statement

"aa....aa" is -k exclusive:

option statement (check_itv operand)

aa....aa: Option name (-k share or -k exclusive)

S: Terminates processing.

O:

"aa....aa" is -k share:
Respecify the command line or the control information file, and then re-execute.

"aa....aa" is -k exclusive:
Delete the check_itv operand or change the command line to -k share and re-execute.

KFPL33501-E E+L

Unable to execute pdrbal due to aa....aa table

pdrbal cannot be executed for table aa....aa.

aa....aa: Table type:

non base:

Table other than a base table

non rebalance:

Table other than a rebalancing table

ADT:

Table in which one of the following abstract data types is specified:

User-defined type

One of the following abstract data types provided by a plug-in:
Has a supertype
Has an abstract data type for the attribute
Attribute is BLOB-type but has no unload function

S: Terminates processing.

O: Stop execution of pdrbal.

KFPL33502-E E+L

Unable to execute pdrbal without aa....aa privilege

Access privilege aa....aa has not been granted for the table that is to be processed.

aa....aa: Access privilege type:

select: SELECT privilege

insert: INSERT privilege

delete: DELETE privilege

S: Terminates processing.

O: Have the table owner grant the executor the access privilege for the table to be processed, and re-execute pdrbal.

KFPL33503-E E+L

Unable to execute pdrbal command without addition of RDAREA, table=aa....aa."bb....bb"

pdrbal cannot be executed without addition of an RDAREA.

aa....aa: Authorization identifier

bb....bb: Table identifier

S: Terminates processing.

O: Check that the name of the table to be rebalanced is correct. If it is, add an RDAREA for the rebalancing table and re-execute pdrbal.

KFPL33504-E E+L

Table aa....aa during execution of pdrbal, table_name=bb....bb."cc....cc"

The rebalancing table was deleted or the table definition was changed during execution of pdrbal.

aa....aa: Reason code:

dropped: Rebalancing table was deleted.

changed: Rebalancing table was changed (or deleted, or created).

bb....bb: Authorization identifier

cc....cc: Table identifier

S: Terminates processing.

O: Based on the reason code, check the definition of the target table.

KFPL33505-E E+L

Activation of dictionary information failed

Activation of dictionary information failed.

S: Terminates processing.

O: Correct the error based on the error message that was output before this message, and re-execute pdrbal.

KFPL33506-E E+L

Unable to execute pdrbal command because of NONDIV_IDX defined, index_name=aa....aa."bb....bb"

pdrbal cannot be executed because a non-partitioning key index is defined in the rebalancing table.

aa....aa: Authorization identifier

bb....bb: Index identifier

S: Terminates processing.

O: Delete the non-partitioning key index and re-execute pdrbal.

KFPL33507-E E+L

Unable to recompile routine, type=aa....aa, name="bb....bb"."cc....cc", error_sql_no=dd....dd, err_sql=ee....ee

Recompilation of the routine failed.

aa....aa: Routine type:

PROCEDURE: Procedure

FUNCTION: Function

bb....bb: Schema name

cc....cc: Routine identifier

dd....dd: Number indicating the SQL procedure statement in the routine that caused the error

For the numbers that indicate SQL procedure statements, see ERR_SQL_NO in GET DIAGNOSTICS in the HiRDB Version 9 SQL Reference.

ee....ee: SQL procedure statement in the routine that caused the error

For SQL procedure statements, see ERR_SQL in GET DIAGNOSTICS in the HiRDB Version 9 SQL Reference.

S: Terminates processing.

O:

Take appropriate action based on ERR_SQL_NO, ERR_SQL, and the message that was output immediately before this message, and recompile the procedure or function using ALTER PROCEDURE or ALTER ROUTINE. (Re-executing the rebalancing utility will not recompile the procedure or function.)

If START is displayed for STATUS in the KFPL33003-I message that was output before this message, take the above action, and then re-execute the rebalancing utility. If END is displayed for STATUS, there is no need to re-execute (an attempt to re-execute will cause an error).

KFPL33508-E E+L

Unable to execute pdrbal using replicated RDAREA, table=aa....aa. "bb....bb"

Cannot execute pdrbal because a replica RDAREA is defined in the target table.

aa....aa: Authorization identifier

bb....bb: Table identifier

S: Terminates processing.

O: When executing pdrbal, delete all replica RDAREAs defined in the target table.

KFPL33509-W E+L

Execution time of pdrbal for COMPRESSED table aa....aa."bb....bb"become long, because execmode is share

When rebalancing a compressed table in shared mode, the time required for rebalancing can be longer than when there are compressed columns, due to the expansion and compression performed during data transfer.

aa....aa: Authorization identifier

bb....bb: Table identifier

S: Continues processing.

O: If you want to shorten the rebalancing execution time, use the pdcancel command to forcibly terminate the rebalancing utility while it is executing, and then re-execute the rebalancing utility in exclusive mode. For details about the pdcancel command, see the manual HiRDB Version 9 Command Reference.

KFPL50000-I L+S

Pdconstck started, func=aa....aa, table=bb....bb."cc....cc"[, constraint=dd....dd."ee....ee"] [, generation=fff]

The integrity check utility was started.
If the constraint type is check, , constraint=ee....ee."ff....ff" is output. If the HiRDB Staticizer Option is installed, , generation=hhh is output.

aa....aa: Facility

check: Integrity check facility

set: Facility to force the setting of check pending status (forced setting)

release: Facility to force the setting of check pending status (forced release)

bb....bb: Authorization identifier

cc....cc: Table identifier

dd....dd: Authorization identifier (displayed on a constraint-by-constraint basis)

ee....ee: Generation to be processed

fff: Generation number (displayed if HiRDB Staticizer Option is installed)

all: All generations

0 to 10: Specified generation

cur: Generation of the current RDAREA

S: Continues processing.

KFPL50001-I L+S

Pdconstck terminated, return code=a

Processing of the integrity check utility terminated.

a: Return code

0: Normal termination

The integrity check found no row data with a constraint violation.

4: Normal termination

The integrity check found row data with a constraint violation; or the processing of the integrity check utility was terminated because the number of key values indicating a constraint violation exceeded the upper limit.

8: Abnormal termination

S: Terminates processing.

O:

Return code 8:

Refer to the error message that is output to standard error or to the message log file, resolve the error, and then re-execute the command.

Return code 4:

Refer to the row data that produced the constraint violation and revise the integrity of the constraint. If necessary, re-execute the command.

To verify the check pending status of the table, refer to the processing results of the integrity check utility or of the database condition analysis facility.

KFPL51200-E E+L

No constraint defined, table=aa....aa.bb....bb

A reference constraint (foreign key) or a check constraint is not defined on the specified table.

aa....aa: Authorization identifier

bb....bb: Table identifier

S: Terminates processing.

P: Revise the table name, and then re-execute the command.

KFPL51201-E E+L

Unable to execute aa....aa command, due to lack of privilege

Command aa....aa cannot be executed because the user has neither of the following privileges on the table:

DBA privilege

Owner of the table

aa....aa: Command name

S: Terminates processing.

P: Take one of the following actions:

Re-execute the command as a user with DBA privilege.

Re-execute the command by granting the DBA privilege to the user.

Re-execute the command by specifying a table owned by the user.

KFPL51202-E E+L

Replica RDAREA insufficient, table=aa....aa."bb....bb"

The utility cannot be executed because there is no replica RDAREA associated with the original RDAREA of table aa....aa."bb....bb".

aa....aa: Authorization identifier

bb....bb: Table identifier

S: Terminates processing.

Action

Use the pdrdrefls command to check the RDAREA associated with the indicated table. Next, use the pddbls command to verify that the RDAREA associated with the table satisfies the conditions indicated below, and then re-execute the utility:

The storage RDAREA does not contain both an RDAREA to which the inner replica facility is applied and one to which it is not applied.

The numbers defined for replica RDAREAs match.

Generation numbers for replica RDAREA definitions are consistent.

KFPL51203-E E+L

Check pending status conflicts, table=aa....aa.bb....bb, constraint type=cc....cc

The check pending status of the dictionary table is inconsistent with the check pending status of the constraint.

If the constraint type is REF:

The value specified for the table in SQL_TABLES (CHKPEND column) differs from the value specified for the table in SQL_REFERENTIAL_CONSTRAINTS (CHKPEND column).

If the constraint type is CHECK:

The value specified for the table in SQL_TABLES (CHKPEND2 column) differs from the value specified for the table in SQL_CHECKS (CHKPEND2 column).

aa....aa: Authorization identifier

bb....bb: Table identifier

cc....cc: Constraint

REF: Reference constraint

CHECK: Check constraint

S: Terminates processing.

Action

Use the integrity check utility with the -k set parameter (pdconstck -k set) to forcibly set the table into check pending status, and then use the check parameter (pdconstck -k check) to perform a constraint integrity check.

KFPL90001-I S

Process aa....aa started. yyy/mm/dd,hh:mm:ss

The aa....aa processing has started.

aa....aa: Processing:

rorg: Reorganization

yyyy/mm/dd: Execution start date

hh:mm:ss: Execution start time

S: Continues processing.

KFPL90002-I S

Process aa....aa ended. return code=bb,yyy/mm/dd,hh:mm:ss

The aa....aa processing has terminated.

aa....aa: Processing:

rorg: Reorganization

bb: Return code

0: Normal termination (all table reorganization was completed)

4: Normal termination (table is being reorganized)

8: Error termination (recovered from a backup)

12: Error termination (recovery from a backup failed)

yyy/mm/dd: Execution termination date

hh:mm:ss: Execution termination time

S: Terminates processing.

O:

Return code is 4:
The time specified in the -m option of pdrorg was not sufficient and the KFPL91101-W message was output; re-editing was not performed. Increase the specification value and re-execute.

Return code is 8 or 12:
For the error detail, check the contents of the execution information file displayed in KFPL90003-E. Correct the error and take appropriate action based on the execution status indicated by the KFPL90021-I to KFPL90028-I progress messages that are output.

KFPL90003-E E

Eliminating the cause of the error, refer to executed information file="aa....aa"

The error shown in the execution information file occurred.

aa....aa: Execution information file name

S: Terminates processing.

O: Check the error detail in the execution information file and correct the error.

KFPL90010-I S

Process aa....aa bb....bb/cc....cc ended.table name=dd....dd

The aa....aa processing, which is number bb....bb out of a total of cc....cc, has terminated.

aa....aa: Processing:

rorg: Reorganization

bb....bb: Number of completed processes

cc....cc: Total number of processes

dd....dd: Name of the processed table

S: Continues processing.

KFPL90021-I S

DB hold step ended

Database shutdown has terminated.

S: Continues processing.

KFPL90022-I S

Before backup step ended

The backup before processing has been completed.

S: Continues processing.

KFPL90023-I S

aa....aa step started

The aa....aa processing has started.

aa....aa: Processing:

Reorganize: Reorganization

S: Continues processing.

KFPL90024-I S

aa....aa step ended

The aa....aa processing has been completed.

aa....aa: Processing:

Reorganize: Reorganization

S: Continues processing.

KFPL90025-I S

After backup step ended

The backup after processing has been completed.

S: Continues processing.

KFPL90026-I S

DB release step ended

Database shutdown release has been completed.

S: Continues processing.

KFPL90027-I S

DB stop process started

The database is being stopped for error recovery.

S: Continues processing.

KFPL90028-I S

Recover step started on aa....aa error

Database recovery from the backup file is being started.

aa....aa: Processing:

rorg: Reorganization

S: Continues processing.

KFPL90029-I S

Recover step ended on aa....aa error

Database recovery from the backup file has terminated.

aa....aa: Processing:

rorg: Reorganization

S: Continues processing.

KFPL90030-I S

DB started process ended

Database startup processing has been completed.

S: Continues processing.

KFPL90101-I R

aa....aa

Outputs the command line during HiRDB command execution.

aa....aa: Command line during pdrorg execution

S: Continues processing.

KFPL90102-I R

aa....aa

Displays one control statement line during pdrorg execution.

aa....aa: Control statement during pdrorg execution

S: Continues processing.

KFPL91000-I E

Usage:aa....aa[-m time] -k func_name

Displays the specification format for the aa....aa command.

aa....aa: Name of the command that was to be executed

S: Terminates processing.

O: Correct the command line error and re-execute.

KFPL91001-E E

Mandatory specification missing in command line

A required option is not specified on the command line.

S: Terminates processing.

O: Specify the required option for the command and re-execute.

KFPL91002-E E

Invalid aa....aa option

Option aa....aa is invalid.

aa....aa: Invalid option

S: Terminates processing.

O: Specify the option correctly and re-execute.

KFPL91003-E E

Invalid value of aa....aa option

Option aa....aa's specification value is invalid.

aa....aa: Option

S: Terminates processing.

O: Specify the option correctly and re-execute.

KFPL91004-E E

Invalid format exists in command line

The format of the command line for the executed utility is invalid.

S: Terminates processing.

O: Correct the command line and re-execute.

KFPL91100-E E

System call error, func=aa....aa, errno=bb....bb

An error occurred during the processing of a HiRDB system function.

aa....aa: Name of the HiRDB system function

bb....bb: Error code

S: Terminates processing.

O: Correct the error based on the error code in this message and the error messages that are output before and after this message.

KFPL91101-W E

Unable to execute aa....aa due to little value of -m option

The aa....aa processing cannot be executed because the value specified in the -m option is too small.

aa....aa: Processing:

rorg: Reorganization

S: Terminates processing.

O: Specify an appropriate value in the -m option and re-execute.

KFPL91102-E E

aa....aa process already executed

Execution of the aa....aa command is already underway.

aa....aa: Name of the command being executed

S: Terminates processing.

O: If necessary, wait for the command being executed to terminate, then re-execute.

KFPL91103-E E

Insufficient memory on PROCESS, size=aa....aa, part=bb....bb, code=cc....cc

A memory shortage occurred.

aa....aa: Insufficient memory size (in bytes)

bb....bb: Part number

cc....cc: Part code

S: Terminates processing.

O: Wait for other programs that are using a significant amount of memory to terminate, then re-execute.

KFPL91104-E E

Unable to aa....aa without bb....bb privilege

The bb....bb access privilege for the aa....aa processing has not been granted.

aa....aa: Name of the command to be executed

bb....bb: Access privilege

DBA: DBA privilege

S: Terminates processing.

O: Obtain the necessary access privilege and re-execute.

KFPL91105-E E

aa....aa invalid

The authorization identifier or password specified by an environment variable is invalid. Or, the password entered in response to an input prompt message is invalid.

aa....aa: Error item:

Auth_id: Authorization identifier

Password: Password

S: Terminates processing.

O: Take one of the following actions, depending on the error item:

Auth_id displayed for aa....aa:

Correct the PDUSER environment variable and re-execute.

Password displayed for aa....aa:

Correct the PDUSER environment variable and re-execute. Or, if a password was entered in response to the input prompt message, re-execute the command and ensure that the correct password is entered.

In the case of Windows, make sure that the character string for the specified authorization identifier or password is not enclosed in single quotation marks (') in the command prompt.

Correct specification example: PDUSER="root"/"root"

KFPL91106-E E

aa....aa error occurred, file=bb....bb

A file access error occurred.

aa....aa: Processing during which the error occurred:

Open: Opening

Read: Loading

Write: Writing

Delete: Deleting

Close: Closing

Lock: Locking

bb....bb: File name (final portion of path name)

S: Terminates processing.

O: Correct the error based on the messages that are output before and after this message.

KFPL91107-E E

System call error, func=aa....aa, errno=bb....bb

A file access error occurred.

aa....aa: Name of the system function in which the error occurred

bb....bb: Error number returned by the system function (errno)

S: Terminates processing (may continue processing in the case of a close error).

O: Correct the error by referring to errno.h and the error number (errno) in the reference manual that describes the applicable function, and re-execute.

2.9 KFPM messages

KFPM20002-E E+S

Invalid define information in pdmibtgt

There is an error in the settings of the MIB command (pdmibcmd) MIB environment definition file pdmibtgt.

S: Terminates processing.

Action

Check for and correct any error in the pdmibtgt file's definition information under the HiRDB-installation-directory/sample. Then re-execute.

KFPM20003-E E+S

System call error,func="aa....aa",errno=bbbb

An error occurred in system function "aa....aa".

aa....aa: System function name

bbbb: Error code

S: Terminates processing.

Action

See 4.2 Detail codes for system-related errors to eliminate the cause of the error, then re-execute the command. If the cause of the error is still unknown, save the files under %PDDIR%\spool and %PDDIR%\tmp, and contact the customer support center.

KFPM20004-E E+S

Command error, command=aa....aa, code=bbb

HiRDB command aa....aa executed in pdmibcmd terminated with return code bbb.

aa....aa: HiRDB command name

bbb: Return code

S: Terminates processing.

Action

Refer to the message that was output before this message to the event log (in UNIX, syslogfile), resolve the error, and then re-execute the command.

KFPM20005-E E+S

Insufficient memory for PROCESS, size=aa....aa

Insufficient memory in the process private area.

aa....aa: Size of the area that was attempted to be allocated.

S: Terminates processing.

Action

Increase the size of the process private memory and re-execute.

KFPM20006-E E+S

System function error occurred, func="aa....aa", errno=bb....bb

An error occurred in a HiRDB function.

aa....aa: HiRDB function name

bb....bb: Error code

S: Terminates processing.

Action

Refer to messages output before and after this message to the event log (in UNIX, syslogfile).

If there is a message, take the action indicated in the message. If a KFPU00215-E or KFPU00241-E message was output, the monitored HiRDB system version may be older than version 07-01. In this case, delete the relevant HiRDB system definition from the pdmibtgt file.

If there is no message, see 4.2 Detail codes for system-related errors, eliminate the cause of the error, then re-execute the command. If the cause of the error cannot be determined, save the files under %PDDIR%\spool and %PDDIR%\tmp, and contact the customer support center.

KFPM20007-E E+S

Make Directry error occurred, directory=aa....aa, errno=bbbb

Creation of the working directory pdmibwork failed.

aa....aa: Directory path name of pdmibwork, creation of which was attempted

bbbb: Error code

S: Terminates processing.

Action

See 4.2 Detail codes for system-related errors, eliminate the cause of the error, and then re-execute.

KFPM20008-E E+S

MIB Data format error occurred

An error occurred during MIB information creation.

S: Terminates processing.

Action

Refer to the message that was output before this message to the event log (in UNIX, syslogfile), resolve the error, and then re-execute the command. If the cause of the error cannot be determined, save the files under %PDDIR%\spool and %PDDIR%\tmp, and contact the customer support center.

KFPM20009-E E+S

File I/O error occurred, func=aa....aa, file=bb....bb, errno=cc....cc

An error occurred during MIB work file I/O.

aa....aa: System function name where the error occurred

bb....bb: MIB work file name

cc....cc: Error code

S: Terminates processing.

Action

See 4.2 Detail codes for system-related errors, eliminate the cause of the error, and then re-execute.

KFPM20010-E E+S

Invalid command line, command="pdmibcmd"

MIB command (pdmibcmd) command arguments, options, or option values are invalid.

S: Terminates processing.

Action

Correct the command line and re-execute.

KFPM20011-E E+S

Invalid define information in pdmibenv, name="aa....aa", system="bbbb"

The contents of the "aa....aa" definition defined in the pdmibenv file of HiRDB system "bbbb" are invalid. Or, they were not defined.

aa....aa: Name of the definition that could not be analyzed

bbbb: Name of the monitored HiRDB system that could not be analyzed

S: Terminates processing.

Action

In the pdmibenv file definition information under the working directory %PDDIR%\conf of the monitored HiRDB system "bbbb", correct the value related to "aa....aa". Then, re-execute.

KFPM20013-E E+S

System call error,func="putenv"

The MIB command (pdmibcmd) attempted to set the environment variables, but failed.

S: Terminates processing.

Action

Contact the customer support center.

KFPM20014-E E+S

Not Active server

Because there is no working server, data could not be collected.

S: Terminates processing.

Action

Start the HiRDB server, then re-execute the command.

KFPM20015-E E+S

Make MIB table error occurred, table kind=aaa

MIB command (pdmibcmd) Table creation failed.

aaa: Table type

S: Terminates processing.

Action

Check the contents of the pdmibenv file under %PDDIR%\conf and the HiRDB system status, then re-execute the command. For details on the operation of the facility for monitoring MIB performance information, see the HiRDB Version 9 System Operation Guide.

KFPM20016-E E+S

Failed MIB data exchanged DAT to CSV

An error occurred during MIB information creation in the MIB command (pdmibcmd) conversion from DAT format to CSV format.

S: Terminates processing.

Action

Save the files under %PDDIR%\spool and %PDDIR%\tmp, and contact the customer support center.

KFPM20017-W E+S

DATADICTIONARY search failed, RDAREA="aa....aa", SQLCODE=bb....bb

Data dictionary search on RDAREA "aa....aa" failed with SQL code bb....bb. Therefore, MIB information for RDAREA "aa....aa" could not be collected.

aa....aa: RDAREA name

bb....bb: SQL code

S: Continues processing (information for the relevant RDAREA is not displayed).

Action

Ensure that the data dictionary RDAREA hold status, or the definition information in the pdmibenv file under %PDDIR%\conf, matches the environment definitions used by HiRDB. For details, refer to the value of the displayed SQLCODE. If there is an error, correct it, and then retry the operation.

2.10 KFPN messages

KFPN00001-E E+L

Cannot allocate bb....bb byte-insufficient memory aa....aa

A memory shortage occurred.

aa....aa: Type of area:

PROCESS: Process private area

bb....bb: Size (in bytes) of area that was to be allocated

S: Terminates processing.

Action

Check if there are other processes using a large amount of memory.

There are processes using a large amount of memory:

Wait for the processes to terminate, then re-execute the command.

There are no processes using a large amount of memory:

Take one of the following actions and wait until there is sufficient memory available:

Reduce the number of simultaneously executing processes.

Increase the size of the swap area.

Increase the amount of memory.

KFPN00002-E L

Internal error, func=aa....aa

An internal contradiction was detected.

aa....aa: Name of the module resulting in the error

S: Terminates processing.

Action

Contact the customer support center.

KFPN00003-E E+L

System call error, func=aa....aa, errno=bb....bb

A system call (function) error occurred.

aa....aa: Name of system call (function)

bb....bb: Error number set in errno

S: Terminates processing.

Action

Check the meaning of the error number (errno: external integer variable indicating the error status), refer to errno.h and to the applicable OS manual to eliminate the cause of the error, then re-execute the command.

KFPN00010-I E+L

Processing completed, table="aa....aa"

Optimizing information about the indicated table has been stored in the dictionary table.

aa....aa: Table identifier subject to collection of optimizing information

S: Resumes processing.

KFPN00011-I E+L

Pdgetcst terminated, return code=aa

Execution of the optimizing information collection utility (pdgetcst) terminated.

aa: Return code

When the -c, -d, or -s option is specified:

0: Terminated normally.

4: If the -c option was specified, the command terminated after storing incomplete optimization information, because at least one of the following occurred:

If message KFPN00207-W was output immediately before this message:
The table that is the target of the optimizing information collection utility has been modified (by a statement such as INSERT, DELETE, UPDATE, or PURGE TABLE), so the optimization information to be stored might be different from the actual contents of the table.

If message KFPN00214-W was output immediately before this message:
The table includes an index in a format that is not supported by the optimizing information collection utility, so the utility skipped the collection of optimization information for that index.

8: Terminated abnormally.

When the -e option is specified:

0: Terminated normally.

4: An error occurred during termination processing, but it finished saving all the optimization information for the specified table or index.

8: Terminated abnormally.

S: Terminates processing.

O:

If the return code is 4:

If optimization information was collected with the -c option specified and message KFPN00207-W was output immediately before this message, take action appropriate to that message. If message KFPN00207-W was not output, no action is necessary.

If the return code is 8:

Eliminate the cause of the error by referring to the error message that was output to the log file or standard error output immediately before this message. Then, re-execute the optimizing information collection utility until it runs with a return code of 0.

If the error persists even after the optimizing information collection utility is re-executed, take corrective action after consulting If an error occurs while registering, updating, or deleting optimizing information in the HiRDB Version 9 System Operation Guide.

KFPN00012-I E+L

Pdgetcat started

Execution of the pdgetcat utility has started.

S: Resumes processing.

KFPN00013-I L

Statistics information of table "aa....aa"."bb....bb" for SQL optimization ccccccc

ccccccc processing on the data dictionary table that optimized information related to target table "aa....aa"."bb....bb" has finished.

aa....aa: Authorization identifier in the table to be processed

bb....bb: Identifier in the table to be processed

ccccccc: Processing type

added: New entry of optimized information

altered: Update of optimized information

dropped: Deletion of optimized information

S: Continues processing.

KFPN00014-I L

Statistics information of table "aa....aa"."bb....bb" for SQL optimization not found

An attempt was made to export optimized information related to target table "aa....aa"."bb....bb", but optimized information had not been entered. As a result, no parameter file containing optimized information was created.

aa....aa: Authorization identifier in the table to be processed

bb....bb: Identifier in the table to be processed

S: Continues processing.

KFPN00015-I L

Specified file aa....aa overwritten

Because a file existed with the same name as the parameter file that contains optimized information specified in the -e option, the pre-existing file was overwritten.

aa....aa: Name of the parameter file that contains optimized information

If the file name is 195 bytes or less, the entire file name is displayed. If the file name exceeds 195 bytes, two periods (..) are added in the front, and the last 193 bytes of the file name are displayed.

S: Continues processing.

KFPN00016-I E+L

Statistics information for SQL optimization exported, table=aa....aa."bb....bb", file=cc....cc

Optimized information related to table "aa....aa"."bb....bb" has been saved to the cc....cc parameter file that contains optimized information.

aa....aa: Authorization identifier

bb....bb: Table identifier

cc....cc: Name of the parameter file that contains optimized information

If the file name is 114 bytes or less, the entire file name is displayed. If the file name exceeds 114 bytes, two periods (..) are added in the front, and the last 112 bytes of the file name are displayed.

In addition, if the KFPN00014-I message is output to the message log file or event log (in UNIX: syslogfile) prior to this message, the cc....cc parameter file that contains optimized information is not created.

S: Continues processing.

KFPN00100-E E

Usage: pdgetcst [-u user_id] [-a auth_id] [-p password] -t {table_name | ALL} [-l result_list_file_name] [[-d] | [-c {lvl1 | lvl2}] [-q generation_number] | [[- v space_level] -s parameter_file_name] | [-e parameter_file_name]]

Displays the format of the pdgetcst utility.

S: Terminates processing.

O: Check the pdgetcst utility parameters for any input errors.

KFPN00101-E E

Identifier "aa....aa" exceeds 30 characters

The authorization identifier, password, or table identifier entered on the command line exceeds 30 characters.

aa....aa: Character string truncated to 30 characters

S: Terminates processing.

O: Correct the data so that it does not exceed 30 characters and re-execute.

KFPN00102-E E+L

Invalid file name

The file name specified in the -s option or -e option is invalid. The following are possible reasons:

The file name was not expressed as an absolute path name.

If the -s option was specified, the specified name is not a regular file.

If the -e option was specified, the file with the specified name exists, but is not a regular file.

S: Terminates processing.

O: Review the following, specify the correct file name, and then re-execute the command:

Whether a file that is not an ordinary file is specified (UNIX edition)

Whether an item that is not a file is specified (Windows edition)

Whether an invalid file is specified

Whether a file name is specified as a relative path name

KFPN00103-E E

Invalid aa....aa

The authorization identifier or password specified in the PDUSER environment variable is invalid.

aa....aa: Type of error:

user_id: Authorization identifier

password: Password

S: Terminates processing.

O:

Correct the value of the PDUSER environment and re-execute. Alternatively, specify the -u or -p option and re-execute.

Note on specifying an authorization identifier or a password (Windows edition only):

When omitting the -u option, make sure that the character string specifying an authorization identifier or password in the command prompt is not enclosed in single quotation marks (').

Example of correct specification: PDUSER="root"/"root"

When specifying an authorization identifier or password in a client environment definition (hirdb.ini), enclose it in single quotation marks (').

Example of correct specification: PDUSER='"root"/"root"'

KFPN00151-E L

Error no: aaaaa-cannot bbbbbb file cc....cc

A file access error occurred.

aa....aa: Value of errno returned from the system call

bbbbbb:Processing resulting in the error:

close: File close processing#

open: File open processing

read: Read processing

write: Write processing

unlink: File deletion processing

chmod: File permission settings processing

#: When the processing code is close, a write error might have occurred when write processing of buffered data was performed during file closing processing.

cc....cc: File name (if the file name consists of fewer than 127 bytes, the entire file name is displayed; otherwise, only the first 126 bytes are displayed, prefixed with two bytes of periods (..))

S: Terminates processing.

Action

Refer to errno to eliminate the cause of the error, and re-execute.

KFPN00201-E L

Invalid index name "aa....aa"

The specified index name is invalid; one of the following conditions applies:

The specified index name is not defined.

The specified index name is defined for another table.

The specified index is not a B-tree index.

aa....aa: Specified index name

S: Terminates processing.

O: Change the index name specified in the parameter file and re-execute.

KFPN00202-E L

Invalid table name "aa....aa"

The specified table name is invalid for one of the following reasons:

Specified table is a viewed table.

Specified table is a dictionary table.

Specified table was not found.

The specified table is a rebalancing table.

The specified table is a temporary table.

aa....aa: Specified table name

S: Terminates processing.

Action

Check the specified name and re-execute.

KFPN00203-E L

Inconsistent definition

Table or index definition was modified during utility execution, or a dictionary is damaged.

S: Terminates processing.

Action

Check if the table of index definition was modified during utility execution.

Modification underway:

Re-execute after the modification is completed.

Modification not underway:

Re-execute.

If this message is reissued during re-execution, recover the database from its backup copy and re-execute.

If the same message is reissued after these actions have been taken, contact the customer support center.

KFPN00204-E L

Invalid RDAREA status, RDAREA="aa....aa"

Indicated RDAREA cannot be analyzed for one of the following reasons:

RDAREA with INITIAL opening attribute:

The RDAREA is not on shutdown-release open status or reference-enabled shutdown and open status.

RDAREA with DEFER or SCHEDULE opening attribute:

The RDAREA is not on shutdown-release open status, shutdown-release closed status, reference-enabled shutdown and open status, or reference-enabled shutdown and closed status.

aa....aa: RDAREA name

S: Terminates processing.

Action

Check the RDAREA's status and re-execute the command.

KFPN00206-E L

Unable to operate table during pdgetcst executing

An attempt was made to update (INSERT, DELETE, UPDATE, PURGE TABLE, or LOCK statement) a table by the optimizing information collection utility (pdgetcst) while a UAP or utility was executing.

S: Terminates processing.

O: Check for any UAP or utility that is accessing the corresponding table for the purpose of updating it. If you use the pdls command to check the transaction and lock status, you can check for relevant UAPs or utilities.

There is a relevant UAP or utility

Wait for the UAP or utility to terminate, and re-execute.

There is not a relevant UAP or utility

If there is not relevant UAP or utility transaction, and only a lock remains, contact the customer support center.

KFPN00207-W L

Optimize information incompleted

Optimizing information to be stored differs from the actual table contents because of updates (INSERT, DELETE, UPDATE, or PURGE TABLE statement) To the table, which the optimizing information collection utility (pdgetcst) was executing.

S: Resumes processing.

O: To acquire valid optimization information, wait until the UAP that is updating the table terminates, then re-execute.

KFPN00208-E L

Invalid column name "aa....aa"

Specified column name is invalid for one of the following reasons:

The specified column name is undefined.

The BLOB column is specified.

The specified column is an abstract data type.

aa....aa: Specified column name

S: Terminates processing.

Action

Specify the correct column name in the optimization information parameter file and re-execute.

KFPN00209-E L

More than 30 characters in identifier "aa....aa"

Name "aa....aa" specified in the optimization information parameter file is longer than 30 bytes.

aa....aa: Specified value (index identifier, column name); if more than 30 bytes are specified, only the first 30 bytes are displayed

S: Terminates processing after completion of analysis of optimization information parameter file.

Action

Correct the value at the line number indicated in the KPFN00300-E message that was output immediately before this message, then re-execute.

KFPN00210-E L

Already specified in parameter file, line=aa....aa

Item at line aa....aa has already been specified in the same section.

aa....aa: Line number

S: Terminates processing after completion of analysis of optimization information parameter file.

Action

Correct the specification so that the item is not duplicated in the same section, then re-execute.

KFPN00211-E L

Invalid parameter, line=aa....aa

Value of item at line aa....aa is invalid. Following are possible reasons:

The specified value is outside the value range permitted for the item.

A mandatory item value is missing.

The length of the value exceeds the permitted maximum number of digits.

aa....aa: Line number

S: Terminates processing after completion of analysis of optimization information parameter file.

Action

Correct the value specification and re-execute.

KFPN00212-E L

Specified keyword before "INDEX" or "COLUMN" keyword, line=aa....aa

Item at line aa....aa is specified before INDEX or COLUMN.

aa....aa: Line number

S: Terminates processing after completion of analysis of optimization information parameter file.

Action

When the item at line number aa....aa is item optimization information

Specify the item after the INDEX specification and re-execute.

When the item at line number aa....aa is item optimization information

Specify the item after the COLUMN specification and re-execute.

KFPN00213-E L

Sectional information number exceeds section count, line=aa....aa

The section number specified in SECTION_NO of row aa....aa in the parameter file that contains optimized information exceeds the section count specified in SECTION_COUNT.

aa....aa: Row number

S: The parameter file that contains optimized information is analyzed, and then the process is terminated.

Action

Correct the section number so that it does not exceed the section count, and then re-execute.

KFPN00214-W L

aa....aa not supported, index name "bb....bb"

Because aa....aa is not supported by the Optimization Information Collection Utility, the collection of optimization information for "bb....bb" was skipped.

aa....aa:

Multi-value column: Repetition column

bb....bb: Index name

S: Resumes processing.

KFPN00215-E L

Table not found, schema="aa....aa"

There is no table in "aa....aa" from which optimization information can be acquired.

aa....aa: Schema name

S: Terminates processing.

O: Check that the table from which optimization information is to be acquired exists in "aa....aa". If not, specify in the -a option the name of the schema in which is located the table from which optimization information is to be acquired.

KFPN00216-E E+L

Invalid aa option

One of the following errors was found in the specification of the aa option:

An error was found in the value specified in the aa option.

When -q is specified as the aa option and the current environment does not support the HiRDB Staticizer Option.

aa: Option name

S: Terminates processing.

O:

An error was found in the value specified in the aa option:
Correct the value specified in the option, and then re-execute.

When the -q option is specified as aa:
Delete the specification of the -q option, and then re-execute. Alternatively, specify the -q option in an environment that supports use of the HiRDB Staticizer Option, and then re-execute.

KFPN00217- E+L

Current RDAREA "aa....aa" analyze

RDAREA "aa....aa" is subject to analysis by the utility as the current RDAREA because no replica RDAREA was found in the specified generation.

aa....aa: RDAREA name

S: Resumes processing.

KFPN00218-E L

"aa....aa" keyword before "SECTION_NO" keyword, line=bb....bb

Section aa....aa of row bb....bb is specified before SECTION_NO.

aa....aa: Section distribution information item names

SEC_TOTAL_COUNT: Cumulative frequency of the number of section elements

SEC_UNIQUE: Number of unique values within a section

SEC_MAX_VALUE: Maximum value inside a section

bb....bb: Row number

S: The parameter file that contains optimized information is analyzed, and then the process is terminated.

Action

Correct the aa....aa item in row bb....bb so that it is specified after the SECTION_NO, and then re-execute.

KFPN00300-E L

Syntax error in parameter file, line=aa....aa

The optimization information parameter file contains a syntax error. Following are possible reasons:

The item name does not begin in the first byte.

Multiple items or values are specified on the same line.

The line consists of more than 80 bytes.

aa....aa: Line number containing the syntax error

S: Terminates processing after completion of analysis of optimization information parameter file.

Action

Correct the specification in the optimization information parameter file and re-execute.

KFPN00301-E L

Data conversion error, column type=aa....aa, line=bb....bb

System was unable to convert to type aa....aa a value specified in the optimization information parameter file. Following are possible reasons:

A numeric value is required, but characters were specified.

The value specified for the column type in the optimization information parameter file cannot be converted.

Overflow occurred in the specified value.

aa....aa: Column type to be converted

bb....bb: Line number resulting in the conversion error

S: Terminates processing after completion of analysis of optimization information parameter file.

Action

Correct the data to be converted in the optimization information parameter file and re-execute.

KFPN00302-E L

Sectional information invalid, column name "aa....aa"

There is an error in the section distribution information in the specification column of the parameter file that contains optimized information. The following are possible causes:

Some items have been omitted from the section distribution information.

There is invalid syntax in some section distribution information items.

The specified section count and the section distribution information count do not match.

aa....aa: Column name specifying invalid section distribution information

S: Analyzes the parameter file that contains optimized information, and then terminates processing.

Action

Specify the correct section distribution information in the parameter file that contains optimized information, and then re-execute.

KFPN00303-E L

RDAREA not found, RDAREA id=aa....aa

The RDAREA to be processed could not be found for the following reason:

The RDAREA to be processed was deleted during utility operation.

aa....aa: RDAREA ID

S: Terminates processing.

O: If the RDAREA to be processed was deleted during utility operation, reconstruct an environment that can execute the utility, and then re-execute. If the RDAREA to be processed was not deleted, contact the customer support center.

KFPN00304-E L

Specify hex format parameter to column with character set specification, line=aa....aa

There is an error in the specification format of row aa....aa of the parameter file that contains optimized information. Values for MAX_VALUE, MIN_VALUE, and SEC_MAX_VALUE columns specifying character sets have been represented in a format other than hexadecimals.

aa....aa: Row number

S: Analyzes the parameter file that contains optimized information, and then terminates processing.

Action

Correct the specification values in row aa....aa so that they are represented in hexadecimals, and then re-execute. For details about the specification format for MAX_VALUE, MIN_VALUE, and SEC_MAX_VALUE in columns specifying character sets, see Specifications in the optimization information parameter file in the manual HiRDB Version 9 Command Reference.

KFPN00400-E E+L

RPC(system) error, func=aa....aa code=bb....bb

An RPC-related error or system-related error occurred.

aa....aa: Name of function resulting in the error

bb....bb: Error detail code

S: Terminates processing.

Action

See 4. Error Detail Codes to eliminate the cause of the error, and re-execute the command. If the error cannot be corrected by the HiRDB administrator, contact the customer support center.

KFPN00401-E L

Error occurred on BES(SDS), server=aa....aa

An error occurred during HiRDB/Single Server processing or during back-end server processing in a HiRDB/Parallel Server.

aa....aa: Name of server resulting in the error

S: Terminates processing.

Action

Correct the error by referring to the message output to standard error, or to standard output, and re-execute.

KFPN00402-E E

Pdgetcst must be executed at unit defined as manager

Execute the pdgetcst utility from the unit where the system manager (MGR) is defined.

S: Terminates processing.

Action

Remotely log on to the unit on which the system manager (MGR) is defined, and then re-execute the command.

KFPN00403-E L

Directory access error

An error occurred while accessing the data directory. The data directory may be damaged.

S: Terminates processing.

Action

Recover the database from its backup copy and re-execute. If this message is reissued, contact the customer support center.

KFPN00404-E E+L

Insufficient memory in message buffer pool due to concurrent execution of "pdgetcst"

A temporary memory shortage occurred in the message storage buffer pool during process allocation when the optimizing information collection utility (pdgetcst) was executed concurrently.

S: Terminates processing.

O: Wait until execution of the current pdgetcst is completed, then re-execute.

Action

If the pdchprc command was used to request services from a server for which the maximum number of startup processes had been set to 0, use the pdchprc command to increase the maximum number of startup processes.

If a service was requested from a server being refreshed by the pdpfresh command, re-execute the utility after the pdpfresh command has finished.

If you are executing utilities concurrently, review and, if necessary, revise the maximum number of utilities that can be executed at the same time. To find out the maximum number of utilities that can be executed concurrently, see the manual HiRDB Version 9 Command Reference.

KFPN00405-E L

Unable to send message from aa....aa to bb....bb

Data cannot be sent from host aa....aa to host bb....bb because a communication error occurred.

aa....aa: Send source host name#

bb....bb: Send destination host name#

#: If the system switching facility is being used, the host name of the primary system is indicated.

S: Terminates processing.

O: Take action appropriate to the KFPN00400-E message that was output before this message. If a physical communication error has not occurred, there may be an inconsistency in the system definitions concerning the relationship between the hosts; check the interhost definitions for the hosts affected by the error and re-execute.

KFPN00406-E E

Current RDAREA changed

The current RDAREA was changed while the utility was running.

S: Terminates processing.

O: Re-execute. Do not change the current RDAREA while the utility is running.

KFPN00450-I L

Deleted optimize information for table "aa....aa"

Optimizing information was deleted from a dictionary table.

aa....aa: Table identifier subject to deletion of optimizing information

S: Resumes processing.

KFPN10000-E E

Invalid directory name, option=aa

The system was unable to set the directory or device name specified in the aa option of the pdgeter command for one of the following reasons:

The specified directory or device was not found.

The command executor did not have the write privilege for the specified directory.

The entity corresponding to the specified directory name did not have the directory attribute.

The entity corresponding to the specified device name did not have the device attribute.

The device name was specified in the -w option.

aa: Invalid option name specified:

-o: Name of output destination directory or device

-w: Name of work directory

S: Terminates processing.

Action

Check the directory name or device name and re-execute the command.

KFPN10050-E E

Unable to set default, option=aa

The system was unable to set the default value for the aa option of the pdgeter command for one of the following reasons:

The command executor did not have the write privilege for $PDDIR or $PDDIR/erinf.

A file with the same default name was found.

aa: Option for which default value setting failed:

-o: Name of the output destination directory

-w: Name of the work directory

S: Terminates processing.

Action

Eliminate the cause of the error and re-execute the command.

KFPN10051-E E

Error information file already exists, directory=aa....aa

The system was unable to acquire error information because the directory or temporary work area at the pdgeter command output destination contained one of the following directories or files:

PDDIR

lib

usr

HiRDB

aa....aa: Directory specified in the -o or -w option or its default value

S: Terminates processing.

Action

If the indicated directory or file is not needed, delete it and re-execute the command. If it is needed, use another directory for the pdgeter command and re-execute the command.

KFPN10100-E E

Invalid parameter

Invalid parameter was specified in the pdgeter command:

An invalid option was specified.

S: Terminates processing.

Action

Correct the parameter in the pdgeter command and re-execute the command.

KFPN10101-E E

Invalid aa option

Specified option aa was invalid in the pdgeter command:

A command argument was missing.

aa: Invalid option:

-o: Name of the output destination directory

-w: Name of the work directory

-x: Name of the host

S: Terminates processing.

Action

Specify the correct parameter in the pdgeter command.

KFPN10200-W E

Unable to get HiRDB files

The -a option was specified in the pdgeter command, but the system was unable to obtain the master directory, data directory, or data dictionary. Following are possible reasons:

$PDDIR/conf/INITCONT (pdinit control statements file) was not found at the command startup host.

$PDDIR/conf/pdsys (system common definition) was not found at the command startup host.

The host containing the master directory, etc. (single server or dictionary server), was not specified in the -x option of the pdgeter command.

The pdstart operand is missing in the system common definition.

The HiRDB file system area specified in $PDDIR/conf/INITCONT (pdinit control statements file) was not found at the host containing the master directory, etc. (single server or dictionary server).

S: Resumes processing.

KFPN10201-W E

Unable to get HiRDB System information, host_name=aa....aa

The system was unable to acquire shared memory dump information or system information for host name aa....aa by the pdgeter command. Following is a possible reason:

The HiRDB is not active.

aa....aa: Name of the host for which acquisition of shared memory information or system information failed

S: Resumes processing.

KFPN10202-W E

Unable to get error information, host_name=aa....aa

The system was unable to acquire error information for host name aa....aa by the pdgeter command. Following are possible reasons:

The specified host name was not found.

A network error occurred.

There was not enough space at the command startup host.

A directory or device specified in the -o option may have been deleted for some reason during execution of the pdgeter command.

A directory specified in the -w option may have been deleted for some reason during execution of the pdgeter command.

Output of execution results failed for an OS command that was issued within the pdgeter command. In this case, the name of the corresponding command startup host is displayed as host_name.

aa....aa: Host name

S: Resumes processing.

Action

To acquire error information about the erroneous host, specify the correct host name in the -x option and re-execute the command. If a network error has occurred, the command must be executed at the corresponding host.

KFPN10203-E E

HiRDB home directory not defined

The system was unable to execute the pdgeter command because the HiRDB directory ($PDDIR) was not set.

S: Terminates processing.

Action

Set the HiRDB directory ($PDDIR) for the HiRDB administrator and re-execute the command.

KFPN10204-W E

HiRDB home directory not defined, host_name=aa....aa

The system was unable to acquire error information about the indicated host, because the $PDDIR environment variable was not set for host name aa....aa specified in the pdgeter command.

aa....aa: Host name

S: Resumes processing.

Action

Set the $PDDIR environment variable for the HiRDB administrator at the corresponding host and re-execute the command.

KFPN10300-I E

Pdgeter started

Execution of the pdgeter command has started.

S: Resumes processing.

KFPN10301-I E

Pdgeter terminated, return code=aa....aa

Execution of the pdgeter command has terminated.

aa....aa: Return code (termination code):

0: Terminated normally.

4: Terminated normally, but a warning message was output.

8: Processing was cancelled due to an error.

12: Processing was cancelled due to an interrupt (signal occurred).

S: Terminates processing.

Action

Return code 4:

Check the warning message that was output during processing and eliminate the cause of the error.

Return code 8:

Check the error message that was output during processing and eliminate the cause of the error.

KFPN10302-I E

Usage: pdgeter [-o dir_name | dev_name] [-w dir_name] [-x host_name [,host_name]...] [-am]

Displays the format of the pdgeter command.

-o: Name of the output destination directory or device

-w: Name of the work directory

-x: Name of the host

-a: Acquire all information

-m: Do not acquire shared memory dump or system information

S: Terminates processing.

Action

Specify the correct parameters in the pdgeter command and re-execute the command.

KFPN10400-I S

Pdinfoget started

Execution of the error information acquisition command (pdinfoget) started.

S: Continues processing.

KFPN10401-I S

Pdinfoget terminated, return code=aa....aa

Execution of the error information acquisition command (pdinfoget) terminated.

aa....aa: Return code (termination code)

0: Terminated normally.

4: Failed to acquire some error information.

8: Processing was cancelled due to an error.

12: Processing was cancelled due to an interrupt (signal generated)#.

#: This return code is only output in UNIX.

S: Terminates processing.

Action

If the return code is 4:

Check the error information that could not be acquired, refer to the error message to eliminate the cause of the error if necessary, and then re-execute the command or acquire the information by another means.

If the return code is 8:

Eliminate the cause of the error based on the message that was output during processing, and then re-execute the command.

If the return code is 12:

If you must re-execute a command, do so after first deleting any unnecessary files and directories under the error information directory.

KFPN10402-I S

Usage: pdinfoget {-m|-e init_dir_name -d detail_dir_name [-w work_dir_name]}[-s syslog_name] [-l watoson_log_name] [-c crash_dump_name] [-b xds_shared_memory_dump_dir_name]

Indicates how to use the error information acquisition command (pdinfoget).

-m: Specify this when estimating error information.

-e: Name of the directory to which initialization information is output

-d: Name of the directory to which error detail information is output

-w: Work directory

-s: syslogfile name (in UNIX)

Event log file name (in Windows)

-l: Watson log file specification (in Windows)

-c: Crash dump specification (in Windows)

-b: Name of the directory to which the shared memory dump of the XDS server is output

S: Terminates processing.

Action

Specify the pdinfoget command correctly, and then re-execute the command.

KFPN10403-I S

aa....aa information file output,file=bb....bb

Error information file output finished.

aa....aa:

init: Initialization information

detail: Error detail information

bb....bb: File path name of initial information or error detail information

S: Continues processing.

KFPN10420-E S

Invalid parameter

There is an error in the parameter specifications for the error information acquisition command (pdinfoget). An invalid option might have been specified.

S: Terminates processing.

Action

Specify the pdinfoget command correctly, and then re-execute the command.

KFPN10421-E S

Invalid aa option

aa option specifications of the error information acquisition command (pdinfoget) contain one or more of the following errors.

No command argument is specified in the option.

The specified path contains a space (in UNIX).

The specified path is not an absolute path.

aa: Name of the invalid option

-e: Name of the directory to which initialization information is output

-o: Name of the directory to which error detail information is output

-w: Work directory

-s: syslogfile name (in UNIX)

-l: Watson log file name (in Windows)

-c: Crash dump name (in Windows)

-b: Name of the directory to which the shared memory dump of the XDS server is output

S: Terminates processing.

Action

Specify the pdinfoget command correctly, and then re-execute the command.

KFPN10422-E S

Same directory specified -e and -d

The same directory is specified for the -e and -d options of the error information acquisition command (pdinfoget).

S: Terminates processing.

Action

Specify different directory names for the -e and -d options, and then re-execute the command.

KFPN10423-E S

Unable to specified combination of option

An invalid option combination was specified in the error information acquisition command (pdinfoget).

The -e or -d option was specified at the same time as the -m option.

Either the -e or -d option was omitted.

S: Terminates processing.

Action

Specify the option correctly and then re-execute the command.

KFPN10430-E S

Invalid directory, option=aa

The specified directory name in the aa option of the error information acquisition command (pdinfoget) is invalid for one of the following reasons.

The specified directory was not found.

The command executor does not have write privileges for the specified directory.

The specified directory name does not have the directory attribute.

aa: Option name that has an invalid specification value

-e: Name of the directory to which initialization information is output

-d: Name of the directory to which error detail information is output

-w: Work directory

-b: Name of the directory to which the shared memory dump of the XDS server is output

S: Terminates processing.

Action

Specify the correct directory name and then re-execute the command.

KFPN10431-E S

Error information file already exists, directory=aa....aa

Because there is a specific directory or file in the directory specified for the -e or -d option of the error information acquisition command (pdinfoget), the error information cannot be obtained.
For details about those directories or files, see Directories that cause an error if located in an output directory under pdinfoget (Acquire error information and estimate its volume) in the manual HiRDB Version 9 Command Reference.

aa....aa: Name of the directory for which the -e or -d option is specified

S: Terminates processing.

Action

If the directory or file is unnecessary, delete it and then re-execute the command. If the directory or file is necessary, specify a separate directory name and then re-execute the command.

KFPN10432-E S

Error work directory already exists, directory=aa....aa

Error information cannot be acquired, because a directory or file with the same name as the work directory was created under the work directory by the error information acquisition command (pdinfoget).

aa....aa: Name of the work directory created under work directory by the pdinfoget command

S: Terminates processing.

Action

If the directory or file with the abovementioned name is unnecessary, delete it and then re-execute the command. If the directory or file with the abovementioned name is necessary, either change the work directory or wait 1 or more seconds before re-executing the command.

KFPN10433-W S

Invalid directory, environment variable=aa....aa

During execution of the error information acquisition command (pdinfoget), the directory specified in environment variable aa....aa was invalid for the following reason:

The root directory is specified.

aa....aa: Name of the environment variable

PDCONFPATH: Directory storing HiRDB system definition files

S: Continues processing.

Action

Error information outside of the HiRDB system definitions cannot be acquired. Error information for the HiRDB system definitions is acquired under the directory specified in the environment variable PDCONFPATH.

KFPN10440-E S

Invalid HiRDB home directory

The error information acquisition command (pdinfoget) cannot be executed, either because the HiRDB directory ($PDDIR) has not been set or because an invalid directory was set in the HiRDB directory.

S: Terminates processing.

Action

Set the correct HiRDB directory ($PDDIR), and then re-execute the command.

KFPN10441-E E

Error occurred, aa....aa errno=bb....bb

An error occurred in error information acquisition command (pdinfoget) processing.

aa....aa: Processing code during which the error occurred

TMPDIR: Default work directory acquisition processing

OpenEventLog: Open processing of the event log

BackupEventLog: Backup processing of the event log

CloseEventLog: Close processing of the event log

bb....bb: Error detail code

S: Terminates processing.

Action

If an error message was output before this message, take an appropriate action in response to that message and then enter the command. If this message is output even after taking such measures, save the contents of the message and contact the customer support center.

KFPN10442-E E

Insufficient memory

A memory shortage occurred.

S: Terminates processing.

Action

Check whether there are other processes that are using a large amount of memory.

If other processes are using a large amount of memory:

Wait for the associated processes to terminate, then re-execute the command.

If no other processes are using a large amount of memory:

Use one of the following methods to make sure that there is sufficient memory:

Reduce the number of concurrently executing processes.

Increase the swapping area.

Increase the real memory.

KFPN10450-W S

Unable to get error information, host_name=aa....aa

Host name aa....aa error information cannot be obtained using the error information acquisition command (pdinfoget). The following are possible reasons:

There is no file to be acquired.

You do not have reference privileges for the file to be acquired.

The required environment variable was not set correctly.

An error occurred while copying the error information.

aa....aa: Host name

S: Continues processing.

Action

Check the error information that could not be acquired, refer as necessary to the OS command error message output by the execution log or console, and then re-execute the command or separately acquire the information.

KFPN10451-I S

Unable to complete aa....aa, code=bb....bb, file=cc....cc

Unable to complete processing function aa....aa by the error information acquisition command (pdinfoget) into file cc....cc. However, the error information is acquired and processing continues.

aa....aa: Processing that could not be completed

ARCFILE: Archive processing of an error information file

COMPRESS: Compression processing of an error information file

ARCHIVE: Archive and compression processing of an error information file

bb....bb: Detail code

cc....cc: Name of file

S: Continues processing.

Action

Because it is still possible to acquire the necessary error information, execute the error information acquisition command (pdinfoget) to acquire error information from all of the files under the output directory for initial information (specifying the -e option), and all the files under the output directory for detail information (specifying the -d option).

KFPN10500-I L

Pdaudput started

Execution of the audit log output utility for JP1/NETM/Audit (pdaudput) was started.

S: Continues processing.

KFPN10501-I L+S

Pdaudput terminated, return code=a, rows=bb....bb, PDLOAD_TIMESTAMP=cc....cc, PDLOAD_SEQNUM=dd....dd

Execution of the audit log output utility for JP1/NETM/Audit (pdaudput) was terminated.

a: Return code

0: Terminated normally.

4: Terminated normally (processing terminated because the audit log output file for JP1/NETM/Audit was swapped).

8: Processing was cancelled due to an error.

bb....bb: Number of rows in which the audit log for JP1/NETM/Audit was output

cc....cc: Last output audit trail PDLOAD_TIMESTAMP value

Note that if bb....bb is 0, the final audit trail information that was output during the previous execution of the pdaudput utility is output. Also, if you use the -k i or -k m option to execute the pdaudput command, one asterisk (*) is output.

dd....dd: Last output audit trail PDLOAD_SEQNUM value

Note that if bb....bb is 0, the final audit trail information that was output during the previous execution of the pdaudput utility is output. Also, if you use the -k i or -k m option to execute the pdaudput command, one asterisk (*) is output.

S: Terminates processing.

O:

If a (the return code) is 4:

The audit trail that was not output in the audit log for JP1/NETM/Audit remains in the audit trail table. Check the audit trails corresponding to cc....cc and dd....dd collected in JP1/NETM/Audit, and then re-execute the pdaudput command. If, after executing the pdaudput command, you plan to delete the output audit trail, execute the pdaudput command until bb....bb becomes 0, and then delete the audit trail table data. For details about how to check whether an audit trail is being collected in JP1/NETM/Audit, as well as for details about how to delete an audit trail that has been completely output after the pdaudput command is executed, see the HiRDB Version 9 System Operation Guide.

If a (the return code) is 8:

Eliminate the cause of the error based on the message that was output during processing.

KFPN10502-I E

Usage: pdaudput [-u user_id] [-k {r | i | m}] [-d directory] [-s file_size] [-w file_name]

Displays how to use the audit log output utility for JP1/NETM/Audit (pdaudput).

S: Terminates processing.

KFPN10503-I L+S

Audit log output file for JP1/NETM/Audit swapping completed. current file:aa....aa

Swap processing of the audit log output file for JP1/NETM/Audit was completed.

aa....aa: Name of the current audit log output file for JP1/NETM/Audit

S: Terminates processing.

KFPN10520-E E+L

Insufficient memory. size=aa....aa bytes, area type=bb....bb

A memory shortage occurred during execution of the audit log output utility for JP1/NETM/Audit (pdaudput).

aa....aa: Area size that was attempted to be secured (in bytes)

bb....bb: Area type

PROCESS: Process private memory

S: Terminates processing.

O: Check whether there are other processes that are using a large amount of memory.

If other processes are using a large amount of memory:

Wait for the associated processes to terminate, then re-execute the pdaudput command.

If no other processes are using a large amount of memory:

Use one of the following methods to make sure that there is sufficient memory:

Reduce the number of concurrently executing processes.

Increase the swapping area.

Increase the real memory.

KFPN10521-E E+L

System call error, func=aa....aa, return code=bb....bb

An error occurred during a system call (function) when the audit log output utility (pdaudput) for JP1/NETM/Audit was executing.

aa....aa: System call (function) name

bb....bb: Detail code of system-related errors

S: Terminates processing.

O: Eliminate the cause of the error by referring to 4.2 Detail codes for system-related errors, and then re-execute the pdaudput command. If the error cannot be corrected, contact the customer support center.

KFPN10522-E E+L

Invalid option for pdaudput, option:aa

There was an error in the specification value of the option for the audit log output utility for JP1/NETM/Audit (pdaudput).

aa: Invalid option

S: Terminates processing.

O: Check the specification format of the option, correct any errors, and then re-execute.

KFPN10523-E E+L

File access error, func=aa....aa, errno=bb....bb, file=cc....cc

An error in file access processing occurred while the audit log output utility (pdaudput) for JP1/NETM/Audit was executing.

aa....aa: Processing code during which the error occurred

open: An open process of a file

close: A close process of a file

fgets: Reading

write: Write processing

unlink: File deletion processing

lockf: lock processing

lseek: Migration processing of the reading or writing file pointer

stat: Processing for acquisition of the file status

fstat: Processing for acquisition of the file status

bb....bb: errno value returned by the system call

cc....cc: File name

If the file name is 128 bytes or less, the entire file name is displayed. If the file name exceeds 128 bytes, two periods (..) are added in the front, and the last 126 bytes of the file name are displayed.

S: Terminates processing.

O: Eliminate the cause of the error by referring to 4.2 Detail codes for system-related errors, and re-execute the pdaudput command. If the error cannot be corrected, contact the customer support center.

KFPN10524-E E+L

Error occurred, reason code=aa(bb....bb)

An error occurred during execution of the audit log output utility for JP1/NETM/Audit (pdaudput).

aa: Reason code

bb....bb: Additional information

S: Terminates processing.

O: Take the action appropriate to the reason code below.

Reason code (aa) | Additional information (bb....bb) | Meaning | Action
01 | ALREADY_STARTED | The pdaudput utility is already executing. | Wait for the executing pdaudput utility to terminate, and then re-execute.
02 | NOT_AUDITOR | You are not an auditor, so you cannot execute the pdaudput command. | Check whether the authorization identifier and password for the auditor have been correctly specified.
03 | NOT_FOUND_AUDIT_TRAIL_TABLE | The audit trail table does not exist. | Create an audit trail table and then re-execute.
04 | NOT_SYSTEM_MANAGER | The pdaudput command cannot be executed because no system manager has been defined for the unit. | Execute the command on the unit where the system manager is defined.

KFPN10525-E E+L

Invalid file, cause:aa file_name:bb....bb

The file that was accessed during execution of the audit log output utility for JP1/NETM/Audit (pdaudput) was invalid.

aa: Reason code

01: Invalid file type

02: Invalid file analysis results

bb....bb: File name

If the file name is 128 bytes or less, the entire file name is displayed. If the file name exceeds 128 bytes, two periods (..) are added in the front, and the last 126 bytes of the file name are displayed.

S: Terminates processing.

O: The invalid file and the corrective action for it are shown below. For details about command options, refer to the manual HiRDB Version 9 Command Reference.

File name (bb....bb)
Action

pdaudputctrl (Management file for pdaudput)
Use the pdaudput -k i command to initialize the management file for pdaudput.

auditmsg1.log or auditmsg2.log
(audit log output file for JP1/NETM/Audit)
Use the pdaudput -k m command to initialize the audit log output file for JP1/NETM/Audit.

File name specified in the -w option
Change the retrieval condition definition file defined in the -w option into a regular file, and then re-execute.

KFPN10526-E E+L

Dictionary access error occurred, SQLCODE=aa....aa, SQLERRMC=bb....bb

During execution of the audit log output utility (pdaudput) for JP1/NETM/Audit, a dictionary access error occurred.

aa....aa: SQL communication area (SQLCA) SQLCODE

bb....bb: SQL communication area (SQLCA) SQLERRMC

A maximum of 524 characters are output to standard error.

S: Terminates processing.

O: In 1.2(4) Notes on messages, see the description of the relationships between message IDs and SQLCODE codes in the SQL Communications Area (SQLCA) used by the UAP, and refer to the message corresponding to SQLCODE(aa....aa). If the cause of the error is one of the following, take corrective action according to the message found there:

Dictionary shutdown

Memory shortage

Lock resource shortage

Lock error

Communication error

I/O error

For other errors, if you cannot take corrective action according to the corresponding message, contact the customer support center.

KFPN10527-E E+L

Unable to execute SQL, SQLCODE=aa....aa, SQLERRMC=bb....bb

During execution of the audit log output utility (pdaudput) for JP1/NETM/Audit, an error occurred while the SQL statement that retrieves the audit trail table was executing.

aa....aa: SQL communication area (SQLCA) SQLCODE

bb....bb: SQL communication area (SQLCA) SQLERRMC

A maximum of 524 characters are output in standard errors.

S: Terminates processing.

O: In 1.2(4) Notes on messages, see the description of the relationships between message IDs and SQLCODE codes in the SQL Communications Area (SQLCA) used by the UAP, and refer to the message corresponding to SQLCODE(aa....aa). If the cause of the error is one of the following, take corrective action according to that message found there:

Dictionary shutdown

Memory shortage

Lock resource shortage

Lock error

Communication error

I/O error

For causes other than those mentioned above, specify the correct search conditions in the search conditions definition file specified in the pdaudput -w option. If search conditions were correctly specified in the search conditions definitions file that was specified in the -w option, contact the customer support center.

KFPN10528-E E+L

Invalid option specified in command line, option=aa

Option aa was specified in the command line of the audit log output utility (pdaudput) for JP1/NETM/Audit, where it cannot be specified.

aa....aa: Invalid option

If there are multiple options that cannot be specified, the first option that cannot be specified is displayed.

S: Terminates processing.

Action

Delete the option represented by aa or correct another option, and then re-execute.

KFPN10570-Q S

"pdaudput -k i" will be initialized, do you really want to continue initialization ? [y:YES , n:NO]

The management file for pdaudput (pdaudputctrl) already exists. When you execute the pdaudput -k i command, all files used in outputting the audit log for the JP1/NETM/Audit are initialized, and recreated. Answer whether or not to initialize.

y: Initialize.

n: Do not initialize.

S: If you answer y, processing continues.

S: If you answer n, processing terminates.

In cases other than those mentioned above, processing terminates.

O: Respond with y or n.

KFPN11000-E E

Invalid directory or file name, option=aa

The directory or file specified in option aa of the pddefrev command cannot be set for one of the following reasons:

The specified directory or file was not found.

The command executor does not have write privilege for the specified directory.

The specified directory does not have directory attribute (name specified as a directory name does not belong to a directory).

The command executor does not have read privilege for the specified file.

aa: Option whose value is invalid:

-o: Definition SQL output file

-w: Work directory name

S: Terminates processing.

Action

Check the directory name or file name and re-execute the command.

KFPN11100-E E

Invalid parameter

The pddefrev command contains an invalid parameter:

An invalid option was specified.

S: Terminates processing.

Action

Correct the parameter in the pddefrev command and re-execute the command.

KFPN11101-E E

Invalid aa option

Option aa is invalid in the pddefrev command for one of the following reasons:

A command argument is missing.

Information specified in -o option is not an absolute path.

aa: Option whose value is invalid:

-f: Control statements file name

-o: Definition SQL output file name

-w: Work directory name

S: Terminates processing.

Action

Check the pddefrev command and correct any invalid parameters.

KFPN11302-I E

Usage: pddefrev -f control_file_name -o output_file_name [-w work_dir_name]

Displays the format of the pddefrev command.

-f: Control statements file name

-o: Definition SQL output file name

-w: Work directory name

S: Terminates processing.

Action

Specify the pddefrev command correctly and re-execute.

KFPN90001-E E

Insufficient memory, required memory size=aa....aa, area type=bbbbbbb

Memory shortage occurred.

aa....aa: Size (in bytes) of area to be allocated

bbbbbbb: Type of area

PROCESS: Process private memory

S: Terminates processing.

Action

Check if there is a process that uses a large amount of memory:

If there is a process that uses a large amount of memory:
Wait until that process has terminated, then re-execute the command.

If there is no process that uses a large amount of memory:
Contact the customer support center.

KFPN90002-E E

Internal error, func=aa....aa

Internal conflict was detected.

aa....aa: Name of the module resulting in the error

S: Terminates processing.

Action

Contact the customer support center.

KFPN90003-E E

System call error, func=aa....aa, errno=bb....bb

System call resulted in an error.

aa....aa: Name of the system call resulting in the error

bb....bb: Value of errno for the system call resulting in the error

S: Terminates processing.

Action

Check the value of the error indicator, correct the error by referencing errno.h and the applicable OS manual, then re-execute.

KFPN90004-E E

Usage: pdvwopt [-d] filename

Displays the format of the pdvwopt command (access path display utility).

S: Terminates processing.

Action

Check the pdvwopt command for any invalid parameters.

KFPN90006-E E

Access path file bb....bb error, file=cc....cc, errno=aa....aa

File access error occurred.

aa....aa: Value of errno returned from the system call

bb....bb: Processing that resulted in the error:

close: File close processing

open: File open processing

read: Read processing

write: Write processing

cc....cc: File name

If the file name is less than or equal to 126 bytes, HiRDB displays the entire file name. Otherwise, it outputs the file name by appending 2-byte periods to the first 126 bytes.

S: Terminates processing.

Action

Check the value of the error indicator, correct the error by referencing errno.h and the applicable OS manual, then re-execute.

KFPN90007-E E

Command version incompatible, access path file version=aa....aa, command version=bb....bb

The version revision number of the access path information file does not match the version revision number of the command.

aa....aa: Version revision number of the access path information file

bb....bb: Version revision number of the command

S: Terminates processing.

O: Use a command with the same version revision number as the access path information file and re-execute.

KFPN90008-E E

Invalid format of access path file aa....aa

The format of specified file aa....aa is invalid.

aa....aa: Name of the specified file

If the file name is less than or equal to 126 bytes, HiRDB displays the entire file name. Otherwise, it outputs the file name by appending 2-byte periods to the first 126 bytes.

S: Terminates processing.

O: Check if the specified file is an access path information file.

KFPN91001-I E

Usage: pdobils [-s server_name] [-r] [-C [delimiter] [-H]] [-e]

There is an error in the pdobils command option format.

S: Terminates processing.

O: Re-execute on the basis of the method of command usage.

KFPN91002-E S

Invalid server name aa....aa

The server name specified in the pdobils command is invalid.

aa....aa: Server name

If the specification is 9 or more characters, the first 9 characters are displayed.

S: Terminates processing.

O: Correct the server name specification in the pdobils command, then re-execute the command.

KFPN91003-E S

Internal function error, func=aa....aa, return code=bb....bb

An error occurred during processing of the pdobils command.

aa....aa: Function name where the error occurred

bb....bb: Detail code of the system-related error

S: Terminates processing.

O: See 4.2 Detail codes for system-related errors, eliminate the cause of the error, and then re-execute the command.

KFPN91004-E S

Insufficient memory on PROCESS, size=aa....aa

An attempt was made during execution of the pdobils command to allocate the process private area, but it could not be allocated due to insufficient memory.

aa....aa: Size of the attempted allocation area (bytes)

S: Terminates processing.

O: Take one of the following actions and wait until there is sufficient memory available:

Reduce the number of simultaneously executing processes.

Increase the size of the swap area.

Increase the amount of memory.

KFPN91005-E S

Unable to execute pdobils command, because unit of hostname aa....aa not online

The pdobils command could not execute because the unit on hostname aa....aa has not started.

aa....aa: Hostname that the pdobils command could not execute

S: Terminates processing.

O: Wait for the system or unit to go online, then re-execute.

KFPN91006-E S

Unable to execute pdobils command, because server aa....aa not active

The pdobils command could not be executed, because server aa....aa has not started.

aa....aa: HiRDB server name that could not execute the pdobils command

S: Terminates processing.

O: Start the HiRDB server, and re-execute.

2.11 KFPO messages

KFPO00100-E E+L

Error occured in system call aa....aa, errno=bbb, function name=cc....cc

A system call that was issued from within a HiRDB system function resulted in an error.

aa....aa: Name of system call

bbb: Return code from the system call (errno)

cc....cc: Name of function resulting in the error

S: Continues processing if processing can be continued. If not, interrupts processing.

O: Contact the HiRDB administrator.

Action

Take one of the following actions:

If an error message or warning message was output before or after this message, follow the action indicated in that message.

See 4.3 System call return codes, and take action.

If none of these actions is effective, contact the customer support center.

KFPO00103-E E

Shared memory pool damaged. location=0xaaaaaaaa (0xbbbbbbbb, 0xcccccccc)

A segment was damaged; the damaged segment is located at address 0xaaaaaaaa from the beginning of the shared memory pool.

aaaaaaaa: Location of the damaged segment relative to the beginning of the shared memory pool

bbbbbbbb: Contents of the first 8 bytes of the damaged segment

cccccccc: Contents of the last 8 bytes of the damaged segment (if the contents cannot be displayed, ******** is displayed)

S: Terminates abnormally.

O: Record the location and segment contents displayed in this message and contact the HiRDB administrator. In UNIX, if a core file dump is output, save it and contact the customer support center.

Action

Check the cause of the damage to the shared memory pool.

KFPO00104-E E

Shared memory subpool damaged. location=0xaaaaaaaa (0xbbbbbbbb, 0xcccccccc)

A memory block was damaged; the damaged memory block is located at address 0xaaaaaaaa from the beginning of the shared memory subpool.

aaaaaaaa: Location of the damaged memory block relative to the beginning of the shared memory subpool

bbbbbbbb: Contents of the first 8 bytes of the damaged memory block

cccccccc: Contents of the last 8 bytes of the damaged memory block (if the contents cannot be displayed, ******** is displayed)

S: Terminates abnormally.

O: Record the location and memory block contents displayed in this message and contact the HiRDB administrator. In UNIX, if a core file dump is output, save it and contact the customer support center.

Action

Check the cause of the damage to the shared memory subpool.

KFPO00105-E E

Server aa....aa (process ID=bb....bb) killed by code=cc....cc

The HiRDB server process terminated due to an error.

aa....aa: Server name for the abnormally terminating process

(if the server name cannot be determined, ******** is displayed)

bb....bb: Process ID of the abnormally terminating process

cc....cc: ABORT code (for details on the ABORT code, see 3. ABORT Codes)

S: If the server process terminated during the processing of system services, HiRDB (in the case of HiRDB/Parallel Server, the unit) terminates abnormally. If the server process was terminated during UAP processing, post-processing is executed. Restart the server if necessary.

O: Save files in the following directories and contact the HiRDB administrator:

%PDDIR%\spool

%PDDIR%\tmp\home

Action

Take action according to the output abort code.

KFPO00106-E E

{"Malloc(aa....aa)"| "Realloc(bb....bb,aa....aa)"| "Calloc(cc....cc, aa....aa)"}failed,process ID=dd....dd, type=0xee....ee

Process private area cannot be allocated due to an error in the standard C function malloc, realloc, or calloc.

aa....aa: Size specified in the malloc, realloc, or calloc function issued internally in the HiRDB system

bb....bb: Area address specified in the realloc function issued internally in the HiRDB system

cc....cc: Number of array elements specified in the calloc function issued internally in the HiRDB system

dd....dd: ID of the process that issued the malloc, realloc, or calloc function

ee....ee: Type code (identification information set by each component of the HiRDB system)

S: If it is possible to continue system operation, resumes processing. Otherwise, terminates the HiRDB system abnormally.

O: Record this message and contact the HiRDB administrator. In UNIX, if a core file dump is output, save it and contact the HiRDB administrator.

Action

Take one of the following actions:

If system processing is being resumed, terminate any unneeded processes.

Reevaluate the value of the pd_max_users operand.

Add a system swap area.

Add the main storage device.

KFPO00107-E E+L

"aa....aa(bb....bb)" failed, errno=cc: dd....dd

An error occurred in a system call that was issued internally in the HiRDB system.

aa....aa: Name of system call

bb....bb: Name of module or function that issued the system call

cc....cc: Value of errno set by the system call error

dd....dd: Nature of system call error

S: Takes one of the following actions according to the severity of the error:

Cancels processing and terminates the process abnormally.

Cancels processing and returns control to the executing process that was the source of the call.

Resumes processing.

O: Refer to the applicable OS manual in order to check the cause of the error on the basis of the system call name and the value of errno. In UNIX, if a core file dump is output, save it and contact the HiRDB administrator.

Action

Refer to the applicable OS manual in order to check the cause of the error on the basis of the system call name and the value of errno, and correct the UAP, change the system definitions, or regenerate the operating system.

Following are the principal methods by which this problem can be resolved:

System call name
Call module
errno
Error description
Action

open
Arbitrary
23
In UNIX, the number of open files exceeds the maximum value defined for the system.
In Windows, a work file for shared memory could not be allocated due to a capacity shortage in installed drives.
In UNIX, increase the value specified for nfile in the operating system kernel parameters. Also, close any extraneous processes and windows.
In Windows, allocate free space on installed drives greater than or equal to the shared memory size.

24
In UNIX, too many files are opened by the indicated process.
In Windows, a work file for shared memory could not be allocated due to a capacity shortage in installed drives.
In UNIX, if the error occurred during execution of a HiRDB operating command or utility, increase the value specified for maxfiles in the operating system kernel parameters.
In Windows, allocate free space on installed drives greater than or equal to the shared memory size.

47
In AIX an attempt was made to open a write-protected volume in write-enabled mode.
If Real Time SAN replication is used, execute the pdrisechk command to verify that the pair logical volume group is configured correctly.

open
logblib.c
999
In the case of Windows, HiRDB work file may have been damaged.
First, ensure that HiRDB has stopped, then delete all the files listed below and recover. Note that the files from number 4 may not always exist.

%PDDIR%\uxpldir\spool\system\filmng.dat

%PDDIR%\uxpldir\spool\system\flg.dat

%PDDIR%\uxpldir\spool\system\shmmng.dat

%PDDIR%\spool\...pdatmode

%PDDIR%\spool\...pdipcid

%PDDIR%\spool\oslmqid

%PDDIR%\spool\oslsmid

%PDDIR%\spool\pdprcsts

%PDDIR%\spool\scdqid1

%PDDIR%\spool\scdqid2

%PDDIR%\tmp\pdommenv

All files under %PDDIR%\uxpldir\spool\shm

%PDDIR%\uxpldir\spool\system\semmng.dat

%PDDIR%\uxpldir\spool\system\msgmng.dat

When starting HiRDB after deleting all these files, check that no other applications, such as Explorer, are accessing %PDDIR%\tmp.

write
uss_dump
uss_dump_h
uss_dump_d
usm_dump
usm_rmdump
usm_svdump
12
The file system containing the HiRDB operation directory is full.
Delete troubleshooting information under the HiRDB directory.
In UNIX, to delete troubleshooting information, use either the OS rm command or the HiRDB pdcspool command.
In Windows, to delete troubleshooting information, use either the OS del command or the HiRDB pdcspool command.

Arbitrary
47
In AIX, an attempt was made to write to a write-protected volume.
If Real Time SAN replication is used, execute the pdrisechk command to verify that the pair logical volume group is configured correctly.

lio_listio
iosplwrt
5
In AIX, could not write to the volume.
Take action according to the errno displayed in the KFPO00107-E message (system call name: write, call module name: iosplwrt) that is output immediately after this message.

shmat
omminit
ommalloc
ommrmalc
12
Consider one of the following:

The number of available resources is insufficient. This includes the case in which no contiguous free area can be allocated in the process space to which shared memory is to be attached.

In Windows, an error occured while referencing the Windows registry.

In Windows, the HiRDB service is not started when shared memory is allocated to the paging file.

Take the following corrective action according to the cause of the error:

For Windows, specify the number of required resources (size of required shared memory) in the system environment variable PDUXPLSHMMAX. For details about how to compute the size of the shared memory to be used, see the Determining Environment Variables Related to the Number of Resources section in the HiRDB Version 9 Installation and Design Guide.
Note that the default value of the system environment variable PDUXPLSHMMAX is 4096. If usable memory cannot be made available, change the HiRDB system definition (for example, by reducing the number of global buffers) to reduce the shared memory requirements.

Check the value specified for the pdntenv command's -shmfile operand. If it is other than regular, page, or blank, the Windows registry might be corrupt. If that is the case, contact the customer support center.

If the shared memory is allocated to the paging file, confirm that the HiRDB service is started. If the HiRDB service is stopped, start the service.

ommalloc
ommrmalc
22
No HiRDB shared memory (HiRDB shared memory might have been deleted).
In UNIX, it is possible that a HiRDB command was entered before the OS was fully started (this includes the case in which a HiRDB command was coded in an OS environment file such as /etc/localrc).
In the case of Windows, the work file under %PDDIR% may have been deleted while HiRDB was active.
Take the following actions:
In UNIX:

If a HiRDB command was executed before the OS was started, re-execute the command after the activation of the OS is completed.

If a HiRDB command was coded in the OS environment file /etc/localrc, the command is executed before the OS is started, which results in an error. Therefore, a HiRDB command should not be coded in the /etc/localrc file.

In Windows:

If a HiRDB command was executed before the OS was fully started, wait for the OS to finish starting, and then re-execute the command.

If HiRDB did not shut down, terminate it forcibly, and then restart HiRDB.

If the above actions do not resolve the problem, contact the customer support center, because the HiRDB shared memory might have been deleted. If a command that is executable regardless of the operation of HiRDB was executed, you can safely ignore this message. In this case, check the execution result of that command to verify that it is working properly.

ommrmalc
24
The number of common memory devices connected to the invocation source process exceeded the system limit.
Specify an appropriate value in the relevant system parameter shown below. For details about how to perform system estimates, see the HiRDB Version 9 Installation and Design Guide.

HP-UX: shmseg

Solaris: shminfo_shmseg

Linux: SHMSEG

For AIX set ON in the EXTSHM environment variable.

shmctl
ommfixed
1
The user executing this command is not a super-user. It is possible that the file was improperly modified by the owner of a file under $PDDIR/bin.
Check the owner of the execute form file (pdommfixed under $PDDIR/bin) and the owner's privileges. If the owner is not root or his or her execution privilege is not s (with file mode -r-sr-xr-x), the owner of a file under $PDDIR/bin was changed after the pdsetup command had been executed. As a superuser, execute the pdsetup -d command, reply y to the message, and then re-create the HiRDB execution environment by using the pdsetup command. After that, restart HiRDB.

close
Arbitrary
47
In AIX, an attempt was made to write to a write-protected volume.
If Real Time SAN replication is used, execute the pdrisechk command to verify that the pair logical volume group is configured correctly.

semget
osysemg
12
In the case of Windows, there is no room for semaphore identifiers.
Estimate the number of semaphore identifiers required by HiRDB and set a value greater than the value in the PDUXPLSEMMAX system environment variable. After setting, terminate HiRDB and restart the service.
For the procedure for estimating the number of semaphore identifiers, see the HiRDB Version 9 Installation and Design Guide.

pdi_osm_get
999

See 4.3 System call return codes, for other representative errnos.

KFPO00109-E L

Shared memory pool(shared memory ID aa....aa, server type=bb....bb) for HiRDB server damaged. location=0xcccccccc(0xdddddddd, 0xeeeeeeee)

A shared memory pool for user server (shared memory ID = aa....aa, server identifier = bb....bb) was damaged.

aa....aa: Identifier of the damaged shared memory pool for user server

bb....bb: Server identifier (if this information cannot be displayed, ******** is displayed)

cccccccc: Location of the damaged segment relative to the beginning of the shared memory pool

dddddddd: Contents of the first 8 bytes of the damaged segment

eeeeeeee: Contents of the last 8 bytes of the damaged segment (if the contents cannot be displayed, ******** is displayed)

S: Terminates abnormally.

O: Record the location and segment contents displayed in this message and contact the HiRDB administrator. In UNIX, if a core file dump is output, save it and contact the HiRDB administrator.

Action

Contact the customer support center. Correct the program, modify the system definitions, or regenerate the operating system.

KFPO00111-E L

Insufficient memory on aa....aa, size=bb....bb

A memory shortage occurred.

aa....aa: Name of defined variable

bb....bb: Size (in bytes) That was to be allocated

S: Terminates processing.

O: Contact the HiRDB administrator and check the cause of the error.

Action

Contact the customer support center.

KFPO00112-E L

Getarea request error, size=aa....aa

A work area shortage occurred.

aa....aa: Size (in bytes) That was to be allocated

S: Terminates abnormally.

O: Contact the HiRDB administrator and check the cause of the error.

Action

Contact the customer support center.

KFPO00113-E L

"shmget(manager)" failed. size=aa....aa, errno=bbb

An error occurred with the shmget system call issued to collect the unit controller shared memory.

aa....aa: Size (in bytes) of shared memory that was to be allocated

bbb: errno value of the shmget system call

S: Terminates abnormally.

O: Take action appropriate to the errno value of the shmget system call:

KFPO00114-E L

"shmget(aa....aa)" failed, size=bb....bb, errno=ccc

An error occurred in the shmget system call while allocating the shared memory for server aa....aa.

aa....aa: Server identifier

bb....bb: Size (in bytes) of shared memory that was to be allocated

ccc: errno value of the shmget system call

S: Terminates processing.

O: Take action appropriate to the errno value of the shmget system call:

errno
Cause
Administrator's action

12
Specified size of shared memory is not available in the operating system.
Terminate the other control statements using the shared memory on the same machine and restart the server where the error occurred. Or, shut down the HiRDB system and increase the real memory in the operating system.

22
The shared memory size exceeded the maximum value for the operating system.
Shut down the HiRDB system and reduce the number of servers defined in the same unit. Or, increase the maximum segment size of the shared memory in the operating system, and re-create the kernel.

28
The shared memory identifiers count exceeded the maximum value for the operating system.
Terminate the other control statements using the shared memory on the same machine and restart the server where the error occurred. Or, shut down the HiRDB system, either reduce the number of shared memory sectors in the operating system or increase the maximum number of shared memory identifiers, then re-create the kernel.

Other
--
Contact the customer support center.

--: Not applicable

KFPO00115-W E+L

Server aa....aa (process ID=bb....bb) killed by code=cc....cc

A process was terminated forcibly due to an error. This message is output if a process is terminated forcibly when a transaction is canceled.

aa....aa: Name of the server where the process terminated abnormally

If the server name cannot be determined, ******** is displayed.

bb....bb: Process ID of the process that terminated abnormally

cc....cc: ABORT code

For ABORT codes, see 3. ABORT Codes.

S: Re-activates the user server process as necessary. In this case, HiRDB (in the case of a HiRDB/parallel server, a unit) does not terminate abnormally.

O: Error information is output if put is specified in the pd_cancel_dump operand. If it is not needed, the error information can be deleted.

2.12 KFPR messages

KFPR00754-I L+S

Pdcopy started

Database copy utility (pdcopy) processing has started.

S: Resumes processing.

KFPR00756-I L+S

Pdcopy terminated, return code=aa

Database copy utility (pdcopy) processing terminated with the indicated return code.

aa: Return code of the database copy utility (pdcopy):

0: Normal termination

8: Abnormal termination (error occurred during copy processing, but some of the files were backed up successfully)

12: Abnormal termination (all copy processing failed)

S: Resumes processing.

Action

In the case of abnormal termination, refer to the error message that was output before this message to eliminate the cause of the error.

KFPR00757-I E+L

Retry reopen aa-time of bb after cc-minute, host=dd....dd, file=ee....ee, reason=ff....ff

Multivolume file reopen processing will be executed cc minutes later. The maximum retries count is bb, and the next retry number is aa. The file name is ee....ee at host dd....dd.

aa: Next retry number

bb: Maximum retries count

cc: Retry interval

dd....dd: Host name

ee....ee: File name

ff....ff: Reason for retry:

No-file: File is not set.

Same-file: The same file as before is set.

S: Resumes processing.

Action

Set the next file during the retry.

KFPR00758-I L

File swapping started, file=aa....aa, reason=bb....bb

Processing of second or subsequent volume of multivolume file aa....aa has started.

aa....aa: File name

bb....bb: Reason code:

ENOSPC: Space ran out at the device.

EOV: End-of-volume was detected.

S: Resumes processing.

KFPR00764-I L+S

Pdrstr started

Database recovery utility (pdrstr) processing has started.

S: Resumes processing.

KFPR00765-I L

Pdrstr terminated, return code=aa

Database recovery utility (pdrstr) processing terminated with the indicated return code.

aa: Return code of the database recovery utility (pdrstr):

0: Normal termination

4: Termination with warning (close error occurred in the backup file or unload log file; or, the backup file does not contain RDAREA data subject to recovery)

8: Abnormal termination (error occurred, but at least one RDAREA was recovered successfully)

12: Abnormal termination (recovery of all RDAREAs failed)

S: Resumes processing.

Action

In the case of abnormal termination, refer to the error message that was output before this message to eliminate the cause of the error.

KFPR00766-I L

Recovery of "aa....aa" ended bb....bb

Recovery of RDAREA "aa....aa" is complete.

aa....aa: RDAREA name

bb....bb: Completion status:

abnormally: Recovery failed.

normally: Recovery was successful.

S: Resumes processing.

Action

If recovery failed, refer to the error message that was output before this message to eliminate the cause of the error, and re-execute recovery of the corresponding RDAREA.

KFPR00767-I E+L

Retry reopen aa-time of bb after cc-minute, host=dd....dd, file=ee....ee, reason=ff....ff

Multivolume file reopen processing will be executed cc minutes later. The maximum retries count is bb, and the next retry number is aa. The file name is ee....ee at host dd....dd.

aa: Next retry number

bb: Maximum retry number

cc: Retry interval

dd....dd: Host name

ee....ee: File name

ff....ff: Reason for retry

S: Resumes processing.

Action

Set the next file during the retry.

KFPR00768-I L

File swapping started, file=aa....aa, reason=bb....bb

Processing of second or subsequent volume of multivolume file aa....aa has started.

aa....aa: File name

bb....bb: Reason code:

ENOSPC: Space ran out at the device.

EOV: End-of-volume was detected.

S: Resumes processing.

KFPR00786-I L+S

Differential recovery by manual mode

Recovery processing that does not use a differential backup management file is being started.

S: Continues processing.

KFPR16003-E L+S

aaaaaa error occurred, file=bb....bb

A file I/O error occurred.

aaaaaa: Processing resulting in the error:

Close: Close processing

Open: Open processing

Read: Read processing

Reopen: Opening of the second or subsequent volume of a multivolume file

Write: Write processing

bb....bb: File name

S: Terminates processing. In the case of the Close error, the system may resume processing.

Action

Refer to the message that was output after this message to eliminate the cause of the error, and re-execute the command.

KFPR16005-E L+S

Insufficient memory for PROCESS, size=aa....aa

An attempt to allocate a work area needed for executing the database copy utility (pdcopy) failed due to insufficient process private area.

aa....aa: Area size (in bytes) That was to be allocated

S: Terminates processing.

O: Contact the HiRDB administrator.

Action

Determine whether there are other processes that use a large amount of memory.

When there is a process using a large amount of memory:

Wait until the process terminates, and then re-execute the command.

When there is no process using a large amount of memory:

Use one of the following methods to ensure that there is sufficient memory:

Reduce the number of simultaneously executing processes.

Increase the size of the swap area.

Increase the amount of memory.

KFPR16014-E L+S

Pdcopy version aa....aa and HiRDB version bb....bb do not match

The version of the database copy utility (pdcopy) does not match the HiRDB version.

aa....aa: Version revision number of the database copy utility

bb....bb: Version revision number of HiRDB

S: Terminates processing.

Action

Execute the database copy utility using the version revision number that is the same as that of the HiRDB being used.

KFPR16102-E E+L

File operation was canceled by aa....aa

Multivolume file exchange was cancelled.

aa....aa: Reason for cancellation:

system: Processing was cancelled by the system.

user: Processing was cancelled by the user.

S: Terminates processing.

P: Re-execute the processing, if necessary.

KFPR16104-E L+S

Dynamic load error occurred, shared library=aa....aa

An error occurred during dynamic loading of a shared library required for processing.

aa....aa: Absolute path name of the shared library

S: Terminates processing.

O: Refer to the KFPR26003-E message that was output before this message.

In UNIX:

Resolve the error as follows, and then re-execute the command:

EasyMT used:
Check that the system has been installed correctly.

EasyMT not used:
Check the specification of the k option flag and correct the specification to nonuse of EasyMT or MTguide.

In Windows:

Review the value specified in the -k option flag, revise it if necessary, and then re-execute the command.

KFPR16108-E L+S

Present directory information conflicts with directory information specified when the backup file was made, RDAREA name="aa....aa", code=b

The present directory information does not match the directory information specified when the previous backup file was created. This mismatch is caused because the structure of the RDAREA has been modified since the previous backup file was made.

aa....aa: Name of RDAREA in which mismatch occurred

b: Error code:

1: Page size mismatch

2: RDAREA attribute mismatch

3: HiRDB file name mismatch

4: RDAREA name mismatch

5: Segment size mismatch

6: Mismatch in the number of HiRDB files comprising the RDAREA

7: RDAREA initialization date

S: Terminates processing.

Action

Use the pdcopy command to make a full backup. In this step, specify creation of a differential backup management file (specify (S) for the differential backup group name in the -g option).

KFPR16110-I L+S

Unable to get a backup file aa....aa

The backup file of a database cannot be created.

aa....aa: Name of backup file

S: If another backup file is specified, executes backup processing for that file. If no other backup file is specified, terminates processing.

Action

Refer to the error message that was output before this message to eliminate the cause of the error, and re-execute.

KFPR16126-E L+S

Master RDAREA is not initialized

The master directory RDAREA has not been initialized, or the specified file is not the master directory.
Possible causes of this error are as follows:

The database initialization utility (pdinit) did not terminate normally.

The specified file is not the master directory RDAREA.

The contents of the master directory RDAREA are damaged.

S: Terminates processing.

Action

Eliminate the cause of the error, correct the status of the master directory RDAREA, then re-execute.

Possible causes of the error are as follows:

A file other than the master directory was specified.

The database initialization utility (pdinit) did not terminate normally.

The contents of the master directory RDAREA are damaged.

In the case of item 1, make sure the file name of the master directory specified using the -m option is correct. If it is in error, correct it, and re-execute the command.

In the case of item 2, verify that the database initialization utility (pdinit) terminated normally, perform HiRDB startup processing, and re-execute the command.

If the error cannot be resolved by either of the above actions, it is possible that the contents of the master directory RDAREA are damaged. Either restore the master directory or contact the customer support center.

KFPR16127-E L+S

Page corrupted, RDAREA name="aa....aa", HiRDB file name=bb....bb, page no. =cc....cc

Page corruption was detected.

aa....aa: RDAREA name

bb....bb: HiRDB file name

cc....cc: Page number in HiRDB file bb....bb

S: Cancels RDAREA backup processing. If there is another backup file, the HiRDB system resumes processing.

Action

Contact the customer support center.

KFPR16129-E L+S

EasyMT error occurred, func=aa....aa, reason=bb....bb

An error occurred during I/O processing of a file used by EasyMT.

aa....aa: Function in which the error was detected

bb....bb: Error detail information

S: Terminates processing.

Action

Based on the error detail information, check the documentation for JP1/Magnetic Tape Access or EasyMT, eliminate the cause of the error, and then re-execute.

KFPR16203-E L+S

aaaaaa error occurred, file=bb....bb

A file I/O error occurred.

aaaaaa: Processing resulting in the error:

Close: Close processing

Open: Open processing

Read: Read processing

Reopen: Opening of the second or subsequent volume of a multivolume file

Write: Write processing

bb....bb: File name (If a system log file I/O error occurred, the file group name is indicated.)

S: Terminates processing. In the case of the Close error, the system may resume processing.

Action

Refer to the message that was output after this message to eliminate the cause of the error, and then re-execute the command. If a system log file I/O error occurred, refer to the message output before this message.

KFPR16205-E L+S

Insufficient memory for PROCESS, size=aa....aa

An attempt to allocate a work area needed for executing the pdrstr or pdbkupls command failed, due to an insufficient process private area.

aa....aa: Area size (in bytes) That was to be allocated

S: Terminates processing.

Action

Check whether there are processes that use a large amount of memory.

There are processes that use a large amount of memory:

Wait for the associated processes to terminate, then re-execute the command.

There are no processes that use a large amount of memory:

Use one of the following methods to ensure that there is sufficient memory:

Reduce the number of simultaneously executing processes.

Increase the size of the swap area.

Increase the amount of memory.

KFPR16214-E L+S

Pdrstr version aa....aa and HiRDB version bb....bb do not match

The version of the database recovery utility (pdrstr) does not match the HiRDB version.

aa....aa: Version revision number of the database recovery utility

bb....bb: Version revision number of HiRDB

S: Terminates processing.

Action

Execute the database recovery utility with the version revision number that is the same as that of the HiRDB being used.

KFPR16301-E L+S

File I/O error occurred, reason=aa....aa, func=bb....bb, errno=cc....cc, (dd....dd)

An error occurred during file I/O processing.

aa....aa: Cause of error:

Empty-file:

The specified file is empty (0 bytes).

File-format:

The specified file format differs from the actual file format. It is possible that the specified file name is incorrect or the file format specified on the command line or in the control statement does not match the contents.

File-lock:

The file to be used is locked by another utility and the file read/write operation cannot be executed. The file name specified in the command line or control statement might be in use by another job. In UNIX, there might be a shortage of file locking resources for an OS kernel parameter.

File-missing:

The specification of the unload log file or the backup file is incorrect. See the KFPR26265-I message that was output before or after this message, eliminate the cause of the error, and then re-execute.

File-sequence:

The sequence of volumes of a multivolume file is invalid.

Invalid-device:

The specified file entry type (attribute) is invalid. Or, if MTguide is being used, MTguide is not activated. If the system can identify the entry type, it displays one alphabetic character enclosed in parentheses. This character is the same as the entry in the mode output by the operating system's ls -l command. It is possible that a directory name was specified in a location that requires a file name (or vice versa), or that a character special file was assigned to a file where a character special file cannot be used.

Invalid-environment:

Because the set value obtained by the uname system call is invalid, a streaming tape device cannot be used. Check that the OS has been installed correctly or that the OS version satisfies the prerequisite conditions of the HiRDB system or related program products.

Invalid-file:

A file was specified that was created incorrectly.

Invalid-parameter:

A combination of specified parameters is invalid.

Invalid-permission:

The specified file version is invalid (access privilege error). It is possible that a file is being used, for which an access privilege has not been granted by a HiRDB administrator, or for MT, may be write-protected.

Invalid-path:

The path name is invalid.

No-file:

File to be opened for the read operation was not found, or a file involved in the write operation was deleted.

No-space:

There is not enough space in the file subject to the write operation. Revise the size or specify a multi-volume.

In UNIX, if this error occurs when there is sufficient disk space, it is possible that either the HiRDB file system area is not defined as a large file, or an operating system kernel parameter restriction applies.

In Windows, if this error occurs when there is sufficient disk space, it is possible that the HiRDB file system area is not defined as a large file (2048 MB or greater) in the pd_large_file_use operand.

No swap-file:

Multivolume swap file cannot be found. Check the size. Or, specify a multivolume file.

Same-file:

The same multivolume file as before was specified (files have not been exchanged). An attempt was made to reuse the same volume during write processing to a multivolume file.

Unmatch-entry:

Header entry for header file does not match the specification in the control statements file. The name of the unmatched entry is enclosed in parentheses.

bb....bb: Name of the function in which the error occurred

If an error was detected by the HiRDB file system, the HiRDB file system function names beginning with p_f_ios

If an error was detected when a function was not being used, ***

If other than the above, the system function name

cc....cc: Error number that is returned by the function (errno)

If an error was detected by the HiRDB file system, the HiRDB file system error code

If an error was detected when a function was not being used, 0

If an error was detected by the operating system, the error number returned by the system function (errno: foreign reference variable that displays the error status)

dd....dd: Name of the source file and the line number at which the error was detected.

S: If aa....aa is File_missing, processing continues according to the KFPR26265-I message output before or after this message. Otherwise, terminates processing.

Action

Take action based on the following table:

Error cause | Action
Error was detected by the HiRDB file system. | See 5.1 Error codes returned from HiRDB file system access requests, eliminate the cause of the error, and then re-execute.
Error was detected by mechanism other than a function. | From the error cause aa....aa, eliminate the cause of the error, and then re-execute.
Error was detected by the operating system. | Refer to the operating system manual, eliminate the cause of the error, and then re-execute.

If an error occurs on re-execution, contact the customer support center.

KFPR16302-E E+L

File operation was canceled by aa....aa

Multivolume file exchange was cancelled.

aa....aa: Reason for cancellation:

system: Cancelled by the system

user: Cancelled by the user

S: Terminates processing.

Action

Re-execute the processing, if necessary.

KFPR16303-E L+S

Invalid aa....aa log file, file=bb....bb

Log file bb....bb is invalid. Check the following:

For unload file:

Whether or not an invalid unload log file is specified

Whether or not both an unload log file before database initialization and an unload log file after database initialization are specified

For system log file:

Whether or not the database was initialized after the backup file was made

aa....aa: Log file type

unload: Unload log file

sys: System log file

bb....bb: Name of the log file for which the error or initialization was detected

For unload log file:

Name of unload log file

For system log file:

File group name

S: Terminates processing.

O:

For unload log file:
Specify the correct unload log file, and then re-execute. If unload log files made both before and after database initialization are specified, specify either unload log files made before database initialization or unload log files made after database initialization, and then re-execute.

For system log file:
Specify the backup file after database initialization, and then re-execute.

KFPR16304-E L+S

Dynamic load error occurred, shared library=aa....aa

An error occurred during dynamic loading of a shared library required for processing.

aa....aa: Full path name of the shared library

S: Terminates processing.

O: Refer to the KFPR26203-E message that was output before this message.

In UNIX:

Resolve the error as follows, and then re-execute the command:

EasyMT used:
Check that the system has been installed correctly.

EasyMT not used:
Check the specification of the -k option flag and correct the specification to nonuse of EasyMT or MTguide.

In Windows:

Review the value specified in the -k option, revise it if necessary, and then re-execute the command.

KFPR16308-E L+S

Present directory information conflicts with directory information specified when the backup file was made, RDAREA name="aa....aa", code=b

A conflict was detected between directory information for an RDAREA as specified in the master directory and as specified when a backup file was made; processing of the RDAREA is terminated.

aa....aa: Name of RDAREA containing contradictory information

b: Error code:

1: Page length does not match.

2: RDAREA attribute does not match.

3: RDAREA file name does not match.

4: RDAREA name does not match.

5: Segment size does not match.

6: RDAREA structure does not match the number of HiRDB files.

S: Processes the next RDAREA without recovering the RDAREA containing contradictory information.

Action

Take one of the following actions:

If the file name specified in the -m option for the first HiRDB file name of the master directory RDAREA is invalid, specify the correct file name, and re-execute the command.

If the configuration of the RDAREA was changed after the applicable backup file was acquired, these RDAREA configuration changes cannot be recovered. Either use a backup file acquired after the RDAREA configuration was changed or specify a time before the RDAREA configuration was changed, and then re-execute the command.

If the error cannot be resolved by either of the above actions, contact the customer support center.

KFPR16318-E L+S

Backup data not found, RDAREA name="aa....aa"

The specified backup file does not contain the backup data of the appropriate RDAREA.

aa....aa: Name of RDAREA whose backup data is missing

S: Recovers the RDAREA without using its backup data. If the unload log file is specified and the update log of the corresponding RDAREA is available, the system recovers the RDAREA only using log information. If the -L option is specified, the HiRDB system cancels processing.

Action

Check the items listed below, correct the error, and then re-execute:

Check the specification of the backup file for an error. If a tape drive is used, determine whether rewinding is specified.

If the -L option is specified, check that there is an RDAREA to be recovered in the backup file created by specifying the -z option for pdcopy execution.

KFPR16328-E L+S

aa....aa error occurred, func=bb....bb, return code=cc....cc

An error occurred during the processing of either of the following:

Sort processing

Magnetic tape I/O processing

aa....aa: Processing that generated the error

SORT: Sort processing

EasyMT: Magnetic tape I/O processing

bb....bb: Name of the function resulting in the error

cc....cc: Return code from the function resulting in the error

S: Terminates processing.

Action

Take the following action:

If aa....aa is SORT:
Refer to 7. Messages Related to Sort Processing, and take corrective action.
Messages related to sort processing are output in the format KBLSnnn-E, where nnn denotes the absolute value of the return code that is output to cc....cc.
The following table summarizes frequently output return codes and the required corrective action:

Return code
Action

-202
Memory shortage. Reduce the work buffer size for sorting specified in the -y operand of the database recovery utility.

-290
Work buffer shortage. Increase the work buffer size for sorting specified in the -y operand of the database recovery utility.

-210, -230
An I/O error occurred. It is possible that there is insufficient space on the disk storing the directory for sorting specified in the -w option of the database recovery utility. If insufficient disk space is the cause of the error, delete unnecessary files to increase the amount of free space. Alternatively, specify a directory on a disk with sufficient space in the -w option.

If the error cannot be resolved, acquire the sortdump, SORTIODUMP, and SORTDMP2 that are output to C:\Windows (in UNIX, /tmp or /usr/tmp), and contact the customer support center.

If aa....aa is EasyMT:
See the documentation for JP1/Magnetic Tape Access or EasyMT, and take the corrective actions indicated there. If no actions are listed in the documentation, or what is listed is not appropriate, contact the customer support center.

KFPR16329-E L+S

EasyMT error occurred, func=aa....aa, reason=bb....bb

An error occurred during I/O processing of a file used by EasyMT.

aa....aa: Function in which the error was detected

bb....bb: Error detail information

S: Terminates processing.

Action

Based on the error detail information, check the documentation for JP1/Magnetic Tape Access or EasyMT, eliminate the cause of the error, and then re-execute.

KFPR16330-E L+S

Log was not found when backup aa....aa at bb....bb -cc....cc, server=dd....dd

Recovery is to be from the backup copy created with the -M s option specified for the backup mode, but the input log does not contain the following log records required for recovery:

First log record

Last log record

aa....aa: Missing date and time:

started: Copy start time

ended: Copy end time

bb....bb: Log record number 1

cc....cc: Log record number 2

dd....dd: Name of server subject to recovery

S: Cancels recovery of the corresponding server.

Action

Specify the log containing the first or last log record required for recovery, and then re-execute.

KFPR16333-E L+S

RDAREA aa....aa at bb....bb, RDAREA name="cc....cc"

Because aa....aa has been executed on RDAREA "cc....cc", the corresponding RDAREA cannot be recovered from the backup copy that was created before that date. Or, no backup file was specified.

aa....aa: Type of RDAREA processing

added: RDAREA addition

altered: RDAREA alteration

deleted: RDAREA deletion

extended: RDAREA expansion

initialized: Reinitialization

bb....bb: Date and time the RDAREA was expanded

cc....cc: Name of expanded RDAREA

S: Recovers the next RDAREA without recovering the indicated RDAREA.

Action

Recover the RDAREA using the correct backup file and log obtained after the RDAREA processing. If no backup file was obtained after manipulation, specify a time bb....bb earlier than the recovery end time of the -T option, and then recover the RDAREA.

KFPR16334-E L+S

RDAREA was updated by logless process, RDAREA name="aa....aa", update time=bb....bb

Because the indicated RDAREA was updated at time bb....bb by a transaction that does not collect a system log, the RDAREA cannot be recovered.

aa....aa: RDAREA name

bb....bb: Update time

S: Recovers the next RDAREA without recovering the indicated RDAREA.

Action

Re-execute using the backup created after the transaction that does not collect a system log has terminated. If there is no backup, specify a time bb....bb earlier than the recovery end time of the -T option.

KFPR16338-E L+S

Master RDAREA is not initialized

The master directory RDAREA has not been initialized or the specified file is not the master directory. Possible causes of this error are as follows:

The database initialization utility (pdinit) did not terminate normally.

The specified file is not the master directory.

The contents of the master directory are damaged.

S: Terminates processing.

Action

Eliminate the cause of the error, correct the status of the master directory RDAREA, and then re-execute.

Possible causes of the error are as follows:

A file other than the master directory was specified.

The database initialization utility (pdinit) did not terminate normally.

The contents of the master directory RDAREA are damaged.

In the case of item 1, make sure the file name of the master directory specified using the -m option is correct. If it is in error, correct it, and re-execute the command.

In the case of item 2, verify that the database initialization utility (pdinit) terminated normally, perform HiRDB startup processing, and re-execute the command.

If the error cannot be resolved by either of the above actions, it is possible that the contents of the master directory are damaged. Either restore the master directory or contact the customer support center.

KFPR16339-E L+S

Invalid backup file, file=aa....aa

The specified backup file is invalid. Check the following:

Whether or not the correct volume was specified in the multivolume specification

Whether or not the correct file was specified in the multi-file specification

aa....aa: Invalid file contents

If Mtguide is used: Device symbolic name or device group name

If Mtguide is not used or in the Windows edition: File name

S: Terminates processing.

Action

Specify the correct backup file, and then re-execute.

KFPR26001-E E+L+S

Communication "aa....aa" error occurred, code=bbbbb

A communication error occurred while executing the database copy utility (pdcopy).

aa....aa: Name of RPC-related function resulting in the error

bbbbb: Error code from the RPC-related function resulting in the error

S: Terminates processing.

Action

See 4. Error Detail Codes to eliminate the cause of the error, and then re-execute. If the error cannot be corrected by the HiRDB administrator, contact the customer support center.

KFPR26002-E L+S

Unable to allocate COMBUF area, size=aaaaaa

A communication area cannot be allocated because a real or virtual memory space shortage occurred.

aaaaaa: Size (in KB) of communication area that was to be allocated

S: Terminates processing.

Action

Re-execute the command after a process that uses a large amount of memory has terminated.

If a value greater than 32 was specified for the buffer size (pd_utl_buff_size operand) in the system common definition, specify 32, and then re-execute the command.

KFPR26003-E L+S

System call error, func=aa....aa, errno=bbb

A system call error occurred.
If the name of the system call is system(pdrdrefls), this indicates that the database copy utility finished copying and terminated normally, but the pdrdrefls command, which is executed internally, did not executed correctly.

aa....aa: Name of the system call resulting in the error

bbb: errno value of the system call resulting in the error

S: Continues processing when the name of the system call is system(pdrdrefls). Terminates processing in all other cases.

Action

Take one of the following actions:

If errno is 0, refer to the processing result output file, eliminate the cause of the error based on the pdrdrefls command messages that were output under <<PDRDREFLS RESULT>>, and then re-execute the pdrdrefls command. If there is a missing RDAREA in the execution results of the pdrdrefls command, add the relevant RDAREA to the copy target, and then re-execute the database copy utility. Note that if the only message output to <<PDRDREFLS RESULT>> is KFPT02004-W, it is not necessary to re-execute the pdrdrefls command.

If errno has a value other than 0, check the value of the error indicator and refer to errno.h or the applicable OS manual to eliminate the cause of the error, and then retry the operation.

KFPR26004-I E

Error exists in command line or control file, usage is as follows

An error was detected in the specified command or control statements file. The correct usage is displayed after this message.

S: Terminates processing.

O: Correct the error in the command or control statements file and re-execute.

KFPR26005-E E+L

Invalid option flag exists in command line

The command line contains an invalid option.

S: Cancels processing after analyzing the command line.

Action

Correct the command line specification and re-execute.

If there are no errors in the command line specification, check whether there are spaces before or after the commas separating the flag arguments, and if there are spaces, remove them and re-execute.

KFPR26006-E E+L+S

Invalid parameter aa....aa exists at -b option in command line

An option on the command line contains an invalid parameter. If it is a list RDAREA or temporary table RDAREA, it will not be copied.

aa....aa: Invalid parameter

b: Option name

S: Cancels processing after analyzing the command line. However, continues processing when all of the following conditions are met:

The -J or -r option is specified.

The KFPR26061-W message was output.

Action

Correct the specification on the command line and re-execute.

If you need to correct the pattern character string of the RDAREA batch specification, see the manual HiRDB Version 9 Command Reference to determine how to specify a correct pattern character string, and then re-execute the command.

KFPR26007-E E+L+S

Duplicate aa....aa at -b option in command line

Information is duplicated in an option on the command line.
If the differential backup facility is used, an existing differential backup file name is specified in the -b option.

aa....aa: Duplicated command name

b: Option name

S: Terminates processing after analyzing the command line.

Action

Correct the specification on the command line and re-execute.

KFPR26008-E E+L+S

Invalid combination of option flags(-a and -b) exists in command line

There is an invalid combination of option flags on the command line.

a: Option flag combined invalidly

b: Option flag combined invalidly

S: Terminates processing after analyzing the command line.

Action

Correct the specification on the command line and re-execute.

KFPR26009-E E+L

Option flag -a is not specified in command line

A required option flag is missing on the command line.

a: Required option flag

S: Terminates processing after analyzing the command line.

Action

Correct the specification on the command line and re-execute.

KFPR26010-E E+L+S

Too long parameter exists at -a option in command line

Parameter specification for an option is too long on the command line.

a: Option name

S: Terminates processing after analyzing the command line.

Action

Correct the specification on the command line and re-execute.

KFPR26011-E E+L

Number of -a option flag in a control file exceeds bb

The number of -a option flags in a control statements file exceeds the maximum of bb.

a: Name of the option exceeding the maximum value

bb: Maximum value of -a option flag

S: Terminates processing after analyzing the command line.

Action

Correct the specification on the command line and re-execute.

KFPR26012-E L+S

HiRDB file aa....aa error, errno=bb....bb, HiRDB file name=cc....cc

Error aa....aa occurred in file cc....cc.

aa....aa: Nature of the error:

close: Close file

create: Create file

fstat: Collect file information

open: Open file

read: Read file

write: Write data to file

expand: Expand file

reopen: Opening of the second or subsequent volume of a multivolume file

bb....bb: Error code

0: Could not perform read or write of the requested size.

Other: See 5.1 Error codes returned from HiRDB file system access requests.

cc....cc: Name of the file where the error occurred

S: For a backup file, aborts processing. However, continues processing when there is another backup file or all of the following conditions are met:

The applicable file is a HiRDB file comprising the RDAREA.

The -J option is specified or the RDAREA is a replica RDAREA.

The content of the error is open or close.

The KFPR26061-W message is output.

Other RDAREAs were not processed.

Action

For database file:

Recover the RDAREA and re-execute.

For backup file:

See 5.1 Error codes returned from HiRDB file system access requests to eliminate the cause of the error and re-execute.

If the error code is -1556 or -1562, the following causes can be assumed:

Error code
Cause

-1556
Secondary allocation expansion of the file failed because the HiRDB file had been expanded the maximum permissible number of times:

An attempt was made to expand the file more times than permitted by the increments count specification (-e specification for pdfmkfs) for the HiRDB file system area

An attempt was made to expand the HiRDB file more than 23 times (the maximum for the system)

-1562
Type of the HiRDB file system area is not UTL.

If the cause cannot be determined, contact the customer support center.

KFPR26015-E L+S

Unable to backup RDAREA at inactive server aa....aa

When either of the following options is specified, an RDAREA in an inactive server cannot be backed up:

-M s

-z

aa....aa: Name of the inactive server

S: Terminates processing if the RDAREA included in the applicable server is to be copied. However, if there are other backup files, continues processing if all of the following conditions are met:

The -J option is specified.

The KFPR26061-W message is output.

Other RDAREAs were not processed.

Action

Activate the stopped server and re-execute. Or, back up the RDAREA with the -M x option specified.

KFPR26017-E L+S

Insufficient memory in message buffer pool due to concurrent execution of "pdcopy"

A temporary memory shortage occurred in the message storage buffer pool during process allocation when the database copy utility (pdcopy) was executed concurrently.

S: Terminates processing.

Action

Too many utilities were executed concurrently. Review and, if necessary, revise the maximum number of utilities that can be executed at the same time. To find out the maximum number of utilities that can be executed concurrently, see the manual HiRDB Version 9 Command Reference.

KFPR26018-E L+S

Unable to send message from aa....aa to bb....bb

Data cannot be sent from host aa....aa to host bb....bb because a communication error occurred.

aa....aa: Send source host name

If the system switching facility is being used, the host name of the primary system is indicated.

bb....bb: Send destination host name

If the system switching facility is being used, the host name of the primary system is indicated.

S: Cancels processing of the backup file resulting in the communication error.

Action

Take action appropriate to the KFPR26001-E message that was output before this message. If a physical communication error has not occurred, there may be an inconsistency in the system definitions concerning the relationship between the hosts; check the interhost definitions for the hosts affected by the error and re-execute.

KFPR26020-E L+S

System manager "aa....aa" failed, return code=bb....bb

System-related function "aa....aa" resulted in an error.

aa....aa: Name of the system-related function resulting in the error

bb....bb: Error code set by the system-related function resulting in the error

S: Terminates processing.

Action

See 4. Error Detail Codes to eliminate the cause of the error, and re-execute. If the error cannot be corrected by the HiRDB administrator, contact the customer support center.

KFPR26021-E L+S

Unable to output result of pdcopy

The result of the database copy utility (pdcopy) cannot be output due to the error reported before this message.

S: Terminates processing.

Action

Eliminate the cause of the error and re-execute. If no other error occurred, backup processing terminated; if the execution result is not needed, there is no need to re-execute the processing.

KFPR26022-I L+S

Output result of pdcopy to aa....aa

The result of the database copy utility (pdcopy) was output to file aa....aa.

aa....aa: Name of output file

S: Terminates processing.

KFPR26023-I L+S

Unable to output result of backup file aa....aa

The processing result of backup file aa....aa cannot be output due to the error reported before this message.

aa....aa: Backup file name

S: Terminates processing.

Action

Eliminate the cause of the error and re-execute. If the KFPR26109 message was issued for the backup file, backup processing was terminated; if the execution result is not needed, there is no need to re-execute the processing.

KFPR26024-E L+S

Unable to remove shared memory, key=aa....aa

Shared memory cannot be deleted.

aa....aa: Shared memory key value

S: Resumes processing.

Action

Use a command to delete the shared memory after processing has terminated.

KFPR26025-E L+S

No RDAREA to copy on aa....aa

Backup file aa....aa does not contain the RDAREA to be copied.

aa....aa: Name of backup file (the last portion of the path name)

S: Terminates processing. However, continues processing when both of the following conditions are met.

The -J option is specified.

Multiple rows in the control statements file are specified.

Action

Correct the specification on the command line and re-execute.

KFPR26026-E L+S

Unable to copy RDAREA's of different servers with -z option

When the -z option is specified, a backup file of RDAREAs in different servers cannot be made concurrently.

S: Terminates processing.

Action

Make the backup file of RDAREAs in the same server and re-execute.

KFPR26027-E L+S

Unable to output Log point information

Log point information cannot be output because of the error indicated by the error message output before this message.

S: Terminates processing.

Action

Eliminate the cause of the error, input the backup file created with pdrstr, then re-create the log point information file by specifying the -z option.

KFPR26028-I L+S

Output Log point information to aa....aa

Log point information has been output to log point information file aa....aa.

S: Resumes processing.

KFPR26029-I L+S

Log point information, (aa....aa, bb....bb, ccc, dd....dd, ee....ee, ff....ff, gg....gg, hh....hh, ii....ii. jj....jj, kk....kk)

Log point has been set.

aa....aa: HiRDB identifier

bb....bb: Unit identifier

ccc: Log file name:

sys: System log file

dd....dd: Server name

ee....ee: Server run ID (8 hexadecimal digits)

ff....ff: Log server run ID (8 hexadecimal digits)

gg....gg: Name of first file group

hh....hh: Generation number of first file group (up to 8 hexadecimal digits)

ii....ii: First block number (up to 8 hexadecimal digits)

jj....jj: Header updates count (up to 8 hexadecimal digits)

kk....kk: Use start time (8 hexadecimal digits)

S: Resumes processing.

KFPR26030-E L+S

Unable to use -M s option to RDAREA for BLOB column with recovery partial or no, RDAREA name=aa....aa

The -M s option cannot be used for the RDAREA containing the target LOB column because recovery partial or recovery no was specified in the LOB column definition of CREATE TABLE.

aa....aa: Name of RDAREA that caused the error

S: Terminates processing if the applicable RDAREA is to be copied. However, continues processing if there are other backup files or all of the following conditions are met:

The -J option is specified.

The KFPR26061-W message is output.

Other RDAREAs were not processed.

O: Specify -M x or -M r and re-execute.

KFPR26031-E L

Unable to output message to standard output, host=aa....aa, file=bb....bb, func=cc....cc, errno=ddd

Messages cannot be output to standard output because a system call error occurred.

aa....aa: Name of the host where the file resulting in the error is located

bb....bb: Name of the file resulting in the error

When the name of the system call resulting in the error is tempnam, ****** is displayed.

cc....cc: Name of the system call resulting in the error

In UNIX, the name of the shell command that was executed is displayed, enclosed in parentheses.

ddd: errno of the system call resulting in the error

S: Resumes processing.

O: Check the value of the error indicator and refer to errno.h or the applicable OS manual to eliminate the cause of the error.

KFPR26032-E L

Unable to remove temporary file, host=aa....aa, file=bb....bb

A temporary file cannot be deleted because of the error that was output before this message.

aa....aa: Name of the host where the file that cannot be deleted is located

bb....bb: File name that cannot be deleted

S: Resumes processing.

O: Waits until processing terminates, then delete the temporary file.

KFPR26033-E L+S

Pdcopy must be executed at unit defined as manager

The database copy utility (pdcopy) must be executed at the unit where the system manager is defined.

S: Terminates processing.

O: Execute remote login at the unit where the system manager (MGR) is defined and re-execute the command.

KFPR26050-E L+S

PDDIR not defined

Environment variable PDDIR has not been set.

S: Terminates processing.

Action

Set the environment variable PDDIR, and then re-execute the database copy utility (pdcopy).

KFPR26051-E L+S

Unable to output history of backup group=aa....aa

Statistical information on differential backup group aa....aa could not be output. For the error cause, refer to the message that was output before this message.

aa....aa: Differential backup group name

S: Terminates processing.

Action

Correct the error and re-execute. If the KFPR26053-I or KFPR26058-I message has been output for the differential backup management file, the backup processing terminated. Therefore, if the history information is not needed, re-execution is not necessary.

KFPR26052-I L+S

Output history of backup group=aa....aa to bb....bb

Displays the statistical information file (file name bb....bb) for differential backup group aa....aa.

aa....aa: Differential backup group name

bb....bb: Name of the statistical information file for the differential backup

S: Continues processing.

KFPR26053-I L+S

Create management file=aa....aa

Differential backup management file aa....aa has been created.

aa....aa: Differential backup management file name

S: Continues processing.

KFPR26054-E L+S

Unable to use management file, reason=aa....aa, name=bb....bb

Differential backup management file bb....bb cannot be used.

aa....aa: Reason:

unfinish maintenance: Maintenance is not completed.

no control block: Control information for the differential backup management file was not found.

bb....bb: Differential backup management file name

S: Terminates processing.

Action

Take one of the following actions:

unfinish maintenance:
If there is a backup of the differential backup management file, use the pdfrstr command to recover the differential backup management file and re-execute. If there is no backup of the differential backup management file, make a backup with the pdcopy command. In this step, specify creation of a differential backup management file (specify (S) for the differential backup group name in the -g option).

no control block:
The specifications of the -g and -K options for the pdcopy command are invalid; make another backup.

KFPR26055-E E+L

Page corrupted, management file name=aa....aa, page number=bb....bb

Page corruption of differential backup management file aa....aa was detected.

aa....aa: Differential backup management file name

bb....bb: Page number in which page corruption was detected

S: Terminates processing.

Action

If there is a backup of the differential backup management file, use the pdfrstr command to recover the differential backup management file and re-execute. If there is no backup of the differential backup management file, make a backup with the pdcopy command. In this step, specify creation of a differential backup management file (specify (S) for the differential backup group name in the -g option).

KFPR26056-E L+S

SystemID of aa....aa is invalid

The file cannot be used because the system ID for aa....aa does not match the system ID of the HiRDB that is running.

aa....aa: File type

management file: Differential backup management file

S: Terminates processing.

Action

The differential backup management file is specified incorrectly. In the KFPR26006-E message that is output simultaneously, check the parameters for the -g and -K options, specify the correct parameters for these options, and re-acquire a differential backup.

KFPR26057-I L+S

Update start, management file name=aa....aa

Updating of differential backup management file aa....aa has begun.

aa....aa: Differential backup management file name

S: Continues processing.

KFPR26058-I L+S

Update complete, management file name=aa....aa

Updating of differential backup management file aa....aa has been completed.

aa....aa: Differential backup management file name

S: Continues processing.

KFPR26059-E E+L

Too many lines for control file

There are too many lines in the command line in the control statements file.

S: Terminates processing.

Action

Correct the command in the control statements file. When using the differential backup facility, enter only one row in the command line described in the control statements file. If the -a or -q option is specified, enter only one line in the command line described in the control statements file.

KFPR26060-I L+S

Backup all used page, RDAREA name=aa....aa, LSN=bb....bb, differential base LSN=cc....cc

Because differential management information for the differential backup could not be obtained, all used pages in this RDAREA will be included. This backup can be used for database recovery.

aa....aa: RDAREA name

bb....bb: Internal information 1

cc....cc: Internal information 2

S: Continues processing.

KFPR26061-W L+S

Unable to backup RDAREA. RDAREA name=aa....aa

aa....aa could not be backed up.

aa....aa: RDAREA name

S: Continues processing.

Action

If RDAREA aa....aa should not be copied, no particular action is required. If RDAREA aa....aa is to be copied, see the message output before or after this message to eliminate the cause of the error, and then re-execute.

KFPR26062-W L+S

Unable to find RDAREA. RDAREA name=aa....aa, generation number=bb

The RDAREA of the specified generation number could not be found. The process for backing up this RDAREA was skipped.

aa....aa: RDAREA name

bb: Generation number

S: Continues processing.

Action

Reevaluate the specified RDAREA name or generation number. If a backup is necessary, correct the RDAREA name or generation number, and then re-execute. If a backup is not required, ignore this message.

KFPR26063-I L+S

Buckup partially ended, file=aa....aa

Backup file aa....aa could not be created. The RDAREA causing an error during the backup process was skipped.

aa....aa: Backup file name

S: Continues processing.

Action

Check if the RDAREA whose processing was skipped is needed as a backup. If it is, eliminate the cause of the error, and then re-execute.

KFPR26066-E L+S

Unable to use the "-k n" option because the JP1/VERITAS NetBackup Agent for HiRDB license not found

The -k n option cannot be specified because the license required to use the JP1/VERITAS NetBackup linkage facility is missing.

S: Terminates processing.

Action

Obtain and install the license required to use the JP1/VERITAS NetBackup linkage facility.

KFPR26067-E L+S

Dynamic load error occurred, shared library=aa....aa, host=bb....bb

Dynamic loading of common library aa....aa on host bb....bb failed.

aa....aa: Full path name of the shared library (in UNIX, the file path name of the shared library)

bb....bb: Host name

S: Terminates processing.

Action

Check if a NetBackup client is installed. If a copy is installed, see the KFPR26003-E message just output to eliminate the cause of the error, and then re-execute.

KFPR26069-E L+S

NetBackup API error occurred, return code=aa....aa(bbbb), func=cc....cc, message=dd....dd

A problem occurred in the application programming interface of NetBackup.

aa....aa: Name of the application programming interface return code for NetBackup

bbbb: Application programming interface return code for NetBackup (hexadecimal)

cc....cc: Application programming interface for NetBackup

dd....dd: The message obtained after the application programming interface error return for NetBackup (displays the first 100 characters if the message length exceeds 100 characters)

S: Terminates processing.

Action

Return code (bbbb) | Return code name (aa....aa) | Meaning | Action
0x03 | SYSTEM_ERROR | NetBackup internal error | Check the error cause at the NetBackup management console, take appropriate action, and then re-execute.
0x0D | FEATURE_NOT_LICENSED | No license was found or the license was invalid | Obtain a license.
0x4B | VERSION_NOT_SUPPORTED | NetBackup version is not supported | Check if the NetBackup version is correct.
0x4D | ACCESS_FAILURE | Cannot access the object | Check if the NetBackup master server or NetBackup media server stopped. If the server did not stop, contact the customer support center#.
Other | -- | -- | Contact the customer support center#.

--: Does not apply.

#: Obtain the following data before contacting the customer support center:

The system log file of the host with a single server or system manager, the host with the -b option specified, or the host with the target RDAREA when executing the utility

Files in the %PDDIR%\spool directory on the host with a single server or system manager, the host with the -b option specified, or the host with the target RDAREA when executing the utility

Error information from the NetBackup management console

Messages output to standard output or standard error

Process results output file from when the utility was executed

KFPR26071-I L+S

NetBackup information, policy=aa....aa, date=bb....bb, time=cc....cc

Obtain a backup with policy name aa....aa.

aa....aa: Policy name

bb....bb: Date (YYYY/MM/DD)

cc....cc: Time (HH:MM:SS)

S: Continues processing.

KFPR26072-E L+S

Invalid time stamp found, RDAREA name=aa....aa, file name=bb....bb, offset=cc....cc, time stamp=(dd....dd,ee....ee)

Some of the pages were found to have an invalid timestamp.

aa....aa: RDAREA name

bb....bb: HiRDB file name. The last 64 bytes are displayed.

cc....cc: Relative position, in decimal, of the pages with an invalid timestamp from the front of the HiRDB file.

dd....dd: Timestamp at the start of the page. It is converted to the format YYYY/MM/DD HH:MM:SS for display.

ee....ee: Timestamp at the end of the page. It is converted to the format YYYY/MM/DD HH:MM:SS for display.

S: Terminates processing.

Action

If the backup is collected in reference updatable mode (pdcopy -Ms):

A backup cannot be acquired because the page to be backed up is undergoing update. Take one of the following actions:

Execute the pdlogsync -w command and re-execute.

Perform an updatable backup hold (pdhold -b -u) and re-execute.

Re-execute in referenceable mode (pdcopy -Mr) or in reference non-updatable mode (pdcopy -Mx).

If backing up in referenceable mode (pdcopy -Mr) or reference non-updatable mode (pdcopy -Mx):

The area of the displayed RDAREA is corrupt. The previous backup must be used to recover.

KFPR26073-E L+S

Unable to backup shared RDAREA with -M s option, RDAREA name="aa....aa"

Backup of the shared RDAREA could not be performed using the pdcopy -M s specification (updatable mode).

aa....aa: RDAREA name

S: Terminates processing.

Action

To back up multiple RDAREAs, including shared RDAREAs, at one time, specify a mode other than updatable mode and re-execute the command.

To back up in multiple parts, specify only the non-shared RDAREAs and re-execute the command. For the shared RDAREAs, specify a backup mode other than updatable mode and re-execute the command.

KFPR26074-W L+S

Result file not output

The result file could not be output.

S: Continues processing.

Action

In the following directories, check whether there is a large quantity of stored result files for names beginning with pdcp1. If there is a large quantity of result files, make sure that all database copy utilities (pdcopy) have terminated, and then either delete unnecessary result files or move them to another directory.
In UNIX:
/tmp, /var/tmp, or environment variable TMPDIR
In Windows:
Environment variable TMP or TEMP, or %PDDIR%\tmp

If the KFPR00756-I message that was output at about the same time as this message indicates that a return code of 0 was received from the database copy utility (pdcopy), you do not need to re-execute.

KFPR26075-I L+S

Last time of in-memory db-sync=aa....aa (bb....bb), RDAREA name="cc....cc"

The most recent time when the RDAREA cc....cc and the in-memory data buffer were synchronized is aa....aa.

aa....aa: Most recent time when synchronization processing was conducted

bb....bb: Internal information

cc....cc: RDAREA name

S: Continues processing.

Action

When acquiring the backup, pay attention to the following precautions.

For details about precautions related to backup acquisition during in-memory processing, see Notes about acquiring backups in the manual HiRDB Version 9 Batch Job Accelerator.

If the RDAREA recovers to the most recent status when the unload log file is used when an error occurs, then you must save everything back to the unload log file, which contains the oldest output time.

To acquire backups in the most recent status, perform one of the following operations on all of the relevant in-memory RDAREAs, and then acquire a backup.
- Acquire synchronization of the RDAREA and in-memory data buffers.
- Release in-memory allocation.

KFPR26089-W L+S

Insufficient of RDAREA about relation

The specification of the relevant copy target RDAREA is missing.
Even though this message was displayed, the copying processing terminated normally.

S: Continues processing.

Action

Examine the processing result output file and add the RDAREA indicated in message KFPT02028-W under <<PDRDREFLS RESULT>> to the copy target, and then re-execute the database copy utility. If the RDAREA indicated in message KFPT02028-W was intentionally removed from the copy target, ignore this message.

KFPR26109-I L+S

Backup completed, file=aa....aa

Database has been backed up into backup file aa....aa.

aa....aa: Name of backup file

S: Resumes processing.

KFPR26110-E L+S

Invalid RDAREA status, RDAREA name="aa....aa"

Because the status of the indicated RDAREA is invalid, it cannot be backed up.
Possible causes of this error are as follows:
(1) -M x was specified, but the specified RDAREA was not in closed status.
(2) The specified RDAREA is being used by another user. Consider the following causes:

-M r was specified, but another user is executing an update SQL statement.

-M x was specified, but another user is modifying the structure.

-M s was specified, but another user executed an SQL statement that caused the page to be released, a conflict occurred for resource type 0152 or 0004, and the process might be waiting for lock release until the transaction terminates. The following SQL statements cause pages to be released:
DROP TABLE
DROP INDEX
PURGE TABLE
An INSERT statement or UPDATE statement for an indexed column
A DELETE statement for an indexed column (with multiple keys)
A DELETE statement or UPDATE statement with variable row length after executing the LOCK statement
An INSERT statement, DELETE statement, or UPDATE statement for a LOB column

(3) The specified RDAREA is shut down due to an error.
(4) -M s was specified, but an in-memory RDAREA was made the backup target.
(5) The -z option was specified for an in-memory RDAREA.
(6) An in-memory RDAREA was made the differential backup target.

aa....aa: RDAREA name

S: Terminates processing when the applicable RDAREA is to be copied. However, continues processing if there is another backup file or if all the following conditions are met:

The -J option is specified.

The KFPR26061-W message is output.

There are other unprocessed RDAREAs.

Action

Perform one of the following corrective actions:

Place the specified RDAREA in closed status with the pdclose command and re-execute.

If another user is using the specified RDAREA, wait until the other user's process terminates, and then retry the operation.

If an error occurred in the RDAREA, change the status of the RDAREA (for example, by recovering or re-opening the RDAREA), and then retry the operation.

If you are specifying -M s to make a backup of an in-memory RDAREA, release the RDAREA from in-memory allocation, and then retry the operation. Alternatively, make the backup by specifying either -M x or -M r.

If you are specifying the -z option for an in-memory RDAREA, release the RDAREA from in-memory allocation, and then retry the operation. Alternatively, do not specify the -z option.

If you are making a differential backup of an in-memory RDAREA, release the RDAREA from in-memory allocation, and then retry the operation. Alternatively, do not use the differential backup function.

KFPR26111-E L+S

To copy Master RDAREA with -M x option, pdstart should be executed with -r option

Start the HiRDB system with pdstart -r when backing up the master RDAREA with -M x specified.

S: Terminates processing. However, continues processing when all of the following conditions are met.

The -J option is specified.

The KFPR26061-W message was output.

There are other unprocessed RDAREAs.

O: Terminate the HiRDB system using the pdstop command, restart it with pdstart -r, then re-execute.

KFPR26201-E E+L+S

Communication "aa....aa" error occurred, code=bbbbb

A communication error occurred while the database recovery utility (pdrstr) was being executed.

aa....aa: Name of the RPC-related function resulting in the error

bbbbb: Error code set by the RPC-related function resulting in the error

S: Terminates processing.

Action

See 4. Error Detail Codes to eliminate the cause of the error, and re-execute. If the error cannot be corrected by the HiRDB administrator, contact the customer support center.

KFPR26202-E L+S

Unable to allocate COMBUF area, size=aaaaaa

A communication area cannot be allocated because a real or virtual memory space shortage occurred.

aaaaaa: Size (in KB) of communication area that was to be allocated

S: Terminates processing.

Action

Re-execute the command after a process that uses a large amount of memory has terminated.

In UNIX, If a value greater than 32 was specified for the buffer size (pd_utl_buff_size operand) in the system common definition, specify 32, and then re-execute the command.

KFPR26203-E L+S

System call error, func=aa....aa, errno=bbb

A system call error occurred.
When the name of the system call is system(pdrdrefls), this indicates that the database recovery utility's recovery processing terminated normally, but the pdrdrefls command, which is executed internally, was not executed correctly.

aa....aa: Name of the system call resulting in the error

bbb: errno value of the system call resulting in the error

S: Continues processing when the name of the system call is system(pdrdrefls). Terminates processing in all other cases.

Action

Take one of the following actions:

If errno is 0, refer to the processing result output file, eliminate the cause of the error based on the pdrdrefls command messages that were output under <<PDRDREFLS RESULT>>, and then re-execute the pdrdrefls command. If there is a missing RDAREA in the execution results of the pdrdrefls command, add the relevant RDAREA to the recovery target, and then re-execute the database recovery utility. Note that if the only message output to <<PDRDREFLS RESULT>> is KFPT02004-W, it is not necessary to re-execute the pdrdrefls command.

If errno has a value other than 0, check the value of the error indicator and refer to errno.h or the applicable OS manual to eliminate the cause of the error, and then retry the operation.

KFPR26204-I E

Error exists in command line or control file, usage is as follows

An error was detected in the specified command or control statements file. The correct usage is displayed after this message.

S: Terminates processing.

O: Correct the error in the command or control statements file and re-execute.

KFPR26205-E E+L

Invalid option flag exists in command line

The command line contains an invalid option.

S: Terminates processing after analyzing the command line.

Action

Correct the command line specification and re-execute.

If there are no errors in the command line specification, check whether there are spaces before or after the commas separating the flag arguments, and if there are spaces, remove them and re-execute.

KFPR26206-E E+L+S

Invalid parameter aa....aa exists at -b option in command line

An option on the command line contains an invalid parameter. If it is a list RDAREA or temporary table RDAREA, it is not eligible for recovery.

aa....aa: Invalid parameter

b: Option name

S: Terminates processing after analyzing the command line.

Action

Correct the specification on the command line and re-execute.

If you need to correct the pattern character string of the RDAREA batch specification, see the manual HiRDB Version 9 Command Reference to determine how to specify a correct pattern character string, and then re-execute the command.

KFPR26207-E E+L

Duplicate aa....aa at -b option in command line

Information is duplicated in an option on the command line.

aa....aa: Duplicated name

b: Option name

S: Terminates processing after analyzing the command line.

Action

Correct the specification on the command line and re-execute.

KFPR26208-E E+L

Invalid combination of option flag (-a and -bb....bb) exists in command line

There is an invalid combination of option flags on the command line.

a: Option flag combined invalidly

bb....bb: Option flag combined invalidly

If "(in control file)" is output after the option flag is combined invalidly, this indicates that the option flags on the command line and the option flags in the control statement are combined invalidly.

S: Terminates processing after analyzing the command line.

Action

Revise the command line or control statement specification and re-execute.

KFPR26209-E E+L

Option flag -aa....aa is not specified in command line

A required option flag is missing on the command line.

aa....aa: Required option flag

If the required option flag is a selection item, all selection candidates are output.

S: Terminates processing after analyzing the command line.

Action

Revise the command line specification and re-execute.

KFPR26210-E E+L+S

Too long parameter exists at -a option in command line

Parameter specification for an option is too long on the command line.

a: Option name

S: Terminates processing after analyzing the command line.

Action

Correct the specification on the command line and re-execute.

KFPR26212-E L+S

HiRDB file aa....aa error , errno=bb....bb, HiRDB file name=cc....cc

Error aa....aa occurred in file bb....bb.

aa....aa: Nature of error:

close: Close file

create: Create file

fstat: Collect file information

open: Open file

read: Read file

write: Write data to file

expand: Expand file

reopen: Open the second or subsequent volume of a multivolume file

bb....bb: Error code

0: Could not perform a read or write in the requested size.

Other: See 5.1 Error codes returned from HiRDB file system access requests.

cc....cc: Name of the file resulting in the error

S:

For database file:

Skips recovery processing of the affected RDAREA and resumes recovery processing of other RDAREAs.

For backup file:

Cancels recovery processing.

Action

For database file:

Provide a separate HiRDB file system area for the affected RDAREA and re-execute.

For backup file:

Use another backup file and re-execute.

If the error content is write and the error code is 0, the operating system file system may have a capacity shortage. If the error content is read and the error code is 0, the error may have occurred when only the log was recovered for the RDAREA of the HiRDB file system area created without specifying the -i option with the pdfmkfs command.

If the cause of the error cannot be determined, contact the customer support center.

KFPR26215-E L+S

Unable to recover RDAREA at inactive server aa....aa

An RDAREA in an inactive server cannot be recovered with -l, -L, or -d specified.

aa....aa: Name of the inactive server

S: Cancels recovery of the RDAREA in this server.

Action

Activate the stopped server and re-execute.

KFPR26217-E L+S

Insufficient memory in message buffer pool due to concurrent execution of "pdrstr"

A temporary memory shortage occurred in the message storage buffer pool during process allocation when the database recovery utility (pdrstr) was executed concurrently.

S: Terminates processing.

Action

Too many utilities were executed concurrently. Review and, if necessary, revise the maximum number of utilities that can be executed at the same time. To find out the maximum number of utilities that can be executed concurrently, see the manual HiRDB Version 9 Command Reference.

KFPR26218-E L+S

Unable to send message from aa....aa to bb....bb

Data cannot be sent from host aa....aa to host bb....bb because a communication error occurred.

aa....aa: Send source host name

If the system switching facility is being used, the host name of the primary system is indicated.

bb....bb: Send destination host name

If the system switching facility is being used, the host name of the primary system is indicated.

S: Cancels processing of the backup file resulting in the communication error.

Action

Take action appropriate to the KFPR26201-E message that was output before this message. If the error is not a physical communication error, there may be an inconsistency in the system definitions concerning the relationship between the hosts; check the interhost definitions for the hosts affected by the error and re-execute.

KFPR26220-E L+S

System manager "aa....aa" failed, return code=bb....bb

System-related function "aa....aa" resulted in an error.

aa....aa: Name of the system-related function resulting in the error

bb....bb: Error code set by the system-related function resulting in the error

S: Terminates processing.

Action

The name of the system function in which the error occurred is pdi_omm_attach and the error code is -144.

To resolve one of the following suspected problems, re-execute the command by specifying the correct host name in the -m option:

The host name was omitted in the -m option and the specified master directory RDAREA is not on the server machine into which the pdrstr command was entered.

A master directory RDAREA was not found on the server machine with the host name specified in the -m option.

If the name of the system-related function resulting in the error begins with p_f_dbh_:

Eliminate the cause of the error based on the messages that are output before and after this message, and then re-execute the recovery.

Other cases:

See 4. Error Detail Codes to correct the cause of the error and re-execute the command. If an error that cannot be corrected by the HiRDB administrator has occurred, contact the customer support center.

KFPR26221-E L+S

Unable to output result of pdrstr

The result of the database recovery utility cannot be output due to the error reported before this message.

S: Terminates processing.

Action

Eliminate the cause of the error and re-execute. If no other error has occurred, recovery processing has terminated (if the execution result is not needed, there is no need to re-execute the processing).

KFPR26222-I L+S

Output result of pdrstr to aa....aa

The result of the database recovery utility was output to file aa....aa.

aa....aa: Name of output file

S: Resumes processing.

KFPR26224-E L+S

Unable to remove shared memory, key=aa....aa

Shared memory cannot be deleted.

aa....aa: Shared memory key value

S: Resumes processing.

Action

Delete the shared memory with a command after processing has terminated.

KFPR26225-E L+S

No RDAREA to restore

The RDAREA to be recovered was not found.

S: Terminates processing.

Action

Correct the specification on the command line and re-execute.

KFPR26226-E L+S

System ID of aa....aa is invalid

Because the system ID for aa....aa does not match the active HiRDB, the database cannot be recovered.

aa....aa: Type of file:

backup file: Backup file

sys log file: System log file

unload log file: Unload log file

management file: Differential backup management file

S: Terminates processing.

Action

Take one of the following actions:

For backup file or unload log file:
Specify the correct file and re-execute.

For system log file
System log file may have been damaged. Check whether the log file definition has been changed and initialized.

For differential backup management file
The specifications of the -g and -K options are invalid. Specify the correct values and re-execute the pdrstr command.

KFPR26227-E L+S

-l or -d option is not specified for backup file with -M s option

No unload log file was specified for recovering data from a backup file that was created with the -M s option specified.

S: Terminates processing.

Action

If -l is specified:

Specify the unload log file and re-execute.

If -d is specified:

Specify the directory where the unload log file is stored and re-execute.

KFPR26228-E L+S

Invalid RDAREA status, RDAREA name="aa....aa"

Because the indicated RDAREA is not on hold or on closed status or is in use by another user, it cannot be restored.

aa....aa: RDAREA name

S: Cancels recovery of this RDAREA and recovers another RDAREA.

Action

Place the RDAREA on hold or on closed status and re-execute. Or, wait until the other user's process terminates, then re-execute.

KFPR26229-E L+S

To recover Master RDAREA, pdstart should be executed with -r option

To recover the master directory RDAREA, start the HiRDB system with pdstart -r.

S: Terminates processing.

O: Terminate the HiRDB system with the pdstop command, start it with pdstart -r, then execute.

KFPR26230-E L+S

Unable to use -c option, deleted RDAREA "aa....aa" exist in backup file

Although the -c option was specified during execution of pdrstr, RDAREA "aa....aa" in the specified backup file does not exist in the system (the RDAREA may have been deleted after the backup file was made).
Consequently, the -c option cannot be specified for the backup file.

S: Terminates processing.

O: Specify the correct backup file and re-execute. Alternatively, specify the RDAREAs to be recovered with an option other than the -c option, then re-execute.

KFPR26232-E L+S

Unable to output Log point information

Log point information cannot be output because of the error that was output before this message.

S: Terminates processing.

Action

Eliminate the cause of the error and re-execute.

KFPR26233-I L+S

Output Log point information to aa....aa

Log point information was output to log point information file aa....aa.

aa....aa: Name of the log point information file

S: Terminates processing.

KFPR26234-E L+S

Log point information not found in backup

Log point information cannot be found in the backup file. Recovery specified by -L or re-creation of the log point information file (-z) cannot be performed.

S: Terminates processing.

Action

Specify the backup file that was acquired by specifying -z and re-execute.

KFPR26235-E L+S

System log file for recovery not swapped

System log file needed for database recovery has not been swapped out.

S: Terminates processing.

Action

Use the pdlogswap command to swap system log files and re-execute.

KFPR26236-E L+S

Error occurred in log file group, file group=aa....aa, reason=(bbb, ccccc)

An error occurred in a log file group.

aa....aa: Name of the log file group resulting in the error

bbb: Reason code

ccccc: Detail code

S: Terminates processing.

Action

Following are the reason codes and actions:

Reason code | Explanation | Action
-1 | Argument is invalid. | Contact the customer support center.
-2 | Fatal error or unexpected error occurred.
-31 | Error in log file definition analysis function | System log file definition has been changed incorrectly; refer to the detail code to revert to the original definition.

Following are the detail codes:

Detail code | Explanation
-1 | File group name in definition is invalid.
-2 | System A file name in definition is invalid.
-3 | System B file name in definition is invalid.

KFPR26237-E L+S

Error occurred in log element file, file group=aa....aa, system A/B:b, reason=(ccc, ddddd)

An error occurred in a system log file.

aa....aa: Name of the file group resulting in the error

b: System in which the error occurred

ccc: Reason code

ddddd: Detail code

S: If the error did not occur in a log file in the other system, the HiRDB system resumes processing using the log file in the other system.

Action

Take action appropriate to the reason code: If a reason code that is not listed is output, contact the customer support center.

Reason code
Explanation
Action

-40
-41
-42
-43
I/O error occurred.
Refer to the detailed code and the error code in 5.1 Error codes returned from HiRDB file system access requests to eliminate the cause of the error.

-50
-51
-52
-53
File contents are invalid.
The log file may have been damaged. Check whether the log file definition has been changed and initialized and whether an invalid status has been set. The detail code is system maintenance information.

KFPR26238-E L+S

Log is out of -T option value, RDAREA name=aa....aa, bb....bb time=(cc....cc), dd....dd time=(ee....ee)

Recovery based on a time specified in the -T option is not possible because the specified time is not within the period covered by the log.

aa....aa: RDAREA name

bb....bb: Start or end time:

"start": Recovery start time specified in the -T option is later than the log end time

"end": Recovery end time specified in the -T option is earlier than the log start time

cc....cc: Recovery start or end time specified in the -T option

dd....dd: First or last unload log file

("first"|"last")

ee....ee: Log start or end time

S: Terminates processing.

O: Correct the -T option and re-execute.

KFPR26239-E L+S

Invalid aa....aa value in -T option for RDAREA name=bb....bb, transaction commited at cc....cc

The recovery end time specified in the -T option for RDAREA bb....bb is invalid. Times earlier and later than the transaction synchronization point time are specified in the -T options as the recovery end times for the RDAREAs updated by the transaction.

aa....aa: Recovery end time specified for the RDAREA

bb....bb: RDAREA name

cc....cc: Time when the transaction synchronization point was reached

S: Terminates processing.

O: Set the -T option recovery end times specified for the RDAREAs updated by the transaction so that they all either include or do not include the synchronization point, then re-execute.

KFPR26240-E L+S

Backup is out of aa....aa in -T option value, RDAREA name=bb....bb

The recovery end time specified in the -T option for RDAREA aa....aa is invalid.

aa....aa: Recovery end time specified for the RDAREA

bb....bb: RDAREA name

S: Terminates processing.

O: Specify in the -T option a recovery end time that is later than the backup acquisition time and re-execute.

KFPR26241-W L+S

Transaction is running at recovery end time, RDAREA name=aa....aa, end time=(bb....bb), Transaction count=cc....cc

The recovery end time specified for recovery of RDAREA aa....aa includes a transaction being executed. A transaction being executed at the recovery end time cannot be recovered.

aa....aa: RDAREA name

bb....bb: Recovery end time of the RDAREA

cc....cc: Number of transactions being executed

S: Resumes processing.

O: To recover a transaction being executed at the recovery end time, specify the time that the transaction ended as the recovery end time and re-execute.

KFPR26242-E L

Unable to output message to standard output, host=aa....aa, file=bb....bb, func=cc....cc, errno=ddd

Messages cannot be output to standard output because a system call error occurred.

aa....aa: Name of the host where the file resulting in the error is located

bb....bb: Name of the file resulting in the error

When the name of the system call resulting in the error is tempnam, ****** is displayed.

cc....cc: Name of the system call resulting in the error

In UNIX, the name of the shell command that was executed is displayed, enclosed in parentheses.

ddd: errno of the system call resulting in the error

S: Resumes processing.

O: Check the value of the error indicator and refer to errno.h or the applicable OS manual to eliminate the cause of the error.

KFPR26243-E L

Unable to remove temporary file, host=aa....aa, file=bb....bb

A temporary file cannot be deleted because of the error that was output before this message.

aa....aa: Name of the host where the file that cannot be deleted is located

bb....bb: Name of file that cannot be deleted

S: Resumes processing.

O: Wait until processing terminates, then delete the temporary file.

KFPR26244-E L+S

Pdrstr must be executed at unit defined as manager

The database copy utility (pdcopy) must be executed at the unit where the system manager is defined.

S: Terminates processing.

O: Execute remote login to the unit where the system manager (MGR) is defined and re-execute the command.

KFPR26250-E L+S

PDDIR not defined

Environment variable PDDIR has not been set.

S: Terminates processing.

Action

Set the environment variable PDDIR, and then re-execute the database recovery utility (pdrstr).

KFPR26254-E L+S

Unable to use management file, reason=aa....aa, name=bb....bb

Differential backup management file bb....bb cannot be used.

aa....aa: Reason:

unfinish maintenance: Maintenance is not completed.

no control block: Control information for the differential backup management file was not found.

bb....bb: Differential backup management file name

S: Terminates processing.

Action

Take one of the following actions:

unfinish maintenance:
If there is a backup of the differential backup management file, use the pdfrstr command to recover the differential backup management file, and then re-execute the pdrstr command. If there is no backup of the differential backup management file, execute recovery without using a differential backup management file. For the recovery procedure when a differential backup management file is not available, see the HiRDB Version 9 System Operation Guide.

no control block:
The specifications of the -g and -K options for the pdcopy command are invalid; specify the correct values and re-execute the pdrstr command.

KFPR26255-E E+L

Page corrupted, management file name=aa....aa, page number=bb....bb

Page corruption of differential backup management file aa....aa was detected.

aa....aa: Differential backup management file name

bb....bb: Page number in which page corruption was detected

S: Terminates processing.

Action

If there is a backup of the differential backup management file, use the pdfrstr command to recover the differential backup management file, then re-execute the pdrstr command.

If there is no backup of the differential backup management file, execute recovery without using a differential backup management file. For the recovery procedure when a differential backup management file is not available, see the HiRDB Version 9 System Operation Guide.

KFPR26257-I L+S

Update start, management file name=aa....aa

Updating of differential backup management file aa....aa has begun.

aa....aa: Differential backup management file name

S: Continues processing.

KFPR26258-I L+S

Update complete, management file name=aa....aa

Updating of differential backup management file aa....aa has been completed.

aa....aa: Differential backup management file name

S: Continues processing.

KFPR26262-W L+S

Unable to find RDAREA. RDAREA name=aa....aa, generation number=bb

An RDAREA with the specified generation number could not be found. Recovery processing of this RDAREA was skipped.

aa....aa: RDAREA name

bb: Generation number

S: Continues processing.

Action

Reevaluate the specified RDAREA name or generation number. When recovering the RDAREA is necessary, correct the RDAREA name or generation number, and then re-execute. When recovering the RDAREA is not necessary, ignore this message.

KFPR26263-E L+S

Invalid log of RDAREA. RDAREA name=aa....aa(bb,cc), information=(dd....dd,ee....ee,ff....ff), (gg....gg,hh....hh,ii....ii)

When the logs for generation bb and generation cc of RDAREA aa....aa were read in, a log indicating that both generations were updated at the same time was found. It is possible that updating of generation bb and generation cc was performed out of synch with each other.
Recovery of RDAREA aa....aa failed. Recovery using the -x option cannot be performed.

aa....aa: RDAREA name

bb: Generation specified in the -q option

cc: Generation specified in the -x option

dd....dd: Output time of the previous log (format: YYYY/MM/DD HH:MM:SS)

ee....ee: Internal information

ff....ff: Internal information

gg....gg: Output time of the log with updates in reverse order (format: YYYY/MM/DD HH:MM:SS)

hh....hh: Internal information

ii....ii: Internal information

S: Continues processing.

Action

For details about what to do if you cannot use second generation RDAREA system logs to recover the RDAREA (if this KFPR26263-E message was output), see the HiRDB Version 9 Staticizer Option Description and User's Guide.

KFPR26264-I L+S

Backup generation differ from recovery generation. backup generation=aa recovery generation=bb

The generation number specified when data was backed up differs from the generation number specified when the database was recovered. Use the aa generation backup to recover the bb generation.

aa: The generation number specified in the -q option during backup

bb: The generation number specified in the -q option during recovery

S: Continues processing.

KFPR26265-I L+S

File sequence error information, RDAREA name = aa....aa server name = bb....bb information = (cc....cc,dd....dd,ee....ee,ff....ff),(gg....gg,hh....hh,ii....ii,jj....jj)

This message outputs the detail information relating to the KFPR16301-E message (reason=File-missing).

aa....aa: RDAREA name

bb....bb: Server name

cc....cc: Output time of the previous log record#

dd....dd: Run ID# of the previous log record output

ee....ee: Generation number# of the system log output by the previous log record

ff....ff: System internal information

gg....gg: Log report output time

hh....hh: Run ID when the log record is output

ii....ii: Generation number of the system log output by the log record

jj....jj: System internal information

#: If the unload log file is not missing, **....** is output.

S: Terminates the recovery process of all RDAREAs on the applicable server. If a server with other RDAREAs that can be recovered is found, continues the recovery process of that server.

Action

cc....cc
Administrator's action

time
The unload log file including log records output from cc....cc to gg....gg is missing. Specify all unload log files, including the log records output at the applicable time, and then re-execute.

**....**
Take one of the following actions:
An unload log file that must be specified first on each server may be missing. Refer to time gg....gg, specify the missing unload log file(s), and then re-execute.
If all unload log files close to time gg....gg are specified, check if the backup file was obtained near time gg....gg. If the backup file was not obtained near the time gg....gg, specify a backup file obtained near time gg....gg, and then re-execute.

KFPR26266-E L+S

Unable to use the "-k n" option because the JP1/VERITAS NetBackup Agent for HiRDB license not found

The -k n option cannot be specified because the license required to use the JP1/VERITAS NetBackup linkage facility is missing.

S: Terminates processing.

Action

Obtain and configure the license required to use the JP1/VERITAS NetBackup linkage facility.

KFPR26267-E L+S

Dynamic load error occurred, shared library=aa....aa, host=bb....bb

Dynamic loading of common library aa....aa on host bb....bb failed.

aa....aa: Full path name of the shared library (in UNIX, the file path name of the shared library)

bb....bb: Host name

S: Terminates processing.

Action

Check if a NetBackup client is installed. If a copy is installed, see the KFPR26003-E message just output to eliminate the cause of the error, and then re-execute.

KFPR26268-E L+S

NetBackup object not found, policy=aa....aa, from=bb....bb, to=cc....cc

A backup of policy name aa....aa obtained in bb....bb to cc....cc cannot be found.

aa....aa: Policy name

bb....bb: The backup search condition start date of the -U option (YYYY/MM/DD HH:MM:SS). ****/**/** **:**:** is output if no start date is specified.

cc....cc: The backup search condition end date of the -U option (YYYY/MM/DD HH:MM:SS). ****/**/** **:**:** is output if no end date is specified.

S: Terminates processing.

Action

Check whether there is a backup file of the policy in the specified period, reevaluate the policy name and specification period, and then re-execute. If the backup search condition start date is ****/**/** **:**:**, the backup search condition start date and time become the policy creation date and time. If the backup search condition end date and time are ****/**/** **:**:**, the backup search condition start date and time are the current new date and time.

KFPR26269-E L+S

NetBackup API error occurred, return code=aa....aa(bbbb), func=cc....cc, message=dd....dd

A problem occurred in the application programming interface of NetBackup.

aa....aa: Name of the application programming interface return code for NetBackup

bbbb: Application programming interface return code for NetBackup (hexadecimal)

cc....cc: Application programming interface name for NetBackup

dd....dd: The message obtained after the application programming interface error return for NetBackup (displays the first 100 characters if the message length exceeds 100 characters)

S: Terminates processing.

Action

Return code (bbbb) | Return code name (aa....aa) | Meaning | Action
0x03 | SYSTEM_ERROR | NetBackup internal error | Check the error cause at the NetBackup management console, take appropriate action, and then re-execute.
0x0D | FEATURE_NOT_LICENSED | No license was found or the license was invalid | Obtain a license.
0x4B | VERSION_NOT_SUPPORTED | NetBackup version is not supported | Check if the NetBackup version is correct.
0x4D | ACCESS_FAILURE | Cannot access the object | Check if the NetBackup master server or NetBackup media server stopped. If the server did not stop, contact the customer support center#.
Other | -- | -- | Contact the customer support center#.

--: Does not apply.

#: Obtain the following data before contacting the customer support center:

The system log file of the host with a single server or system manager, the host with the -b option specified, or the host with the target RDAREA when executing the utility

Files in the %PDDIR%\spool directory on the host with a single server or system manager, the host with the -b option specified, or the host with the target RDAREA when executing the utility

Error information from the NetBackup management console

Messages output to standard output or standard error

The process results output file when executing the utility

KFPR26270-W L+S

Log information, specified log Run ID=aa....aa Gen No=bb....bb, log Run ID=cc....cc Gen No=dd....dd in RDAREA name="ee....ee"

Unload log files required for the recovery of the database are not specified in the -l or -d option of the pdrstr command. The log information stored in the RDAREA and the log information in the unload log file specified in the -l or -d option of the pdrstr command is displayed.

Note:

If the backup was made under one of the following circumstances, this warning message is output even if all unload log files needed for database recovery have been specified; in this case, this warning message can be ignored:

Backup was made after HiRDB terminated normally.
This warning message is also output when all unload log files that store the system logs used in the next and subsequent normal starts are specified in the -l or -d option.

System log files were swapped after the pdclose command had been entered, and then the backup was made.
This warning message is also output when all unload log files that store the system logs used after swapping of system log files are specified in the -l or -d option.

System log files were swapped after reference-possible backup-hold (update WAIT mode) or updatable backup-hold (WAIT mode), and then the backup was made.
This warning message is also output when all unload log files that store the system logs used after swapping of system log files are specified in the -l option.

aa....aa:

ID of the log information stored in the oldest unload log file#¹ in the directory specified in the -l option or specified in the -d option (log server run ID of the system log file)

bb....bb:

Log information stored in the oldest unload log file#¹ in the directory specified in the -l option or specified in the -d option (generation number of the system log file)

cc....cc:

ID of the log information stored in the RDAREA (log server run ID of the system log file)#²

dd....dd:

Log information stored in the RDAREA (generation number of the system log file)#²

ee....ee: RDAREA name

#1: The first unload log file at each server is used.

Example:

-l bes1_unlog01, bes1_unlog02, bes2_unlog01, bes2_unlog02

When the -l option is specified as described previously, the log information of unload log files bes1_unlog01 (unload log file of back-end server 1) and bes2_unlog01 (unload log file of back-end server 2) is displayed.

#2: Log information is stored in an RDAREA in the following cases:

When an RDAREA is on backup-hold

When an RDAREA is closed

When HiRDB has terminated normally

Action

When specifying the -l option of the pdrstr command, specify all unload log files that are required for the recovery of the database. Alternatively, when specifying the -d option of the pdrstr command, either specify all unload log files that are required for the specified directory or increase the number of directories to be specified. Refer to cc....cc and dd....dd to determine which unload log files are required.

KFPR26271-I L+S

NetBackup information, policy=aa....aa, date=bb....bb, time=cc....cc

Backup of policy name aa....aa obtained by date bb....bb and time cc....cc was restored.

aa....aa: Policy name

bb....bb: Date (YYYY/MM/DD)

cc....cc: Time (HH:MM:SS)

S: Continues processing.

KFPR26272-W S+L

No unload log file in specified directory, directory name = aa....aa

There is no unload log file in the specified directory.

aa....aa: Directory name (if it exceeds 100 characters, the last 100 characters are output)

S: Continues processing.

Action

Check the directory name aa....aa. If the directory name is invalid, revise the directory name and re-execute.

KFPR26273-E S+L

Error occurred directory analysis, directory name = aa....aa

An error occurred during analysis of directory aa....aa.

aa....aa: Directory name (if it exceeds 100 characters, the last 100 characters are output)

S: Terminates processing.

Action

On the basis of the KFPR26203-E message output before or after, eliminate the cause of the error, and then re-execute.

KFPR26274-E E+L

Too many parameter exists at -a option in command line.

Too many parameters are specified in the command line options.

a: Option name

Action

The option name and action are listed below:

Option name | Action
d | The total number of specified directory names exceeds the maximum number of 128 that can be specified. Revise the specified number of directories to within 128, move the unload log files in the specified directories, then re-execute.

KFPR26275-I S+L

Pdbkupls started.

The pdbkupls command has been started.

S: Continues processing.

KFPR26276-I S+L

Pdbkupls terminated, return code=aa

The pdbkupls command terminated with return code aa.

aa: Command return codes

0: Normal termination

12: Error termination

S: Continues processing.

Action

If the return code shows an error termination (12), refer to the error messages output before and after this message to the event log (in UNIX, syslogfile). See the action listed for the error message, eliminate the cause of the error, and then re-execute.

KFPR26277-E S+L

Required backup files not specified.

The backup files required to display the information are insufficient.

S: Terminates processing.

Action

Specify all required backup files and re-execute.

KFPR26278-I L+S

aa....aaGbyte processing.

aa....aa Gigabytes are being read from the backup files.

aa....aa: Size of data read so far

S: Continues processing.

KFPR26279-I L+S

aa....aaGbyte reading completed.

Reading of the backup file has completed approximately aa....aa gigabytes.

aa....aa: Size of the backup file (gigabytes)

Rounded up to the nearest 0.01 gigabyte (a backup file of less than 0.01 gigabytes is displayed as 0.01 gigabyte).

S: Continues processing.

KFPR26280-E S+L

Specified backup file invalid. filename=aa....aa, code=bb....bb

The specified backup file is invalid.

aa....aa: Name of the invalid backup file (if it exceeds 100 characters, the last 100 characters of the backup file name are output).

bb....bb: Error cause

diff: Backup file prepared by the differential backup facility

other: Backup file prepared by other than pdcopy

error: Backup file prepared by pdcopy, which terminated with an error (return code 12)

S: Terminates processing.

Action

Specify the correct backup file name and re-execute.

KFPR26281-I L

aa....aa bb....bb. server name=cc....cc

Processing aa....aa of server name cc....cc performed bb....bb.

aa....aa: Processing details

Roll forward: Recovery processing using a log (updated log) acquired in log acquisition mode

Roll back: Recovery processing using a log (updated log) acquired in pre-update log acquisition mode

bb....bb: Start or termination of processing

started: started

ended: ended

cc....cc: Server name

S: Continues processing.

KFPR26282-I L

Log file aa....aaGbyte processing

The unload log file or system log file specified in recovery processing is undergoing aa....aa GB processing. Note that this message is output in 5-GB units.

aa....aa: File size read until present (units: GB)

S: Continues processing.

KFPR26283-W L+S

Result file not output

Result file output failed.

S: Continues processing.

Action

In the following directories, check whether there is a large quantity of stored result files for names beginning with pdrs2. If there is a large quantity of result files, either delete unnecessary result files or move them to another directory.
In UNIX:
/tmp, /var/tmp, or environment variable TMPDIR
In Windows:
Environment variable TMP or TEMP, or %PDDIR%\tmp

If the KFPR00765-I message that was output at about the same time as this message indicates that a return code of 0 or 4 was received from the database recovery utility (pdrst), you do not need to re-execute.

KFPR26287-E L+S

Invalid RDAREA status, RDAREA name="aa....aa"

The RDAREA is not in a status in which the database recovery utility can be executed.

aa....aa: RDAREA name

S: If there is an RDAREA that can be recovered, processing continues.

Action

Change to a status in which the database recovery utility can be executed, and then re-execute.

Note that if the in-memory RDAREA is recovered, the RDAREA and in-memory data buffer must be in one of the following statuses:

The RDAREA must be in shutdown or closed status (pddbls command execution result is CLOSE HOLD(CMD) or CLOSE HOLD)

The in-memory data buffer must be in buffer error status (pddbls -M command execution result is Y(OBST-MEM))

KFPR26288-E S+L

Log has been input to "pdrstr", server=aa....aa, inf1=0xbb....bb,cc....cc, inf2=0xdd....dd,ee....ee

A log that was used once for recovery was detected in a check for re-use of the same log.
For details about how to check re-use of identical logs, see the HiRDB Version 9 System Operation Guide.

aa....aa: Server name

bb....bb: Internal information

cc....cc: Internal information

dd....dd: Internal information

ee....ee: Internal information

S: Terminates recovery processing of the server indicated by aa....aa.

Action

Follow the procedure described in When recovery processing is interrupted under Same log reuse check in the HiRDB Version 9 System Operation Guide, and recover.

KFPR26289-W S+L

Insufficient of RDAREA about relation

Specification of the relevant recovery target RDAREA is missing.
Even though this message was displayed, recovery processing terminated normally.

S: Continues processing.

Action

Refer to the processing result output file, add the RDAREA indicated in message KFPT02028-W under <<PDRDREFLS RESULT>> to the recovery target, and then re-execute the database recovery utility. If the RDAREA indicated in message KFPT02028-W was intentionally removed from the recovery target, ignore this message.

KFPR26309-I S+L

Backup file=aa....aa

Restores by using backup file aa....aa.

aa....aa: RDAREA name

S: Continues processing.

2.13 KFPS messages

KFPS00010-I R+S

HiRDB setup start, func = aa....aa, HIRDB directory=bb....bb

HiRDB setup processing has started.

aa....aa: Function name:

add: HiRDB registration in OS

delete: HiRDB deletion from OS

bb....bb: Name of HiRDB directory

S: Resumes processing.

KFPS00011-I R+S

HiRDB setup ended, return code=aa

HiRDB setup processing has terminated.

aa: Termination code:

0: Terminated normally

8: Error occurred during processing

S: Terminates processing.

Action

If the termination code is not 0, take action appropriate to the message output before this message. If the text busy status has just occurred, HiRDB's zombie process may still remain. In such a case, terminate the zombie process with UNIX's kill command and re-execute.

KFPS00012-I S

Library setup for character code set aa....aa

Library for using aa....aa character codes has been set up.

aa....aa: HiRDB character codes:

CHINESE: EUC Chinese kanji codes

CHINESE-GB18030: Chinese GB18030 codes

LANG-C: One-byte character codes

SJIS: Shift JIS kanji codes

UJIS: EUC Japanese kanji code

UTF-8: Unicode(UTF-8)

S: Terminates processing.

KFPS00014-I S

Load module setup completed for aa....aa

The load module for aa....aa has been set up.

aa....aa: Load type:

POSIX: POSIX library version of HiRDB

S: Continues processing.

KFPS00015-E S

Unable to setup aa....aa, reason code=bb....bb

The load module for aa....aa could not be set up.

aa....aa: Load type:

POSIX: POSIX library version of HiRDB

NO-POSIX: Non-POSIX library version of HiRDB

bb....bb: Reason code:

REMOVED: This module has been deleted

S: Terminates processing.

O: Reinstall HiRDB.

KFPS00016-E S+L

Error occurred while setup HiRDB

An error occurred during HiRDB setup processing.

S: Terminates processing.

Action

Check whether, before or after this message was issued, a memory shortage occurred in the /etc or /tmp directory. If a memory shortage occurred, allocate free disk space. Also, determine whether a disk failure occurred. If a disk failure occurred, recover from the disk failure. Then, re-execute the command.

KFPS00020-E S

Pdsetup already used by another user

The pdsetup command cannot be input because it is being used by another user.

S: Terminates processing.

Action

Wait until the pdsetup command being executed by the other user terminates, then re-execute.

KFPS00021-E S

Invalid user name, user=aa....aa

The authorization identifier of the HiRDB administrator is invalid.

aa....aa: Authorization identifier

However, if a check of the authorization identifier cannot be performed due to a memory shortage, ******** is output.

S: Terminates processing.

Action

Take one of the following actions:

If ******** is output for the authorization identifier:
Stop unneeded programs and re-execute.

Other than above (in UNIX)
Take one of the following actions:
Change the user name to the name that corresponds to the user ID of the HiRDB administrator defined in /etc/passwd.
Change the HiRDB administrator and the owner of the HiRDB operation directory.

Other than above (in Windows)
Change the HiRDB administrator and the owner of the HiRDB operation directory.

KFPS00022-E S

Language "aa....aa" not installed

Language aa....aa has not been installed.

aa....aa: Language name

S: Terminates processing.

Action

Install language aa....aa.

KFPS00030-E S

Permission denied

Specified processing is not permitted.

S: Terminates processing.

Action

Ask the super user to execute the pdsetup and pdopsetup command.

KFPS00031-E S

Specified HiRDB system already catalogued

Specified HiRDB system has already been registered.

S: Terminates processing.

Action

Check the specified HiRDB directory, enter pdsetup -d, then re-execute, if necessary.

KFPS00032-E S

Specified HiRDB system not catalogued

Specified HiRDB system has not been registered.

S: Terminates processing.

Action

Check the specified HiRDB directory, enter pdsetup, and re-execute, if necessary.

KFPS00033-E S

Specified HiRDB home directory not exist

Specified HiRDB directory was not found.

S: Terminates processing.

Action

Check the specified HiRDB directory and re-execute.

KFPS00034-E E+L+S

Insufficient disk capacity

There is not enough disk space.

S: Terminates processing.

Action

Allocate sufficient space to the specified HiRDB directory and re-execute. If the text busy status has just occurred, HiRDB's zombie process may still remain.

Terminate the process with the kill command (in UNIX) or with the pdkill command (in Windows), and re-execute.

KFPS00035-I S

Creates files necessary for execution

File required for execution is created.

S: Resumes processing.

KFPS00036-Q S

Specify whether to delete files necessary for execution from specified HiRDB home directory ? [y:YES , n:NO]

Asks whether or not the files under the specified HiRDB directory that are required for execution are to be deleted.
y: Delete; n: Do not delete.

S: Resumes processing.

O: Enter y (yes) or n (no).

KFPS00038-E S

Specified HiRDB home directory not full pathname

Asks the absolute pathname for the HiRDB directory.

S: Terminates processing.

Action

Specify the absolute pathname of the HiRDB directory and re-execute.

KFPS00040-I R+S

Delete files necessary for execution

The files required for execution have been deleted.

S: Resumes processing.

KFPS00050-E S

Root directory specified

No root directory was specified for the HiRDB directory.

S: Terminates processing.

Action

Because the root directory cannot be changed to the HiRDB directory, create a separate HiRDB directory and re-execute.

KFPS00054-E S

Unable to specify HiRDB home directory pathname more than aaa bytes

The specified HiRDB directory path exceeds the maximum length.

aaa: Maximum HiRDB directory path length

Linux: 118

Other than Linux: 128

S: Terminates processing.

Action

Specify a HiRDB directory path whose length does not exceed 128 bytes (118 bytes in Linux). When using a symbolic link, be sure that the length of the actual path to be linked to does not exceed 128 bytes (118 bytes in Linux).

KFPS00055-E S

"program ID" invalid

The length of the character string of the specified program ID exceeds 256 bytes.

S: Terminates processing.

Action

Specify the program ID with a maximum length of 256 bytes.

KFPS00056-I S+L

OS shutdown action setup mode=aa....aa

During OS shutdown, the function that terminated HiRDB was set to aa....aa.

aa....aa:

on: Explicitly terminate HiRDB.

off: Do not terminate HiRDB (depending on the OS, terminates the HiRDB process).

S: Terminates processing.

KFPS00060-E S

Usage: aa....aa

Command format aa....aa is invalid.

aa....aa:

HP-UX (32-bit mode):
pdsetup { -d [-f] | [-c { sjis|chinese|lang-c|ujis|utf-8|chinese-gb18030 }] [-p program][-l load][-k {on|off}]} HiRDB_home_directory

HP-UX (64-bit mode):

pdsetup { -d [-f] | [-c { sjis|chinese|lang-c|ujis|utf-8|chinese-gb18030 }][-k {on|off}]} HiRDB_home_directory

Solaris (32-bit mode):
pdsetup { -d [-f] | [-c { sjis|chinese|lang-c|ujis|utf-8|chinese-gb18030 }][-l load] [-k {on|off}]} HiRDB_home_directory

Solaris (64-bit mode):
pdsetup { -d [-f] | [-c { sjis|chinese|lang-c|ujis|utf-8|chinese-gb18030 }][-k {on|off}]} HiRDB_home_directory

AIX (32-bit mode):
pdsetup { -d [-f] | [-c { sjis|chinese|lang-c|ujis|utf-8|chinese-gb18030 }][-l load]} HiRDB_home_directory

AIX (64-bit mode):
pdsetup { -d [-f] | [-c { sjis|chinese|lang-c|ujis|utf-8|chinese-gb18030 }]} HiRDB_home_directory

Linux:
pdsetup { -d [-f] | [-c { ujis|chinese|lang-c|utf-8|sjis|chinese-gb18030 }][-k {on|off}]} HiRDB_home_directory

S: Terminates processing.

Action

Check the operands and re-execute the command.

KFPS00320-I R

RPC Info. RC=aa....aa, Func:bb....bb, Msg:cc....cc, Local(Pid=dd....dd, Port=ee....ee)

Displays RPC information.

aa....aa: Return code

bb....bb: Maintenance information 1 (function name, module name, etc.)

cc....cc: Maintenance information 2

dd....dd: ID of local process

ee....ee: Local port number

S: Resumes processing.

KFPS00326-E E+R

Insufficient memory for RPC. Local pid=aa....aa, Local port number=bb....bb

A system call issued to execute RPC, such as socket() or send(), terminated abnormally due to a memory shortage.

aa....aa: ID of local process

bb....bb: Local port number

S: Terminates the displayed server abnormally.

Action

Take appropriate action as indicated in 4.1 Detail codes for RPC-related errors.

KFPS00327-E R

Too few sockets. RPC is unavailable. Local pid=aa....aa, Local port number=bb....bb, error number=cc....cc

RPC cannot be executed because there is no available socket.

aa....aa: ID of local process

bb....bb: Port number of local process

cc....cc: Error number

S: If the error number is 20490, terminates abnormally; otherwise, resumes processing.

Action

If the error number is 20490, contact the customer support center.

For any other error number, take appropriate action as indicated in 4.1 Detail codes for RPC-related errors.

KFPS00328-E E

No data in RPC trace file aa....aa

Specified file aa....aa contains no data.

aa....aa: Specified file name

S: Cancels the applicable command's processing.

Action

Check the file name and reenter the command.

KFPS00330-E E

RPC trace file aa....aa not found

Specified file aa....aa was not found.

aa....aa: Specified file name

S: Cancels the applicable command's processing.

Action

Check the file name and reenter the command.

KFPS00332-E E

RPC trace file access error. Return information=aa....aa, Function name=bb....bb

One of the following possible errors is displayed:

Memory shortage occurred

RPC trace file I/O error occurred

aa....aa: Return information

bb....bb: Function name

S: Cancels the applicable command's processing.

Action

Contact the customer support center.

KFPS00335-E R

Time out occurred in chained RPC. Service group=aa....aa, local pid=bb....bb

The call target already aborted a chained RPC (a server in the same service function group was called more than once within the same transaction using a reply RPC). Or, the transaction was not terminated within the specified time since the last chained RPC call.

aa....aa: Name of service group

bb....bb: Local process number

S: Terminates the displayed server abnormally.

P: Contact the HiRDB administrator.

Action

Take appropriate action as indicated in the message output to the message log.

KFPS00336-E E+R

RPC of message received from client or server with different HiRDB version. Local pid=aa....aa, Remote node address=bb....bb, Remote port number=cc....cc

The version of the text at the send side does not match the version at the receive side.

aa....aa: Received process ID

bb....bb: Node address of send side

cc....cc: Port number of send side (up to 5 numeric digits)

S: Resumes processing after discarding the message resulting in output of this message (does not send a message to that effect to the send side).

Action

Check the HiRDB version of the server that output this message and the HiRDB version of the HiRDB client or server that sent the message. If they do not match, use matching versions.

KFPS00337-E E+R

Unable to open RPC trace file aa....aa

An open error or a definition analysis error occurred in an RPC trace file.

aa....aa: Name of RPC trace file

If the path name of the RPC trace file exceeds 187 characters, the last 187 characters of the RPC trace file path name are output.

S: Resumes processing (RPC trace will not be collected).

Action

Check the following operands for an error:

pd_rpc_trace_name

pd_rpc_trace_size

If this message is reissued after correcting these operands, contact the customer support center. If there is a shortage of system resources (disk space shortage, file count shortage, etc.), change the operating system kernel parameters.

KFPS00345-W L

Insufficient HiRDB registered ports, reason code=aaa. Use OS assigned ports

Port numbers assigned automatically by the OS are being used because the number of ports being used for communication by HiRDB exceeded the number of ports specified in the pd_registered_port operand, or because all port numbers specified in the pd_registered_port operand are in use by other programs.

aaa: Reason code:

-10: The number of ports specified in the pd_registered_port operand was exceeded

-20: All port numbers specified in the pd_registered_port operand are in use by other programs

S: Continues processing.

Action

Take one of the following actions:

Reason code
Action

-10
Check the value specified in the pd_registered_port operand; there may be too few port numbers.

-20
Check the value specified in the pd_registered_port operand; all port numbers in the specified range may be in use by other programs.
If this is the case, re-evaluate the specification; if all port numbers are not being used by other programs, there may be too few ports specified in the pd_registered_port operand.

When this message is output, it is recommended that the statistics analysis utility (statistical information related to system operations) be executed. Check the following items:

Number of HiRDB reserved ports being used (#OF REGISTERED PORTS)

Number of ports assigned automatically (by the OS) that were being used when the number of HiRDB reserved ports was exceeded (#OF ASSIGNED PORTS)

KFPS00346-E E+L

Port number in registered ports definition invalid

The specification of the pd_registered_port operand is invalid.

S: Terminates the pdconfchk command or HiRDB startup processing.

Action

Modify the contents of the pd_registered_port operand in the system common definition or unit control information definition, and then re-execute the pdconfchk command or HiRDB startup processing.

KFPS00347-E L

Insufficient shared memory. Required memory size=aa....aa bytes

A shortage of shared memory space occurred.

aa....aa: Size of shared memory that needs to be allocated

S: Terminates HiRDB startup processing.

Action

Reconsider the shared memory estimate. Also, if an error message was output before this message, take the action indicated in that message. If this message is output even after these measures, save the contents of the message and contact the customer support center.

KFPS00348-E E+L

Duplicate registered ports, type=aa....aa, port number=bb....bb

There is a duplication of a port number that must not be duplicated in the range of port numbers specified in the pd_registered_port operand.

aa....aa: Type of duplicate port number:

NAME

Port number specified in pd_name_port operand or in -p option of pdunit operand.

SERVICE

Port number specified in the -s option of the pd_service_port operand, pd_scd_port operand, or pdunit operand is a duplicate.

SERVICES

Port numbers in the following services file are duplicated:

In UNIX: /etc/services

In Windows: %windir%\system32\drivers\etc\services

However, in an NIS or DNS environment, the files defined in the NIS or DNS configuration are used.

TRN:

Port number specified in the -t option of the pd_trn_port operand or pdunit operand is a duplicate.

MLG:

Port number specified in the -m option of the pd_mlg_port operand or pdunit operand is a duplicate.

ALV:

Port number specified in the -a option of the pd_alv_port operand or pdunit operand is a duplicate.

bb....bb: Duplicated port number

S: Terminates the pdconfchk command or HiRDB startup processing.

Action

Review the value specified in the pd_registered_port operand of the system common definition or unit control information definition, and the value of the duplicated port number, and, if necessary, set the correct values. Then, re-execute the pdconfchk command or HiRDB startup processing.

Because this message shows only the first duplicated port number, it is wise to check for any other duplicated port numbers.

KFPS00349-E L

Insufficient network port

An attempt to allocate a communication port number failed.
If this message is output, the system attempts to reacquire the communication port number. If successful, the HiRDB process will run without problem. If this message is output frequently or a communication error causes a HiRDB process error after this message is output, one of the following is the most likely cause:

There is a shortage of automatically allocated port numbers for the operating system

The network of the IP address described in the KFPS00352-I message output immediately after this message terminated abnormally

There is an error in the IP address of the host name used by the HiRDB specified in the hosts file (in UNIX, /etc/hosts, and in Windows, OS-installation-directory\system32\drivers\etc\hosts)

There is a memory shortage

The port number output in the KFPS00352-I message is already in use
(when it is the same as the value of the port number set by HiRDB, such as the value specified in the pd_name_port operand)

S: Continues processing. Attempts to reacquire communication port number.

Action

Take the following actions:

If there is a shortage of port numbers, check if a program other than HiRDB is using many communication ports. If another program is using many communication ports, reduce the number of ports it uses.
Alternatively, do one of the following to secure the communication ports required for HiRDB.
Modify OS parameters and configure the settings to prevent a shortage of TCP ports. For details about the settings to prevent a shortage of TCP ports, see Ways to avoid a shortage of ports in the HiRDB Version 9 Installation and Design Guide.
Use the HiRDB reserved port facility to secure the communication ports required for HiRDB. For details about the HiRDB reserved port facility, see the HiRDB Version 9 Installation and Design Guide.
Also, if this message is output by a server machine specifying a system manager on HiRDB/Parallel Server, or for HiRDB/Single Server, specifying 1 in the PDTCPCONOPT operand in the client environment definition is often effective. For details about the PDTCPCONOPT operand, see the HiRDB Version 9 UAP Development Guide.

If the network terminates abnormally, start the network.

Re-evaluate the content of the hosts file, and check if an incorrect IP address is specified in the host name entries defined by HiRDB. Correct any incorrect IP addresses found, and then start HiRDB.

If there is a memory shortage, re-estimate the memory. Alternatively, terminate any unneeded processes.

If the port number is already in use, revise the value of the port number set by HiRDB (such as the value specified in the pd_name_port operand) to a value that is not in use

KFPS00350-W L

Process memory over pd_svr_castoff_size value. Server=aa....aa, memory size=bb....bb, value= size=cc....cc

Server processing has been terminated because the amount of memory space used exceeded the value specified in the pd_svr_castoff_size operand.

aa....aa: Server name (server name specified in the pdstart operand of the system common definition)

bb....bb: Memory size used (in MB)

cc....cc: Size specified in pd_svr_castoff_size operand (in MB)

S: Terminates processing.

Action

If this message is output often, the effectiveness of resident processes will decline. In addition, frequent processing terminations and startups, as well as large amounts of output to the system and message logs, will result in overall performance degradation. Therefore, specify the pd_svr_castoff_size operand value for each server so that the following condition is satisfied:

a - b < c

a: Server process virtual memory size after SQL process termination

b: Server process virtual memory size immediately following HiRDB startup

c: Value set in pd_svr_castoff_size operand

Use an operating system command (e.g., the top command in HP-UX) to check the virtual memory size.

KFPS00351-E L

Hostname (aa....aa) not found

Host name aa....aa could not be obtained.
aa....aa: Host name
S: Terminates processing.

Action

The following are possible causes of this problem; eliminate the cause and re-execute the processing:

In UNIX:

The host name or IP address was not found in the hosts file.

Referencing privilege for the hosts file has not been granted.

The hosts file was modified while HiRDB was running. When the hosts file is modified, terminate normally, and then start HiRDB.

If DNS or NIS is being used, the host name or IP address was not found in the database to be retrieved.

If DNS or NIS is being used, then either the referencing privilege for the database to be retrieved or for the environment setup file of DNS has not been granted, or one or both of these settings is invalid.

If DNS or NIS is being used, the setting of the /etc/nsswitch.conf file is invalid.

In Windows:

The host name or IP address was not found in the hosts file.

Reference privilege for the hosts file has not been granted.

The hosts file was modified while HiRDB was running. After the hosts file is modified, terminate normally, and then start HiRDB.

If DNS or WINS is being used, the host name or IP address was not found in the database to be retrieved.

If DNS or WINS is being used, either there is no reference privilege for the database to be retrieved or one of the settings is invalid.

KFPS00352-I L

Port number maintenance information,(aa....aa)

This is the port number maintenance information of the KFPS00349-E message.

aa....aa: Maintenance information

S: Continues processing.

Action

This is the maintenance information of the KFPS00349-E message output immediately before this message. Take action according to the KFPS00349-E message.

KFPS00353-E L

System call error occurred while communication, func=aa....aa, errno=bb....bb, info=cc....cc

An error occurred in the processing of inbound communication, and no requests could be accepted for a period of 3 minutes.
HiRDB relies on server-client and inter-process communications. If an error occurs while it is processing inbound communications and no execution requests can be accepted, other errors might result, such as online processing delays. To mitigate the effects of such errors, if the system enters a state in which no execution requests can be accepted for a period of 3 minutes, this message is output, and the process that detected the error is terminated. Monitoring whether this message is output allows you to detect errors such as online processing delays at an early stage.

aa....aa: Name of the system call

bb....bb: System call return code

cc....cc: Internal information

S: Outputs an abort code (Psrc780), and terminates the process that detected the error. If the process is the system server, the unit is shut down.

Action

Check whether a port scanner or similar program is making a large number of connection requests to a HiRDB process, and, if so, terminate that program.

In cases other than the above, refer to the OS's documentation to determine the cause of the error based on the name of the system call and the return code that are displayed in this message. For typical system call return codes, see 4.3 System call return codes. Once you identify the cause of the error, eliminate it, and take corrective action to prevent errors from occurring in the processing of inbound communication.

After eliminating the cause of the error, restart HiRDB if it terminated abnormally.

If the cause of the error cannot be determined, contact the customer support center.

KFPS00354-W E+L

Duplicate registered ports, port number=aaaaa

The port number specified as the HiRDB reserved port duplicates the port number registered in the following services file:

In UNIX: /etc/services

In Windows: %windir%\system32\drivers\etc\services

However, in an NIS or DNS environment, the files defined in the NIS or DNS configuration are used.

aaaaa: Duplicate port number

S: Does not use the duplicate port number as the HiRDB reserved port.

Action

Review the value set in the system common definition or in the unit control information definition pd_registered_port operand and in the services file, and, if necessary, set the correct value.

KFPS00355-E E+L

Loopback address not specified

The loopback address was not specified in the -x option of the pdunit operand in the system common definition. If Y or S is specified in the pd_rpc_bind_loopback_address of the system common definition, you must specify the loopback address in the -x option of the pdunit operand in the system common definition.

S: Terminates the pdconfchk command or HiRDB start processing.

Action

Perform one of the following actions, and then re-execute the pdconfchk command or HiRDB start processing:

If one of the following applies, specify the loopback address in the -x option of the pdunit operand in the system common definition.
- In a system configuration in which a HiRDB client and HiRDB server exist on the same server machine, in order to record an entry on the Windows Firewall exceptions list for HiRDB server processes, specify Y in the pd_rpc_bind_loopback_address of the system common definition.
- In a system configuration in which a HiRDB client and HiRDB server exist on different server machines, in order to record only those processes receiving connection requests from the HiRDB client on the Windows Firewall exceptions list for HiRDB server processes, specify S in the pd_rpc_bind_loopback_address of the system common definition.

If neither of the configurations described in 1 apply, specify N in the pd_rpc_bind_loopback_address operand in the system common definition.

KFPS00356-E E+L

Port number of scheduler process not specified.

The scheduler process port number was not specified.
If S is specified in the pd_rpc_bind_loopback_address operand in the system common definition, you must specify the scheduler process port number.

S: Terminates the pdconfchk command or HiRDB start processing.

Action

Perform one of the following actions, and then re-execute the pdconfchk command or HiRDB start processing:

As mentioned previously, in a system configuration in which a HiRDB client and HiRDB server exist on different server machines, in order to record only those processes receiving connection requests from the HiRDB client on the Windows Firewall exceptions list for HiRDB server processes, you must specify S in the pd_rpc_bind_loopback_address of the system common definition. When specifying S as just described, also specify one of the following operands to set the scheduler process port number.
pd_service_port operand
pd_scd_port operand
-s option of the pdunit operand

In a system configuration in which a HiRDB client and HiRDB server exist on the same server machine, in order to record an entry on the Windows Firewall exceptions list for HiRDB server processes, specify Y in the pd_rpc_bind_loopback_address of the system common definition.

If neither 1 nor 2 apply, specify N in the pd_rpc_bind_loopback_address operand in the system common definition.

KFPS00403-E E+L

Unable to start lock service. reason code=aa....aa

An error occurred during lock service function startup or restart processing.

aa....aa: Reason code indicating the nature of the error

S: Terminates the HiRDB system abnormally.

Action

Take action appropriate to the reason code, as listed below, and restart:

Reason code | Explanation | Action
10 | Error occurred during definition analysis startup processing. | If an error message was issued before this message, take action appropriate to that message
20 | Communication error occurred.
30 | Space shortage occurred. | Check for excessive memory allocation. If too much memory is allocated, release unneeded resources.
40 | Shared memory shortage occurred | Re-evaluate the value of the pd_lck_pool_size operand and pd_lck_pool_partition operand specified in the corresponding server definition#.
60 | There is no directory for output of deadlock information. | Create a %PDDIR%\spool\pdlckinf directory.

#

For the front-end server, re-evaluate the value of the pd_fes_lck_pool_size operand and pd_fes_lck_pool_partition operand.

KFPS00412-E L

Error occurred while terminating lock service; continues processing. reason code=aa....aa

An error occurred during lock service function termination.

aa....aa: Reason code indicating the nature of the error

S: Resumes processing.

Action

Take action appropriate to the reason code, as listed below:

Reason code | Explanation | Action
10 | Communication error occurred. | If an error message was issued before this message, take action appropriate to that message.

KFPS00421-W E+L

Too big aa....aa. bb....bb assumed, server=cc....cc

A value larger than that specified for the bb....bb operand was specified for the aa....aa operand. The value specified for bb....bb is assumed.

aa....aa: Operand name

bb....bb: Operand name

cc....cc: HiRDB server name

S: Continues processing.

Action

Revise the value specified for the aa....aa operand.

KFPS00430-E L

Unable to execute aa....aa command. reason code=bb....bb

The indicated command cannot be executed due to an invalid parameter or execution error.

aa....aa: Command name

bb....bb: Reason code indicating the nature of the error

S: Cancels command execution and terminates.

Action

Take action appropriate to the reason code, as listed below, and reenter the command:

Reason code | Explanation | Action
10 | Communication error occurred. | If an error message was issued before this message, take action appropriate to that message
30 | Space shortage occurred. | Check for excessive memory allocation. If too much memory is allocated, release unneeded resources.
40 | Versions do not match | Check the version of each library in HiRDB.
50 | Name server daemon is inactive. | Check if the name server daemon is active

KFPS00433-E E

Unable to execute aa....aa command command execution mode not set up for lock service.

The lock service function is inactive. Or, the command cannot be executed because the system is being terminated.

aa....aa: Command name

S: Cancels command processing.

O: Check that the system has started, then re-enter the command.

KFPS00434-E E

Unable to execute the command versions of the aa....aa command and lock service library different.

Unable to execute the aa....aa command because the command version and the lock HiRDB library version do not match.

aa....aa: Command name

S: Cancels command processing.

Action

Check the command as to whether or not it supports the HiRDB being used, take appropriate action, then re-execute the command.

KFPS00440-W L

Deadlock occurred. server=aa....aa

Deadlock occurred.

aa....aa: Name of the server resulting in deadlock

S: Resumes processing.

KFPS00441-I L

Deadlock information output to aa....aa file.

Deadlock information was output.

aa....aa: Name of the file containing the deadlock information

S: Resumes processing.

Action

Check the output deadlock information and eliminate the cause of the deadlock, if necessary. Delete deadlock information that is no longer needed.

For the output contents of deadlock information, see the HiRDB Version 9 System Operation Guide; for details on how to handle deadlock, see the HiRDB Version 9 UAP Development Guide.

KFPS00442-E E+L

Unable to output deadlock information. reason code=aa....aa

Deadlock information cannot be output.

aa....aa: Reason code indicating the nature of the error

S: Resumes processing.

Action

Take action appropriate to the reason code, as listed below:

Reason code
Explanation
Action

10
Acquisition of the value of PDDIR environment variable failed.
Check if the value of PDDIR has been set.

20
File open processing failed.
Check if there is a %PDDIR%\spool\pdlckinf directory.
Check if there are too many files. If there are too many files, delete any unneeded ones.

30
Error occurred while writing data into a file.
Check if there are too many files. If there are too many files, delete any unneeded ones.

40
Acquisition of time failed.
--

50
Space shortage occurred.
Check for excessive memory allocation. If too much memory is allocated, release unneeded resources.

--: Not applicable

KFPS00443-I L

Insufficient memory in lock table. server=aa....aa, code=bb, using=cc....cc, total=dd....dd, PROGRAM=ee....ee

Server aa....aa does not have enough space in the lock pool (or lock pool partition if the lock pool is divided into partitions) to be used during lock processing.

aa....aa: Server name

bb: Error code

cc....cc: Number of the table currently being used for managing locked resources in which the error occurred

dd....dd: Total number tables for managing locked resources available to all users

ee....ee: UAP identification information

Identification information about the UAP specified in the client environment definition PDCLTAPNAME is displayed. For a utility, the command name is displayed. Some utilities cannot be displayed, in which case the symbol ******** is displayed.

S: Resumes processing.

Action

Take the following action according to the error code:

Error code
Explanation
Action

10
30
A shortage of space for storing tables used to manage locked resources or shared-resource lock waits
Check the cause of this problem by referring to the information about tables for managing locked resources indicated in a KFPS00447-I message, which is output following this message (if multiple messages are output, see the message with a matching process ID in the information attached to the message). For details on tables for managing locked resources, see the HiRDB Version 9 System Operation Guide.
If a UAP is making too many lock requests, revise the UAP to reduce its lock requests. The number of lock requests made per UAP varies with SQL. For details on how to estimate the number of locked resources, see the HiRDB Version 9 System Definition.
A maximum number of lock requests per UAP can be set in the PDLOCKLIMIT client environment definition.
If the estimated number of tables for managing locked resources is too small, either execute the UAP at a different time of day when there is less need to use tables for managing locked resources or change the definitions shown below. When changing a definition, shut down and re-start the entire HiRDB system or the unit in which the problem occurred.

Front-end server:

Increase the value specified in the operand pd_fes_lck_pool_size in the server definition in which the error occurred.

Other servers:

Increase the value specified in the operand pd_lck_pool_size in the server definition in which the error occurred.

20
40
50
A shortage of tables used for storing the lock resource tables to manage transactions or lock-release waits
Reduce the number of UAPs or utilities that are concurrently executed.

60
A shortage of space used for managing locked resources specified in UNTIL DISCONNECT
Increase the value specified in the operand pd_lck_until_disconnect_cnt in the server definition in which the error occurred.

KFPS00444-I L

Number of lock requests exceeds the limit, server=aa....aa, number=bb....bb

Lock requests reached the maximum value at server aa....aa.

aa....aa: Server name

bb....bb: Number of lock requests

S: Resumes processing.

Action

Increase the PDLOCKLIMIT operand value in the client environment definition.

KFPS00446-W L

Lock queue length reached aaa, server=bb....bb, resource type=cccc, resource id=dd....dd

During lock processing of the resource indicated by ID dd....dd, the number of users waiting for locking has reached aaa.

aaa: Number of users waiting for resource lock release

bb....bb: Server name

cccc: Resource type

dd....dd: Resource information

S: Resumes processing.

P: Check whether or not locking of this resource is valid.

O: Check the value specified in the pd_lck_queue_limit operand. If the value is correct, check whether or not locking of this resource is valid. For details on resources, see 6. Lock Control Errors.

KFPS00447-I L

Insufficient exclusive control table information output to aa....aa file

Information about tables for managing locked resources was output.
aa....aa: Name of the file to which information about tables for managing locked resources was output.

S: Continues processing.

P: Check the information about tables for managing locked resources that was output. Determine whether the number of locked resources used by users is appropriate. If necessary, take an action according to the preceding KFPS00443-I message (if multiple messages are output, see the message with a matching process ID in the information attached to the message).

For details on tables for managing locked resources, see the HiRDB Version 9 System Operation Guide.

Action

Check the information on tables for managing locked resources that was output. If necessary, take action according to the preceding KFPS00443-I message (if multiple messages are output, see the message with a matching process ID in the information attached to the message).

For details on tables for managing locked resources, see the HiRDB Version 9 System Operation Guide.

In addition, because the data file for the locked resources management table increases in size, after detection has been completed, or for files that do not need to be detected, delete files where appropriate using one of the following methods:

pdcspool command

The OS's rm command (in UNIX)

Explorer (in Windows)

KFPS00448-E E+L

Unable to output insufficient exclusive control table information. Reason code=aa....aa

Information about tables for managing locked resources cannot be output.

aa....aa: Reason code describing the nature of the error

S: Resumes processing.

Action

Take the following action according to the reason code.

Reason code
Explanation
Action

10
Environment variable PDDIR get failure
Make sure that a value is assigned to PDDIR.

20
File opening failure
Check whether the %PDDIR%\spool\pdlckinf directory exists and make sure that there are not too many files in it. If there are too many files, delete unneeded files using one of the following methods:

pdcspool command

the OS's rm command (in UNIX)

Explorer (in Windows)

30
File write error

40
Time get error
--

50
Shortage of swap area
Make sure that there are no unneeded processes or processes with an excessive amount of memory. If a problem is found, stop the affected process.

--: Not applicable

KFPS00450-W L

Waiting time for exclusive control release out. server=aa....aa, wait_time=bb....bb

Lock release wait timeout occurred.

aa....aa: Name of the server resulting in timeout

bb....bb: Lock-release wait time (seconds)

S: Resumes processing.

KFPS00451-I L

Timeout information output to aa....aa file.

Timeout information was output.

aa....aa: Name of the file to which timeout information was output

S: Resumes processing.

Action

Check the output timeout information and eliminate the cause of the timeout, if necessary. Delete any timeout information that is no longer needed.

For the output contents of timeout information, see the HiRDB Version 9 System Operation Guide.

If timeout resulted from a deadlock, take action appropriate to the deadlock.

For details on how to handle deadlock, see the HiRDB Version 9 UAP Development Guide.

KFPS00452-E E+L

Unable to output timeout information. reason code=aa....aa

Timeout information cannot be output.

aa....aa: Reason code indicating the nature of the error

S: Resumes processing.

Action

Take action appropriate to the reason code, as listed below:

Reason code | Explanation | Action
10 | Acquisition of the value of PDDIR environment variable failed. | Check if the value of PDDIR has been set.
20 | File open processing failed. | Check if there is a %PDDIR%\spool\pdlckinf directory. Check if there are too many files. If there are too many files, delete any unneeded ones.
30 | Error occurred while writing data into a file. | Check if there are too many files. If there are too many files, delete any unneeded ones.
40 | Acquisition of time failed. | --
50 | Space shortage occurred. | Check for excessive memory allocation. If too much memory is allocated, release unneeded resources.

--: Not applicable

KFPS00460-E E+L

Insufficient memory. size=aa....aa bytes, area type=bb....bb

A memory shortage occurred.

aa....aa: Size of memory that was to be allocated

bb....bb: Type of area resulting in memory shortage:

DYNAMIC_SHMPOOL: Dynamic shared memory area

PROCESS: Process area

STATIC_SHMPOOL: Static shared memory area

S: Resumes processing.

Action

If the memory shortage occurred in the process area, re-evaluate the number of processes, etc., and take appropriate action. If the same error recurs, contact the customer support center.

KFPS00601-I E+L

Shared memory aa....aa found insufficient while executing name service; another bb....bb bytes required.

A shortage occurred in the shared memory while executing the name service function.

aa....aa: HiRDB's internal information

bb....bb: Size insufficiency (in bytes)

S: Cancels the processing requested to the name service function. If the HiRDB system is engaged in startup processing, the startup processing is suspended.

Action

Re-examine the shared memory estimation. Also, if an error message was output before this message, take the action indicated in that message. If this message is output even after these measures, save the contents of the message and contact the customer support center.

KFPS00602-W E

Error occurred during name service for HiRDB/client. reason code=aa....aa, maintenance information=bb....bb

The name service function is no longer available to the HiRDB client functions.

aa....aa: Cause code

bb....bb: Maintenance information

S: Resumes the regular name service function. However, the name service function is no longer available to the client functions.

Action

If the reason code is nclt001 or nclt007, there is a shortage in the process native memory. In this case, take action such as reducing the number of processes.

If the reason code is other than the above, save the contents of this message and contact the customer support center.

Furthermore, if the HiRDB client environment variable specifies a UAP that specified PDHOST, this does not influence the name service facility.

KFPS00606-E E

Definition variable aa....aa specifies undefined host name bb....bb. definition file=cc....cc

Node name bb....bb specified in definition variable aa....aa has not been defined.

aa....aa: HiRDB's internal information

bb....bb: Node name

cc....cc: Erroneous definition file:{SERVER}

SERVER: %PDCONFPATH%\pdsys

S: Resumes analysis of the configuration definition, but does not execute the name service.

Action

Correct the definition file or hosts file and re-execute HiRDB.

KFPS00608-W E+L+R

Interprocess communication error occurred in name service.maintenance information=aa....aa

An interprocess communication error occurred during name service execution.

aa....aa: Maintenance information

S: Resumes processing.

O: Check the following items and take appropriate action:

If any host constituting the HiRDB system has not been started, start it. Similarly, if the LAN has not been started, start it. If this message is output even though all other hosts and the LAN have been started, ignore the message (for example, when starting HiRDB in a parallel configuration).

If communication errors occur frequently, contact the HiRDB administrator and have the administrator check the cause.

Contact the HiRDB administrator and have the administrator check for errors in the HiRDB definition information.

Action

Check the items shown below and take appropriate action:

If the cause of frequent communication error occurrences is known, stop HiRDB, take appropriate action, and then restart HiRDB.

Check that the following definition information is correct; if the information is incorrect, stop the HiRDB system, correct the definition information, then restart the system:
Name of host for which the -x and -c options were specified in the pdunit operand of the system common definition

If neither of the above applies, contact the customer support center.

KFPS00609-E E+L

Unable to analyze definition file due to insufficient memory

A shortage of process memory was detected. The system common definition file cannot be analyzed.

S: Terminates processing.

Action

Use the following methods to increase the amount of available memory and restart the HiRDB system:

Reduce the number of other processes running in the same machine.

Increase the swap area.

Add more real memory.

KFPS00610-I L

Transaction queuing started, queuing unit=aa....aa, down unit=bb....bb

If rapid system switchover or standby-less system switchover (1:1):

Transaction queuing started at the aa....aa unit because the bb....bb unit is terminating abnormally.

If standby-less system switchover (effects distributed):

Because server bb....bb is abnormally terminating, transaction queuing has started on unit aa....aa.

This message is output when the unit queuing the transaction receives a transaction queuing communication.

aa....aa: Name of the unit queuing the transaction

bb....bb:

If rapid system switchover or standby-less system switchover (1:1): Name of the unit that is abnormally terminating

If standby-less system switchover (effects distributed): Name of the server that is abnormally terminating

cc....cc:

If rapid system switchover or standby-less system switchover (1:1): unit

If standby-less system switchover (effects distributed): server

S: Starts transaction queuing. There are also cases when a transaction start error occurs and the retry process queues a transaction before this message is output.

KFPS00611-I L

Transaction queuing ended, queuing unit=aa....aa, down unit=bb....bb

If rapid system switchover or standby-less system switchover (1:1):

The aa....aa unit terminates transaction queuing because the bb....bb unit is ready to receive a transaction.

If standby-less system switchover (effects distributed):

The aa....aa server terminates transaction queuing because the bb....bb unit is ready to receive a transaction.

This message is output if the unit that is queuing a transaction receives a communication from the receiving unit that it is ready to receive a transaction.

aa....aa: Name of the unit that is queuing a transaction

bb....bb:

If rapid system switchover or standby-less system switchover (1:1): Name of the unit that is ready to receive a transaction

If standby-less system switchover (effects distributed): Name of the server that is ready to receive a transaction

cc....cc:

If rapid system switchover or standby-less system switchover (1:1): unit

If standby-less system switchover (effects distributed): server

S: Terminates transaction queuing.

KFPS00612-E L

Timeout for transaction queuing occurred, reason=aa....aa, queuing unit=bb....bb, down unit=cc....cc

The transaction queuing process for the bb....bb unit timed out for one of the following reasons:

Even though the value of the pd_ha_trn_queuing_wait_time operand was exceeded, the abnormally terminating unit or server did not communicate that it was ready to receive a transaction.

Even though the value of the pd_ha_trn_restart_retry_time operand was exceeded, the abnormally terminating unit or server did not start.

aa....aa: Timeout reason

pd_ha_trn_queuing_wait_time: Exceeded the value of the pd_ha_trn_queuing_wait_time operand

pd_ha_trn_restart_retry_time: Exceeded the value of the pd_ha_trn_restart_retry_time operand

bb....bb: Name of the unit queuing a transaction

cc....cc:

If rapid system switchover or standby-less system switchover (1:1): Name of the unit that is abnormally terminating

If standby-less system switchover (effects distributed): Name of the server that is abnormally terminating

dd....dd:

If standby-less system switchover (1:1): unit

If standby-less system switchover (effects distributed): server

S: Terminates transaction queuing. All transactions issued after this transaction generate an error, and none is queued.

Possible causes:

The value of the pd_ha_trn_queuing_wait_time operand or the value of the pd_ha_trn_restart_retry_time operand is too small

The rapid system switchover facility process failed

System switchover processing failed

When the abnormally terminating unit or server becomes ready to receive a transaction, the transaction is processed normally without any error occurring.

Action

Take the following actions:

When aa....aa is pd_ha_trn_queuing_wait_time:
Possible causes:

The HiRDB startup process could not be completed within the pd_ha_trn_queuing_wait_time operand value (time). In this case, increase the pd_ha_trn_queuing_wait_time operand value.

An error occurred during the restart process of the abnormally terminating unit or server, and restart failed. See the message output before this message to determine the cause of the error.

When aa....aa is pd_ha_trn_restart_retry_time:
Possible causes:

The unit or server that abnormally terminated did not restart within the pd_ha_trn_restart_retry_time operand value (time). During system switchover, the disk disconnection process could be taking a long time. In this case, increase the pd_ha_trn_restart_retry_time operand value.

If the system switchover process failed, see the message output before this message to determine the cause of the error. Alternatively, also see the operating system messages or cluster software messages.

KFPS00613-E E+L

Duplicate port number=aa....aa, type=bbbb,cccc

Port numbers bbbb and cccc are duplicates of each other.

aa....aa: Duplicate port number

bbbb and cccc: Duplicate port number types

NAME: HiRDB port number

(Specified in the -p option of the pd_name_port operand or pdunit operand)

SCD: Scheduler port number

(Specified in the -s option of the pd_service_port operand, pd_scd_port operand, or pdunit operand)

TRN: Transaction server port number

(Specified in the -t option of the pd_trn_port operand or pdunit operand)

MLG: message log server port number

(Specified in the -m option of the pd_mlg_port operand or pdunit operand)

ALV: Monitoring server port number between units

(Specified in the -a option of the pd_alv_port operand or pdunit operand)

S: Terminates processing.

Action

Re-examine the contents of the operands corresponding to the port number types (bbbb and cccc), and change the setting values to the correct values. Then, re-execute processing.

KFPS00614-E E+L

Port number not fixed, type=aaaa, unit=bbbb

The aaaa port number was not specified.

aa....aa: Port number

NAME: HiRDB port number

(Specified in the -p option of the pd_name_port operand or pdunit operand)

SCD: Scheduler port number

(Specified in the -s option of the pd_scd_port operand or pdunit operand)

TRN: Transaction server port number

(Specified in the -t option of the pd_trn_port operand or pdunit operand)

MLG: message log server port number

(Specified in the -m option of the pd_mlg_port operand or pdunit operand)

ALV: Monitoring server port number between units

(Specified in the -a option of the pd_alv_port operand or pdunit operand)

bbbb: Unit name

S: Terminates processing.

Action

If you specify Y in the pd_name_fixed_port_lookup operand, you must specify the operand that corresponds to aaaa to specify the port number of the system server that is performing communication between units. If you do not set a port number, when you resolve the address of the system sever that uses port number aaaa, communication processing to all units is generated. If you set a port number, do one of the following:

If an error occurs in the pdconfchk command, specify the operand that corresponds to aaaa, and then re-execute.

If an error occurs in HiRDB start processing, specify the operand that corresponds to aaaa. Then, restart HiRDB.

For details about how to specify each operand, see the manual HiRDB Version 9 System Definition.

KFPS00615-W L

Multi-connection address definition invalid, reason code=aa, hostname=bb....bb

There is an invalid specification related to the multi-connection address facility specified in the system common definition.

aa: Reason code

bb....bb:

Reason code 01: ****

Reason code 02 or 03: Invalid host name specification

S: Continues HiRDB startup processing.

Reason code 01:

Host names for which the -n option of the pdstart operand was set will not be enabled in the multi-connection address facility.

Reason code 02 or 03:

Host names indicated in bb....bb will not be enabled in the multi-connection address facility.

Action

Terminate HiRDB normally, change the system common definition according to the reason code, and then start up HiRDB.

Reason
Code
Meaning
Action

01
The -n option was specified in the pdstart operand, but the -m option corresponds to one of the following:

The -m option has not been specified.

None of the host names specified in the -m option can be resolved.

If the -m option is not specified in the pdstart operand, specify it there.
In all other cases, revise the host name specified in the -m option of the pdstart operand. Take action based on the KFPS00615-W (reason code 02) message.

02
Either the host name specified in the -m option of the pdstart operand in the system common definition is invalid, or the name cannot be resolved.
If the host name is invalid, specify the correct host name.
For other cases, the host name has not been resolved. Record the host name in the hosts file or in the DNS.

03
Either the host name specified in the -n option of the pdstart operand in the system common definition is invalid, or the name cannot be resolved.

KFPS00700-E E+L

Error occurred in system call aa....aa. errno=bbb, function name=cc....cc

A system call aa....aa resulted in an error.

aa....aa: Name of system call

bbb: Return code of the system call

cc....cc: Name of the function resulting in the error

S: Resumes processing, or terminates the HiRDB system abnormally.

Action

Check errno.h or the OS manual for the details of errno (external integer variable indicating the error status), eliminate the cause of the error, then re-execute.

For representative errno, see 4.3 System call return codes.

KFPS00701-E L

Unable to continue processing due to file system error.

A system call for manipulating a file terminated abnormally.

S: Terminates the system.

Action

If another message was output immediately before this message, refer to that message. If there is no problem with the access privilege to the file to be operated on, contact the customer support center.

KFPS00703-E L

Insufficient memory. required memory size=aa....aa bytes, area type=bb....bb

A memory shortage occurred.

aa....aa: Size of the area that was to be allocated

bb....bb: Type of area resulting in memory shortage:

PROCESS: Process private area

STATIC_SHMPOOL: Static shared memory

S: Terminates the system.

Action

If the memory shortage occurred in the process private area, check the number of processes and re-execute.

If the same error recurs, check the cause of the error and contact the customer support center.

KFPS00705-E L

Error found while analyzing definition file.

An error was detected while analyzing a HiRDB system definition file.

S: Waits for the start command.

O: Correct the HiRDB system definition file and enter the pdstart command.

Action

If another message was output immediately before this message, refer to that message. If there is no error in the HiRDB system definition file, contact the customer support center.

KFPS00707-E L

Max number of processes in process service definition invalid

The specified maximum number of processes is invalid in the system common definition or unit control information definition.

S: Waits for the start command.

O: Correct the definition file and reenter the pdstart command. If the definition file is correct, contact the customer support center.

KFPS00709-E L

Process monitoring time in process service definition invalid

The specified process monitoring interval is invalid in the system common definition or unit control information definition.

S: Waits for the start command.

O: Correct the definition file and reenter the pdstart command. If the definition file is correct, contact the customer support center.

KFPS00710-E E+L

Shared memory unavailable; unable to continue processing.

Shared memory is not available to a process server process. Another possibility is that shared memory is not available to a command.

S: Terminates the system. In the case of a command, terminates it abnormally.

O:

In the case of a process server process:

Contact the customer support center.

In the case of a command:

Reenter the command. If HiRDB is not started or if it is in the process of starting, wait for HiRDB start processing to complete and then execute the command. If the same message is output even after executing this command a number of times, contact the customer support center.

KFPS00712-E E+L

Unable to continue processing due to program error or hardware failure.

Processing cannot continue due to a program error or a hardware failure.

S: Terminates the system.

Action

Check the cause of the error and contact the customer support center.

KFPS00713-E L

Load module bb....bb for server aa....aa not found.

Load module bb....bb for server aa....aa was not found.
aa....aa: Server name
bb....bb: Load module name
S: Terminates the system abnormally.

Action

Determine the cause of the error and contact the customer support center.

KFPS00714-E L

Load module bb....bb for server aa....aa not executable file.

Load module bb....bb for server aa....aa is not an executable file.

aa....aa: Server name

bb....bb: Load module name

S: Terminates the system abnormally.

Action

Determine the cause of the error and contact the customer support center.

KFPS00715-E E+L

Unable to continue processing serious error occurred (reason code=aaa). enter pdrpause

HiRDB processing cannot continue due to an error.

aaa: Reason code

1: One of the following errors was found:

An error was found in the setting of environment variable PDDIR.

The content of /etc/inittab is invalid (in UNIX).

The installation directory name contains a space (in UNIX).

The HiRDB installation target is invalid (in Windows).

The HiRDB installation did not terminate normally (in Windows).

2: There is a memory shortage.

3, 4, 13, 44, 101: Failed to open the status file.

5, 104: Failed to read the status file.

6: Failed to acquire the time.

7: HiRDB terminated abnormally three consecutive times during the restart process. However, if the pd_term_watch_count operand is specified, HiRDB terminated abnormally the number of consecutive times this operand was specified.

8: The content of the status file is invalid.

9, 105: Failed to move the file pointer in the status file.

10, 14, 42, 102: Failed to write to the status file.

11, 15, 103: Failed to close the status file.

16: Common memory is corrupted.

20: This is a definition error.

21: Failed to move the directory.

22: Failed to copy the common library (the file system is full or text busy).

30: No related program product is installed.

43: Failed to change privileges of the status file.

S: Terminates processing.

Action

Take the following action:

Ignore this message if 1 is specified in the pd_start_level operand in the system definition and it is okay to continue the start process, except for the unit in the additional information of this message.

Execute the pdstop -f command if this message is output, and then the pdstart command did not terminate.

If an error message or a warning message in the event log (in UNIX, syslogfile) of the system manager unit was output before or after this message, take the action for that message.

If an error message or a warning message in the event log (in UNIX, syslogfile) of a unit in the additional information of this message before or after this message was output, take the action for that message.

Eliminate the cause of the error according to the reason code for a unit in the additional information of this message.

In UNIX, execute the pdrpause command for a unit in the additional information of this message.

In Windows: Restart the service. If the service did not stop, stop the service, and then restart it.

Execute the pdstart command.

If a problem occurs that the HiRDB administrator cannot resolve, contact the customer support center.

KFPS00717-E L

System went down aaa consecutive times.

The system shut down aaa times in a row.

aaa: Abnormal terminations count

S: Cancels HiRDB restart processing.

Action

Refer to the message that was output before this message to eliminate the cause of the error, then restart. If the error cannot be corrected by the HiRDB administrator, contact the customer support center.

KFPS00719-E E+L

Message output error. message ID= aaa

An error occurred during message output.

aaa: ID of the message that was to be output

S: Resumes processing.

O: Take an operator's action appropriate to the displayed message ID.

Action

Take a HiRDB administrator's action appropriate to the displayed message ID.

KFPS00720-E L

Load module name not defined in definition file of server aa....aa

A load module name (set module =) is not defined in the server definition file.

aa....aa: Server name (same as the definition file name)

S: Resumes processing.

O: Specify the load module name in the definition file and restart the server.

Action

Contact the customer support center.

KFPS00721-E E

Versions of process service library and process service daemon different.

The process server process does not match the version of the library that issued a service request to the process server process. Therefore, the process server process cannot execute the service.

S: Cancels processing.

Action

Re-create the user server or command using a library that is supported by the HiRDB system that is being used, and restart. If the same error recurs, contact the customer support center.

KFPS00722-E E+L

Unable to excute recover process, code=aa....aa

Process activation failed while recovering an abnormally terminated process.

aa....aa: Error code:

-729: Attempt was made to activate more processes than the value specified in the pd_max_server_process operand

Other: Internal error occurred

S: Terminates abnormally.

Action

Take action appropriate to the error code:

-729: Increase the value of the pd_max_server_process operand in the system common definition or unit control information definition

Other: Take appropriate action to the message output before this message

KFPS00727-E L

HA monitor has been stopped

The HA monitor or the Hitachi HA Toolkit Extension is currently stopping.

S: Terminates abnormally.

O: Start the HA monitor or the Hitachi HA Toolkit Extension and restart HiRDB.

KFPS00728-E L

System error detected during communication with HA monitor. error code=aaaa, detail code=bbbb

A system error was detected during communication processing with the HA monitor or Hitachi HA Toolkit Extension.

aaaa: The HA monitor or Hitachi HA Toolkit Extension's return code

bbbb: The HA monitor or Hitachi HA Toolkit Extension's detail return code

S: Terminates abnormally.

Action

Check whether the HA monitor or Hitachi HA Toolkit Extension is running. If it is running, contact the customer support center.

KFPS00729-E L

Unable to continue HiRDB unit processing because server process went down aa....aa times; stops HiRDB unit bbbb

Unit bbbb terminated abnormally because a HiRDB server process terminated abnormally aa....aa times within the monitoring interval of the process abnormal termination count monitoring facility (the pd_down_watch_proc operand).

aa....aa: Number of times the server process terminated abnormally

bbbb: Unit identifier

S: Abnormally terminates.

Action

See the message output after this message and start HiRDB if necessary. To avoid abnormal termination of HiRDB due to abnormal termination of a server process, either omit the pd_down_watch_proc operand or specify 0. For details about the abnormal termination monitoring facility, see the HiRDB Version 9 System Operation Guide.

KFPS00730-I S

pdpfresh ended, return code = aa....aa

The pdpfresh command ended with return code aa....aa.

aa....aa: Return code (see Action below)

S: Continues processing if the -c option is not specified when the pdpfresh command is executed and the return code is 0 or 4. Otherwise, terminates processing.

Action

Take action according to the following return codes:

Return code
Processing results of the pdpfresh command
Action

0
No -c
Started refreshing the server process.
None.

-c
No server process is currently refreshing.

1
No -c
Is not set.
Procedure:

Execute the pdls -d prc -c command. The server process whose STATUS is C might be accessing a HiRDB file system area, including subsystem RDAREAs.

If it is okay to forcibly refresh this process, execute the pdpfresh -f command again. If you decide not to refresh this process, re-execute the pdpfresh command after the running process terminates (if necessary, take action so the server process will terminate).

-c
A server process is currently refreshing.

4
The warning ended (an error occurred on at least one server).
Check the status of the server where the error occurred. If it is running, that server's server process might remain in a state in which it is accessing an RDAREA (which prevents resynchronizing of the pair volume). Specify that server in the pdpfresh command, and then retry the operation.

6
Terminated because the utility is running.
After the utility terminates, re-execute the pdpfresh command. Alternatively, if it is okay for an error to occur in the currently running utility, re-execute the pdpfresh -p command.

8
Abnormally terminated.
Contact the customer support center.

KFPS00731-E L

Unable to create desktop, because of insufficient desktop heap. Required memory size=aa....aa(bb....bb) bytes

Desktop heap is insufficient, so desktop creation failed.

aa....aa: Memory size that the system attempted to allocate

bb....bb: Insufficient memory size

S: Terminates the command abnormally.

Action

Stop any other processes that are running. In addition, calculate how much desktop heap is used by HiRDB, specify in the pd_max_server_process operand a value at or below the maximum desktop heap value, and then restart HiRDB. For details about how much desktop heap is used by HiRDB, see the manual HiRDB Version 9 System Definitions.

KFPS00750-E E

Unable to execute command due to insufficient memory. required memory size=aa....aa bytes, area type=bb....bb

A command cannot be executed due to a memory shortage.

aa....aa: Size of the area that was to be allocated

bb....bb: Type of area resulting in memory shortage:

PROCESS: Process private area

STATIC_SHMPOOL: Static shared memory

S: Terminates the command abnormally.

Action

If the memory shortage occurred in the process private area, check the number of processes and re-execute.

If the same error recurs, check the cause of the error and contact the customer support center.

KFPS00751-E E

Command syntax incorrect.

A syntax error was detected in a command.

O: Check the command syntax.

KFPS00752-E E

Load module name invalid.

The length of a pdls command argument (load module name) is invalid.

O: Set the correct argument.

KFPS00753-E E

Server name invalid.

The length of a pdls command argument (server name) is invalid.

O: Set the correct argument.

KFPS00754-E E

Process ID invalid.

The length of a pdls command argument (process ID) is invalid.

O: Set the correct argument.

KFPS00755-E E+L

Inter-process communication unavailable.

A command cannot be executed because inter-process communication is not available. Possible reasons are as follows:

HiRDB is not active.

An inter-process communication environment has not been set up

S: Terminates processing.

O: Enter the command when the HiRDB system is active.

KFPS00756-E E

Command argument invalid.

A command argument is invalid.

O: Set the correct argument.

KFPS00759-E E

Service group name invalid.

The length of a pdls command argument (service group name) is invalid.

O: Set the correct argument.

KFPS00760-E E

Unable to execute pdrpause command, HiRDB unit is not PAUSE

The pdrpause command cannot be executed because the pause of HiRDB startup or restart processing has been released.

S: Terminates processing.

O: There is no need to execute the pdrpause command.

KFPS00791-I S

Usage: pdls -d prc {[-a |-s server ID |-g service group name |-l load module name |-p process ID]}

Displays the format of the pdls command. This message is displayed when the command specification is invalid.

S: Terminates the command abnormally.

O: Reenter correctly the specified command.

KFPS00793-I S

Usage : pdrpause

The specification format of the pdrpause command is invalid.

S: Terminates processing.

O: Specify the command correctly and re-execute.

KFPS00803-E E+L

Unable to start scheduler. reason code=aa....aa

An error occurred during scheduler normal startup or restart processing.

aa....aa: Reason code indicating the nature of the error

S: Cancels HiRDB system normal startup or restart processing.

Action

Take action appropriate to the reason code in the list, and restart HiRDB. The following table shows the reason codes and actions:

Reason code
Explanation
Action

1
Impossible to allocate shared memory
If an error message has been output before this message, take action appropriate to that message and restart HiRDB.

2
Definition analysis error

5
Communication error
The port number specified in the -s option of the pd_service_port operand, pd_scd_port operand, or pdunit operand might be the same as the port number of another definition or program. If they are the same, change one of the values in the port number settings so that they do not overlap, and then restart.
Otherwise, if any error messages were output before this message, take corrective action according to those messages, and then restart.

6
Queue information file access error
Check whether there is an access privilege to the spool directory under the HiRDB working directory. If there is an access privilege, contact the customer support center.

KFPS00830-E E+L

Unable to start server aa....aa, reason code=b

An error occurred during the server start process.

aa....aa: Name of the server that cannot start

b: Reason code indicating the error content

S: Aborts the server start process.

O: If it is necessary to start the applicable server, after the HiRDB administrator takes action, start the server using the pdstart -s command.

Action

Take action appropriate to the reason code, as listed below:

Reason code
Explanation
Action

1
Server already active
Specified server or service group has already been started; if the specification is invalid, specify the correct server name and enter the pdstart -s command.

2
Timing error
Scheduler has not been started or is engaged in termination processing; enter the pdstart -s command after restarting the system.

3
Invalid number of servers
The maximum number of servers that can be run under the scheduler has been exceeded; check the schedule service definition, take appropriate action, then enter the pdstart -s command.

4
Communication error
If an error message has been output before this message, take action appropriate to that message and enter the pdstart -s command.

5
Incompatible program versions
Check the version of each library in the HiRDB system, take appropriate action, then enter the pdstart -s command.

6
Unable to activate a resident process
Check and, if necessary, change the number of processes that the applicable server machine can start (for example, pd_process_count and pd_max_server_process). If this message is output after HiRDB starts, execute the pdstart command and restart HiRDB. If this error occurs when executing the pdstart -s command, re-execute the pdstart -s command.

7
Memory shortage
Check the memory size specified in the definition, take appropriate action, then enter the pdstart -s command.

8
Definition analysis error
If an error message has been output before this message, take action appropriate to that message and enter the pdstart -s command.

KFPS00835-E E+L

Unable to terminate server aa....aa. reason code=bb....bb

An error occurred during server termination processing.

aa....aa: Name of server that cannot be terminated

bb....bb: Reason code indicating the nature of the error

S: Cancels server termination processing.

O: If the server needs to be terminated, take the appropriate HiRDB administrator's action and terminate the server with the server termination command (pdstop -s).

Action

Take action appropriate to the reason code, as listed below:

Reason code | Explanation | Action
1 | Server inactive | Specified server or service group has not been started; if the specification is invalid, specify the correct server name and enter the pdstop -s command.
2 | Timing error | Scheduler has not been started or is engaged in termination processing; enter the pdstart -s command after restarting the system.
3 | Communication error | If an error message has been output before this message, take action appropriate to that message and enter the pdstart -s command.
4 | Incompatible program versions | Check the version of each library in the HiRDB system, take appropriate action, then enter the pdstop -s command.
5 | Memory shortage | Check the memory size specified in the definition, take appropriate action, then enter the pdstop -s command.
6 | Definition analysis error | If an error message has been output before this message, take action appropriate to that message and enter the pdstart -s command.

KFPS00836-E E+L

Unable to create a server process. server=aa....aa, reason code=bb....bb (cc....cc)

Server processing generation occurred during server scheduling.

aa....aa: Name of the server that could not create the process

bb....bb: Reason code for process creation error

cc....cc: Internal code

S: Resumes processing.

Action

Take action appropriate to the reason code:

Reason code
Explanation
Action

1
Maximum number of processes was exceeded
Decrease the number of processes being executed. Alternatively, increase the value specified in the pd_max_server_process operand.

2
Memory shortage (fork error)
Correct the memory shortage.

99
HiRDB internal error
Check the message or the internal and error detail codes that were output before this message and eliminate the cause of the error.
If the standby-less system switchover (effects distributed) facility is being used, internal code -725 may be output during system switchover, but this is not a problem because server startup is suppressed during switchover.

KFPS00840-E E+L

Error occurred while analyzing definitions. server attribute=aa....aa

An error occurred while analyzing the system definition information.

aa....aa:

Type of server subject to system definition information analysis:

"SYSTEM": System server

"USER": Front-end server, back-end server, or dictionary server

The system processing and action to take differ depending on the server attributes.

System server:

S: Terminates HiRDB abnormally.

Action

If an error message was output before this message, take the action indicated in that message, and restart HiRDB. If the same error recurs, contact the customer support center.

HiRDB/Parallel Server:

S: Cancels the server processing and terminates the process.

Action

Check the corresponding server definition, take appropriate action, and then restart the server with the pdstart -s command. If the same error recurs, contact the customer support center.

KFPS00841-E E+L

Service group name not defined in server definition file. server=aa....aa

A service group name is not defined in the server definition file.

aa....aa: Name of the server resulting in the definition error

S: Cancels server startup processing.

O: If the server needs to be started, take the appropriate HiRDB administrator's action and enter the server startup command (pdstart -s).

Action

Specify the server group name in the corresponding server definition file.

KFPS00843-I S+L

Changed process count. server: aa....aa

The number of resident server processes and the maximum number of startup processes have been changed.

aa....aa: Name of the server for which the values have been changed

S: Resumes processing.

KFPS00844-E E+L

Error code in pdchprc command. server:aa....aa, reason code=bb

An error occurred during pdchprc command execution.

aa....aa: Name of the server resulting in the error

Depending on the timing of the error, ******** may be output as the server name.

bb: Reason code indicating the nature of the error

S: Terminates processing.

Action

Take action appropriate to the reason code:

Reason code
Explanation
Action

11
Server inactive
If an invalid server name was specified, enter the pdchprc command with the correct server name specified.

12
Invalid server name
Enter the pdchprc command with the correct server name specified.

13
Server terminating
If an invalid server name was specified, enter the pdchprc command with the correct server name specified.

14
Unit did not start up
After startup of the server aa....aa unit is complete, execute the pdchprc command.

16
Alternating
The number of normal BES server processes cannot be changed, because processing is alternating with alternate BES units. To change the number of normal BES server processes that are alternating with alternate BES units, change the number of alternate BES server processes. However, the number of alternate BES server processes at this time will be the total number of normal BES server processes that are alternating with alternate BES units. For details, see Server process allocation after system switchover in the HiRDB Version 9 System Operation Guide.

21
Definition analysis error
If an error message was output before this message, take action appropriate to that message.

22
Communication timeout

23
Memory shortage
Take appropriate action to prevent a memory shortage.

24
Mismatched program versions
Check the version of each HiRDB library and take appropriate action.

25
Maximum number of processes exceeded
Reduce the number of processes being executed.

26
Communication error
If an error message was output before this message, take action appropriate to that message.

Other
Does not apply
If an error message was output before this message, take the action indicated in that message. If no message was output, contact the customer support center.

KFPS00847-W E+L

Unable to delete message queue automatically in next system startup; queue information failed to be cataloged. server=aa....aa

The message queue cannot be deleted automatically at the next system startup, because the queue information file write operation failed.

aa....aa: Name of the server resulting in the queue information write error

If the unit is applicable to the standby-less system switchover (effects distributed) facility, ****** may be output instead of the server name.

S: Resumes processing.

Action

Take action appropriate to the error message output before this message. When HiRDB is stopped, use the ipcrm command to delete the relevant message queue.

KFPS00849-W E+L

Specified aa....aa is too large for max users, assumed limit bbb, server:cc....cc

The number of processes specified in the pdchprc command is greater than the maximum number of startup server processes defined for the HiRDB.
The system resumes processing assuming the maximum number of startup server processes specified in the HiRDB definition.

aa....aa: Item whose value is to be modified:

max_process_count: Maximum number of startup processes

resident_process_count: Number of resident processes

bbb: Maximum number of startup server processes specified in the HiRDB definition

cc....cc: Server name

S: Resumes processing.

O: If there are too many processes, enter the pdchprc command to reduce their number.

KFPS00850-E E+L

Unable to perform scheduling for server bb....bb due to an error in system call aa....aa. errno=cc....cc

The indicated server cannot be scheduled, because system call aa....aa resulted in an error.

aa....aa: Name of the system call resulting in the error

bb....bb: Name of the server on which the error occurred

If the unit is applicable to the standby-less system switchover (effects distributed) facility, ****** may be output instead of the server name.

cc....cc: System call return code

S: Terminates the scheduling on the indicated server; continues other scheduling operations. However, if the server name is ******, startup of the unit is terminated.

Action

In UNIX:

Based on the return information, determine and correct the cause of the error. If the cause cannot be determined, contact the customer support center.

If an error occurs in the MSGGET system call, the value of the operating system parameter (kernel parameter) msgmni (message queue identifier count) in the operating system may be too small. Estimate the amount required for all programs to run on the server machines when msgmni is invoked. Reboot the applicable server machines after changing the specified value.

If an error occurs in the MSGSND or MSGRCV system calls, the value of the operating system parameters (kernel parameters) msgmni or msgtql in the operating system may be too small. Estimate the amount required for all programs to run on the server machines. Reboot the applicable server machines after changing the specified value. Also, the message queue HiRDB uses may have been improperly deleted by the ipcrm or other command. If the message queue was deleted, forcibly terminate HiRDB if it does not abnormally terminate. Then, reboot the applicable server machines.

If the HiRDB server's start processing terminates without outputting message KFPS01851-E, even though errno=11 (EAGAIN) occurred in the MSGSND system call, the HiRDB server's start processing has terminated normally and this message KFPS00850-E can be ignored.

In Windows:

Estimate the number of message queue identifiers required by HiRDB, and specify a value at least that large in the PDUXPLMSGMNI and PDUXPLMSGTQL system environment variables. Then, terminate HiRDB and restart all services. For details on how to estimate the number of needed message queue identifiers, see the HiRDB Version 9 Installation and Design Guide.
In addition, if message KFPS02179-I is output frequently, consider following the actions described in message KFPS02179-I to reduce the number of skips in synchronization point processing.

If the HiRDB server's start processing terminates without outputting message KFPS01851-E, even though errno=11 (EAGAIN) occurred in the MSGSND system call, the HiRDB server's start processing has terminated normally and this message KFPS00850-E can be ignored.

KFPS00851-E E

Unable to delete message queue due to an error occurred in MSGCTL system call. errno=aa....aa, queue ID=bb....bb

In UNIX:

The message queue cannot be deleted, because the MSGCTL system call resulted in an error.

In Windows:

The message queue cannot be deleted, because an error occurred.

aa....aa: Return code of the system call

bb....bb: ID of the message queue resulting in the error

S: Resumes processing.

O: To delete message queues in UNIX, use the ipcrm command to delete the appropriate message queues.

In the case of Windows, restart the HiRDB service. If the error recurs even after a restart or if the cause cannot be determined, contact the customer support center.

Action

In UNIX, refer to the OS manual to determine the cause on the basis of the return code of the system call, and take action. If the cause of the error cannot be identified or the message is reissued, contact the customer support center.

KFPS00852-E E

Unable to delete message queue due to queue information acquisition failed. reason code=aa....aa

The message queue cannot be deleted, because acquisition of queue information failed.

aa....aa: Reason code

S: Cancels message queue deletion processing.

Action

If an error message has been output before this message, take action appropriate to that message. The following table lists the reason codes and the actions to be taken:

Reason code | Explanation | Action
1 | Memory shortage | Terminate any unneeded processes and restart.
2 | Queue information file access error | If an error message has been output before this message, take action appropriate to that message and restart. Also, check for any unauthorized access to a file under %PDDIR%\spool.
3 | Incompatible program versions | Check the versions of HiRDB commands, libraries, etc., take appropriate action, then restart.
4 | Invalid environment variable | Set the correct environment variable and restart.

KFPS00854-W E+L

Insufficient memory in message buffer pool. server=aa....aa

During allocation on the indicated server, a memory shortage occurred in the message storage buffer pool. Because of this the service cannot be executed on the indicated server.

aa....aa: Name of the server where the buffer shortage occurred

S: Resumes processing.

Action

Take the following actions:

If the name of the server is _trnrcv

There is insufficient space in the transaction recovery message queue. Refer to the pd_trn_rcvmsg_store_buflen operand in the manual HiRDB Version 9 System Definition and increase the size of the transaction recovery message queue.

If the name of the server is not _trnrcv

If this message is output during execution of a UAP:

If you are executing UAPs concurrently, reduce the number of UAPs that are executed concurrently.

If the pdchprc command was used to request services from a server for which the maximum number of startup processes had been set to 0, use the pdchprc command to increase the maximum number of startup processes.

If the pdpfresh command was used to request services from a server that is being refreshed, re-execute the UAP after the pdpfresh command terminates.

If this message is output during execution of a utility:

If you are executing utilities concurrently, review and, if necessary, change the maximum number of utilities that can be executed concurrently. To find out the maximum number of utilities that can be executed concurrently, see the manual HiRDB Version 9 Command Reference.

If the pdchprc command was used to request services from a server for which the maximum number of startup processes had been set to 0, use the pdchprc command to increase the maximum number of startup processes.

If the pdpfresh command was used to request services from a server that is being refreshed, re-execute the utility after the pdpfresh command terminates.

If this message is output during execution of a command:

If you are executing commands concurrently, reduce the number of commands that are executed concurrently.

If the pdchprc command was used to request services from a server for which the maximum number of startup processes had been set to 0, use the pdchprc command to increase the maximum number of startup processes

If the pdpfresh command was used to request services from a server that is being refreshed, re-execute the command after the pdpfresh command terminates.

KFPS00855-W E+L

Insufficient memory. required area size=aa....aa bytes, area type=bb....bb

A memory shortage occurred.

aa....aa: Size of the area that was to be allocated

bb....bb: Type of area resulting in memory shortage:

DYNAMIC SHMPOOL: Dynamic shared memory area

PROCESS: Process private area

STATIC SHMPOOL: Static shared memory area

S: Resumes processing.

Action

If an error message was output before this message, take the action indicated in the message. If the type of the area where a memory shortage occurred is a process private area, take the following action and then re-execute.

Reduce the number of resident HiRDB server processes.

Stop unnecessary processes.

Extend the virtual memory.

If the same error recurs, contact the customer support center.

KFPS00856-E E+L

Scheduler library and scheduler daemon have different version

The version of the scheduler library does not match the version of the scheduler process.

S: Terminates processing.

Action

Contact the customer support center.

KFPS00857-E E+L

Mismatched version found during scheduler processing, version type=aa....aa

A version mismatch was detected during scheduler processing.

aa....aa: Type of version resulting in mismatch:

COMMAND: Command version

HOLD: Shutdown file version

NAMDATA: Name server registration version

QUEUE: Queue information file version

REQUEST: Service request header version

STATUS: Status file version

TABLE: Table version

S: Terminates processing.

Action

Check the current HiRDB environment, take appropriate action, and restart HiRDB.

KFPS00860-W E+L

Pd_service_port ignored, reason code=aaaa(bbbbb), cannot use PDSERVICEPORT for HiRDB/client.

HiRDB ignored the specification of the pd_service_port operand for the reason indicated in aaaa(bbbbb), and continued processing. A HiRDB client cannot use the high-speed connection feature. An attempt to use a high-speed connection to the HiRDB where this message was output fails because the HiRDB server is not active.

aaaa: Reason code

bbbbb: Maintenance information for the displayed reason code:

Reason code 1:
0

Reason code 2 or 3:
-208: HiRDB-provided load module is invalid

S: Resumes processing.

O: Take action appropriate to the reason code:

Reason code
Explanation
Action

1
The value of the pd_service_port operand is the same as the value of the pd_name_port operand.
The port number specified in the pd_service_port operand in the system common definition or unit control information definition is the same as the port number specified in the pd_name_port operand. Change a definition so that these values are not duplicated, then re-execute HiRDB.

2
3
Definition analysis is invalid.

Maintenance information: -208
HiRDB may not have been installed correctly, or the HiRDB-provided load module may be invalid. Reinstall and set up HiRDB, then re-execute.

Maintenance information: Other than -208
Contact the administrator.

Action

If none of the reasons provided under "O" applies, contact the customer support center.

KFPS00880-I S

Usage: pdls -d scd [-s server name]

The format of an option is invalid in the pdls -d scd command.

S: Terminates processing.

Action

Reenter correctly the specified command.

KFPS00888-W L

Server aa....aa exceeded pd_queue_watch_time value. value=bb....bb

No message can be acquired from the message queue even if the message queue monitoring time (pd_queue_watch_time operand value) of the message queue monitoring facility is exceeded. The problem occurred on server aa....aa. For details about the message queue monitoring facility, see the HiRDB Version 9 System Operation Guide.
Possible causes of the message queue monitoring time being exceeded:

The CPU load reduced the processing capacity.

I/O is delayed by an I/O error.

The number of processes available is less than the number required for fetching messages from the message queue because the number of HiRDB server processes is too small for the number of multiply executing UAPs and utilities.

The number of HiRDB server processes is restricted by the following operands:

pd_max_server_process
If there are several servers running within a unit, perform a detailed estimate of the value specified for this operand. Also, if the standby-less system switchover facility is being used, the estimate must include the case of a system switchover.

pd_max_bes_process
If multiple front-end servers are being used or if the standby-less system switchover (1:1) facility is being used, perform a detailed estimate of the value specified for this operand.

pd_max_dic_process
If multiple front-end servers are being used, perform a detailed estimate of the value specified for this operand.

pd_ha_max_server_process
If the standby-less system switchover (effects distributed) facility is being used, perform a detailed estimate of the value specified for this operand.

pd_max_users
If there are numerous concurrent connections, an appropriate value must be selected.

aa....aa: Server name

bb....bb: Value of the pd_queue_watch_time operand

S: Continues processing.

Action

For details on causes of and actions for server processes not responding, and messages remaining in the message queue, see the HiRDB Version 9 System Operation Guide.

If you are unable to determine the cause of the problem, contact the customer support center.

KFPS00889-E L

Server aa....aa exceeded pd_queue_watch_time value, Unit terminated.

No message can be acquired from the message queue even if the message queue monitoring time (pd_queue_watch_time operand value) of the message queue monitoring facility is exceeded. The problem occurred on server aa....aa.
The unit is terminated because stop was specified in the pd_queue_watch_timeover_action operand. For details about the message queue monitoring facility, see the HiRDB Version 9 System Operation Guide.
Possible causes of the message queue monitoring time being exceeded:

The CPU load reduced the processing capacity.

I/O is delayed by an I/O error.

The number of processes available is less than the number required for fetching messages from the message queue because the number of HiRDB server processes is too small for the number of multiply executing UAPs and utilities.

The number of HiRDB server processes is restricted by the following operands:

pd_max_server_process
If there are several servers running within a unit, perform a detailed estimate of the value specified for this operand. Also, if the standby-less system switchover facility is being used, the estimate must include the case of a system switchover.

pd_max_bes_process
If multiple front-end servers are being used, or if the standby-less system switchover (1:1) facility is being used, perform a detailed estimate of the value specified for this operand.

pd_max_dic_process
If multiple front-end servers are being used, perform a detailed estimate of the value specified for this operand.

pd_ha_max_server_process
If the standby-less system switchover (effects distributed) facility is being used, perform a detailed estimate of the value specified for this operand.

pd_max_users
If there are numerous concurrent connections, an appropriate value must be selected.

aa....aa: Server name

S: Abnormally terminates HiRDB.

Action

For details on causes of and actions for server processes not responding, and messages remaining in the message queue, see the HiRDB Version 9 System Operation Guide.

If you are unable to determine the cause of the problem, contact the customer support center.

KFPS00890-E E

Error occurred during scheduler command processing. reason code=aa....aa, command=bb....bb

An error occurred during scheduler command processing.

aa....aa: Reason code indicating the nature of the error

bb....bb: Command name

S: Cancels command processing.

O: Take action appropriate to the reason code, as listed below, and reenter the command:

Reason code | Explanation | Action
31 | Memory shortage | Determine the number of active processes, and reduce the amount of memory used. Also, if an error message was output before this message, take the action indicated in that message. After taking action, re-execute the command.
33 | Definition analysis error | If an error message has been output before this message, take action appropriate to that message and reenter the command.

KFPS00891-E E

Invalid use of command aa....aa

The usage of command aa....aa is invalid.

aa....aa: Command name

S: Terminates processing.

Action

Reenter the command with the correct usage.

KFPS00892-E E

Scheduler inoperable; unable to execute aa....aa command

The scheduler is inactive. Or, the indicated command cannot be executed because the system is engaged in termination processing.

aa....aa: Command name

S: Cancels command processing.

O: Reenter the command after system startup is completed.

KFPS00894-E E

Scheduler aa....aa command and scheduler daemon have different version

The version of scheduler command aa....aa does not match the version of the process program.

aa....aa: Command name

S: Cancels processing.

Action

Check the commands available to the HiRDB that is being used, take appropriate action, then reenter the command. If the same error recurs, contact the customer support center.

KFPS00900-I L

Communication protocol error occurred. status code=aaaaaa, request code=bbbb, branch number=ccccc, server=dddddd

A communication protocol error occurred during transaction processing.

aaaaaa: HiRDB internal code (status code)

bbbbbb: HiRDB internal code (request code)

cccccc: HiRDB internal code (branch number)

dddddd: Server name

Action

Take one of the following actions:

Tune the RPC and socket-related communication parameters by referring to the manual for the OS being used, a TCP/IP network guide, and the HiRDB Version 9 System Definition manual.

Increase the concurrency level of the corresponding server.

Check the network workload of the server machine where the corresponding server is located.

KFPS00935-I L

Transaction decision resending aa....aa, TRNGID=bb....bbcc....cc, TRNBID=bb....bbdd....dd, server=ee....ee, completion type=f

Retransmission processing of a rollback request has either started or stopped. This message is output either at the expiration of the maximum wait time for rollback completion response specified in the pd_trn_rollback_watch_time operand in the system common definition, or when the transaction is completed after retransmission of the rollback request.

aa....aa: Processing event

start: Processing started

stop: Processing stopped

bb....bb: HiRDB identifier, and unit identifier

cc....cc: Global transaction number

dd....dd: Transaction branch number

ee....ee: Name of server

f: Global transaction completion type

r: Rollback

S: Continues processing.

KFPS00936-E L

Transaction decision resending timeout occurred, TRNGID=aa....aabb....bb, TRNBID=aa....aacc....cc, server=dd....dd, reason=ee....ee

Retransmission stopped because the rollback instruction retransmission time limit elapsed. This message is output after the start of retransmission processing of the rollback request, at the expiration of the rollback instruction retransmission time limit specified in the pd_trn_rollback_watch_time operand in the system common definition.

aa....aa: HiRDB identifier, and unit identifier

bb....bb: Global transaction number

cc....cc: Transaction branch number

dd....dd: Name of server

ee....ee: Reason code

COMMUNICATION: An inter-process communication error occurred.

S: Abnormally terminates the relevant HiRDB server process.

O: Contact the HiRDB administrator.

Action

Execute the pdls -d svr command to make sure that the dictionary server and all back-end servers are up and running. Check the status information, and if there is a server that is not running, restart it according to the description of the execution results of the pdls -d svr command in the manual HiRDB Version 9 Command Reference.

KFPS00955-E E+L

Unable to start transaction service. reason code=aaaa

An error indicated by the reason code occurred while starting or restarting the transaction server process. As a result, the transaction server process cannot be started.

aaaa: Reason code

S: Terminates HiRDB abnormally.

Action

Take an action appropriate to the reason code, as listed below, and restart HiRDB:

Reason code
Explanation
Action

0001
Memory shortage occurred in the process.
Reduce the number of processes and restart HiRDB. If this message is reissued, contact the customer support center.

0002
Read error occurred in the transaction manager management file.
Contact the customer support center.

0100
Shared memory shortage occurred
Contact the customer support center.

0200
Definition analysis startup processing resulted in an error.
If an error message has been output before this message, take action appropriate to that message.

0201
Analysis of the system common definition or unit control information failed.
Check the system common definition or unit control information and restart HiRDB. If the definition is correct, contact the customer support center.

0300
Communication error occurred.
The port number specified in the -t option of the pd_trn_port operand or pdunit operand might be the same as the port number of another definition or program. If they are the same, change the values in the port number settings so that they do not overlap, and then restart HiRDB.
Otherwise, if an error message has been output before this message, take action appropriate to that message.

0600
Registration of service information in the name service function failed.
If an error message has been output before this message, take action appropriate to that message.

1100
Error occurred while starting the statistics log service function.

1800
Activation of transaction recovery process failed

1801
Error occurred while reporting server completion to the system manager.

KFPS00956-E E+L

Error occurred while terminating transaction service; continues processing. reason code = aaaa

An error occurred while terminating the transaction server process.

aaaa: Reason code

S: Resumes processing.

Action

Check the reason code to determine why the transaction server process cannot be terminated normally, then take appropriate action, as listed below:

Reason code | Explanation | Action
0001 | Memory shortage occurred in the process. | Reduce the number of processes and restart HiRDB. If this message is reissued, contact the customer support center.
0300 | Communication error occurred. | If an error message has been output before this message, take action appropriate to that message.
0601 | Deletion of service information by the name service function failed.
1101 | Error occurred while terminating the statistics log service function.
1802 | Termination of transaction recovery process failed.

KFPS00957-E E+L

Unable to change definition at transaction service restart

During restart or during start of a log application site, the value specified for the pd_max_users, pd_max_bes_process, or pd_max_dic_process operand has changed since the previous normal startup.

S: Resumes processing.

Action

Transaction execution site, or if Real Time SAN Replication with the log-only synchronous method is not used
Start the HiRDB system by restoring the system definition that should not be changed. After that, terminate the HiRDB system normally and change the system definition.

Log application site
Make the operand value the same as that of the application site, perform system log optimizations, and then restart.

KFPS00958-I E+L

Unit terminating; stops receiving new transations

No new transactions will be accepted because unit termination has been requested. The transaction server process is starting preparations for termination processing.

KFPS00961-E E+L

Unable to start transaction recovery service. reason code = aaaa

The error indicated by the reason code occurred while starting the transaction recovery process. As a result, the transaction recovery process cannot be started.

aaaa: Reason code

S: Terminates HiRDB abnormally.

Action

Take action appropriate to the reason code, as listed below, and restart HiRDB:

Reason code | Explanation | Action
0200 | Definition analysis startup processing resulted in an error. | If an error message has been output before this message, take action appropriate to that message.
0300 | Communication error occurred
0800 | Registration of the schedule service function of the transaction recovery process failed
1801 | Error occurred while reporting completion of the process activation to the system manager

KFPS00962-E E+L

Error occured while terminating transaction recovery service; continues processing. reason code=aaaa

An error occurred while terminating the transaction recovery process.

aaaa: Reason code

S: Resumes processing.

Action

Check the reason code to determine why the transaction server process cannot be terminated normally, then take appropriate action, as listed below:

Reason code | Explanation | Action
0300 | Communication error occurred. | If an error message has been output before this message, take action appropriate to that message.

KFPS00965-E E+L

Insufficient memory. required memory size=aa....aa bytes, area type=bb....bb

A memory shortage occurred.

aa....aa: Size of the area that was to be allocated

bb....bb: Type of area resulting in memory shortage:

DYNAMIC SHMPOOL: Dynamic shared memory area

PROCESS: Process private area

STATIC SHMPOOL: Static shared memory area

S: Cancels processing.

Action

If the memory shortage occurred in the process private area, re-evaluate the number of processes, take appropriate action, then re-execute.

If the same error recurs, contact the customer support center.

KFPS00969-E L

Error occurred during aa....aa processing, reason code=bbbb, TRNGID=ccccccccdddddddd, TRNBID=cccccccceeeeeeee, server=ff....ff, PID=gg....gg

An error occurred during transaction completion processing.
TRNGID: Global identifier of the transaction
TRNBID: Branch identifier of the transaction

aa....aa: Transaction completion processing

prepare: One-phase commit processing

commit: Two-phase commit processing

rollback: Rollback processing

bbbb: Reason code

cccccccc: HiRDB system identifier and unit identifier

dddddddd: Global transaction number

eeeeeeee: Transaction branch number

ff....ff: Server name

gg....gg: Process ID of the HiRDB server

S: Terminates the process.

Action

Take action based on the reason code.

Transaction completion processing | Reason code | Explanation | Action
commit | 0001 | During transaction commit processing, synchronization with the transaction on another server failed. | For whatever reason, a server other than the one where the message was output (excluding recovery-unnecessary front-end servers) could not continue processing the transaction. Check the status of the network, system, and server.

KFPS00970-E E

Unable to execute aa....aa command of transaction, reason code=bbbb

A transaction command aa....aa cannot be executed.

aa....aa: Command name

bbbb: Reason code

S: Cancels processing.

Action

Take action appropriate to the reason code, as listed below:

Reason code
Explanation
Action

0001
Memory shortage occurred on process
Reduce the number of processes and restart HiRDB. If this error recurs, contact the customer support center.

0003
The number of characters in a flag argument is outside the permitted range.
Check the flag argument, correct the error, then reenter the command.

0004
Character string in a flag argument contains an invalid character.

0005
A decimal character string in a flag argument is outside the permitted range.

0008
There is no information to be displayed.
The transaction cannot be concluded.
(1) The possible causes are given below. If necessary, change the status of the unit or server, and re-execute the command.

The applicable transaction cannot be found.

The transaction server process cannot be used.

The transaction status does not allow the transaction to be concluded.

There is no server running.

Because this is a log application site, the transaction cannot be displayed or resolved.

(2) Because the transaction was executed on a recovery-unnecessary front-end server, the transaction cannot be completed. Refer to the section on methods for finishing incomplete transactions in the manual HiRDB Version 9 System Operations Guide, and make sure the transaction finishes automatically.

0009
Option flag or flag argument is invalid.
Check the option flag or flag argument, correct the error, then reenter the command.

0010
System call error occurred because of a temporary memory shortage.
Wait a while, then reenter the command.

0200
Definition analysis startup processing resulted in an error.
If an error message has been output before this message, take action appropriate to that message.

0300
Communication error occurred.
Reasons are:

The communication error was caused by the error that was reported before this message; take action appropriate to the error message.

The communication error was caused by a temporary memory shortage; reduce the number of processes and reenter the command.

0301
Timeout occurred.

0602
Versions do not match.
Check the version of each library in the HiRDB system, take appropriate action, then reenter the command.

0700
An error occurred during file access.
If an error message was output before this message, take the action indicated in the message.

0701
An error occurred during transaction commit processing.

0702
An error occurred during transaction rollback processing.

0703
An error occurred during transaction forcible termination processing.

0704
An error occurred during transaction status information acquisition.

0705
The unit that contains the system manager is not running.
Start the unit with the system manager, then execute the command.

0706
The command was entered from a server machine that does not contain the system manager.
Execute the command from the server machine that contains the system manager.

0707
An environment information acquisition error occurred.
If an error message was output, follow the action indicated in the message. Eliminate the error, and then restart HiRDB.

KFPS00971-I L+S

Command accepted; (aa....aa)

The aa....aa command has been accepted.

aa....aa: Character string of entered command

S: Resumes processing.

KFPS00972-I L

Error occurred during commit processing; reason code=aaaa, TRNGID=bb....bb PROGRAM=cc....cc

An error occurred during commit processing.

aaaa: Reason code

bb....bb: Global transaction identifier

cc....cc: UAP identification information

S: Resumes processing.

Action

Take action appropriate to the reason code:

Reason code | Explanation | Action
0001 | Transaction was concluded by rollback processing because a timeout occurred while the system was waiting to receive communication from a child branch for the commit request. | Check the status of the network, system, and server. Or, check the maximum response wait time that has been set.

KFPS00973-I L

Transaction branch completed. TRNGID=aaaaaaaabbbbbbbb, TRNBID=aaaaaaaacccccccc, server=dd....dd, service=ee....ee, completion type=ff

Because an error occurred in a transaction branch, a rollback was completed.

TRNGID: Transaction global identifier

TRNBID: Transaction branch identifier

aaaaaaaa: HiRDB system identifier and unit identifier

bbbbbbbb: Global transaction number

cccccccc: Transaction branch number

dd....dd: Server name

ee....ee: HiRDB system internal code

ff: Transaction completion type

r: Rollback

hr: Heuristic rollback

S: Continues processing.

KFPS00974-I E+S

Usage: pdfgt {-A [-x host_name |-u unit_id] [-s server_name] |-t TRNGID [-x host_name |-u unit_id] [-s server_name]

Displays the format of the pdfgt command (to forcibly terminate transaction). This message is displayed in the following cases:

The format of a specified option or argument of the command is invalid.

-h was specified as a command option.

S: Terminates processing.

O: If the command specification is invalid, reenter the command specified correctly.

KFPS00975-I E+S

Usage: pdls -d trn {[-t TRNGID] [-{a |c}] |-bc |-B system_node_ID [-{ a |c }] |-rc |-R RM_name [-{ a |c }] [-s server _name]}

Displays the format of the pdls command that displays transaction status.
This message is displayed in the following cases:

-h was specified as a command option.

The format of a command option or argument is invalid.

S: If the command specification is invalid, cancels command processing.

O: If the command specification is invalid, reenter the command specified correctly.

KFPS00976-I E+S

Usage: pdcmt {-A [-x host_name |-u unit_id] [ -s server_name] |-t TRNGID [-x host_name |-u unit_id] [ -s server _name]}

Displays the format of the pdcmt command that commits a transaction. This message is displayed in the following cases:

The format of a command option or argument is invalid.

-h was specified as a command option.

S: If the command specification is invalid, cancels command processing.

O: If the command specification is invalid, reenter the command specified correctly.

KFPS00977-I E+S

Usage: pdrbk {-A [-x host_name |-u unit_id] [ -s server_name] |-t TRNGID [-x host_name |-u unit_id] [ -s server _name]}

Displays the format of the pdrbk command that rolls back a transaction. This message is displayed in the following cases:

The format of a command option or argument is invalid.

-h was specified as a command option.

S: If the command specification is invalid, cancels command processing.

O: If the command specification is invalid, reenter the command specified correctly.

KFPS00978-E E

Command aa....aa used invalidly

The usage of command aa....aa is invalid.

aa....aa: Command name

S: Cancels command processing.

O: Reenter the command with the correct usage.

KFPS00979-E E

Transaction service inoperable; unable to execute aa....aa command

The transaction server process has not been started, or it is engaged in termination processing. As a result, command aa....aa cannot be executed.

aa....aa: Command name

S: Cancels command processing.

O: Reenter the command after the system has been started.

KFPS00980-W E+L

Unable to monitor elapsed time for transaction branch. TRNGID=aaaaaaaabbbbbbbb, TRNBID=aaaaaaaacccccccc, server=dd....dd, service=ee....ee

Transaction branch elapsed time cannot be monitored.
TRNGID: Transaction's global identifier
TRNBID: Transaction's branch identifier

aaaaaaaa: HiRDB system identifier and unit identifier

bbbbbbbb: Global transaction number

cccccccc: Transaction branch number

dd....dd: Server name

ee....ee: HiRDB's internal code

S: Resumes processing.

Action

If there is no need to monitor the elapsed time, ignore this message. Otherwise, terminate HiRDB, refer to the timer service function message that was displayed before this message to eliminate the cause of the error, then restart HiRDB.

KFPS00981-I E+S

Usage: pdtrndec -i input_file_name[,input_file_name...] [-r rollback_script_file_name] [-o output_directory_name]

This shows the method for using the pdtrndec command (the command to forcibly complete uncompleted transactions). This message is output in the following cases:

If the method of specifying the pdtrndec command options or arguments was incorrect

If the pdtrndec command was specified with the -h option

S: If the command specification method was incorrect, terminates the command processing.

Action

If the command specification method was incorrect, re-execute the command using a correct specification method.

KFPS00982-E E

System call error, func=aa....aa, errno=bb....bb, path name=cc....cc

Error aa....aa occurred in file or directory cc....cc.

aa....aa: Name of the system call where the error occurred

open: File or directory open

close: File or directory close

read: File or directory read

write: File or directory write

fseek: File pointer or directory setting

bb....bb: errno of the system call where the error occurred

cc....cc: Absolute path name of the file or directory where the error occurred

If the path name exceeds 163 bytes, the path name is displayed preceded by an ellipsis (...), and the last 161 bytes are displayed.

S: Terminates processing.

Action

See error.h and the OS manual, and eliminate the cause of the error.

KFPS00983-I L

Current transaction cancel occurred, server = aa....aa, transaction count = bb....bb

The current transaction was forcibly terminated.

aa....aa: Server name

bb....bb: The number of forcibly terminated transactions

S: Continues processing.

Action

If an error message is output before this message, see that message to eliminate the error.

KFPS00985-I E+L

Undetermined transaction information stored in aa....aa

Information about unsettled transactions was collected in aa....aa.

aa....aa: Absolute pathname of a file

S: Resumes processing.

KFPS00986-W E+L

Unable to store undetermined transaction information in aa....aa. reason code=bbbb

Information about unsettled transactions could not be collected in aa....aa.

aa....aa: Absolute pathname of a file

bbbb: Reason code

S: Resumes processing.

Action

Take action appropriate to the reason code, as listed below:

Reason code | Explanation | Action
0001 | Memory shortage occurred in the process. | Reduce the number of processes and restart HiRDB. If this message is reissued, contact the customer support center.
0052 | File manipulation failed. | Refer to the reason code in the message that was output before this message to check the cause of the error, and take appropriate action.
0056 | Environment variable is invalid. | Set the correct value in the environment variable and re-execute.

KFPS00988-I L

Transaction information. TRNGID=aaaaaaaabbbbbbbb, TRNBID=aaaaaaaacccccccc, PID=dd....dd, C-PID=ee....ee(ff....ff), TIME=gghhii, PROGRAM=jj....jj, TMID=kkkk, XID=llllllllllllllll,mmmmmmmmmmmmmmmm,ENVGRP=nnnn

This message, which displays additional information about a transaction error, is output in the following cases:

When a transaction-related error has occurred.

When a transaction is still being processed while planned termination is underway.

TRNGID: Transaction's global identifier

TRNBID: Transaction's branch identifier

aaaaaaaa: HiRDB system identifier and unit identifier

bbbbbbbb: Global transaction number

cccccccc: Transaction branch number

dd....dd: Process ID of the server processing the transaction as part of UAP or utility processing

ee....ee: Process ID of the client (a UAP or a utility) that was connected to a server process. However, 0 is displayed in the following cases:

A server process that is not connected to the client

A server process that is connected to a client linked to a client library version prior to 04-00

A server process that is connected to a Type 4 JDBC Driver

ff....ff: IP address of the client (a UAP or a utility) that was connected to a server process. However, if no server process is connected to the client, 0.0.0.0 is displayed.

gghhii: Time (hour, minute, second) the service request was accepted.

If you are collecting statistics about the UAP from the statistics analysis utility on a per-transaction basis:
The transaction's execution start time is displayed.

If you are collecting statistics about the UAP from the statistics analysis utility on a per-connection basis, or you are not collecting statistics about the UAP from the statistics analysis utility:
The connection start time is displayed.

The PDSTJTRNOUT operand in the client environment definition specifies whether statistics about the UAP are collected on a per-transaction or per-connection basis.

In the case of a server process that is not connected to the client, 999999 is displayed for the time the service request was accepted.

jj....jj: UAP identification information (UAP name specified in PDCLTAPNAME in the client environment definition):

PDCLTAPNAME not set:
Unknown is displayed.

Utility:
The name of the utility is displayed.

However, if the utility was running on a utility server process or if there was an error, such that the UAP identifier information could be not obtained, spaces may be displayed.

kkkk: OLTP identifier of the connected OLTP (HiRDB_PDTMID or PDTMID in the client environment definition)

This information is output if the client (UAP) connected to the HiRDB server process is an XDS client or an application complying with X/Open. If no OLTP identifier has been specified, **** is displayed.

When an XDS client is used, HRDB is displayed.

llllllllllllllll,mmmmmmmmmmmmmmmm:

One of the following is output:

The transaction identifier assigned by OLTP
This information is output when the client (UAP) connected to the HiRDB server process is an application complying with X/Open and the OLTP is OpenTP1 or TPBroker for C++.

The transaction identifier assigned by XDS
This information is output when the client (UAP) connected to the HiRDB server process is an XDS client.

nnnn: Environment variable group identifier assigned by OLTP

This is output when the client (UAP) connected to the HiRDB server process is an X/Open-compliant application and it uses the multi-connection facility; if the multi-connection facility is not used, **** is displayed.

S: Resumes processing.

O: Follow the HiRDB administrator's instructions.

Action

Transaction-related error occurred:

This message is used to investigate the cause of the error indicated by one of the following error messages, which was output before this message:

KFPS00972-I

KFPS00973-I

KFPS00990-I

KFPS00991-I

KFPS00992-E

KFPS00993-I

KFPS00935-I

KFPS00936-E

Transaction still executing while planned termination is underway:

This message is used to check for transactions that have not been completed.

KFPS00990-I E+L

Transaction branch recovery complete. TRNGID=aaaaaaaabbbbbbbb, TRNBID=aaaaaaaacccccccc, server=dd....dd, service=ee....ee, completion type=f,gg

Recovery of a transaction branch has been completed.

TRNGID: Transaction's global identifier

TRNBID: Transaction's branch identifier

aaaaaaaa: HiRDB system identifier and unit identifier

bbbbbbbb: Global transaction number

cccccccc: Transaction branch number

dd....dd: Server name

ee....ee: HiRDB's internal code

f: Completion type of the corresponding transaction branch:

c: Commit

r: Rollback

gg: Completion type of the corresponding global transaction:

c: Commit

hc: Heuristic commit

hh: Heuristic hazard

hm: Heuristic mix

hr: Heuristic rollback

r: Rollback

S: Resumes processing.

KFPS00991-I E+L

Unable to recover from transaction branch. TRNGID=aaaaaaaabbbbbbbb, TRNBID=aaaaaaaacccccccc, server=dd....dd, service=ee....ee, determination type=ff

Transaction branch recovery will be re-executed because recovery could not be completed.

TRNGID: Transaction's global identifier

TRNBID: Transaction's branch identifier

aaaaaaaa: HiRDB system identifier and unit identifier

bbbbbbbb: Global transaction number

cccccccc: Transaction branch number

dd....dd: Server name

ee....ee: HiRDB internal code

ff: Settlement type:

c: Commit

hc: Heuristic commit

hh: Heuristic hazard

hm: Heuristic mix

hr: Heuristic rollback

r: Rollback

S: Resumes processing.

Action

If an error message has been output before this message, correct the error.

KFPS00992-E E+L

Unable to determine commit or rollback for transaction branch. TRNGID=aaaaaaaabbbbbbbb, TRNID=aaaaaaaacccccccc, server=dd....dd, service=ee....ee

A transaction branch cannot be committed or rolled back by the system due to a communication error, etc.

TRNGID: Transaction's global identifier

TRNBID: Transaction's branch identifier

aaaaaaaa: HiRDB system identifier and unit identifier

bbbbbbbb: Global transaction number

cccccccc: Transaction branch number

dd....dd: Server name

ee....ee: HiRDB internal code

S: Retains the transaction branch status and resumes processing.

Action

Prepare for transaction commit with the pdcmt or pdrbk command if you cannot recover from the error. Another possibility is that the OLTP system might not have started. Check whether the OLTP system has started and, if not, start it.

If the pdcmt or pdrbk command is used to commit the transaction, use the same commit type as the other transaction branches with the same TRNGID.

For other transaction branches, use the same commit type as the transaction branch with the same TRNGID displayed in the KFPS00990-I message that is output after recovery processing has been completed. If there is no KFPS00990-I message containing the same TRNGID and no other transaction branch is found by pdls -d trn, use the pdrbk command to conclude the transaction.

KFPS00993-I L

Accepted process abnormal end request. PID=aa....aa, TRNGID=bb....bb, TRNBID=cc....cc, REQUEST=dd....dd

A request for forced termination of the server process was received for one of the following reasons:

A related server process stopped.

A related unit terminated abnormally.

A cause that must abort the transaction occurred.

aa....aa: Process ID subject to forced termination

bb....bb: Transaction identifier (transaction's global identifier)

cc....cc: Transaction identifier (transaction's branch identifier)

dd....dd: Request type:

abnormal_unit_branch:

Request for forced termination of the abnormal unit-related branch

clt_attention:

Request for forced termination accompanied by an interrupt at the client (this applies as well if Ctrl+C is pressed at the keyboard during execution of the client UAP)

force_end:

Request for forced termination based on a recovery instruction from OLTP or XDS (In the case of OLTP, this only applies to OpenTP1; for example, if OpenTP1 is abnormally terminated, and then restarted. In the case of XDS, this applies to internal rollback of the transaction and similar situations)

pdcancel_end:

Request for forced termination by pdcancel

PDCWAITTIME_over:

Request for forced termination due to the end of client's PDCWAITTIME

subordinate_branch:

Request for forced termination of a subbranch (for example, this applies if the subbranches related to a transaction are forcibly terminated due to another error)

superior_branch:

Request for forced termination of a master branch (for example, this applies if the master branch of a transaction is forcibly terminated due to an abnormality in one of the subbranches)

abnormal_tran_end:

Forced termination request from the skip count monitoring facility for enabling a synchronization point dump

log_remain_check

Request for forced termination from the facility for monitoring free area for the system log file

abnormal_svr_branch:

Request to forcibly terminate a branch related to an abnormal server

S: Terminates abnormally by terminating the indicated server process.

P: Contact the HiRDB administrator. After taking action, re-execute the process.

Action

Take a corrective action according to the message output by the related server process, the related unit, or the transaction.

If the request type is abnormal_tran_end:
If, in the KFPS00988-I message that is output following this message, the UAP identification information is hdssqle[aa....aa]bb (aa....aa: reflection-group-name, bb: extraction-source-HiRDB Datareplicator-identifier), see the description of the skipped effective synchronization point dump monitoring facility in the HiRDB Version 9 System Operation Guide.

KFPS01001-I L+S

aa....aa assigned as current logical status file. server kind:bb server:cc....cc

The status file aa....aa was allocated as the current file.

aa....aa: Name of the current status file

bb: Server type:

00: Unit

01: Server

cc....cc: Name of the server used to allocate the file (if the server type is 00, the unit name is displayed; if it is 01, the server name is displayed)

S: Resumes processing.

Action

If HiRDB is started when there is a status file in which an error occurred, the information displayed in the message is required for the specification of the following operands:

The unit control information definition pd_syssts_last_active_file operand (if this message is output by a log application site, the pd_syssts_last_active_subfile operand)

The server definition pd_sts_last_active_file operand (if this message is output by a log application site, the pd_sts_last_active_subfile operand)

KFPS01005-E E+L

Unable to status service due to aa....aa.

The status server process cannot be started.

aa....aa: Reason code indicating the nature of the error

S: Terminates HiRDB abnormally.

Action

Take action appropriate to the reason code, as listed below, and restart HiRDB:

Reason code
Explanation
Action

0000000001​
Error in the definition environment of the status server process
Take action as indicated in the message output before this message. Eliminate the cause of the error, and then restart HiRDB.

0000000003​
Error in the definition of the status server process
Revise the unit control information definition or server definition, and then restart HiRDB.

0000000004​
All status files specified in the unit control information definition or server definition are in hold status.
Take action as indicated in the message output before this message. Eliminate the cause of the error, and then restart HiRDB.

0000000005​
0000000006​
Memory shortage
Take action as indicated in the message output before this message.
Determine the cause of and take measures against memory shortage.
Revise the operating system parameters (maximum number of processes, maximum memory allocation per process, etc.), and then restart HiRDB.

0000000007​
0000000008​
Status file error
Take action as indicated in the message output before this message. Eliminate the cause of the error, and then restart HiRDB.

0000000009​
Swapping error

0000000010​
An error occurred in the status file. Because stop was specified in the pd_syssts_initial_error operand or the pd_sts_initial_error operand, HiRDB start processing was terminated.
Take action as indicated in the message output before this message. Eliminate the cause of the error and restart HiRDB.
If HiRDB terminates with this error code again after restarting, consider that during HiRDB startup there may be a status file in which an error occurred. For the procedure on starting HiRDB with a status file in which an error occurred, see the HiRDB Version 9 System Operation Guide.

0000000011​
0000000012​
0000000013​
0000000014​
Internal processing error
If an error message was output before this message, take action as indicated in that message. If no error message was output before this message, contact the customer support center.

0000000015​
The current file name indicated by HiRDB does not match the file name indicated in the pd_syssts_last_active_file operand or the pd_sts_last_active_file operand (if this message was output by a log application site, the pd_syssts_last_active_subfile or the pd_sts_last_active_subfile operand).
See the section on the procedure for starting HiRDB with a status file for which an error occurred in the HiRDB Version 9 System Operation Guide.
Determine whether the file name of the previous operation is specified in the pd_syssts_last_active_file operand or the pd_sts_last_active_file operand (if this message was output by a log application site, the pd_syssts_last_active_subfile or the pd_sts_last_active_subfile operand). If the file name of the previous operation is not specified, specify the file name of the previous operation in the pd_syssts_last_active_file operand or the pd_sts_last_active_file operand (if this message was output by a log application site, the pd_syssts_last_active_subfile or the pd_sts_last_active_subfile operand), and start HiRDB. If this reason code is output even though the current file name used during the previous session was specified, an error occurred in the current file name used during the previous session. Follow the procedure when HiRDB (unit) cannot be restarted because an error occurred in the current file on both systems in the HiRDB Version 9 System Operation Guide, and then start HiRDB.

0000000016​
If the pd_syssts_last_active_file operand or the pd_sts_last_active_file operand (if this message was output by a log application site, the pd_syssts_last_active_subfile or the pd_sts_last_active_subfile operand) was not specified, the file name of the previous operation could not be indicated, and HiRDB startup processing was interrupted. If the pd_syssts_last_active_file operand or the pd_sts_last_active_file operand (if this message was output by a log application site, the pd_syssts_last_active_subfile or the pd_sts_last_active_subfile operand) was specified, there is no spare file, and HiRDB startup processing was interrupted.
If the pd_syssts_last_active_file operand or the pd_sts_last_active_file operand (if this message was output by a log application site, the pd_syssts_last_active_subfile or the pd_sts_last_active_subfile operand) was not specified, see the section on the procedure for starting HiRDB when an error occurred in the status file in the manual HiRDB Version 9 System Operation Guide. Specify the file name of the previous operation in the pd_syssts_last_active_file operand or the pd_sts_last_active_file operand (if this message was output by a log application site, the pd_syssts_last_active_subfile or the pd_sts_last_active_subfile operand), and start HiRDB.
If the pd_syssts_last_active_file operand or the pd_sts_last_active_file operand (if this message was output by a log application site, the pd_syssts_last_active_subfile or the pd_sts_last_active_subfile operand) was specified, prepare a spare file, and then start HiRDB.

0000000017​
The normal system of the current file indicated by HiRDB does not match the system specified in the pd_syssts_last_active_side operand or the pd_sts_last_active_side operand (if this message was output by a log application site, the pd_syssts_last_active_side_sub or the pd_sts_last_active_side_sub operand).
See the section on the procedure for starting HiRDB when an error occurred in the status file in the HiRDB Version 9 System Operation Guide.
Confirm that the normal system of the file indicated in the previous operation was specified in the pd_syssts_last_active_side operand or the pd_sts_last_active_side operand (if this message was output by a log application site, the pd_syssts_last_active_side_sub or the pd_sts_last_active_side_sub operand). If the normal system was not specified, specify the normal system in the pd_syssts_last_active_side operand or the pd_sts_last_active_side operand (if this message was output by a log application site, the pd_syssts_last_active_side_sub or the pd_sts_last_active_side_sub operand), and then start HiRDB. If this reason code was output even though the normal system was specified, an error occurred in the file name specified in the previous operation. Follow the procedure when HiRDB (unit) cannot be restarted because an error occurred in the current file on both systems in the HiRDB Version 9 System Operation Guide, and start HiRDB.

0000000018​
Because the normal system of the current file of the previous operation cannot be determined, HiRDB start processing was terminated.
See the section on the procedure for starting HiRDB when an error occurred in the status file in the manual HiRDB Version 9 System Operation Guide. Specify the normal system of the current file in the pd_syssts_last_active_side operand or the pd_sts_last_active_side operand (if this message was output by a log application site, the pd_syssts_last_active_side_sub or the pd_sts_last_active_side_sub operand), and then start HiRDB.

0000000102​
There is no inheritance information from the application site.
Consider the following causes:
(1) During preparation for log application, the secondary status file was not created as per the procedure
(2) The current secondary status file was deleted
If (1), determine whether there is an error in the preparation for log application procedure, and then re-execute the preparation for log application.
If (2), preparation for log application is required to start the log application site HiRDB. Perform preparation for log application, and then restart HiRDB.
For details about preparation for log application, see the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide.

KFPS01006-E E+L

aa....aa statement in status service definition is invalid. reason code=bb....bb

There is a specification error in the unit control information definition or the server definition aa....aa operand. An error occurred during analysis of the unit control information definition or the server definition.

aa....aa: Name of the operand specified in the unit control information definition or the server definition

bb....bb: Reason code indicating the nature of the error (table below lists the reason codes and actions to be taken)

S: Continues processing.

O: Correct the unit control information definition or the server definition.

Action

Determine the cause from the following reason codes, and correct the unit control information definition or server definition.

Reason code | Explanation | Action
0000000001​ | Duplicated information was specified in the definition. | Revise the unit control information definition or the server definition, and then restart HiRDB.
0000000002​ | A definition statement is missing or is invalid.
0000000003​ | Invalid value was specified in the definition.
0000000004​ | The number of characters specified in the definition is invalid.
0000000005​ | The file name specified in the definition was not found.
0000000006​ | Combination of definition statements is invalid.
0000000101​ | The logical file name of the secondary status file does not match the logical file name of the corresponding primary status file.
0000000102​ | There is no definition for the secondary status file that corresponds to the primary status file.
0000000103​ | There is no definition for the primary status file that corresponds to the secondary status file.

KFPS01008-I E+L

aa....aa file unable to be used as standby status file due to bb....bb

Indicated file cannot be used as a reserve status file.

aa....aa: Path name of the status file or name of the status file

If the path name of the status file exceeds 152 characters, the last 152 characters of the status file path name are output.

bb....bb: Reason code indicating the nature of the error

S: Terminates processing.

Action

Take action appropriate to the reason code, as listed below:

Reason code | Explanation | Action
0000000001​ | Record length does not match that of the current file. | Use the same record length as the current file.
0000000002​ | The numbers of records in file versions A and B do not match. | Match the numbers of records in file versions A and B.
0000000003​ | Record lengths of file versions A and B do not match. | Match the record lengths of file versions A and B.

KFPS01009-E E+L

File consistency error occurred in physical status file aa....aa

A file inconsistency error occurred in a status file.

aa....aa: Path name of the status file

If the path name of the status file exceeds 161 characters, the last 161 characters of the status file path name are output.

S:

Reserve status file available:
Swaps the files.

Reserve status file not available:
Cancels startup processing and places the erroneous file on shutdown status.

O: Check the previous session for any online shutdown or file system error and the status file for any allocation error. Correct the status file error and either provide a status file or restart HiRDB.

KFPS01010-E E+L

Error occurred in last updated status file aa....aa. reason code=bb....bb

An error occurred in the status file containing the most recent file.

aa....aa: Path name of the status file

If the path name of the status file exceeds 144 characters, the last 144 characters of the status file path name are output.

bb....bb: Reason code indicating the nature of the error (the table below lists the reason codes and actions to be taken)

S:

0000000006 set as the reason code:
Recovers the file error and resumes processing.

Other than 0000000006 set as the reason code:
If a reserve status file is available, swaps the files; otherwise, cancels startup processing and places the erroneous file on shutdown status.

Error occurred in both file versions A and B:
Cancels startup processing.

Action

Take action appropriate to the reason code, as listed below:

Reason code | Explanation | Action
0000000001​ | The numbers of records or record lengths of file versions A and B do not match. | Use the same number of records or the same record length as the normal file version and initialize the file with the pdstsinit command.
0000000002​ | The numbers of records or record lengths of file versions A and B do not match, and a data error was detected. | Match the numbers of records or record lengths of file versions A and B and initialize them with the pdstsinit command.
0000000003​ | Record update numbers do not match in file versions A and B. | Initialize file version B with the pdstsinit command.
0000000004​ | Record update error was detected in both file versions A and B. | Initialize both file versions A and B with the pdstsinit command.
0000000005​ | Record input error was detected. | Take action appropriate to the KFPS01040-E message that was output before.
0000000006​ | Incomplete file update status was detected. | No action is necessary. However, if both file versions A and B resulted in an error, initialize the erroneous files with the pdstsinit command.

KFPS01011-I L+S

HiRDB system selected aa....aa as last updated status file

Of the open files, status file aa....aa holds the most recent information. If continue or excontinue was specified in the pd_syssts_initial_error operand or the pd_sts_initial_error operand, and the current file of the previous session could not be determined, the name of the file from among the open status files that holds the most recent information is shown in aa....aa.
The name of the file output in aa....aa is not restricted to the current file of the previous session. For details on conditions where the current file of the previous session cannot be determined, see the explanation of the pd_syssts_initial_error operand or the pd_sts_initial_error operand in the manual HiRDB Version 9 System Definition.

aa....aa: Name of the status file

S: Resumes processing.

KFPS01012-I L+S

Error occurred in last updated status file b on aa....aa system

An error occurred in the one-way system of the status file aa....aa that holds the most recent information.

aa....aa: Name of the current status file

b: System where the error occurred {A | B}

S: Continues processing.

KFPS01040-E E+L

aa....aa error occurred in physical status file bb....bb. reason code=cc....cc

Error aa....aa occurred in status file bb....bb. HiRDB processing after this message is output differs depending on HiRDB startup or command execution.

While HiRDB is running
If it is before the current file was allocated (before the KFPS01001-I message was output): Error shutdown is performed on the file where the error occurred.
If it is after the current file was allocated (after the KFPS01001-I message was output): Error shutdown is performed on the file where the error occurred, after which, if the status file where the error occurred is the current file, the file is swapped.

During command execution
Continues processing.

aa....aa: Nature of the error:

close: File Close

create: File creation

delete: File deletion

filecheck: File validity checking

fstat: File status report

logical: Inconsistent record

open: File Open

read: Record input

write: Record output

bb....bb: Path name of the status file

If the path name of the status file exceeds 144 characters, the last 144 characters of the path name are output.

cc....cc: Reason code indicating the nature of the error

S: If a reserve status file is available, swaps files; otherwise, places the erroneous file on shutdown status and resumes processing.

Action

Determine the cause from the following reason codes, and take the appropriate action.

Reason code
Explanation
Action

0000000001​
Invalid status file record occurred.
Initialize the applicable status file with the pdstsinit command.

0000000002​
Contact the customer support center.

0000000003​
Status file update incomplete.
Initialize the applicable status file with the pdstsinit command.

0000000004​
HiRDB file system error occurred.
Contact the customer support center.

0000000005​
Invalid status file management area occurred.
Initialize the applicable status file with the pdstsinit command.

0000000006​
The applicable file is not defined as a status file.
Check that the path name of status file bb....bb is correct.
Correct the unit control information definition or the server definition.

0000000007​
Erroneous file has not been initialized.
Delete the applicable status file with the pdstsrm command, and initialize it with the pdstsinit command.

0000000008​
Invalid status file initialization occurred.
Initialize the applicable status file with the pdstsinit command.

0000000009​
Invalid status file management area occurred.

0000000010​

0000000011​

0000000020​
No access privilege for a character special file
Revise the access privilege to the HiRDB file system area that stores the status file.

0000000021​
No access privilege for a file.
Revise the status file access privilege.

0000000022​
Lock error (in use by another process) occurred.
The pdstsrm, pdstsinit, or pdcat -d sts -e command may have been executed for the open status file. Execute the pdls -d sts command, and check that the specified file is open. If it is open, take the following actions:

For the pdstsrm or the pdstsinit command, close the status file using the pdstscls command and then re-execute the command.

For the pdcat -d sts -e command, use the pdstscls command to close the status file. Or, omit the -e option and re-execute the command.

0000000023​
System resource (file lock) shortage occurred.
If an error message was output immediately before this, take the action indicated in the message. Revise the operating system parameters (number of files that can be open simultaneously, etc.).

0000000024​
No write privilege for file
Revise the access privilege to the status file. If Real Time SAN Replication is used, it is possible that the pair volume that stores the status file is an S-VOL. See the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide, and determine whether there is an error in the HiRDB startup procedure.

0000000025​
System resource (file descriptor) shortage occurred.
If an error message was output immediately before this, take the action indicated in the message. Revise the operating system parameters (number of files that can be open simultaneously, etc.).

0000000026​
Not initialized as a HiRDB file system area.
Check that the path name of status file bb....bb is correct.
Use the pdfmkfs command to initialize as a HiRDB file system area.

0000000027​
I/O error occurred.
Check if a disk error or operating system error occurred, and take appropriate action. Check that the disk where the status file was allocated is enabled. If the disk is not enabled, enable it. If an attempt was made to start individual units in a multiple-unit HiRDB/Parallel Server configuration that uses Real Time SAN Replication with the log-only synchronous method, it is possible that the combination of the use of the pdstart command -l option, the site status, and the disk settings is inappropriate. Use a correct combination of the pdstart command -l option, site status, and disk settings. For details about appropriate combinations, see the section on pdstart command notes in the manual HiRDB Version 9 Command Reference.

0000000028​
Memory shortage occurred.
Revise the operating system parameters (maximum number of processes, maximum memory allocated per process, etc.).

0000000029​
File not found
Check that the path name of status file bb....bb is correct. Or, revise the unit control information definition or server definition.

0000000030​
In UNIX, the number of character special files that can be opened has been exceeded. In Windows, the number of files that can be opened has been exceeded.
If an error message was output immediately before this, take the action indicated in the message. Revise the operating system parameters (number of files that can be open simultaneously, etc.).

0000000031​
Invalid file name.
Consider the following causes:

An illegal character was used in the path name.

The path name length exceeded the limit (167 characters).

The HiRDB file name length exceeded the limit (30 characters).

Check the status file name specified in the command argument, or re-evaluate the unit control information definition or the server definition.

0000000032​
Internal processing error occurred.
Contact the customer support center.

0000000033​

0000000034​

0000000035​

0000000036​

0000000037​
Specified path is not a HiRDB file system area.
If an error message was output immediately before this, take the action indicated in the message.
Check that the path name of status file bb....bb is correct.
Initialize the applicable status file using the pdfmkfs command.

0000000038​
There is a shortage of area in the HiRDB file system area.
Increase the area of the HiRDB file system area, and re-initialize using the pdfmkfs command.
Allocate the status file to another HiRDB file system area.

0000000039​
The system version of the HiRDB file does not match.
If an error message was output immediately before this, take the action indicated in the message.
The HiRDB file system area that contains bb....bb cannot be used. Either specify another HiRDB file system area or use the pdfmkfs command to re-initialize the HiRDB file system area.

0000000040​
Internal processing error occurred.
Contact the customer support center.

0000000041​

0000000042​

0000000043​
Attempt was made to create a status file in a HiRDB file system area that is not for system files.
Check the HiRDB file system area name, use the pdfstatfs command to check the purpose of use of the HiRDB file system area, and create a status file in a HiRDB file system area for use with system files.

0000000051​
The possible causes are:

Attempt was made to open a status file created in a HiRDB file system area that exceeds 2 GB, but N is specified in the pd_large_file_use operand.

Attempt was made to open a status file created in a HiRDB file system area created by the pdfmkfs -a command, but N is specified in the pd_large_file_use operand.

Take the following actions:

Specify Y in the pd_large_file_use operand, or omit the specification.

Delete status file bb....bb with the pdstsrm command, and then initialize the settings with the pdstsinit command.

KFPS01041-I E+L

Physical status file with error is closed and status service is placed in shutdown state. remove the closed file with pdstrsrm command and switch over to standby status file with pdstsinit command and pdstsopen command

The status server process will be placed in shutdown status after closing the erroneous status file. Delete the erroneous file with the pdstsrm command, and provide a reserve status file with the pdstsinit and pdstsopen commands.

S: Resumes processing.

O: Delete the erroneous file with the pdstsrm command. Initialize a file with the pdstsinit command and switch to a reserve status file with the pdstsopen command.

KFPS01042-E E+L

Logical status file aa....aa is short of capacity

An area shortage error occurred in the status file.

aa....aa: Name of the status file

S: If a reserve status file is available, swaps files; otherwise, cancels swapping.

Action

Check the size of the status file.

KFPS01043-I E+L

Fragmentation occurred in logical status file aa....aa

Fragmentation occurred in the status file.

aa....aa: Name of the status file

S: If a reserve status file is available, swaps files; otherwise, cancels swapping.

KFPS01044-I L+S

Current logical status file aa....aa is placed in the one-system operation state. The normal system is b. Take appropriate action immediately.

Current status file aa....aa was placed in single operation mode. The normal system is displayed. Take appropriate action immediately.

aa....aa: Name of current status file

b: Normal file version { A | B }

S: Continues processing.

Action

Take either of the following actions:

Prepare a reserve file, and use the pdstsswap command to swap the status file.

Determine the cause of the error and take action, use the pdstsinit command to initialize the system where the error occurred to the current file, and then open using the pdstsopen command.

If you are starting HiRDB when using the status file in single-operation mode, the information displayed in this message must be specified in the following operands:

pd_syssts_last_active_file (if a log application site, pd_syssts_last_active_subfile)

pd_syssts_last_active_side (if a log application site, pd_syssts_last_active_side_sub)

pd_sts_last_active_file (if a log application site, pd_sts_last_active_subfile)

pd_sts_last_active_side (if a log application site, pd_sts_last_active_side_sub)

KFPS01050-E E

Inter-process communication error occurred

An inter-process communication error occurred.
An inter-process communication error occurred while processing a service request to the status server process. Another possibility is that an RPC error occurred while the status server process was active.

S: Cancels processing.

O: Check the HiRDB operating environment, eliminate the cause of the error, and then reissue the service request to the status server process.

KFPS01051-I E+L

Physical status file with error is closed and status service is placed in shutdown state

The status server process will be placed in shutdown status after closing the erroneous physical status file.

S: Initialize the erroneous file with the pdstsinit command, and switch to a reserve status file with the pdstsopen command.

KFPS01060-I L+S

Status file aa....aa open

Status file aa....aa has been opened (the system has completed opening of the status file).

aa....aa: Path name of the status file or name of the status file

S: Resumes processing.

KFPS01061-I L+S

Status file aa....aa closed

Status file aa....aa has been closed (the system has completed closing of the status file).

aa....aa: Path name of the status file or name of the status file

S: Resumes processing.

KFPS01062-I L+S

Status file swapping started. reason=aaaaaaaa

Status file swapping has started.

aaaaaaaa: Reason for swapping:

COMMAND: Swap command (pdstsswap) was entered

ONLINE: Access error occurred in the current file in the online mode

START: Error occurred in the current file while starting or restarting the status server process (access error, logical error between file versions A and B)

S: Resumes processing.

KFPS01063-I L+S

Status file swapping completed. current logical status file: aa....aa

Status file swapping has been completed.

aa....aa: Name of the current status file

S: Resumes processing.

Action

If you are starting HiRDB when an error occurred in the status file, the information displayed in this message must be specified in the following operands:

pd_syssts_last_active_file (if a log application site, pd_syssts_last_active_subfile)

pd_sts_last_active_file (if a log application site, pd_sts_last_active_subfile)

KFPS01064-E E+L

Error occurred during status file swapping. reason code=aa....aa

Status file swapping resulted in an error.

aa....aa: Reason code (the table below lists the reason codes and actions to be taken)

S: Cancels swapping.

O: Take action appropriate to the reason code, as listed below:

Reason code
Explanation
Action

0000000001​
No available reserve status file
Prepare a reserve status file.

0000000002​
0000000003​
Allocation of the process private area failed.
Take the action indicated in the error message that was output immediately before this.

0000000004​
No reserve status file exists for the swap target. A status file other than the current file is in hold or reserve status. Or, there is an area shortage.
Prepare a reserve status file. If this reason code is output even when there is a reserve status file, there is an area shortage in the reserve status file. Revise the estimate of the status file area to prepare a larger reserve status file. Once the larger status file has been made the current status file, increase the size of the remaining status files.

0000000005​
Error occurred in the current status file.
If an error message was output immediately before this message, take the action indicated in the message. If no message was output, contact the customer support center.

0000000006​
Internal processing error occurred.
Contact the customer support center.

0000000007​
If an error message was output immediately before this message, take the action indicated in the message. If no message was output, contact the customer support center.

0000000008​
0000000009​
Contact the customer support center.

KFPS01070-E E+L

Error occurred during aa....aa command processing. reason code=bb....bb

An error occurred while processing command aa....aa (error occurred while processing a status service function command).

aa....aa: Command name

bb....bb: Reason code (the table below lists the reason codes and actions to be taken)

S: Terminates command processing.

O: Check the error message output before, correct the error, the reenter the command.

Reason code
Explanation
Action

0000000001​
Invalid information in status file management record (STR)
If an error message has been output before this message, take action appropriate to that message. Or, check the arguments specified in the command. If the cause of the error cannot be identified, retain the file and contact the HiRDB administrator.

0000000002​
Invalid information in status file management record (SHR)

0000000003​
Record length differs from that of the current file, or the sizes of file versions A and B are different
Check the record length or the number of records in the status file with the pdls command specifying the -d sts option. Or, initialize the file with the pdstsinit command.

0000000004​
File status does not allow command entry
Check the file status with the pdls command specifying the -d sts option. Correct the file status and re-execute the command.

0000000005​
Basic file system error
If an error message has been output before this message or a message has been output from the status server process, take action appropriate to that message.

0000000006​
Specified file name is undefined in the unit control information definition or server definition
Check the arguments specified in the command.

0000000007​
Inter-process communication error
If an error message has been output before this message, take action appropriate to that message. Correct the error and re-execute the command.

0000000008​
No reserve status file exists.
Provide a reserve status file.

0000000009​
Swapping error
Provide a status file and restart HiRDB.

0000000010​
System call error
Correct the error and re-execute the command.

0000000011​
Status file is being used (OPEN) by another status server process or is being processed by another status service function command.
Check the system definition and server definition for a duplicate physical file name.
Alternatively, close the status file that is being used by the other status server process, or wait until the status service function or command has terminated.

0000000012​
System definition analysis error
Re-evaluate the system definition.

0000000013​
Inter-process communication initialization error
Correct the error and re-execute the command.

0000000014​
No commands are being accepted
Re-execute the command while HiRDB is active.

0000000015​
Invalid data length in RPC text
Contact the customer support center.

0000000016​
Current file was specified
Check the file status and the arguments specified in the command with the pdls command specifying the -d sts option. Or, swap status files and re-execute the command.

0000000017​
Status of a specified file has already been changed
Check the file status with the pdls command specifying the -d sts option.

0000000018​
Error was detected during file checking
Initialize the erroneous file with the pdstsinit command.

KFPS01081-I E+S

Usage: pdstsinit [-x host_name |-u unit_id] -f full_path_name[-l record_length] [-c record_number] pdstsinit -s server_name -f full_path_name [-l record_length] [-c record_number]

Displays the format of the pdstsinit command for a HiRDB/Single Server. This message is output when the command format is invalid.

Usage

pdstsinit -f file-name[-l record-length] [-c record-count]

S: Terminates processing.

O: Reenter correctly the specified command.

KFPS01081-I E+S

Usage: pdstsinit {-x host_name | -u unit_id} -f full_path_name [-l record_length] [-c record_number] [-D]
pdstsinit -s server_name [-x host_name | -u unit_id] -f full_path_name [-l record_length] [-c record_number] [-D]

Displays the format of the pdstsinit command for a HiRDB/Parallel Server. This message is output when the command format is invalid.

Usage

pdstsinit -f file-name [-l record-length] [-c record-count] [-D]

S: Terminates processing.

O: Reenter correctly the specified command.

KFPS01082-I E+S

Usage: pdstrsrm [-x host_name |-u unit_id] -f full_path_name
pdstrsrm -s server_name [-x host_name|-u unit_id] -f full_path_name

Displays the format of the pdstsrm command for a HiRDB/Single Server. This message is output when the command format is invalid.

Usage

pdstsrm -f file-name

S: Terminates processing.

O: Reenter correctly the specified command.

KFPS01082-I E+S

Usage: pdstsrm {-x host_name | -u unit_id} -f full_path_name [-D]
pdstsrm -s server_name -f full_path_name [-D]

Displays the format of the pdstsrm command for a HiRDB/Parallel Server. This message is output when the command format is invalid.

Usage

pdstsrm -f file-name [-D]

S: Terminates processing.

O: Reenter correctly the specified command.

KFPS01083-I E+S

Usage: pdstsopen [-x host_name |-u unit_id] {-f full_path_name |-n logical_file_name}
pdstsopen -s server_name {-f full_path_name |-n logical_file_name}

Displays the format of the pdstsopen command for a HiRDB/Single Server. This message is output when the command format is invalid.

Usage

pdstsopen { -f file-name |-n logical-file-name }

S: Terminates processing.

O: Reenter correctly the specified command.

KFPS01083-I E+S

Usage: pdstsopen {-x host_name |-u unit_id} {-f full_path_name |-n logical_file_name}
pdstsopen -s server_name {-f full_path_name| -n logical_file_name}

Displays the format of the pdstsopen command for a HiRDB/Parallel Server. This message is output when the command format is invalid.

Usage

pdstsopen { -f file-name |-n logical-file-name }

S: Terminates processing.

O: Reenter correctly the specified command.

KFPS01084-I E+S

Usage: pdstscls [-x host_name |-u unit_id] {-f full_path_name |-n logical_file_name}
pdstscls -s server_name {-f full_path_name |-n logical_file_name}

Displays the format of the pdstscls command for a HiRDB/Single Server. This message is output when the command format is invalid.

Usage

pdstscls { -f file-name |-n logical-file-name }

S: Terminates processing.

O: Reenter correctly the specified command.

KFPS01084-I E+S

Usage: pdstscls {-x host_name |-u unit_id} {-f full_path_name |-n logical_file_name}
pdstscls -s server_name {-f full_path_name |-n logical_file_name}

Displays the format of the pdstscls command for a HiRDB/Parallel Server. This message is output when the command format is invalid.

Usage

pdstscls { -f file-name |-n logical-file-name }

S: Terminates processing.

O: Reenter correctly the specified command.

KFPS01086-I E

Usage: pdstsswap [-x host_name |-u unit_id]
pdstsswap -s server_name

Displays the format of the pdstsswap command for a HiRDB/Single Server. This message is output when the command format is invalid.

Usage

pdstsswap

S: Terminates processing.

O: Reenter correctly the specified command.

KFPS01086-I E

Usage: pdstsswap {-x host_name |-u unit_id}
pdstsswap -s server_name

Displays the format of the pdstsswap command for a HiRDB/Parallel Server. This message is output when the command format is invalid.

Usage

pdstsswap

S: Terminates processing.

O: Reenter correctly the specified command.

KFPS01090-E E+L

Error occurred in system call aa....aa [error code=bb....bb] function with error: cc....cc

System call aa....aa resulted in an error.

aa....aa: Name of the system call resulting in the error

bb....bb: Return value of the system call

cc....cc: Name of the function that issued the system call

S: Either resumes processing or terminates HiRDB abnormally, depending on the nature of the error.

Action

Contact the customer support center.

KFPS01091-E E+L

Insufficient memory. required memory size=aa....aa bytes, area type: bb....bb

A memory shortage occurred in the status server process.

aa....aa: Size (in bytes) of the area to be allocated

bb....bb: Type of area in which the memory shortage occurred:

PROCESS: Process private area

STATIC SHMPOOL: Static shared memory

S: Either resumes processing or terminates HiRDB abnormally, depending on the error.

Action

Take action appropriate to the area type in which the memory shortage occurred:

Static shared memory:

If the unit terminated abnormally when the error occurred at the startup of a user server (executed by specifying the -s option of the pdstart command) that is not a back-end server using the standby-less system switchover (effects distributed) facility, specify server in the pd_shmpool_control operand in the system common definition, and then restart the unit. Otherwise, contact the customer support center.

Process private area:

Check the usage of the process private area, take appropriate action, and then re-execute the function.

If the error recurs, contact the customer support center.

KFPS01099-E E+L

Error occurred with aa....aa function. error code=bb....bb function: cc....cc

Function aa....aa (an HiRDB function) resulted in an error.

aa....aa: Name of the HiRDB function resulting in the error

bb....bb: Internal return value of the HiRDB function

cc....cc: Name of the function that issued the HiRDB function

S: Either resumes processing or terminates HiRDB abnormally, depending on the nature of the error.

Action

Check the message output before or after this message to find the cause of the error, eliminate the error, and then re-execute. If no message was output before or after this message, see 4.1 Detail codes for RPC-related errors and 4.2 Detail codes for system-related errors. If the codes are the same as the HiRDB function internal return values, take the action appropriate for the codes. In UNIX, if HiRDB terminates abnormally, collect thecore file.

KFPS01103-E E+L

Unable to start log service. reason code=aaaa

The log server process cannot be started.
An error occurred while starting or restarting the log server process.

aaaa: Reason code indicating the nature of the error (the table below lists the reason codes and actions to be taken)

S: Abnormally terminates HiRDB.

Action

Check the reason code to determine why the log server process cannot be started or restarted, take appropriate action, and then restart HiRDB.

Reason code
Explanation
Action
Remarks

101
Memory shortage occurred.
Re-evaluate the memory usage.
--

103
Network error occurred.
Correct the error and restart the system.

405
Error was detected during definition analysis.
Check the definition file, correct the specification, and restart the system.
Error details are provided in a KFPU002XX message.

501
The number of HiRDB servers exceeded the maximum.
Correct the defined information and restart the system.
--

502
The information required to recover the system was not found in the status file.
Re-evaluate the operand related to the status file for the server in each server definition.
Possible causes:

The status file name specified in the pd_sts_file_name_1-7 (if a log application site, pd_sts_subfile_name_1-7) operand has been changed

The status file specified in the pd_sts_file_name_1-7 (if a log application site, pd_sts_subfile_name_1-7) operand has been initialized

The logical file name specified in the pd_sts_last_active_file and pd_sts_last_active_side (if a log application site, pd_sts_last_active_subfile and pd_sts_last_active_side_sub) operands or the status file that was current in the previous system operation are different

503
Error occurred during status file I/O processing.
Check the cause of the error, correct the error, and restart the system.
--

504
Error occurred while activating the log server process.
Check the cause of the error, correct the error, and restart HiRDB.

508
Error occurred while activating the log s process.

512
Error occurred while analyzing the log swapper process-related definitions.

514
Error occurred while activating the log swapper process.
Check the cause of the error, correct the error, and restart HiRDB.
Details of the cause of the error are displayed before this message.

515
Error occurred while analyzing the log swapper process definitions.
Correct the definition according to the message that was output before this message and restart HiRDB.
--

516
Activation of an internal thread failed in the log server process.
Check the cause of the error, correct the error, and restart HiRDB.
Details of the cause of the error are displayed before this message.

541
Error occurred while activating the status server process.
Correct the error on the basis of the message that was output before this message and restart the system.
--

--: Not applicable

KFPS01104-W L

Unable to recover previous log service conditions referring to status file; continues restart processing without status file. reason code=aaaa

The status of the previous log server process could not be restored from the status file. The system resumes restart processing without the status file.

aaaa: Reason code indicating the nature of the error (the table below lists the reason codes and actions to be taken)

S: Resumes processing.

Action

Take action appropriate to the reason code, as listed below:

Reason code
Explanation
Action
Remarks

502
Previous online status was not found in the status file
For a log application site, if a failure occurred during startup, perform preparation for system log application, and then restart. If other than the above, no action is required in response to this message.
Possible reason is:

Error occurred while writing the status during the previous session

For a log application site, all secondary status files have been initialized

503
Error occurred during status record I/O processing.
If restart fails, take action appropriate to the status server process message (KFPS010xx) that was output before this message.
--

--: Not applicable

KFPS01108-W L

Error occurred while terminating log service; continues processing. reason code=aaaa

An error occurred while terminating the log server process, but processing continues.

aaaa: Reason code indicating the nature of the error (the table below lists the reason codes and actions to be taken)

Action

Refer to the reason code in order to check the cause of the error and take appropriate action, if necessary.

Reason code | Explanation | Action
101 | Memory shortage occurred. | Check the memory size before the next startup.
103 | Network error occurred. | Correct the network error before the next startup.
503 | Error occurred during status file I/O processing. | Check the cause of the error and take appropriate action before the next startup.

KFPS01109-W E+L

Minor error occurred while analyzing definitions for log service. file being analyzed aa....aa, record number=bb....bb, reason code=cc....cc

A minor error occurred while analyzing the log server process-related definitions.

aa....aa: Name of definition file being analyzed

bb....bb: Record number resulting in the error

cc....cc: Reason code indicating the nature of the error (the table below lists the reason codes and actions to be taken)

S: Ignores the definition statement containing the erroneous pdlogadfg or pdlogadpf operand and starts or restarts the log server process (assumes that the definition statement has not been specified).

Action

Re-evaluate the log server process-related definitions.

Reason code
Explanation
Action
Remarks

408
The pdlogadfg operand is invalid:

-g option is not specified.

Specified file group name is duplicated.

If necessary, terminate the system, correct the definition, then restart.
--

409
-g option is invalid in the pdlogadpf operand:

-g option is not specified.

File group specified in the -g option is undefined in the pdlogadfg operand specified in the previous row

If necessary, stop the system, check the following items, and correct the pdlogadpf operand. Then, restart the system.

Is the g option specified?

Is the file group name specified in the -g option correct?

Is the file group specified in the -g option defined in the pdlogadfg operand specified in the previous row?

411
-a option is invalid in the pdlogadpf operand:

-a option is not specified.

Length of path specified in the -a option exceeds the character maximum.

Length of the HiRDB file system area name specified in the -a option exceeds the limit (117 characters).

Length of HiRDB file name specified in the -a option exceeds the maximum (30 characters).

HiRDB file name specified in the -a option duplicates another HiRDB file name.

If necessary, terminate the system, correct the definition, then restart.

412
-b option is invalid in the pdlogadpf operand:

-b option is not specified (applicable when dual log is used).

Length of path specified in the -b option exceeds the character maximum.

Length of the HiRDB file system area name specified in the -b option exceeds the limit (117 characters).

Length of HiRDB file name specified in the -b option exceeds the maximum (30 characters).

HiRDB file name specified in the -b option duplicates another HiRDB file name.

Applicable when dual log is used.

413
The number of pdlogadfg operands exceeds the maximum.
An erroneous pdlogadfg operand is not included in the operands count.

415
More than one pdlogadpf operand with the same file group name was specified.
--

422
-d option is invalid in the pdlogadfg operand or is not specified.

423
-d option is invalid in the pdlogadpf operand or is not specified.

--: Not applicable

KFPS01113-E E+L

Unable to start aaaa(xx....xx) log file service. reason code=bbbb

The aaaa(xx....xx) log server process cannot be started.
An error occurred while starting or restarting the log server process.

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

bbbb: Reason code indicating the nature of the error (the table below lists the reason codes and actions to be taken)

S: Cancels unit startup processing.

Action

Take action appropriate to the reason code, as listed below, then restart HiRDB:

Reason code
Explanation
Action
Remarks

101
Memory shortage occurred.
Check the memory size in use.
--

103
Network error occurred.
Correct the error and restart the system.

114
Required information was not found in the message queue identifier table in the system.
Reconfigure the kernel, changing the value of message-related msgmni parameter.

117
Because the value specified for the operand changed, an attempt was made to allocate more memory than the size of the shared memory that was allocated at system startup.
For the formula for calculating the log server, see the section on formulas for calculating shared memory used by unit controllers in the manual HiRDB Version 9 Installation and Design Guide, and change the definition values to make the size of the log server shared memory less than 2 GB. For HiRDB/Parallel Server, calculate using 1 as the value for number-of-servers-in-unit+D and number-of-FES-in-unit.
--

405
Error was detected during definition analysis.
Check the definition file, correct the error, then restart the system.
Error details are provided in a KFPU002XX message.

414
The number of valid log file group definitions is less than the minimum number of generations required for system startup.
Correct the pdlogadfg operand in the applicable HiRDB server definition and restart the system.
A valid definition means a correct pdlogadfg operand with ONL specified.

416
The file group names specified in the -g option of the pdlogadfg operand include file groups not defined in the pdlogadpf operand; or file groups are defined in the pdlogadpf operand before the pdlogadfg operand.
Check the following items, and correct the pdlogadfg operand and pdlogadpf operand of the corresponding HiRDB server definition. Then, restart the system.

Is the file group name specified in the -g option correct?

Is the pdlogadpf operand defined after the pdlogadfg operand definition?

--

503
Error occurred during status file I/O processing.
Check the cause of the error, correct the error, then restart the system.

504
Error occurred while activating the log swapper process.

508
Error occurred during startup of the log swapper process.
Details of the error have been displayed before this message.

510
Error was detected during log file checking.

--: Not applicable

KFPS01114-W E+L

Error occurred while terminating aaaa(xx....xx) log file service;continues processing. reason code=bbbb

An error occurred while terminating the aaaa(xx....xx) log server process, but processing continues.

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

bbbb: Reason code indicating the nature of the error (the table below lists the reason codes and actions to be taken)

Note

Even though this message was output, the log server process will start normally the next time.

S: Resumes termination processing.

Action

Take action appropriate to the reason code as listed below, if necessary:

Reason code | Explanation | Action | Remarks
101 | Memory shortage occurred. | Check the memory size before the next startup. | --
103 | Network error occurred. | Recover the network environment before the next startup.
503 | Error occurred during status file I/O processing. | Check the cause of the error and take appropriate action before the next startup.
511 | Error occurred during log file termination processing. | Check the cause of the error and take appropriate action before the next startup. | Details of the error have been displayed before this message.

--: Not applicable

KFPS01115-E E+L

Unable to start I/O service of aaaa(xx....xx) log file. reason code=bbbb

aaaa(xx....xx) log swapper process cannot be started.

aaaa: Type of log file

sys: System log file

xx....xx: HiRDB server name

bbbb: Reason code indicating the nature of the error (the table below lists the reason codes and actions to be taken)

S: Terminates HiRDB.

Action

Take action appropriate to the reason code, as listed below, then restart HiRDB:

Reason code | Explanation | Action | Remarks
101 | Memory shortage occurred. | Check the memory size in use. | --
103 | Network error occurred. | Correct the error and restart the system.
405 | Error was detected during definition analysis. | Check the definition file, correct the error, then restart the system. | Error details are provided in a KFPU002XX message.
503 | Error occurred during status file I/O processing. | Check the cause of the error, correct the error, then restart the system. | --

--: Not applicable

KFPS01116-W L

Error occurred while terminating I/O service of aaaa(xx....xx) log file; continues processing. reason code=bbbb

An error occurred while terminating the aaaa(xx....xx) log swapper process, but the system resumed processing.

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

bbbb: Reason code indicating the nature of the error (the table below lists the reason codes and actions to be taken)

Note

Even though this message was output, the log server process will start normally the next time.

S: Resumes termination processing.

Action

Take action appropriate to the reason code, as listed below, if necessary:

Reason code | Explanation | Action
101 | Memory shortage occurred. | Check the memory size before the next startup.
103 | Network error occurred. | Recover the network environment before the next startup.
503 | Error occurred during status file I/O processing. | Check the cause of the error and take appropriate action before the next startup.

KFPS01121-E L

Insufficient memory. required memory size=aa....aa, area type:bb....bb

A memory shortage occurred.

aa....aa: Size of the area that was to be allocated

bb....bb: Type of the area resulting in the error:

STATIC_SHMPOOL: Static shared memory

S: Cancels processing.

Action

If the unit terminated abnormally when the error occurred at the startup of a user server (executed by specifying the -s option of the pdstart command) that is not a back-end server using the standby-less system switchover (effects distributed) facility, specify server in the pd_shmpool_control operand in the system common definition, and then restart the unit. Otherwise, revise the system definitions, and then retry the operation.

KFPS01125-E L

Unable to use log service server aaaa(xx....xx). reason code=cccc-dd

Server aaaa(xx....xx) cannot use the log service function.

aaaa: Server name

xx....xx: HiRDB internal code

cccc: Reason code indicating the nature of the error (the table below lists the reason codes and actions to be taken)

dd: HiRDB internal code

S: Depends on server message aaaaaaaa that is issued after this message.

O: Take action appropriate to the reason code, as listed below:

Reason code | Explanation | Operator's action | HiRDB Administrator's action
101 | Memory shortage occurred. | -- | Take action appropriate to the message output after this message.
104 | Log server process is not online. | Terminate the system and restart it. | Check the cause of the error to determine why HiRDB has not started normally.
903 | Server with the same name attempted to use the log service function. | -- | Check the server name or startup mode.
904 | This server cannot be restarted because the log service function has started normally. | Take action appropriate to the message output after this message.
905 | Log service cannot be provided to this server due to a status file access error. | Check the cause of the status file access error.
906 | Log required for server restart is not available due to a log file I/O error or other error. | Check the cause of the log file error as required.
907 | Attempt was made to start the synchronization point service function, but this service cannot be provided to this server. | Take action appropriate to the message that is output after this message. | Check the HiRDB server definition for an error.
908 | Synchronization point service definition was defined for a server that does use the synchronization point service function. | --

--: Not applicable

KFPS01128-W L

Unable to specify bb....bb in aa....aa operand, replace bb....bb with cc....cc, server=dd....dd

bb....bb cannot be specified in the aa....aa operand. bb....bb has been replaced with cc....cc.

aa....aa: Operand name

bb....bb: Specified value of the aa....aa operand

cc....cc: Value replacing the aa....aa operand

dd....dd: Server name

S: Continues processing.

Action

Referring to the manual HiRDB Version 9 System Definition, re-evaluate the value specified in the aa....aa operand. Pay particular attention to the following points:

Check if values that cannot be combined are specified.

Check if values that cannot be changed during startup have been changed.

KFPS01129-E E+L

Definition analysis error. definition name=aa....aa, server name=bb....bb, reason code=cc....cc

An analysis error occurred on the aa....aa operand in the definition analysis of the server bb....bb.

aa....aa: Operand name

bb....bb: HiRDB server name

cc....cc: Reason code indicating the nature of the error

1: The specified value is greater than the operand specification range.

2: The specified number of operands is invalid.

606: Other than the above

S: Terminates processing.

Action

Referring to the manual HiRDB Version 9 System Definition, re-evaluate the value specified in the aa....aa operand.

KFPS01130-W L

Error occurred while starting aaaa(bb....bb) log service; continues processing. reason code=cccc

An error occurred while the aaaa(bb....bb) log service facility was being started, but processing continues.

aaaa: Type of log file:

sys: System log file

bb....bb: HiRDB server name

cccc: Reason code indicating the nature of the error:

1654: Invalid file for data linkage

S: If the reason code is 1654, the system continues system startup processing using the same HiRDB Datareplicator extraction-completed or extracting status in the system log file as the last time HiRDB was terminated. Extracting status will not be released even for a log file whose extraction was completed when HiRDB was terminated at the corresponding server.

O: If the reason code is 1654, check the HiRDB Datareplicator linkage file by entering the pdls -d rpl -j command to determine whether or not the linkage operation can continue. If linkage processing with HiRDB Datareplicator cannot be continued, contact the administrator.

Action

If the reason code is 1654 and the HiRDB Datareplicator linkage cannot be performed, see the HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide, and redo the data linkage.

KFPS01150-E L

Auto log unload service terminated. server=aa....aa:create dir=bb....bb:reason=cccc

The automatic log unloading facility was terminated in server aa....aa.

aa....aa: HiRDB server name

bb....bb: Unload log file creation directory

cccc: Reason code indicating the error cause:

1660: Unloading of system log files failed in all unload log file creation directories.

1661: Creation of log server process failed.

1664: The unload log file that was to be created is already being used by another process.

S: Continues processing.

Action

Take corrective action according to the reason code.

1660 displayed as the reason code (when an unload log file creation directory is specified in the pd_log_auto_unload_path operand)
The possible causes are listed in the table below. After taking corrective action, resume the automatic log unloading facility by executing the pdlogatul -b command or by restarting HiRDB normally.

No. | Cause | Action
1 | A disk space shortage occurred in the unload log file creation directory. | Allocate more free disk space.
2 | A disk error occurred in the unload log file creation directory. | Correct the disk error.

1660 displayed as the reason code (when a HiRDB file system area is specified in the pd_log_auto_unload_path operand)
The possible causes are listed in the table below. After taking corrective action, resume the automatic log unloading facility by executing the pdlogatul -b command or by restarting HiRDB normally.

No.
Cause
Action

1
A disk space shortage occurred in the HiRDB file system area.
Allocate more free disk space.

2
A disk error occurred in the HiRDB file system area.
Correct the disk error.

3
One of the following items, which were specified when the HiRDB file system area was created, has reached its maximum value.

Maximum number of files (value specified in the -l option)

Maximum number of extensions (value specified in the -e option)

HiRDB file system area size (value specified in the -n option)

Increase the value specified for the item that has reached its upper limit#, and then re-create the HiRDB file system area.
For appropriate values for each item, see Guidelines for options to be specified in the pdfmkfs command under Using the automatic log unloading facility in the HiRDB Version 9 System Operation Guide.
The procedure for re-creating the HiRDB file system area is as follows:

Use the pdfbkup command to back up the unload log files in the HiRDB file system area.

Use the pdfmkfs command to re-create the HiRDB file system area. Increase the value specified for the item that has reached its upper limit.

Use the pdfrstr command to restore the HiRDB file system area. Using the backups from step 1, store the unload log files inside the re-created HiRDB file system area.

#

Execute the pdfstatfs command to check for items that have reached their upper limit. Check the following items in the execution results of the pdfstatfs command:

remain file count: Displays the number of HiRDB files that can be created. If 0 is displayed, the maximum number of files (the value specified in the -l option) has been reached.

available expand count and current expand count: Displays the value specified in the -e option in available expand count, and the total number of extensions in current expand count. When the values in available expand count and current expand count are the same, the maximum number of extensions (the value specified in the -e option) has been reached.

If neither of the two items above are applicable, the HiRDB file system area size (the value specified in the -n option) has reached its upper limit. Check the amount of unused space in the HiRDB file system area in remain user area capacity in the execution results of the pdfstatfs command.

1661 displayed as the reason code
Check the maximum number of processes that can be executed in the server machine and terminate unnecessary processes; also check if sufficient system resources, such as memory space, are available.

1664 displayed as the reason code
Check if there is another process that is manipulating a file in the unload log file creation directory. Then resume the automatic log unloading facility by executing the pdlogatul -b command or by restarting HiRDB normally.

In all other cases
Obtain the following information and contact the customer support center:
All files under %PDDIR%\spool
HiRDB system definition files
Event log (in UNIX, syslogfile)
Execution results of the pdlogls -d sys command

KFPS01151-I L

aa....aa changed auto log unload directory from bb....bb to cc....cc.reason=dddd

The unload log file creation directory to be used by server aa....aa was switched from bb....bb to cc....cc.

aa....aa: HiRDB server name

bb....bb: Unload log file creation directory before the switch

If the name of the unload log file creation directory before the switch exceeds 76 characters, the last 76 characters of the name of the unload log file creation directory before the switch is output.

cc....cc: Unload log file creation directory after the switch

If the name of the unload log file creation directory after the switch exceeds 76 characters, the last 76 characters of the name of the unload log file creation directory after the switch is output.

dddd: Reason code:

1665: The disk in which the unload log file creation directory is located became full.

S: Continues processing.

Action

Move unload log files in the unload log file creation directory to another area or delete unneeded unload log files.

KFPS01152-W L

No use aa....aa as auto log unload directory. server=bb....bb:reason=cccc

Directory cannot be switched to the unload log file creation directory (directory name aa....aa) used by server bb....bb. Another directory is being used as the switching destination.

aa....aa: Name of the unload log file creation directory

bb....bb: HiRDB server name

cccc: Detail code (see the list of detail codes in the Action section)

S: Continues processing.

Action

Take the action appropriate to the detail code, as shown below:

Detail code
Meaning
Action

1661
A shortage of resources occurred (such as memory space, file descriptors, or lock segments).
Recheck the amount of memory that is required. In UNIX, change the values of the following operating system parameters as necessary:

maxfiles

nfile

nflocks

1666
A permission error occurred.
Grant the write privilege for the unload log file creation directory.

1667
An I/O error occurred.
Correct the error on the disk in which the unload log file creation directory is located. If the unload log files necessary for database recovery have been lost, make a backup.

1668
An unload log file creation directory or a HiRDB file system area for creation of unload log files does not exist.
Create an unload log file creation directory or a HiRDB file system area for unload log files.

1669
Unload log files created during the previous operation remain in the unload log file creation directory.
Move the unload log files to another area or delete unneeded unload log files.

1670
The type of the unload log file creation directory or HiRDB file system area for unload log files is invalid.

Check that the path name of the unload log file creation directory is correct.

Check that a HiRDB file system area for unload log files has been created for utilities.

KFPS01153-I L

Auto log unload service restart. server=aa....aa:create dir=bb....bb:reason=cccc

The automatic log unloading facility will be restarted in server aa....aa.

aa....aa: HiRDB server name

bb....bb: Unload log file creation directory

cccc: Reason code:

1662: The automatic log unloading facility was restarted because the pdlogatul -b command was executed.

1682: The automatic log unloading facility was restarted because the system log files were swapped, or because of normal or planned termination of HiRDB.

S: Continues processing.

KFPS01154-I L

Auto log unload service stopped. server=aa....aa:create dir=bb....bb:reason=cccc

The automatic log unloading facility was stopped in server aa....aa.

aa....aa: HiRDB server name

bb....bb: Unload log file creation directory

cccc: Reason code:

1662: The automatic log unloading facility was stopped because the pdlogatul -t command was executed.

S: Continues processing.

KFPS01155-W L

aa....aa changed auto log unload directory from bb....bb to cc....cc.reason=dddd

Because an error occurred in the unload log file creation directory (directory name bb....bb) to be used by server aa....aa, the directory was switched from bb....bb to cc....cc.

aa....aa: HiRDB server name

bb....bb: Unload log file creation directory before the switch

If the name of the unload log file creation directory before the switch exceeds 76 characters, the last 76 characters of the name of the unload log file creation directory before the switch are output.

cc....cc: Unload log file creation directory after the switch

If the name of the unload log file creation directory after the switch exceeds 76 characters, the last 76 characters of the name of the unload log file creation directory after the switch are output.

dddd: Detail code (see the list of detail codes in the Action section)

S: Continues processing.

Action

Take the action appropriate to the detail code, as shown below:

Detail code
Meaning
Action

1661
A shortage of resources occurred (such as memory space, file descriptors, or lock segments).
Recheck the amount of memory that is required. In UNIX, change the values of the following operating system parameters as necessary:

maxfiles

nfile

nflocks

1666
A permission error occurred.
Grant the write privilege for the unload log file creation directory.

1667
An I/O error occurred.
Correct the error on the disk in which the unload log file creation directory is located. If the unload log files necessary for database recovery have been lost, make a backup.

1668
An unload log file creation directory or a HiRDB file system area for creation of unload log files does not exist.
Create an unload log file creation directory or a HiRDB file system area for unload log files.

1669
Unload log files created during the previous operation remain in the unload log file creation directory.
Move the unload log files to another area or delete unneeded unload log files.

1670
The type of the unload log file creation directory or HiRDB file system area for unload log files is invalid.

Check that the path name of the unload log file creation directory is correct.

Check that a HiRDB file system area for unload log files has been created for utilities.

KFPS01156-I L

aa....aa wait for auto log unloading.file group=bb....bb:create dir=cc....cc

Server aa....aa is waiting for automatic log unloading to be completed. System log files of file group bb....bb are being unloaded at this time.

aa....aa: HiRDB server name

bb....bb: File group name of the system log files being unloaded currently

cc....cc: Unload log file creation directory

S: Continues processing.

KFPS01157-W L

Unable to use auto log unload service. server=aa....aa:reason=bbbb

The automatic log unloading facility cannot be used in server aa....aa.

aa....aa: HiRDB server name

bbbb: Reason code:

1662: HiRDB system definition is invalid.

1663: Status file information is invalid.

1664: For a log application site HiRDB, the automatic log unloading facility cannot be started.

S: Continues processing.

Action

Take one of the following actions:

Reason code is 1662:

Check if the value specified in the pd_log_auto_unload_path operand is correct. If it is, restart HiRDB normally and start the automatic log unloading facility.

Reason code is 1663:

If this message was preceded by an error message related to the status file, take the action recommended in that message. If there has been no error in the status file, restart HiRDB normally and start the automatic log unloading facility.

Reason code is 1664:

For a transaction execution site HiRDB, start the automatic log unloading facility.

In all other cases:

Save the following information and contact the customer support center:

All files under %PDDIR%\spool

HiRDB system definition files

Event log (in UNIX, syslogfile)

Execution results of the pdlogls -d sys command

KFPS01158-W L

Unable to restart auto log unload service. server=aa....aa

The automatic log unloading facility cannot be restarted on server aa....aa.

aa....aa: HiRDB server name

S: Stops trying to restart the automatic log unloading facility, and resumes termination processing of the server.

Action

Check the reason code in message KFPS01150-E, which was output to the event log on the system manager unit (syslogfile in UNIX), to determine the cause, and then take corrective action.

In addition, because the automatic log unloading facility has stopped, the system log file group remains on unload wait status. Execute either of the following commands to set it to unload completed status:

pdlogunld command

pdstart command (unloads using the automatic log unloading facility the next time the server is started)

KFPS01160-E L

Insufficient system log space. Transaction service stopped. Transactions terminate by force, server = aa....aa, output file name = bb....bb

The free space percentage of the system log file became less than the warning value. The target server is aa....aa. The system log file free area monitoring facility suppresses the scheduling of new transactions to the aa....aa server and forcibly terminates all transactions on the server. This facility also outputs the system log file status information file to %PDDIR%\spool\pdjnlinf\bb....bb.
For details about monitoring the free area for system log files, see the HiRDB Version 9 System Operation Guide.

aa....aa: HiRDB server name

bb....bb: Status information file name of the system log file

S: Continues processing.

O: Contact the HiRDB administrator.

Action

Take the following actions:

Check the status of the system log file using the pdlogls command, and then increase the number of system log files created at the swap destination.

Suppress the issuing of new transactions to the aa....aa server until the KFPS01161-I message is output.

After taking these actions, eliminate the cause of the free area shortage in the system log file of server aa....aa.

For details about the actions to be taken by the HiRDB administrator if the free space percentage for the system log files becomes lower than the warning value, see the description of monitoring the free area for system log files in the HiRDB Version 9 System Operation Guide.

If Real Time SAN Replication is applicable and if a KFPS02178-E message was output before this message, take the action indicated in the KFPS02178-E message.

KFPS01161-I L

System log available space gained. Transaction service restart, server = aa....aa, rest = bb....bb%

The free percentage of the system log file became greater than the warning value because new areas ready for system log output were acquired. The target server is aa....aa. Cancels scheduling suppression of new transactions by the free space monitoring facility for system log files. For details about monitoring the free area for system log files, see the HiRDB Version 9 System Operation Guide.

aa....aa: HiRDB server name

bb....bb: Percentage of remaining system log file space the system log can output.

This percentage is based on a value of 100% for the entire system log file space.

S: Continues processing.

Action

Take the following actions:

Cancel the suppression of the issuing of new transactions.

If no action was taken according to the KFPS01160-E message, take action immediately.

When bb....bb is low, the cause of the system log file free space shortage was not resolved. If operation continues in this state, the problem of insufficient free space for the system log file may recur. For details about how to recover from insufficient free space, see the description of monitoring free space for system log files in the HiRDB Version 9 System Operation Guide.

KFPS01162-W L

Insufficient system log space, server = aa....aa, output file name = bb....bb

The free percentage of the system log file became less than the warning value. The target server is aa....aa. The status information file of the system log file is output to %PDDIR%\spool\pdjnlinf\bb....bb.

aa....aa: HiRDB server name

bb....bb: Status information file name of the system log file

S: Continues processing.

O: Contact the HiRDB administrator.

Action

Check the status of the system log file using the pdlogls command and increase the number of status system log files created at the swap destination. For details about the actions to be taken by the HiRDB administrator if the free space percentage for the system log files becomes lower than the warning value, see the description of monitoring the free area for system log files in the HiRDB Version 9 System Operation Guide.

After taking these actions, eliminate the cause of the free area shortage in the system log file of server aa....aa.

If Real Time SAN Replication is applicable and if a KFPS02178-E message was output before this message, take the action indicated in the KFPS02178-E message.

KFPS01163-W L

Waiting for transaction completion, server = aa....aa, current transaction count = bb....bb

The system manager is waiting for completion of the transaction. The target server is aa....aa. Because the RDAREA may perform an error shutdown if the transaction waiting for termination is forcibly terminated, do not forcibly terminate the transaction.

aa....aa: HiRDB server name

bb....bb: The number of transactions waiting for termination

Action

Suppress the issuing of new transactions to the aa....aa server until the KFPS01161-I message is output. For details about how to determine the transaction for which completion is pending, see the description of monitoring free space for system log files in the HiRDB Version 9 System Operation Guide.

KFPS01170-E L

Unable to read system log file, server=aa....aa, reason=bbbb(cc....cc)

The update log of the system log file could not be read with discrepancies application of online reorganization.

aa....aa: HiRDB server name

bbbb: Reason code (see Action below)

cc....cc: Detail information (see Action below)

S: Terminates processing.

Action

See the reason code and detail information in the following table, and then take appropriate action. For details about re-executing updatable online reorganization, see the HiRDB Version 9 Staticizer Option Description and User's Guide.

Reason code
(bbbb)
Detail information
(cc....cc)
Meaning
Action

101
Memory size to be allocated
Failed to secure the necessary memory area.
Re-evaluate the system virtual memory capacity. If there is a shortage, expand the virtual memory capacity. If the memory capacity cannot be extended, secure more free virtual memory by stopping other unnecessary resident programs or processes.

106
Internal information
Cannot access common memory HiRDB uses.
If this message is output when HiRDB is inactive, restart HiRDB, and then re-execute the pdorend command.
If this message is output when HiRDB is active, either the common memory area was deleted or the access privilege is invalid. If a system call error message is output immediately before this message, take action according to that message. If the system call error message is not output, check the following items for problems:

Is the person executing the updatable online reorganization the HiRDB administrator?

Is the file in the spool directory in the HiRDB operation directory improperly falsified?

If the problem cannot be determined, contact the customer support center.

112
Internal information
Executed updatable online reorganization, but server did not start the unit.
Start the applicable unit.

711
Generation number
The generation number is missing from the file group of the system log file in the detail code.
Use the pdlogls -d sys command to check if the file group of the system log file with the applicable generation number exists.
If the file group of the system log file does not exist, updatable online reorganization cannot continue because the system log file was overwritten and the required update log records cannot be input. To re-execute updatable online reorganization, re-execute from the pdorbegin command.
If the file group of the system log file exists, prepare the following data and contact the customer support center:

Execution result of the pdls -d org -a command

Execution result of the pdlogls -d sys command

Applicable system log file or a backup file of the applicable system log file (except for the unload file)

1001
701
Cannot find the file group of the system log file the system log target start point indicates.
Execute the pdls -d org -a command and check the file group name of the system log for the system log target start point. In addition, use the pdlogls -d sys command to check for the file group of the system log file.
If the file group of the system log file cannot be found, updatable online reorganization cannot continue because the system log file was overwritten and the necessary update log records cannot be input. To execute updatable online reorganization, re-execute from the pdorbegin command.

702
Cannot open the system log file the system log target start point indicates.
See the KFPS01171-E message just output to determine the cause of the error and take appropriate action. Then, execute the pdorend command and re-execute updatable online reorganization.

1605
Generation information of the system log file the system log target start point indicates is invalid.
Execute the pdls -d org -a command and check the generation number and run ID of the file group for the system log file the system log target start point indicates. In addition, use the pdlogls -d sys command to check if the generation number and run ID match the generation number and run ID of the file group of the system log file.
If the generation numbers or run IDs do not match, updatable online reorganization cannot continue because the system log file was overwritten and the necessary update log records cannot be input. To re-execute updatable online reorganization, re-execute from the pdorbegin command.
If the generation numbers and run IDs are the same, prepare the following data and contact the customer support center:

Execution result of the pdls -d org -a command

Execution result of the pdlogls -d sys command

Applicable system log file or a backup file of the applicable system log file (except for the unload log file)

1653
701
Cannot find the file group of the system log file the system log target point indicates.
Execute the pdls -d org -a command and check the file group name of the system log file the system log target start point indicates. In addition, use the pdlogls -d sys command to check for the file group of the system log file.
If the file group of the system log file cannot be found, updatable online reorganization cannot continue because the system log file was overwritten and the necessary update log records cannot be input. To execute updatable online reorganization, re-execute from the pdorbegin command.

702
Cannot open the system log file the system log target start point indicates.
See the KFPS01171-E message just output to determine the cause of the error and take appropriate action. Then, execute the pdorend command and re-execute updatable online reorganization.

1602
Found missing system log block(s) in the system log file input from the system log target point.
Execute the pdlogls -d sys command and check for the file group of the system log file including the system log block number of the input target for the KFPS01171-E message just output.
If the file group of the system log file cannot be found, updatable online reorganization cannot continue because the system log file was overwritten and the necessary update log records cannot be input. To execute updatable online reorganization, re-execute from the pdorbegin command.

1605
Generation information of the system log file the system log target start point indicates is invalid.
Execute the pdls -d org -a command and check the generation number and run ID of the file group for the system log file the system log target start point indicates. In addition, use the pdlogls -d sys command to check if the generation number and run ID match the generation number and run ID of the file group of the system log file.
If the generation numbers or run IDs do not match, updatable online reorganization cannot continue because the system log file was overwritten and the necessary update log records cannot be input. To re-execute updatable online reorganization, re-execute from the pdorbegin command.
If the generation numbers and run IDs are the same, prepare the following data and contact the customer support center:

Execution result of the pdls -d org -a command

Execution result of the pdlogls -d sys command

Applicable system log file or a backup file of the applicable system log file (except for the unload log file)

KFPS01171-E L

Error occurred while reading system log file, server=aa....aa, file_group=bb....bb, system A/B=c, reason=dddd(ee....ee)

An error occurred in the system log file input in updatable online reorganization.

aa....aa: The HiRDB server name

bb....bb: File group name of the system log file

c: System where the error occurred (A or B)

dddd: Reason code (see Action below)

ee....ee: Detail information (see Action below)

S: Continues processing.

Action

See the reason code and detail information in the following table, and then take appropriate action.

Reason code
(dddd)
Detail information
(ee....ee)
Meaning
Action

213
Error code of the HiRDB file system
An open error occurred with the system log file
Check for the error cause and fix the error based on 5.1 Error codes returned from HiRDB file system access requests.
For detail information other than error codes of the HiRDB file system, contact the customer support center.

215
Error code of the HiRDB file system
A read error occurred with the system log file.

219
1652
Internal code
Invalid log lock data was detected in the system log file input.
When the system log file is duplexed, processing continues using the system where no errors occurred.
When the system log file is not duplexed, or an error occurs on both duplexed systems, updatable online reorganization cannot continue. To re-execute updatable online reorganization, first abort updatable online reorganization using the pdorend -u command, and then re-execute from the pdorbegin command. If this error message is repeatedly output even when re-executing updatable online reorganization, prepare the following data, and then contact the customer support center:

All directories or files under %PDDIR%\spool

The HiRDB system definition file

The execution result of the pdlogls -d sys -e command executed on the server that caused the error

The backup file created by executing the pdfbkup command on the system log file in the overwriting denied status for online reorganization

Event log (in UNIX, syslogfile)

602
Internal code
Invalid log record data was found in the system log file input.
When the system log file is duplexed, processing continues using the system where no errors occurred.
When the system log file is not duplexed, or an error occurs on both duplexed systems, the systems abnormally terminate because updatable online reorganization cannot continue. To re-execute updatable online reorganization, first abort updatable online reorganization using the pdorend -u command, and then re-execute from the pdorbegin command. If this error message is repeatedly output even when re-executing updatable online reorganization, prepare the following data, and then contact the customer support center:

All directories or files under %PDDIR%\spool

The HiRDB system definition file

The execution result of the pdlogls -d sys -e command executed on the server that caused the error

The backup file on the server where the error occurred created by executing the pdfbkup command on the system log file in the overwriting denied status for online reorganization

Event log (in UNIX, syslogfile)

1602
System log number of the input target
Found missing system log block(s) in the system log file input.
Execute the pdlogls -d sys command and check for the file group of the system log file including the system log block number of the input target.
If the file group of the system log file including the system log block number of the input target cannot be found, the file group of the applicable system log file may have been overwritten. If this causes updatable online reorganization to discontinue, the KFPS01170-E message is immediately displayed. See the actions for the KFPS01170-E message.
If there is a file group of the system log file that includes the system log block number of the input target, processing can continue by using the system where the error did not occur, if the system log file is duplexed. However, if the system log file is not duplexed, or if the error occurs on both duplexed systems, updatable online reorganization cannot continue. In this case, the KFPS01170-E message is immediately displayed. See the actions for the KFPS01170-E message.

1605
Generation information of the system log file#
Cannot process input of the update log record(s) because the generation information of the system log file does not match.
If the system log file is duplexed, processing can continue using the system where the error did not occur.
If the system log file is not duplexed, or if the error occurs on both duplexed systems, there are cases in which updatable online reorganization cannot continue. In this case, the KFPS01170-E message is immediately displayed. See the actions for the KFPS01170-E message.

1653
Generation information of the system log file#
The generation information of the system log file does not match the system log target start point, so the information cannot be used in update log record input processing.
If the system log file is duplexed, processing can continue using the system where the error did not occur.
If the system log file is not duplexed, or if the error occurs on both duplexed systems, updatable online reorganization cannot continue. In this case, the KFPS01170-E message is immediately output. See the actions for the KFPS01170-E message.

#: Formats:

AA....AA,BB....BB,CC....CC

AA....AA: Run ID

BB....BB: User run ID

CC....CC: Generation number

KFPS01175-W L

Online DB Reorganization overwrite status in all log file group changed and retrying swap, server=aa....aa, type=bbb

A system log file in the overwrite denied status for online reorganization was found, but because pd_log_org_no_standby_file_opr=continue was specified in the system definition, all system log files on the server were changed from the overwrite denied status for online reorganization to the overwrite permitted status for online reorganization, and the system log files were swapped.

aa....aa: HiRDB server name

bbb: Type of log file:

sys: System log file

S: Continues processing.

Action

After this message is output, all system log files enter the overwrite permitted status for online reorganization. Therefore, the update information required for discrepancies application of online reorganization is overwritten, and in some cases, updatable online reorganization cannot continue. In such cases, see the KFPS01170-E when it is output.

KFPS01180-E L

Skipped blocks detected while reading log. type: aaaa(xx....xx), previous read point: bb....bb,cc....cc, current read point: dd....dd, ee....ee, read direction: g

A missing block was detected while reading the log.

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

bb....bb: Name of the log file group that was read immediately before the missing block was detected

cc....cc: Log block number that was read immediately before the missing block was detected

dd....dd: Name of the log file group that has just been read

ee....ee: Log block number that has just been read

g: Log block read direction:

f: Forward

b: Backward

Note

If no log block was read, ********,******** is displayed for bb....bb,cc....cc.

S: Resumes processing.

Action

Refer to the messages listed below to check the cause of the error; if a file error, recover from the error. If the data can be recovered, recover the data and then restart HiRDB. If the data cannot be recovered, restore the data from a backup and then restart HiRDB. If the cause cannot be identified, contact the customer support center:

KFPS01181-E

KFPS01183-E

KFPS01184-E

KFPS01181-E L

Log read error. type:aaaa(xx....xx), read point: bb....bb,cc....cc, read direction: d, element file: ee....ee, system A/B: f, reason code=gggg-hh

A log read error occurred.

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

bb....bb: File group name

cc....cc: Block number

d: Log block read direction:

f: Forward

b: Backward

ee....ee: File group name of the system log file

f: File version resulting in the error:

a: A

b: B

gggg: Reason code:

213: The file group being read contains a closed file.

214: The file group being read contains a shutdown file.

215: The file group being read contains a file that cannot be read.

209: An I/O error occurred in the file group that was being read.

hh: HiRDB internal code

S: Resumes processing.

Action

Check the cause of the error on the basis of the reason code displayed in this message or the KFPS01203-E message, if it has been output before this message.

KFPS01182-I L

Generation file groups changed for further reading of log blocks. type: aaaa(xx....xx), from: bb....bb,cc....cc, to: dd....dd,ee....ee, read direction: g

File generations were changed for reading the log.

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

bb....bb: File group name before change

cc....cc: Generation number before change

dd....dd: File group name after change

ee....ee: Generation number after change

g: Log block read direction:

f: Forward

b: Backward

KFPS01183-E L

Skipped generations detected while reading log blocks. type: aaaa(xx....xx), range: bb....bb,cc....cc to dd....dd,ee....ee, skipped generations: ff....ff to gg....gg, read direction: h

A missing generation was detected while reading the log.

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

bb....bb: Name of the first log file group from which log blocks are read

cc....cc: Number of the first log generation from which log blocks are read

dd....dd: Name of the last log file group from which log blocks are read

ee....ee: Number of the last log generation from which log blocks are read

ff....ff: Number of the first generation missing a generation

gg....gg: Number of the last generation missing a generation

h: Log block read direction:

f: Forward

b: Backward

Note

During recovery of the log service function, ********,******** is displayed for dd....dd,ee....ee. If only one generation is missing, the same information is displayed in ff....ff to gg....gg.

S: Resumes processing.

KFPS01184-E L

Invalid log data detected while reading log. type:aaaa(xx....xx), read point: bb....bb,cc....cc, element file: dd....dd read direction: e, system A/B: f

Invalid log data was detected while reading the log.

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

bb....bb: Name of the log file group in which invalid log data was detected

cc....cc: Number of the log block that was to be read

dd....dd: File group name of the system log file

e: Log block read direction:

f: Forward

b: Backward

f: File version resulting in the error:

a: A

b: B

S: Resumes processing.

Action

Because the log file may be damaged, stop using the log file and check the cause of the error.

KFPS01185-E L

Unable to read log file group. type: aaaa(xx....xx), read point: bb....bb,cc....cc, read direction: d, reason code=eeee-ff

While reading log files, a file group was detected that cannot be read.

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

bb....bb: File group name

cc....cc: Generation number

d: Log block read direction:

f: Forward

b: Backward

eeee: Reason code:

1001: The indicated file group cannot be read, because the last location of the log was lost in the file group

ff: HiRDB internal code

S: Resumes processing.

KFPS01200-E L

Failure to open aaaa(xx....xx)log file. element file: bb....bb, system A/B: c, reason code= ddd-ee....ee

The system failed to open log file aaaa(xx....xx). A file cannot be opened.

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

bb....bb: File group name

c: File version:

a: A

b: B

ddd: Reason code

ee....ee: HiRDB internal code

S: Shuts down the erroneous file and resumes processing.

O: Take an action given in the Operator's action column appropriate to the reason code, as listed in the table below.

Action

Take an action given in the HiRDB Administrator's action column appropriate to the reason code, as listed in the following table.

Reason code
Explanation
Operator's action
HiRDB Administrator's action

101
Memory shortage occurred.
--
Re-estimate the memory.

201
File name is invalid.
Consider the following causes:

An invalid character was specified in the path name.

The length of the HiRDB file name exceeds the maximum (30 characters).

Specify the file name correctly and re-execute the command.
--

202
In UNIX:
The specified file name is not a character special file. Or, there is no device that corresponds to this file.
In Windows:
This is not a direct disk; or there is no device that corresponds to this file.
--
Re-evaluate the pdlogadpf operand specification.
For a log application site, determine whether the absolute path of the system log file is the same as for a transaction execution site.

203
The device specified in path has not been initialized for the HiRDB file system.

207
Maximum value was exceeded when a character special file was being opened.
Close files that are not being used by the log service function and reopen the file.
Re-evaluate the maximum number of files that can be opened per process, and re-create the kernel, if necessary.

208
There is no access privilege for the specified character special file.
--
Modify the access privileges for the specified HiRDB file system area using OS commands (chmod, for example.).

209
I/O error occurred.
Check the cause of the I/O error and take appropriate action.
--

210
HiRDB file system versions do not match.
Re-create the HiRDB file system with the pdfmkfs command, and re-create the log file with the pdloginit command.

211
There is no access privilege for the specified file.
--
Modify the access privileges for the HiRDB file system area where the specified file is stored using OS commands (chmod, for example).

212
Specified file was not found.
--
Re-evaluate the pdlogadpf operand specification.
For a log application site, determine whether the absolute path of the system log file is the same as for a transaction execution site.

218
219
Specified file cannot be used as a log file.
Delete the erroneous file with the pdlogrm command, then re-create the file with the pdloginit command.
For a log application site, determine whether the absolute path of the system log file is the same as for a transaction execution site.
--

220
Specified file is not a log file.
--
Re-evaluate the pdlogadpf operand specification.
For a log application site, determine whether the absolute path of the system log file is the same as for a transaction execution site.

221
Lock segment shortage occurred.
Re-evaluate the number of record lock segments specified during the construction of the OS system.

222
Attempt was made to open a log file, but it was being used by another process.
Check the applicable log file as to whether or not it is being used by another process. Reopen the file, if necessary.
--

229
The possible causes are:

Attempt was made to open a system log file created in a HiRDB file system area that exceeds 2 GB, but N is specified in the pd_large_file_use operand.

Attempt was made to open a system log file created in a HiRDB file system area created with the pdfmkfs -a command, but N is specified in the pd_large_file_use operand.

--
Specify Y for the pd_large_file_use operand, or omit the specification.

--: Not applicable

KFPS01201-E L

Failure to close aaaa(xx....xx) log file. element file: bb....bb, system A/B: c,reason code=dddd-ee

The system failed to close log file aaaa(xx....xx). A file cannot be closed.

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

bb....bb: System log file name

c: File version:

a: A

b: B

dddd: Reason code:

101: Memory shortage occurred.

209: I/O error occurred.

221: Lock segment shortage occurred.

ee: HiRDB internal code

S: Ignores the error and resumes processing.

O: Check the cause of the file I/O error and correct the error.

In the case of a lock segments shortage, re-evaluate the number of record lock segments specified during construction of the OS system.

Action

If a memory shortage occurred, the memory must be re-estimated.

KFPS01202-E L

Failure to write to aaaa(xx....xx) log file. element file: bb....bb, system A/B: c, reason code=dddd-ee

The system failed to write data into log file aaaa(xx....xx). Data cannot be written into a file.

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

bb....bb: System log file name

c: File version:

a: A

b: B

dddd: Reason code:

209: I/O error occurred.

226: Shortage of disk space.

ee: HiRDB internal code

S: Shuts down the file that failed and continues processing.

Action

Take one of the following actions:

When the reason code is 209:
Check for the cause of the I/O error in the file, eliminate the cause of the error, and then reallocate the file to HiRDB.

When the reason code is 226:
Take one of the following actions:
Move the files HiRDB does not use from the disk with the memory shortage to another disk, or delete the files.
In UNIX, use character special files.
Specify the -i option in the pdfmkfs command and create a HiRDB file system area.
Replace the hard disk with a larger capacity disk, and then recover the HiRDB file system areas from backup files.

KFPS01203-E L

Failure to read from aaaa(xx....xx) log file. element file: bb....bb, system A/B: c, reason code=dddd-ee

An attempt to read the aaaa(xx....xx) log file failed. The file cannot be read.

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

bb....bb: System log file name

c: File version:

a: A

b: B

dddd: Reason code:

209: I/O error occurred.

ee: HiRDB internal code

S: Ignores the error and resumes processing.

O: Check the cause of the file I/O error, correct the error, then reallocate the file in HiRDB.

KFPS01204-E L

Error occurred while handling log element file of aaaa(xx....xx) log file. reason code=bbbb-cc

An error occurred while processing log file aaaa(xx....xx) {open|close|read|write}.

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

bbbb: Reason code:

101: Memory shortage occurred.

103: Network error occurred.

105: A time-out occurred during communication or file I/O processing.

cc: HiRDB internal code

S: Terminates processing.

Action

When the reason code is 101:
Re-estimate the amount of required memory.

When the reason code is 103:
Check for the cause of the network error, and then take appropriate action. Restart HiRDB.

When the reason code is 105:
Check the status of the network or system. Reduce the load placed on the system. If a hardware error message is output to the disk that created the system log files, check the status of that disk.
Alternatively, restart HiRDB.

KFPS01205-E L

Failure to concurrent access aaaa(xx....xx) log file. element file: bb....bb, system A/B: c, reason code=dddd-ee

An error occurred while concurrently accessing (opening) log file aaaa(xx....xx).

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

bb....bb: File group name

c: File version:

a: A

b: B

dddd: Reason code:

101: Memory shortage occurred.

207: Number of open files exceeded the maximum.

208: There is no access privilege.

209: I/O error occurred when a log file created in the HiRDB file system was accessed.

210: File initialization version is invalid.

ee: HiRDB internal code

S: Stops HiRDB.

Action

Take action appropriate to the reason code, as listed below.

Reason code
Meaning
Action

101
There is a memory shortage.
Re-estimate the amount of memory required. Add real memory if necessary.

207
The number of open files exceeded the maximum.
For HP-UX, use the sam command to change the value of the nfile operating system parameter.
For Solaris, use the limit or ulimit command to change the maximum file descriptor count, rebuild the system, and then re-execute.
For Linux, wait for the other processes to terminate, and then re-execute.

208
User has no access privilege.
Re-evaluate your file access privileges.
For Windows, if this error occurred in an area using the raw I/O facility, check if a formatted disk was specified.

209
An I/O error occurred when accessing the system log file.
Take action according to errno of the KFPO00107-E message output immediately before this message.

210
Initialization version of the system log file is invalid.
Check the absolute path name of the system log file. When downgrading the initialization version, normally terminate HiRDB, re-create the system log file, and then start HiRDB.

214
A shortage of file lock segments occurred.
For HP-UX, use the sam command to change the value of the nflocks operating system parameter.
For other than HP-UX, wait for other processes that are using locks to terminate, and then re-execute.

KFPS01206-E E+L

Unable to open aaaa(bb....bb) log file because file record size is unavailable. element file: cc....cc, system A/B: d, record size=eeee, pd_log_rec_leng=ffff

The record length for a system log file is inconsistent with the value specified in the pd_log_rec_leng operand; the system log file cannot be opened.

aaaa: Type of log file:

sys: System log file

bb....bb: Server name

cc....cc: File group name of the system log file

d: System in which the error occurred

eeee: Record length for the system log file (in bytes)

ffff: Value of the pd_log_rec_leng operand

S: Resumes processing.

O: Make the record length for the system log file equal to the value specified in the pd_log_rec_leng operand. For details on how to change the record length for a system log file, see the HiRDB Version 9 System Operation Guide.

KFPS01207-E E

HiRDB file system area sector size, record size or record count is invalid. reason code=aaaa, HiRDB file system area sector size=bb....bb, valid record size range=cc....cc

The sector length of the HiRDB file system, a specified record length, or a specified record count is invalid.

aaaa: Reason code

bb....bb: Sector length of HiRDB file system area (bytes)

cc....cc: Displays the range of specifiable record counts in a minimum to maximum format

For a reason code 1611 or 1612, this code displays a ***

S: Terminates processing.

O: Take an action given in the Operator's action column appropriate to the reason code, as listed in the table below.

Action

Take an action given in the HiRDB Administrator's action column appropriate to the reason code, as listed in the following table:

Reason code
Meaning
Operator's action
HiRDB administrator's action

1604
The value specified in the -n option of the pdloginit command is outside the range indicated by cc....cc.
Check the values specified in the -l and -n options of the pdloginit command.
Re-execute the pdloginit command according to the HiRDB administrator's instructions.
Check the value specified in the pd_large_file_use operand, and review the values specified in the -l and -n options of the pdloginit command.

1611
The sector length of the HiRDB file system area is greater than 4,096 bytes. The HiRDB file cannot be created in the specified HiRDB file system area.
Re-execute the pdloginit command according to the HiRDB administrator's instructions.
Re-create the HiRDB file system area on a hard disk or partition whose sector length does not exceed 4,096 bytes.

1612
The value specified in the -l option of the pdloginit command is smaller than the sector length of the HiRDB file system area.
Re-execute the pdloginit command according to the HiRDB administrator's instructions.
Check and, if necessary, change the sector length of the HiRDB file system area and the value specified in the -l option of the pdloginit command.

KFPS01211-I L

aa....aa log file group unload start. server=bb....bb:gen no=cc....cc

Unloading of system log file aa....aa of server bb....bb by the automatic log unloading facility is starting.

aa....aa: File group name of the system log file

bb....bb: HiRDB server name

cc....cc: Generation number of the system log file

S: Continues processing.

KFPS01212-I L

aa....aa log file group unload completed. server=bb....bb:unload log file name=cc....cc

Unloading of system log file aa....aa of server bb....bb by the automatic log unloading facility has been completed. The name of the created unload log file is cc....cc.

aa....aa: File group name of the system log file

bb....bb: HiRDB server name

cc....cc: Unload log file name

If the name of the unload log file exceeds 138 characters, the last 138 characters of the unload log file name are output.

S: Continues processing.

KFPS01213-W L

aa....aa log file group already unloaded. Change log file group status to be unloaded.server=bb....bb:gen no=cc....cc

An attempt was made to unload system log file aa....aa automatically, but the file had already been unloaded. The status of system log file aa....aa has been changed to unloaded.

aa....aa: File group name of the system log file

bb....bb: HiRDB server name

cc....cc: Generation number of the system log file

S: Continues processing.

KFPS01215-I L

File group bb....bb of aaaa(xx....xx) log opened

bb....bb of log aaaa(xx....xx) was opened.
A log group was opened.

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

bb....bb: Name of the opened file group

KFPS01216-I L

File group bb....bb of aaaa(xx....xx) log closed

bb....bb of log aaaa(xx....xx) was closed.
A log group was closed.

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

bb....bb: Name of the closed file group

KFPS01217-I L

File group bb....bb of aaaa(xx....xx) log became available

Log file (bb....bb) of aaaa(xx....xx) is now usable by HiRDB.

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

bb....bb: Name of the usable log file group

KFPS01218-I L

File group bb....bb of aaaa(xx....xx) log became unavailable

Log file bb....bb of aaaa(xx....xx) is no longer usable by HiRDB.

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

bb....bb: Name of the log file group that is no longer usable

KFPS01220-E L

Request to swap aaaa(xx....xx) log file unable to be executed because there is no standby log file group available

A request to swap the aaaa(xx....xx) log file was issued, but no swappable system log file was found. Reasons no swappable system log files were found:

There is no standby log file.

A standby file group is on one of the following statuses:

Waiting for unload

Cannot overwrite (now acquiring synchronization point dump corresponding to the applicable log file)

Reading data for HiRDB recovery

Being used for command processing

Waiting for extraction of data linkage information by the HiRDB Datareplicator

Overwriting denied for online reorganization

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

S: Terminates the system.

Action

Take one of the following actions:

Place the log file on usable status, or add a log file.

Unload the log file.

If there is a reserved file, make it available in the online mode, then swap the files.

Increase the number of log files.
For details, see the restarting procedures under When a HiRDB (unit) terminates abnormally due to a system log file shortage in the HiRDB Version 9 System Operation Guide.

KFPS01221-I L

aaaaaaaa assigned as current file group of bbbb(xx....xx) log file. generation number=cc....cc, first block number=dd....dd

Log file group aaaaaaaa has been assigned as the current log file for HiRDB server bbbb(xx....xx).

aaaaaaaa: Name of the assigned log file group

bbbb: Type of log file:

sys: System log file

xx....xx: HiRDB server name

cc....cc: Log generation number

dd....dd: First log block number in file

KFPS01222-I L

aa....aa released from bbbb(xx....xx) log file. generation number=cc....cc, first block number=dd....dd, last block number=ee....ee

The bbbb(xx....xx) system log file is no longer current.

aa....aa: File group name of the system log file that is no longer current

bbbb: Type of log file:

sys: System log file

xx....xx: HiRDB server name

cc....cc: Log generation number

dd....dd: First log block number in file

ee....ee: Last log block number in file (0 means that no log item has been output)

KFPS01223-E L

Error occurred during aaaa(xx....xx) log swap processing. reason code=bbbb

An error occurred while swapping log file aaaa(xx....xx).

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

bbbb: Reason code:

101: Memory shortage occurred

103: Network error occurred; possible causes are as follows:

Error in hardware, such as Ethernet board or cable

Invalid network definition

Target node is not active, or HiRDB is not running at that node

Target process is not executing

105: Timeout error occurred

S: Terminates the system.

Action

Reason code 101
Ensure that the memory estimate is correct.

Reason code 103
Perform the following:
Use an operating system command to check the connection status of the server machine.
Use a HiRDB command to check the run status of each server.

Reason code 105
Perform the following:
Reduce the system load.
If a hardware failure message was output on the disk where the system log file was created, check the disk status.
Determine whether the value specified in the pd_log_swap_timeout operand is too small, and, if necessary, increase the value.

KFPS01224-I L

aaaa(xx....xx) log does not have standby file group available for next swapping

aaaa(xx....xx) does not have a swappable file group for the next swapping; a swappable log file group needs to be provided.

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

O: Unload any log file group that has not been unloaded. If there is no such log file group but there is a reserve file group, open the reserve file group.

KFPS01225-I L

Request to swap aaa(xx....xx) log occurred, but no standby file group available. system opened file groups having been closed to get available standby

The system needs to swap system log file aaa(xx....xx) but no file group is standing by as a swappable target. The system is looking for a reserve status file group as a swappable target.

aaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

S: Continues processing.

KFPS01226-E L

bb....bb file group of aaaa(xx....xx) log opened but unable to be assigned as current file group; now closing

Log file bb....bb of aaaa(xx....xx) was opened, but it was closed again because this log file cannot be assigned as the current file.
A closed file was opened, but it was closed again because its log file group has not been unloaded and cannot be used as the current file.

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

bb....bb: Name of opened log file group

S: Closes log file bb....bb and resumes processing.

KFPS01227-W E+L

aaaa (bb....bb) log does not have standby file group available for next swapping; stop datareplication and continues swapping

Swapping failed because aaaa(bb....bb) file was on HiRDB Datareplicator extracting status. The system terminates HiRDB Datareplicator linkage and continues swapping of log files because pd_log_rpl_no_standby_file_opr=continue is specified.

aaaa: Type of log file:

sys: System log file

bb....bb: HiRDB server name

S: Resumes processing.

O: HiRDB Datareplicator was terminated forcibly. To restart HiRDB Datareplicator linkage, the target database must be re-created. For details about what action to take, see the HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide.

Action

Referring to the HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide, restart data linkage. To restart data linkage, you must re-create the database on the reflection side.

KFPS01228-W L

Error occurred aaaa(bb....bb) log for waiting syncpoint acquisition opportunities. reason code=cccc

When the pdlogswap or pdlogsync command was executed with the -w option specified, validation of a synchronization point dump was not completed within the monitoring interval time.

aaaa: Type of log file:

sys: System log file

bb....bb: Server name

cccc: Reason code:

105: Timeout occurred while waiting for validation of synchronization point dump during execution of pdlogswap command with the -w option specified.

S: Resumes processing

O: Re-execute the pdlogswap command after taking appropriate action as described below. If the same event recurs when the pdlogswap command is executed or none of the events listed below applies, contact the customer support center.

Action

Check whether there is a transaction that is taking a long time to execute.

Time-consuming transaction present:

Transaction cannot be cancelled:

Wait until the transaction terminates. After confirming that the synchronization point can be enabled, re-execute either the pdlogswap or pdlogsync command.

To allow the synchronization point to be held until the current transaction terminates, specify a large enough value in the -t option and then re-execute either the pdlogswap or pdlogsync command.

Transaction can be cancelled:

Cancel the transaction and re-execute either the pdlogswap or pdlogsync command.

No time-consuming transactions present:

Re-execute either the pdlogswap or pdlogsync command.

KFPS01229-I L

Next aa....aa log file restart point, generation number=bb....bb, block number=cc....cc. restart end point, generation number=dd....dd, block number=ee....ee. last acquired syncpoint dump ffff/gg/hh ii:jj:kk

Displays the system log input starting position, the system log input termination position, and the date and time when the synchronization point dump was last enabled for the next restarting of server name aa....aa.
If an error occurs in the synchronization point dump file or status file before the server is restarted, the system log input starting position indicated in this message may differ from the position at which the system log is actually input.

aa....aa: Server name

bb....bb: System log generation number that will be the input starting position#¹

cc....cc: System log block number that will be the input starting position#¹

dd....dd: System log generation number that will be the input termination position#¹

ee....ee: System log block number that will be the input termination position#¹

ffff/gg/hh: Date the current synchronization point was enabled#²

ii:jj:kk: Time the current synchronization point was enabled#²

#1: If the value to be displayed in the generation number or block number cannot be determined, the system displays the symbol *******.

#2: If an enabling date cannot be determined, the symbol ****/**/** is displayed; if an enabling time cannot be displayed, the symbol **:**:** is displayed.

S: Resumes processing.

O: If the server cannot be restarted unless a system log file is added, or when determining the number of system log files to be added, or when determining an approximate length of time required to restart the server next time, see both output information about this message and the execution results of the pdlogls command. If the generation number and block number of this message display ********, refer to the message output during the previous unit shutdown. For HiRDB/Single Server, this message is output to the message log file and the event log (in UNIX, syslogfile). For HiRDB/Parallel Server, the output target differs depending on the condition. The conditions and output targets are listed below.

Condition
Message output target

Unit terminated abnormally

Failure at server startup

Failure at server shutdown

Messages are output to the message log file and the event log (in UNIX, syslogfile) of the unit where the system manager resides. However, if a communication error occurs between the unit (or server) and the unit where the system manager resides, or if the unit where the system manager resides is stopped, messages will be output to the event log (in UNIX, syslogfile) of the affected unit.

Unit terminated forcibly

Server terminated forcibly

Messages will be output to the event log (in UNIX, syslogfile) of the affected unit.

KFPS01230-E E+L

Unable to read log file reason=(aaaa, bbbbbbbb)

The system was unable to execute HiRDB Datareplicator log input processing.

aaaa: Reason code

bbbbbbbb: Detail code

The detail codes and operator's actions for reason code aaaa are listed in the table below.

S: Terminates processing.

O: Take action appropriate to the reason code and detail code, as shown below:

Reason code
Detail code
Explanation
Operator's action

101
Size to be allocated
Memory shortage occurred.
Check the number of processes, take appropriate action, then re-execute.

203
Error code for HiRDB file system
Log file open error or read error occurred.
See 5.1 Error codes returned from HiRDB file system access requests to determine the cause of the error. If the displayed detail code is not found in the list of error cause codes, contact the customer support center.

212
0
Access to all files failed except for the one at the input startup point.
Execute the pdlogls command to determine the cause of the error on the basis of the result.

405
101
Memory shortage occurred during definition analysis.
Re-execute after the current process has terminated. If a system call error message was output immediately before this message, take action appropriate to that message.

403
Open error occurred in a definition file.
Check the cause of the error on the basis of the definition file open error message that was output immediately before this message.

404
Open error occurred in an analysis file.
Check the cause of the error on the basis of the analysis file open error message that was output immediately before this message.

405
Error was detected during analysis processing.
Check the cause of the error on the basis of the analysis error message that was output immediately before this message.

414
The number of valid log file groups was 0.
Correct the pdlogadfg and pdlogadpf operands in the corresponding server definition and re-execute.

410
0
File group names of the system log file were duplicated.
Correct the pdlogadfg and pdlogadpf operands in the corresponding server definition and re-execute.

413
0
The maximum file group count of the system log file was exceeded.
Correct the pdlogadfg and pdlogadpf operands in the corresponding server definition and re-execute.

1602
Block number
A missing block was detected in the log file.
The log file may have been overwritten. Check the cause.

1653
0
Log input location is invalid.
Check the contents of the definition file.
If there is no error in the definition file, check that there was a file at the input startup point output by the pdls -d rpl -j command and that the file is accessible.
If the file exists and is accessible, enter the pdls -d rpl -j and pdlogls -d sys commands. HiRDB Datareplicator linkage cannot be established unless the system log displayed by the pdls command as being extracted is not listed under the log block output status of all system log files displayed by the pdlogls command. Take an appropriate action according to the system administrator's instructions so that HiRDB Data-replicator linkage can be restarted. If the system log displayed by the pdls command as being extracted is listed under the log block output status of all system log files displayed by the pdlogls command, contact the customer support center.

Action

Terminate HiRDB Datareplicator linkage, if it is in effect. To restart HiRDB Datareplicator linkage, the target database must be re-created. For details about what action to take, see the HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide.

However, if reason code 203 was output, the system log file may temporarily have been unreferenceable. See the KFPS01231-W or KFPO00107-E message output immediately before, correct the temporary device busy or other problem with the disk that stores the system log file so that it can be referenced, and restart the HiRDB Datareplicator.

KFPS01231-W E+L+R

Error occurred while reading log element file, file group=aa....aa, system A/B: b, reason=(cccc,dd....dd)

Error occurred while reading a file for system b in log file group aa....aa.

aa....aa: Name of log file group

b: System where the error occurred:

a: System A

b: System B

cccc: Reason code

dd....dd: Detail code

The detail codes and operator's actions for reason code cccc are listed in the table below.

S: Terminates processing.

O: Take action appropriate to the reason code and detail code, as shown below:

Reason code | Detail code | Explanation | Operator's action
213 | HiRDB file system error code | Log file open error occurred. | See 5.1 Error codes returned from HiRDB file system access requests to determine the cause of the error. If the displayed detail code is not found in the list of error cause codes, contact the customer support center.
215 | HiRDB system error code | Log file read error occurred.
1602 | Log block number | A missing block was detected in the log file. | The log file may have been overwritten. Check the cause.

KFPS01232-E E+L

Datareplication stopped for aaaa(bb....bb); reason code=cccc, continues processing.

Log service aaaa(bb....bb) can no longer output data linkage information for reason cccc, but HiRDB operation will be continued as is.

aaaa: Type of log file:

sys: System log file

bb....bb: HiRDB server name

cccc: Reason code indicating the nature of the error:

115: Cancellation of HiRDB Datareplicator extraction processing was detected

212: File for data linkage was not found

S: Resumes processing.

O: HiRDB Datareplicator linkage has been terminated forcibly. Take appropriate action based on the HiRDB Version 9 System Operation Guide and the HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide.

Action

To re-execute HiRDB Datareplicator linkage, the target database must be re-created.

Referring to the HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide, return the HiRDB Datareplicator linkage to a state in which it can once again be restarted. Then, either enter the pdrplstart command or, after confirming that pd_rpl_init_start=Y is set in the system common definition (pdsys under PDCONFPATH), start HiRDB normally, and then restart HiRDB Datareplicator.

KFPS01233-E E+L

HiRDB Datareplicator access communication file for aaaa(bb....bb) is invalid; continues processing. reason code=cccc

An error was detected by HiRDB Datareplicator in the file for data linkage. HiRDB operation will be continued, but data can no longer be linked by HiRDB Datareplicator.

aaaa: Type of log file:

sys: System log file

bb....bb: HiRDB server name

cccc: Maintenance information

S: Continues processing without changing the system log file's HiRDB Datareplicator extraction-completed or extracting status.

O: Enter the pdls -d rpl command to determine whether or not HiRDB is writing data linkage information. If HiRDB is writing data linkage information, data can no longer be linked using HiRDB Datareplicator. Enter the pdrplstop command to terminate HiRDB Datareplicator linkage. Also, terminate both HiRDB Datareplicators at the data extraction source and target.

Action

To re-execute HiRDB Datareplicator linkage, the target database must be re-created.

Referring to the HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide, return the HiRDB Datareplicator linkage to a state in which it can once again be restarted. Then, either enter the pdrplstart command or, after confirming that pd_rpl_init_start=Y is set in the system common definition (pdsys under PDCONFPATH), start HiRDB normally, and then restart HiRDB Datareplicator.

KFPS01234-I L

No extract database in aa....aa.

Server aa....aa contains no database subject to data extraction by HiRDB Datareplicator. The system will no longer manage the system log file's extraction status (extraction-completed/extracting status) at this HiRDB server.

aa....aa: HiRDB server name

S: Continues system operation, removing the HiRDB Datareplicator extraction-completed/extracting status in the system log file at this HiRDB server.

O: There is no problem if there is no database subject to data linkage at this HiRDB server. If the extraction system definition or extraction definition for HiRDB Datareplicator is invalid, data linkage cannot be continued. Execute the pdrplstop command to terminate HiRDB Datareplicator linkage. Also, terminate both HiRDB Datareplicators at the data extraction source and target.

Action

To re-execute HiRDB Datareplicator linkage, the target database must be re-created.

If a HiRDB Datareplicator extraction system definition or extraction definition is invalid, referring to the HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide, correct the invalid definition, and return the HiRDB Datareplicator linkage to a state in which it can once again be restarted. Then, either enter the pdrplstart command or, after confirming that pd_rpl_init_start=Y is set in the system common definition (pdsys under PDCONFPATH), start HiRDB normally, and then restart HiRDB Datareplicator.

KFPS01235-E E+R+L

Log file generation may be skipping between log file group aa....aa (cc....cc, dd....dd) and bb....bb (ee....ee, ff....ff)

The file group of the read system log files was switched from aa....aa to bb....bb by data extraction, but a system log file generation skipping error may have occurred during that time.

aa....aa: File group name of the previous system log file that was read

bb....bb: File group name of the system log file that was read

cc....cc: Run ID of aa....aa (hexadecimal)

dd....dd: Generation number of aa....aa (hexadecimal)

ee....ee: Run ID of bb....bb (hexadecimal)

ff....ff: Generation number of bb....bb (hexadecimal)

S: Continues processing.

O: A mismatch may have occurred between the extracted database and the target database. Use the pdhold command to put the extracted database in reference-possible backup hold status. Then, perform the target process up to the newest data and check for mismatches between the extracted database and the target database.

If there are no mismatches
Resume updating of the extracted database. HiRDB Datareplicator linkage can continue.

If there are mismatches
You must synchronize, and then initialize the data linkage environment between the extracted database and the target database. For details about how to handle a mismatch between databases, see the HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide.

If the unit stops during normal startup and this message is output when no disk error occurred in the system log file, no mismatches occur between the databases.

KFPS01240-E L

Element file aa....aa unable to be used as bbbb(xx....xx) log file. file group: cc....cc, system A/B: d, reason code=eeee

A file was found that cannot be used as a log file.

aa....aa: Name of the system log file where the error occurred

bbbb: Type of log file:

sys: System log file

xx....xx: HiRDB server name

cc....cc: Name of log file group resulting in the error

d: File version:

a: A

b: B

eeee: Reason code

The table below lists the reason codes and actions to be taken.

S: Releases this file and resumes processing.

O: Take action appropriate to the reason code, as listed below:

Reason code
Explanation
Operator's action
HiRDB Administrator's action

223
File is too small to collect the maximum amount of defined record data.
Obtain the estimated file size from the HiRDB administrator and determine whether or not the size is correct. If the file size is incorrect, re-create the file at the correct size.
Check the definition to determine whether or not the maximum record data length is correct. If it is incorrect, re-estimate the file size and change the definition. If the maximum record data length is correct, instruct the operator to re-create the file at the estimated size.

601
File failed to open.
Take appropriate action according to the KFPS01200-E or KFPS01203-E message that was output immediately before this message.
--

602
Management information in the file failed to be read.

603
Management information is damaged in the file.
Initialize this file.

604
The HiRDB identifier recorded in the system log file is different from the HiRDB definition. Files of another system might also be corrupted.
Check with the HiRDB administrator as to whether the file can be used with this system. If the file can be used with this system, initialize it.
Check the file as to whether or not it is used with another system. If it is used with another system, change the definition so that this file will not be used with this system.

605
File configuration in the file is different from that of the current file configuration; the file configuration may have been changed.
Check with the HiRDB administrator as to whether or not the file configuration has been changed. If it has not been changed, initialize this file.
Check the definition and determine whether or not the log file group and element file using the corresponding file have been changed. If the file configuration has been changed, change it to the initial configuration in the definition.

606
File is the current file.
An error may have occurred in this file during the previous session. Unload the log information, then change the file status or initialize the file.
--

If other than the above, contact the HiRDB administrator.
If a unit shuts down between the time that it is made primary and startup processing finishes, the header information might not be written correctly before close processing.
If not performing recovery using the system log, use the pdlogchg command to change the status.
If performing recovery using the system log, use the pdlogunld command to unload, and then use the pdlogchg command to change the status.

--: Not applicable

Note

Use the following procedure to initialize a file:

Delete the file with the pdlogrm command.

Re-create the file with the pdloginit command.

To change the file status, use the pdlogchg command; to unload log information, use the pdlogunld command.

KFPS01250-I L

aaaa(xx....xx) log file group bb....bb is not unloaded; unload.

Log file group bb....bb of aaaa (xx....xx) has not been unloaded. Or, log information has not been unloaded from this log file group; unload the log information (otherwise, this log file group cannot be swapped).

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

bb....bb: Name of the log file group whose log information has not been unloaded

S: Resumes log server process startup.

O: Enter the pdlogunld command to unload the log information.

KFPS01251-I L

aaaa(xx....xx) log file group bb....bb is in invalid state; change file group state.

The status of log file group bb....bb of aaaa(xx....xx) is invalid. Correct the file group's status.
The status of this log file group is invalid, because an error occurred during the previous online session. Log information cannot be collected unless the status is changed. Either unload the log information or change the file group status.

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

bb....bb: Name of the log file group on invalid status

S: Resumes log server process startup.

O: Either enter the pdlogunld command to unload the log information or enter the pdlogchg command to change the file group status.

KFPS01252-I L

aaaa(bb....bb) log file group cc....cc is not extracted; extract.

Extraction by HiRDB Datareplicator of aaaa(bb....bb) with log file group cc....cc has not been completed. Use HiRDB Datareplicator to extract the system log. This log file group cannot be subject to swapping unless system log extraction is completed.

aaaa: Type of log file:

sys: System log file

bb....bb: HiRDB server name

cc....cc: Name of log file group whose extraction by HiRDB Datareplicator has not been completed

S: Resumes processing.

O: If HiRDB Datareplicator is not active, start it and extract the system log.

KFPS01253-I L

aaa(bb....bb) log file group cc....cc not reflected by Online DB Reorganization; retry Online DB Reorganization or cancel Online DB Reorganization

The file group of the aaa(bb....bb) system log file did not terminate that online reorganization discrepancy application that was using the update log.

aaa: Type of log file:

sys: System log file

bb....bb: HiRDB server name

cc....cc: File group name of the system log file

S: Continues processing.

Action

Perform one of the following actions:

Execute the pdorend command to continue online reorganization discrepancy application processing.

Execute the pdorbegin -u or pdorend -u command to suspend updatable online reorganization.

KFPS01255-W L

Number of available file groups of aaaa(xx....xx) log is insufficient; open log file groups.

The number of log file groups for aaaa(xx....xx) is less than the required minimum. Open more log file groups.
If operation is continued, the destination of log information cannot be changed in the future, because the number of available log file groups is less than the required value. Open more log file groups immediately.

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

S: Resumes processing.

O: Enter the pdlogopen command to open file groups.

KFPS01256-E L

No standby file groups of aaaa(xx....xx) log are available.

There are no log file groups available for aaaa(xx....xx).
The current log file group cannot be selected, because there is no available log file group for the destination of log information.

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

S: Outputs message KFPS01113-E and cancels log server process startup processing.

O: Eliminate the cause of this error so that the current file group cannot be selected.

KFPS01257-E L

Unable to restore current aaa(xx....xx) log file group.

For a transaction execution site, or if Real Time SAN Replication with the log-only synchronous method is not used, all files in use when the system was previously online are initialized, and the current log file group cannot be recovered.
For a log application site, all system log files are initialized, and log applications cannot be started.

aaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

S: Outputs a KFPS01113-E message, and stops HiRDB restart processing.

O: Take the following actions:

For a transaction execution site, or if Real Time SAN Replication with the log-only synchronous method is not used
Execute forced normal startup of HiRDB and recover the database.

For a log application site
After completing the preparation for log application, start the log application site.

KFPS01258-W L

Unable to swap current aaaa(xx....xx) log file group for a standby file group because no standby is available; ignores "rerun swap" and continues processing.

Because there are no files that can be the target of a swap, the system log file represented by aaaa(xx....xx) is not swapped.

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

S: Determine whether there are system log files in unload wait status. If so, unload them.

KFPS01260-E L

Log generation file for system recovery not found; stops recovery processing. type: aaaa(xx....xx)

Recovery processing was cancelled, because there was no log generation file subject to system recovery.

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

S: Terminates the system.

Action

Refer to the KFPS01240-E message in order to check the cause of the error.

KFPS01261-E L

Error occurred while reading log blocks; stos recovery processing. type: aaaa(xx....xx)

Recovery processing was cancelled, because an error occurred while reading the log.

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name
S: Terminates the system.

Action

Refer to the following messages that are output immediately after this message to check the cause of the error:

KFPS01180-E

KFPS01181-E

KFPS01183-E

KFPS01184-E

KFPS01262-I L

Log block reading started. type:aaaa(xx....xx), read start point: bb....bb,cc....cc,dd....dd

Log read operation has started.

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

bb....bb: First file group name that was read

cc....cc: First generation number that was read

dd....dd: First block number that was read

KFPS01263-I L

Log block reading completed. type: aaaa(xx....xx), read end point: bb....bb,cc....cc,dd....dd

Log read operation is completed (log was read during system recovery).

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

bb....bb: Last file group name that was read

cc....cc: Last generation number that was read

dd....dd: Last block number that was read

Note

If no log block was read, ********,********,******** is displayed for bb....bb,cc....cc,dd....dd.

KFPS01264-E L

Error occurred during inter-system adjustment for duplicated log files. type: aaaa(xx....x)

An error occurred during inter-system adjustment for dual log files at the time of HiRDB recovery.
When dual log files are used, an error occurs in the last location of the log between file versions A and B depending on the HiRDB termination timing. Inter-system adjustment is performed to adjust such an error during HiRDB restart.

aaaa: Type of log file:

sys: System log file

xx....xx: HiRDB server name

S: Resumes processing.

O: Check the cause of the error on the basis of the following messages:

KFPS01202-E

KFPS01203-E

KFPS01265-I L

Log block reading started for database recovery. type: aaaa(bb....bb), read start point: cc....cc,dd....dd,ee....ee

Log read processing for database recovery has been started.

aaaa: Type of log file:

sys: System log file

bb....bb: HiRDB server name

cc....cc: Name of the first file group to be read

dd....dd: Number of the first generation to be read

ee....ee: Number of the first block to be read

S: Resumes processing.

KFPS01266-I L

Log block reading completed for database recovery. type: aaaa(bb....bb), read end point: cc....cc,dd....dd,ee....ee

Log read processing for database recovery has been completed.

aaaa: Type of log file:

sys: System log file

bb....bb: HiRDB server name

cc....cc: Name of the last file group read

dd....dd: Number of the last generation read

ee....ee: Number of the last block read

Note

If no log block was read, **..** is displayed for bb....bb, cc....cc, and ee....ee.

S: Resumes processing.

KFPS01267-E E+L

Error occurred while database recovery for aaa(bb....bb). reason code=(cc....cc, dd....dd)

An error occurred in database recovery during restart, or in the preparation for log application processing.

aaa: Type of log file:

sys: System log file

bb....bb: HiRDB server name

cc....cc: Reason code

dd....dd: Maintenance information

S: Terminates abnormally.

O: See the following table and take action.

Action

Take action appropriate to the reason code listed below.

If a reason code not in the list is output, contact the customer support center.

Reason code
Explanation
Operator's action
HiRDB Administrator's action

107
Error occurred during message queue processing.
Contact the HiRDB administrator.
Contact the customer support center.

114
Error was detected during message queue processing.
Run again.
If the error recurs, contact the customer support center.

209
I/O error occurred in the log file being input.
Contact the HiRDB administrator.
If this reason code is output, or a KFPS01203-E message was output before this message, investigate the cause.

213
A closed file was found in the log file being input.

214
A shutdown file was found in the log file being input.

215
A file that cannot be input was found in the log file being input.

550
After a transaction execution site terminated with a status other than normal, it was started using the pdstart dbdestroy command or the pdstart -i command, so the integrity of the log application site database cannot be guaranteed.
Contact the HiRDB administrator.
For a transaction execution site, or if Real Time SAN Replication with the log-only synchronous method is not used:
Collect the following data, and contact the customer support center:

HiRDB system definition file

Files under %PDDIR%\spool

Event log (in UNIX, syslogfile)

For a log application site:
After executing preparation for log application, restart the log application site.

711
A log file generation was skipped.
Check the log file definition to make sure that changes were made correctly.
If there is no error in the log file definition, collect the following data, and contact the customer support center:

HiRDB system definition file

Files under %PDDIR%\spool

System log file of the relevant HiRDB server, or system log file backup file (collected using the pdfbkup command)

Status file of the relevant HiRDB server, or status file backup file (collected using the pdfbkup command)

Event log (in UNIX, syslogfile)

1001
No log file exists at the input start position.
Contact the HiRDB administrator.
If Real Time SAN Replication with the log-only synchronous method is not used, or for a transaction execution site when Real Time SAN Replication with the log-only synchronous method is used:
Determine whether the log file definition was mistakenly changed. Also, confirm that the system log file was not initialized. If the system log file was initialized and HiRDB cannot be restarted, see the section on measures to be taken when HiRDB cannot be restarted due to an error in the current file of both systems in the manual HiRDB Version 9 System Operation Guide.
If the above actions cannot resolve the problem, collect the following data, and contact the customer support center:

HiRDB system definition file

Files under %PDDIR%\spool

System log file of the relevant HiRDB server, or system log file backup file (collected using the pdfbkup command)

Status file of the relevant HiRDB server, or status file backup file (collected using the pdfbkup command)

Event log (in UNIX, syslogfile)

For a log application site:
After executing preparation for log application, restart the log application site.

1602
An invalid log block was detected.
Contact the HiRDB administrator.
If Real Time SAN Replication with the log-only synchronous method is not used, or for a transaction execution site when Real Time SAN Replication with the log-only synchronous method is used:
The log file may be corrupt. Use the following procedure for recovery:
1. Collect the following data, and contact the customer support center:

HiRDB system definition file

Files under %PDDIR%\spool

System log file of the relevant HiRDB server, or system log file backup file (collected using the pdfbkup command)

Status file of the relevant HiRDB server, or status file backup file (collected using the pdfbkup command)

Event log (in UNIX, syslogfile)

2. Recover the database using a method other than restart, and start HiRDB.
For a log application site:
After executing preparation for log application, restart the log application site.

1610
A missing log block was detected.

KFPS01268-E L

Invalid log data detected while reading log. type:aa....aa(bb....bb), read point:cc....cc, dd....dd.

Invalid log data was detected while loading a system log.

aa....aa: File type:

sys: System log file

bb....bb: HiRDB server name

cc....cc: File group name of the system log file in which the invalid data was detected

dd....dd: Block number of the system log that was to be loaded

S: Terminates processing.

Action

The action to be taken differs depending on the abort code output before or after this message.

When Psjnr38 is output
Take the action recommended when Psjnr38 is output.

When Psjnr38 is not output
Save the files and system log files under %PDDIR%\spool and contact the customer support center.

KFPS01269-I L

Reading log block. type:aaaa(bb....bb), reading point:cc....cc, dd....dd, ee....ee

Reports the system log file being loaded during a HiRDB restart.

aaaa: File type:

sys: System log file

bb....bb: HiRDB server name

cc....cc: File group name of the system log file being loaded

dd....dd: Generation number of the system log being loaded

ee....ee: Block number of the system log being loaded

S: Continues processing.

KFPS01270-E E+L

Unable to use log file due to I/O error. element file: aa....aa, system A/B: b

A log file cannot be used due to an I/O error.

aaaa: Name of the system log file where the error occurred

b: Erroneous file version:

a: A

b: B

S: Resumes processing.

O: Eliminate the cause of the error and reenter the command.

Action

Refer to the message that was output immediately before this message to check the cause of the error, and correct the error.

KFPS01271-I E+L

Unloading completed. generation number=aa....aa, start block number=bb....bb, end block number=cc....cc

Unload processing is completed. Displays the range of unloaded block numbers.

aa....aa: Generation number of the log file group from which log was unloaded

bb....bb: First block number unloaded

cc....cc: Last block number unloaded

Note

If no log block was unloaded, ******** is displayed for cc....cc.

KFPS01272-E E+L

Unable to unload log file. element file: aa....aa, system A/B: b, reason code=cccc-dd

An attempt was made to unload a file group containing a system log file that cannot be unloaded.

aa....aa: Name of the system log file where the error occurred

b: Erroneous file version:

a: A

b: B

cccc: Reason code

dd: HiRDB internal code

S: Resumes processing.

O: Take action appropriate to the reason code, as listed below.

Action

Take action appropriate to the reason code, as listed below:

Reason code | Explanation | Operator's action | HiRDB Administrator's action
220 | This file is not the system log file. | -- | Re-evaluate the system log file names in the file group.
603 | The management information in the file is corrupted. | Suspend unloading of the applicable file group, and then disconnect from HiRDB. | --
605 | The configurations of the file and the definition file are different. | -- | Check if the definition related to the system log file was changed.
1603 | The system log file is in unload completed status. | Re-evaluate the file group name specified in the command.
1607 | The system log file is not used by HiRDB. | --

--: Not applicable

KFPS01273-E E+L

Unable to change log file status. element file: aa....aa, system A/B: b,reason code=cccc-dd

Cannot change the status of some system log files in the target file group.

aa....aa: Name of the system log file where the error occurred

b: Erroneous file version:

a: A

b: B

cccc: Reason code (the table below lists the reason codes and actions to be taken)

dd: HiRDB internal code

S: Resumes processing.

O: Take action appropriate to the reason code, as listed below.

Action

Take action appropriate to the reason code, as listed below:

Reason code | Explanation | Operator's action | HiRDB Administrator's action
220 | This file is not the system log file. | -- | Re-evaluate the system log file names in the file group.
603 | The management information in the file is corrupted. | Suspend unloading of the applicable file group, and then disconnect from HiRDB. | --
605 | The configurations of the file and the definition file are different. | -- | Check if the definition related to the system log file was changed.
1603 | The system log file is in unload completed status. | Re-evaluate the file group name specified in the command. | --
1607 | The system log file is not used by HiRDB.

--: Not applicable

KFPS01274-E E+L

Failure to open log element file. element file: aa....aa, system A/B: b, reason code=cccc-dd

Failed to open the system log file.

aa....aa: System log file name

b: Erroneous file version:

a: A

b: B

cccc: Reason code

dd: HiRDB internal code

S: Resumes processing.

O: Take action appropriate to the reason code, as listed below.

Action

Take action appropriate to the reason code, as listed below:

Reason code
Explanation
Operator's action
HiRDB Administrator's action

101
Memory shortage occurred.
Re-execute the command after the current process has terminated.
Re-estimate the memory size.

201
File name is invalid.
Consider the following causes:

An invalid character was specified in the path name.

The length of the HiRDB file name exceeds the maximum (30 characters).

Specify the file name correctly and re-execute the command.
--

202
HiRDB file system area name specified in the path is not an HiRDB file system area.
Check the HiRDB file system name specified in the path and re-execute the command.
Re-evaluate the specification of the pdlogadpf operand file.

203
The device specified in the path has not been initialized for the HiRDB file system.
--

207
Maximum value was exceeded when the HiRDB file system area specified in the path was opened.
--

208
User does not have access privilege for the HiRDB file system area specified in the path.
Execute the command with a user ID that has access privilege for the specified HiRDB file system area.
Modify the access privileges for the specified HiRDB file system area using OS commands (chmod, for example).

209
I/O error occurred.
Check the cause of the I/O error and take appropriate action.
--

210
HiRDB file system versions do not match.
--
Re-evaluate the specification of the pdlogadpf operand file.

211
There is no access privilege for the specified file.
Execute the command with a user ID that has access privilege for the HiRDB file system area where the specified file is stored.
Modify the access privileges for the HiRDB file system area where the specified file is stored using OS commands (chmod, for example).

212
Specified file was not found.
--
Re-evaluate the specification of the pdlogadpf operand file.

221
Lock segment shortage occurred.
Re-evaluate the number of record lock segments specified during construction of the OS system.

222
The applicable system log file is being used by another process.
Check the run status of the applicable system log file or the file group to which the file belongs, and then re-execute the command.
--

--: Not applicable

KFPS01275-E E+L

Minor error occurred while analyzing definitions for log service. file being analyzed: aaaaaaaa, record number=bbbbbbbbbb, reason code=cccc

A minor error occurred while analyzing the log file-related definitions.

aaaaaaaa: Name of definition file being analyzed

bbbbbbbbbb: Record number resulting in the error

cccc: Reason code indicating the nature of the error (the table below lists the reason codes and actions to be taken)

S: Resumes processing the log service function command.

Action

Check the log service function-related definitions.

Reason code
Explanation
Action

409
One of the following errors was found in the specification of the -g option with the pdlogadpf operand:

The -g option was not specified

The length of the system log file group name is incorrect

Correct the specification of the pdlogadpf operand, and then re-execute the command.

410
More than one pdlogadpf operand specified the same file group name.

411
One of the following errors was found in the specification of the -a option with the pdlogadpf operand:

The -a option was not specified

The file name was not specified

412
One of the following errors was found in the specification of the -b option with the pdlogadpf operand:

The -b option was not specified when duplexing

The file name was not specified

422
An error was found in the specification of the -d option with the pdlogadfg operand, or the -d option was not specified.
Stop the system if necessary, and then correct the definition content and restart.

423
An error was found in the specification of the -d option with the pdlogadpf operand, or the -d option was not specified.

KFPS01277-E L

Log point information is invalid. info=aaaa

Invalid log point information was detected.

aaaa: System maintenance information

S: Resumes processing.

O: Check the items shown below and take appropriate action:

Check that the correct backup file is specified in the pdrstr command; if it is not the correct file, specify the correct file name and re-execute the command.

Refer to both the log point information file that was re-created from the backup file with the pdrstr command and the execution result of the pdlogls command, check whether the log file recorded in the log point information file exists, and report the result to the administrator.

Action

Check the items shown below and take appropriate action:

If the log file recorded in the log point information file does not exist, check whether the log file specification in the server definitions was manipulated. If the log file that was used was removed from the definitions after that backup was made, add the file and re-execute the command.
If the above log file was deleted or the log file recorded in the log point information file was overwritten, the database cannot be recovered by specifying -L in the pdrstr command.

If neither of the above applies, contact the customer support center.

KFPS01278-W L

Failure to processing log file group. type: aaa(bb....bb), file group: cc....cc, reason code=dddd-ee

The cc....cc log file group, which is used by the bb....bb server, cannot be processed because status referencing has been disabled due to dddd.

aaa: Log type (sys or lar)

bb....bb: HiRDB server name

cc....cc: Name of file group

dddd: Reason code:

209: I/O error occurred in log file.

213: Open error occurred in log file.

215: Input is disabled for log file.

222: Another process is using this file group.

1601: Target log file does not exist.

ee: System maintenance information

S: Resumes processing and does not process the log file group.

O: If the log file is not being used, no problem exists.

During pdrstr (database recovery utility) execution:
If the log file was being used from the time the backup was made to the current time, the database may not be recovered correctly.
If the KFP01279-W message was output, consider the message contents, contact the administrator, take appropriate action, then re-execute the command.

During pdlogchg (log file status change command) execution:
When the reason code is 222:
The memory status does not match the status of the system log file itself for the log file group. Close the log file group with the pdlogcls command and then reopen it with the pdlogopen command.
For all other reason codes:
Take appropriate action for the reason code and then re-execute the command. If the KFPS01279-W message is output, correct the error that is reported by that message and then re-execute the command.

Action

If the log file is not needed for execution of the pdrstr or pdlogchg command, no problem exists. If the log file is needed for execution of the above commands, check the items shown below and take appropriate action.

If an error occurred in the log file group or the log file group was initialized after being used online, recover the log file if it is recoverable, then re-execute the command.

Check that the log file description in the server definition is correct, correct any errors, then re-execute the command.

If reason code 222 is output after the pdlogchg -z command is executed while HiRDB is active, the log file cannot be reused. Close the log file and then reopen it.

If neither of the above applies, contact the customer support center.

KFPS01279-W L

Unable to use log file. element file: aa....aa, system A/B: b, reason code=ccc-dd

The file status of the aa....aa log file cannot be referenced because of the reason indicated by cccc. The log file cannot be processed.

aa....aa: Name of log file

b: System in which the error occurred (a or b)

cccc: Reason code

dd: System maintenance information

S: Resumes processing and does not process the log file.

O: If the log file is not being used, no problem exists. If the KFPS01278-W message is not output for the file group of the log file, no problem exists. If neither of the above applies, determine the cause of the error from the reason code and contact the administrator.

Action

If the log file is not needed for execution of the pdrstr or pdlogchg command, no problem exists. If the log file is needed for execution of the above commands, check the cause from the reason code, recover the file from the information displayed in the KFPS01278-W message, then re-execute the command. Following are the reason codes:

Reason code
Explanation
Operator's action
HiRDB Administrator's action

101
Memory shortage occurred.
Re-execute the command after the current process has terminated.
Re-estimate the memory.

201
File name is invalid.
Consider the following causes:

An invalid character was specified in the path name.

The length of the HiRDB file name exceeds the maximum (30 characters).

Specify the file name correctly and re-execute the command.
--

202
HiRDB file system area name specified in the path is not an HiRDB file system area.
Check the HiRDB file system name specified in the path and re-execute the command.
Re-evaluate the file specification of the pdlogadpf operand.

203
The device specified in the path has not been initialized for the HiRDB file system.
--

207
Maximum value was exceeded when the HiRDB file system area specified in the path was opened.
--

208
User does not have access privilege for the HiRDB file system area specified in the path.
Execute the command with a user ID that has access privilege for the specified HiRDB file system area.
Modify the access privileges for the HiRDB file system area using OS commands (chmod, for example).

209
I/O error occurred.
Determine the cause of the I/O error and take appropriate action.
--

210
HiRDB file system versions do not match.
--
Re-evaluate the file specification of the pdlogadpf operand.

211
User does not have access privilege for the specified file.
Execute the command with a user ID that has access privilege for the HiRDB file system area where the specified file is stored.
Modify the access privileges for the HiRDB file system area where the specified file is stored using OS commands (chmod, for example).

212
Specified file was not found.
--
Re-evaluate the file specification of the pdlogadpf operand.

221
Lock segment shortage occurred.
Re-evaluate the number of record lock segments specified during startup of the OS system.

222
The applicable system log file is being used by another process.
Check the run status of the applicable system log file or the file group it belongs to, and then re-execute the command.
--

603
The maintenance information in the file is corrupted.
Initialize this file.

605
The file configuration of the file does not match the current file. The file configuration may have been changed.
Check with the HiRDB administrator as to whether or not the file configuration has been changed. If it has not been changed, initialize this file.
Check the definition and determine whether or not the log file group and element file using the corresponding file have been changed. If the file configuration has been changed, change it to the initial configuration in the definition.

1067
The file is not used by HiRDB.
Check the corresponding file group.
--

--: Not applicable

KFPS01280-E E+L

Unable to execute aa....aa command due to bbbb-cc

Cannot execute the aa....aa command.

aa....aa: Command name that could not be executed

bbbb: Reason code

cc: HiRDB internal code

S: Terminates command execution.

O: Take action appropriate to the reason code and re-execute the command, if necessary.

Action

Take action appropriate to the reason code, as listed below:

Reason code
Explanation
Operator's action
HiRDB Administrator's action

101
Memory shortage occurred.
Re-execute the command after the current process has terminated (if a system call message has been issued immediately before this message, take action appropriate to that message).
If one of the following commands was executed while HiRDB was active, also take the action called for:

pdlogchg command
Mismatch between the memory status and the system log file's status may have occurred. Close the file group with the pdlogcls command and then reopen it with the pdlogopen command. If the file group is on unload wait status at this point, re-execute the pdlogchg command.

pdlogunld command
If the KFPS01271-I message is output immediately after this reason code, the unload log file has been created normally. However, a mismatch between the memory status and the system log file's status has occurred. Close the file group with the pdlogcls command and then reopen it with the pdlogopen command. If the KFPS01271-I message is not output, re-execute the pdlogunld command.

Re-estimate the memory.

102
The shared memory library service function cannot be provided, because the number of shared memory segments attached to the read process would exceed the permitted maximum.
If a system call message has been issued immediately before this message, take action appropriate to that message.
Re-estimate the shared memory.

103
Network error occurred; possible causes are as follows:

Error in hardware, such as Ethernet board or cable

Invalid network definition

Target process is not executing

Check the cause of the error using the procedure described below and take appropriate action:

Check the server machine connection status with the applicable OS command.

Check the execution status of each server with the applicable HiRDB command.

If one of the following commands was executed while HiRDB was active, also take the action called for:

pdlogchg command
A mismatch between the memory status and the system log file's status may have occurred. Close the file group with the pdlogcls command and then reopen it with the pdlogopen command. If the file group is on unload wait status at this point, re-execute the pdlogchg command.

pdlogunld command
If the KFPS01271-I message is output immediately after this reason code, the unload log file has been created normally. However, a mismatch between the memory status and the system log file's status has occurred. Close the file group with the pdlogcls command and then reopen it with the pdlogopen command. If the KFPS01271-I message is not output, re-execute the pdlogunld command.

Re-estimate the shared memory.

104
The log server process is not online, or required information in the shared memory cannot be referenced.
Use the pdls command to examine the status information of the corresponding unit and server, and, after it is running, re-execute the command.
If the standby-less system switchover (effects distributed) facility is being used, take the following actions:

If the unit where the system manager resides is running
The corresponding server might be temporarily stopped due to a system switchover. Use the pdls command to examine the server status information, and, after it is running, re-execute the command.

If the unit where the system manager resides is stopped
(a) If executed with the -u option specified
The corresponding server is not running on the unit specified in the -u option. Use the pdls command to investigate the unit that the server is running on, and specify the unit identifier of the unit in the -u option.
(b) If executed without the -u option specified
The corresponding server is not running on a regular unit. Use the pdls command to investigate the unit that the server is running on, and specify the unit identifier of the unit in the -u option.

--

105
Timeout was detected during command execution.
If the corresponding HiRDB unit is not online, wait until it is placed online and re-execute the command.
If the corresponding HiRDB unit is already online and a reason code is displayed by executing the pdlogswap command with the -w option specified, check for any transaction that has been executing for a long time.

If there is a transaction that has been executing for a long time:
(a) If the transaction cannot be cancelled:
Wait until the transaction has terminated, make sure that the synchronization point dump can be validated, then re-execute the pdlogswap command.
Re-execute the pdlogswap command with a sufficiently large value specified in the -t option so that validation of the synchronization point dump can be delayed until the current transaction has terminated.
(b) If the transaction can be cancelled:
Cancel the transaction and re-execute the pdlogswap command.

If there is no transaction that has been executing for a long time:
Re-execute the pdlogswap command.

--

106
Shared memory cannot be used.
Take action appropriate to the system call error message that was output immediately before this message.
--

107
System call error occurred.
Refer to the system call error message that was output immediately before this message to check the cause of the error.
--

108
Specified option is invalid for non-dual log file.
Specify only those options permitted for non-dual log file and re-execute the command.
--

110
Command specification is not valid in the execution environment of the target system.
Check the option specified with -d. Or, check the execution environment of the target system.
--

116
The pdlogswap command with the -w option specified cannot be executed because the system is waiting for validation of a synchronization point dump for the previous pdlogswap command that was executed with the -w option specified.
Check for any transaction that has been executing for a long time.

If there is a transaction that has been executing for a long time:
(a) If the transaction cannot be cancelled:
Wait until the transaction has terminated, make sure that the synchronization point dump can be validated, then re-execute the pdlogswap command.
Re-execute the pdlogswap command with a sufficiently large value specified in the -t option so that validation of the synchronization point dump can be delayed until the current transaction has terminated
(b) If the transaction can be cancelled:
Cancel the transaction and re-execute the pdlogswap command.

If there is no transaction executing for a long time:
Re-execute the pdlogswap command.

--

201
File name is invalid.
Consider the following causes:

An invalid character was specified in the path name.

The length of the HiRDB file name exceeds the maximum (30 characters).

Specify the correct file name and re-execute the command.
--

202
The specified HiRDB file system area was not found.
Check the specified HiRDB file system area and re-execute the command.
--

203
The specified device has not been initialized for the HiRDB file system.
Check the file name. If the file name is correct, initialize the device for the HiRDB file system.
--

204
Specified file already exists.
Check the file name. If the file name is correct, delete the file with the pdlogrm command and re-execute the pdloginit command.
--

205
Area necessary for file creation cannot be allocated.
Use a different device to create the file. Or, delete any unneeded file or back up the file, re-create the HiRDB file with the pdfmkfs command, restore the file, then create the file.
Re-estimate the file size.

206
Maximum number of files specified during file system initialization was exceeded.

207
In UNIX, the number of character special files that can be opened has been exceeded.
In Windows, the number of direct disks that can be opened has been exceeded.
--

208
There is no access privilege for the specified HiRDB file system area.
Execute the command with a user ID that has access privilege for the specified HiRDB file system area.
Modify the access privileges for the specified HiRDB file system area using OS commands (chmod, for example).

209
I/O error occurred while accessing a log file in the HiRDB file system.
Investigate the cause of the I/O error and take appropriate action. If the the pdloginit command could not be executed, create the HiRDB file system area on a different disk device or partition from the one where the I/O error occurred, and re-execute the command.
--

210
HiRDB file system versions do not match.
Re-create the HiRDB file system.
--

211
There is no access privilege for the specified file.
Execute the command with a user ID that has access privilege for the HiRDB file system area where the specified file is stored.
Modify the access privileges for the HiRDB file system area where the specified file is stored using OS commands (chmod, for example).

212
Specified file was not found.
Specify the correct file name and re-execute the command.
--

216
Specified file is not a log file or synchronization point dump file.

217
Specified file is not an unload log file.

221
Lock segment shortage occurred.
--
Re-evaluate the number of record lock segments specified during construction of the OS system.

222
Attempt was made to use a log file, but it was being used by another process.
Check if the file specified in the command is being used by another process. Re-execute the command, if necessary. If one of the following commands was executed while HiRDB was active, also take the action called for:

pdlogopen, pdlogcls, or pdlogswap command
Re-execute the command.

pdlogchg command
A mismatch between the memory status and the system log file's state may have occurred. Close the file group with the pdlogcls command and then reopen it with the pdlogopen command. If the file group is on unload wait status at this point, re-execute the pdlogchg command.

pdlogunld command
If the KFPS01271-I message is output immediately after this reason code, the unload log file has been created normally. However, a mismatch between the memory status and the system log file's status has occurred. Close the file group with the pdlogcls command and then reopen it with the pdlogopen command. If the KFPS01271-I message is not output, re-execute the pdlogunld command.

--

224
Specified file is on unload wait status.
Check the file name. If the file name is correct, either place the file on unloaded status with the pdlogunld or pdlogchg command or re-execute pdlogrm specifying the -u option.
--

225
Attempt made to create a file in an HiRDB file system area that is not for system files.
Check the usage of the HiRDB file system area by specifying the HiRDB file system area name in the pdfstatfs command, and create the file in an HiRDB file system area for system files.
--

227
Specified file is on extracting status.
Check the file name. If the file name is correct, either use the pdlogchg command to place the file on extraction-completed status or re-execute the pdlogrm command with the -u option specified.
--

228
The specified file is in the overwriting denied status for online reorganization.
Re-evaluate the file name. If the file name is correct, use the pdlogchg command to put the file in the overwriting permitted status for online reorganization, or execute the pdlogrm -u command.
--

301
Specified file already exists.
Use an operating system command to re-execute the command with the correct file name.
--

302
Specified file is a directory.

303
Error occurred while opening an unload log file.
Refer to the open system call error message that was output immediately before to check the cause of the error.
--

304
Error occurred while closing an unload log file.
Refer to the close system call error message that was output immediately before to check the cause of the error.
--

305
Error occurred while accessing an unload log file.
Refer to the write system call error message that was output immediately before to check the cause of the error.
--

306
Error occurred in an unload log file created in a HiRDB file system area.
Check the cause of the error based on the preceding KFPS01300-E message.
--

307
Error occurred while reading an unload log file.
Investigate the error on the basis of the error message for the read system call output immediately before.
--

403
Definition file open error occurred.
Refer to the definition file open error message that was output immediately before to check the cause of the error.
--

404
Analysis file open error occurred.
Refer to the analysis file open error message that was output immediately before to check the cause of the error.
--

405
Error was detected during definition analysis processing.
Check the cause of the error on the basis of the analysis error message that was output immediately before.
--

410
A duplication error was detected in the file group name of the system log file during definition analysis processing.
Check if the file group name specified in the -g option of the pdlogadpf operand was duplicated.
--

413
A limit error was detected in the file group count of the system log file during definition analysis processing.
Check if the pdlogadpf operand number exceeds the limit of the file group count for system log files.
--

414
Number of valid log file group definitions is less than the minimum number of generations necessary to start the system. A valid log file group definition is an error-free pdlogadfg operand for which ONL is specified.
Revise the pdlogadfg operand for the corresponding HiRDB server definition and restart the system.
--

417
An error was detected during definition analysis processing.
Find the error cause based on the analysis error message output immediately before this message.
--

701
File group was not found.
Check the status of the file group with the pdlogls command and re-execute the command, if necessary. If a definition file analysis error has been output immediately before this message, refer to that message to check the cause of the error.
--

702
A file group failed to open.
Refer to the KFPS01200-E or KFPS01201-E message that was output to the log file to check the cause of the error, and take an appropriate action.
--

703
A file group failed to close.

704
Specified file group has already been opened.
Check the status of the file group with the pdlogls command, specify the correct file group name, then re-execute the command.
--

705
Specified file group has already been closed.

706
Specified file group cannot be closed.

707
Specified file group is being used for system recovery processing or by the pdlogunld or pdlogchg command.
Check the status of the file group with the pdlogls command, specify the correct file group name, then re-execute the command.
--

708
Specified file group cannot be closed, because there would be no overwritable file group if it is closed.
--
--

709
File open processing was cancelled, because the same generation of the file group already exists.
Delete the physical files comprising the corresponding file group with the pdlogrm command and re-create the physical file with the pdloginit command
--

710
Specified file group is the current file group.
Check the status of the file group with the pdlogls command and re-execute the command, if necessary.
--

712
The system log file could not be closed because the percentage of free system log files was less than the warning value.
Increase the percentage of free system log files, and then re-execute the pdlogcls command.
For details about the free space percentage for system log files, see the HiRDB Version 9 System Operation Guide.
--

1101
An attempt to open the target file failed.
Follow the instructions in the KFPS01240-E message.
--

1301
Specified resource group name was not found.
Check the resource group name with the pdlogls command.
--

1601
There is no log file that can be unloaded or whose status can be changed.
Check the specified file group name.
--

1602
Missing block was detected in a log file.
The log file may have been damaged. Cancel unloading of the corresponding file group and contact the HiRDB administrator.
The system log file cannot be unloaded. Acquire a backup so that the database can be recovered without using the unload log of that system log file. Also, to help with investigating the cause, acquire the system log file for which the unload failed, and contact the customer support center.

1603
Specified file group has already been unloaded.
Check the specified file group name. If the specified file group is correct and the pdlogls command indicates that this file group is waiting to be unloaded, the previously entered pdlogunld or pdlogchg command may have caused an error that prevented the status from being updated in memory (the unload processing itself was successful). In such a case, close the affected file group with the pdlogcls command, then reopen the file group with the pdlogopen command to correct the status mismatch.
--

1604
Specified -n option value in the pdloginit command is outside the range 12 to104,857,600.
Specify a value in the -n option in the range 12 to 104,857,600 and re-execute the pdloginit command.
--

1606
During the execution of the command, HiRDB assumed one of the following states:

HiRDB starting processing

HiRDB terminating processing

HiRDB running

This command is terminated to protect the system log file.
--
Use the pdls -d svr command to check the operating status of HiRDB. If HiRDB is shut down, re-execute the pdlogchg or pdlogunld command.
If this message is output during the execution of the pdlogunld command, any unload log file that was created cannot be used for database recovery.

1607
The specification pd_log_unload_check=N is specified and HiRDB is operating; the status of the file group cannot be changed.
--
Specify the -R option in the pdlogchg command; specify the -f option in the pdlogunld command.

1609
Specified file group is in extraction-completed status.
Check the name of the specified file group. If the specified file group is correct and the pdlogls command displays that this file group is on extracting status, an error may have occurred during the previous pdlogchg command execution that makes it impossible to update the status in memory. In such a case, this conflict can be resolved by closing the corresponding file group with the pdlogcls command and then reopening it with the pdlogopen command.
--

1612
The value specified in the -l option of the pdloginit command is out of the 1024 to 4096 range.
Change the value specified in the -l option to fall within the 1024 to 4096 range and re-execute the pdloginit command.
--

1613
The sector length of the HiRDB file system area, the specified record length, or the specified record count is invalid.
Check the cause of the error based on a preceding KFPS01207-E message.
--

1614
The name of a HiRDB file specified in the pdloginit command is invalid.
Specify the system log file name using the absolute path name, and then re-execute the pdloginit command.
--

1615
The applicable file group is in the overwriting permitted status for online reorganization.
Re-evaluate the specified file group name. If the specified file group name is correct and the pdlogls command indicated this file group is in the overwriting denied status for online reorganization, the previously executed pdlogchg command may have caused an error that prevented updating of the memory status. In this case, close the applicable file group using the pdlogcls command, and then open the group using the pdlogopen command (the mismatch between the files and memory is resolved).
--

1616
Even though pd_large_file_use=N is specified, an attempt was made to use the pdloginit command to create a system log file in a HiRDB file system area created with the pdfmkfs -a command.
--
If you want to create a file in a HiRDB file system area created with the pdfmkfs -a command, specify Y in pd_large_file_use, or omit the specification.

1660
The directory that is the output target of the unload log file for the automatic log unloading facility cannot be used.
When a directory is specified as the output target for the unload log file:
There is a shortage of free disk space in the unload log file creation directory, or a disk failure occurred. Allocate more free disk space, or recover from the disk failure.
When a HiRDB file system area is specified as the output target for the unload log file:
The unload log file cannot be created, for reasons such as a shortage of space in the HiRDB file system area, or the number of extensions reaching its limit. After saving the unload log file, for example by making a backup of the HiRDB file system area with the pdfbkup command, use the pdfmkfs command to re-create the HiRDB file system area.
--

1664
The command cannot be executed on a log application site.
The aa....aa command can be executed only on a transaction execution site. Check the site that corresponds to command execution.
--

1670
None of the unload log file creation directories can be used.
Take action by referring to the reason code of the KFPS01152-W message.
--

1676
1677
Automatic log unloading facility cannot be used.

If HiRDB was started normally:

Check if the following operands were specified in the server definition of the applicable server when HiRDB was started:

pd_log_auto_unload_path

pd_log_unload_check=Y

If HiRDB was shut down by planned termination or was restarted:

Check if the automatic log unloading facility was used successfully during the previous operation of HiRDB. Also check if the following operand was specified in the server definition of the applicable server when HiRDB was started:

pd_log_unload_check=Y

--

1678
Automatic log unloading facility is already running.
Use the pdlogatul command to check if the automatic log unloading facility is running.
--

1679
Automatic log unloading facility has already stopped.
Use the pdlogatul command to check if the automatic log unloading facility has stopped.
--

1680
During monitoring for automatic log unloading stop, the automatic log unloading facility stopped for one of the following reasons:

None of the unload log file creation directories can be used.

Unload log file name is not unique.

Resource shortage occurred.

Determine why the automatic log unloading facility stopped based on other output messages, take appropriate action, and then restart the automatic log unloading facility (by executing the pdlogatul -b command). Then, re-execute the pdlogatul -t -w command.
--

1681
Because a timeout occurred during monitoring for automatic log unloading stop, monitoring was halted and the automatic log unloading facility was stopped.
Check if an I/O delay has occurred on the disk where the unload log creation directory is located. Then, restart the automatic log unloading facility (by executing the pdlogatul -b command) and re-execute the pdlogatul -t -w command.
--

--: Not applicable

KFPS01281-E E

Invalid command format.

Command format is invalid.

S: Cancels command execution.

O: Check the command format and re-execute the command.

KFPS01282-E E

bb....bb specified with aa option not found.

bb....bb specified in option aa was not found.

aa: Option code:

-g: Option for specifying a file group name

bb....bb: File group name

S: Cancels command execution.

O: Specify the correct option argument and re-execute the command.

KFPS01283-W E

Minor error occurred during aa....aa command execution. reason code=bbbb-cc

A minor error occurred while executing command aa....aa.
Command processing terminated normally, but the minor error indicated by the reason code occurred during execution.

aa....aa: Name of the command resulting in the minor error

bbbb: Reason code

cc: HiRDB internal code

S: Resumes processing.

O: Take action appropriate to the reason code, as listed below, and re-execute the command, if necessary.

Action

Take action appropriate to the reason code, as listed below:

Reason code | Explanation | Operator's action
1102 | Some of the files to be opened could not be opened (in this case, the opening of successfully opened files is valid). | If necessary, take action according to the KFPS01240-E message output to the log file.
1103 | All files to be opened are already open. | If necessary, use the pdlogls command (specify the -e option) to check the status of the files comprising the file group, specify the correct file group name, A system or B system, and then reenter the command.
1104 | All files to be closed are already closed.

KFPS01284-I E

Usage: pdlogsync -d sys [-s servername] [-w [-t wait time]]

The pdlogsync command contains an input format error (HiRDB/Single Server).

S: Terminates processing.

O: Enter the correct command.

KFPS01284-I E

Usage: pdlogsync -d sys -s servername [-w [-t wait time]]

The pdlogsync command contains an input format error (HiRDB/Parallel Server).

S: Terminates processing.

O: Enter the correct command.

KFPS01285-E E

Command unable to be executed due to swap processing.

Command cannot be executed because the system log file is being processed.

S: Cancels command processing.

O: Re-execute the command after swap processing is completed.

KFPS01286-E E

Unable to perform swapping because no standby log file group is available.

Files cannot be swapped because there is no standby log file group.

S: Cancels the swap command.

O: Place a file group on unloaded status with the pdlogunld or pdlogchg command in order to provide a standby log file group. Or, place a reserve log file on online status with the pdlogopen command in order to provide a standby log file group. Then, re-execute the command, if necessary.

KFPS01290-I E

Usage: pdlogswap -d sys [-s server_name] [-w [-t wait_time]]

Displays the format of the pdlogswap command for a HiRDB/Single Server. This message is displayed when the specified command format is invalid.

S: Resumes processing.

KFPS01290-I E

Usage: pdlogswap -d sys -s server_name [-w [-t wait_time]]

Displays the format of the pdlogswap command for a HiRDB/Parallel Server. This message is displayed when the specified command format is invalid.

S: Resumes processing.

KFPS01291-I E

Usage: pdlogls -d {sys [-s server_name] [-g file_group_name] [-e] [-C [-H]] [-E]|spd [-s server_name] [-g file_group_name] [-e] [-l]}

Displays the format of the pdlogls command for a HiRDB/Single Server. This message is displayed when the specified command format is invalid.

KFPS01291-I E

Usage: pdlogls -d {sys -s server_name [-u unit_id] [-g file_group_name] [-e] [-C [-H]] [-E]|spd -s server_name [-g file_group_name] [-e] [-l]}

Displays the format of the pdlogls command for a HiRDB/Parallel Server. This message is displayed when the specified command format is invalid.

KFPS01292-I E

Usage: pdloginit {-d sys [-s server_name] -f file_name -n record_count [-l record_size] |-d spd [-s server_name] -f file_name -n record_count}

Displays the format of the pdloginit command for a HiRDB/Single Server. This message is displayed when the specified command format is invalid.

KFPS01292-I E

Usage: pdloginit {-d sys -s server_name [-u unit_id] -f file_name -n record_count [-l record_size] | -d spd -s server_name [-u unit_id] -f file_name -n record_count} [-D]

Displays the format of the pdloginit command for a HiRDB/Parallel Server. This message is displayed when the specified command format is invalid.

KFPS01293-I E

Usage: pdlogrm -d sys|spd [-s server_name] -f file_name [-u]

Displays the format of the pdlogrm command for a HiRDB/Single Server. This message is displayed when the specified command format is invalid.

KFPS01293-I E

Usage: pdlogrm -d sys|spd -s server_name [-X unit_id] -f file_name [-u] [-D]

Displays the format of the pdlogrm command for a HiRDB/Parallel Server. This message is displayed when the specified command format is invalid.

KFPS01294-I E

Usage: pdlogopen -d sys|spd [-s server_name] -g file_group_name [-a] [-b]

Displays the format of the pdlogopen command for a HiRDB/Single Server. This message is displayed when the specified command format is invalid.

KFPS01294-I E

Usage: pdlogopen -d sys|spd -s server_name -g file_group_name [-a] [-b]

Displays the format of the pdlogopen command for a HiRDB/Parallel Server. This message is displayed when the specified command format is invalid.

KFPS01295-I E

Usage: pdlogcls -d sys|spd [-s server_name] -g file_group_name [-a] [-b]

Displays the format of the pdlogcls command for a HiRDB/Single Server. This message is displayed when the specified command format is invalid.

KFPS01295-I E

Usage: pdlogcls -d sys|spd -s server_name -g file_group_name [-a] [-b]

Displays the format of the pdlogcls command for a HiRDB/Parallel Server. This message is displayed when the specified command format is invalid.

KFPS01296-I E

Usage: pdlogunld -d sys [-s server_name] -g file_group_name [-o output_file_name] [-n] [-f] [-k file_kind] [-i init_size [,expand_size]]

Displays the format of the pdlogunld command for a HiRDB/Single Server. This message is displayed when the specified command format is invalid.

KFPS01296-I E

Usage: pdlogunld -d sys -s server_name [-u unit_id] -g file_group_name [-o output_file_name][-n] [-f] [-k file_kind] [-i init_size [,expand_size]]

Displays the format of the pdlogunld command for a HiRDB/Parallel Server. This message is displayed when the specified command format is invalid.

KFPS01297-I E

Usage: pdlogchg{-d sys [-s server_name] -g file_group_name [-R|-G] | -z log_point_information [-x host_name]}

Displays the format of the pdlogchg command for a HiRDB/Single Server. This message is displayed when the specified command format is invalid.

KFPS01297-I E

Usage: pdlogchg {-d sys -s server_name [-u unit_id] -g file_group_name [-R|-G] | -z log_point_information [-x host_name]}

Displays the format of the pdlogchg command for a HiRDB/Parallel Server. This message is displayed when the specified command format is invalid.

KFPS01299-I E

Usage: pdlogatul -d sys [-s server_name][-b| -t| -i]

Displays the format of the pdlogatul command in a HiRDB/Single Server. This message is output when the command is entered incorrectly.

S: Continues processing.

KFPS01299-I E

Usage: pdlogatul -d sys -s server_name [-b| -t| -i]

Displays the format of the pdlogatul command in a HiRDB/Parallel Server. This message is output when the command is entered incorrectly.

S: Continues processing.

KFPS01300-E E+L

aa....aa error occurred, file=bb....bb

An I/O error occurred in an unload log file created in a HiRDB file system area.

aa....aa: Error detail:

Close: File close error

Open: File open error

Read: File loading error

Write: File write error

bb....bb: Name of the unload log file in which the error occurred

If the path name of the unload log file exceeds 150 characters, the last 150 characters of the unload log file path name are output.

S: Continues processing.

O: Take action appropriate to the message that is output after this message. Eliminate the cause of the error, and then re-execute the command.

KFPS01301-E E+L

System call error, func=aa....aa, errno=bb....bb

A system call error occurred in an unload log file created in a HiRDB file system area.

aa....aa: Name of the system call in which the error occurred

bb....bb: errno of the system call in which the error occurred

S: Terminates processing.

O: Check the error number (errno: external integer variable indicating error status) and refer to errno.h or to the applicable OS manual to correct the error. Then, re-execute the pdlogunld command.

KFPS01302-E E+L

File I/O error occurred, reason=aa....aa, func=bb....bb, errno=cc....cc, (dd....dd)

An error occurred during an I/O operation for an unload log file created in a HiRDB file system area.

aa....aa: Error cause:

File-format:

Specified file format does not match the actual file format.

File-lock:

Specified file is read/write-disabled because it has been locked by another utility.

Invalid-device:

The entry type of the specified file is invalid. Entry types that can be identified by the system consist of a single alphabetic character enclosed in parentheses. In UNIX, this alphabetic character is the same as the entry for the mode output using the OS ls -l command.

Invalid-environment:

Because the setting obtained by the uname system call is invalid, a streaming tape device cannot be used (check that the OS has been installed correctly or that the OS version is compatible with the HiRDB and related products).

Invalid-parameter:

Combination of specified parameters is invalid.

Invalid-path:

Path name of the unload log file is invalid.

Invalid-permission:

Permission for the specified file is invalid.

No-file:

File that is to be opened for loading does not exist, or file that was being written was erased.

No-space:

There is not enough space in the file to be written (check the file size or if the maximum number of size increases has been reached).

Unmatch-entry:

For a file with a header, the entry in the header does not match the specification in the control information file (the mismatching entry name is displayed in parentheses).

bb....bb: Name of the system function in which the error occurred

If the error occurred in a HiRDB file system area, the function name of the HiRDB file system area is displayed. Otherwise, *** is displayed.

cc....cc: Error number returned by the system function (errno)

If the error occurred in a HiRDB file system area, the error code of the HiRDB file system area is displayed. For details on the error codes, see 5.1 Error codes returned from HiRDB file system access requests.

In all other cases, 0 is output.

dd....dd: Name of the source file and row number in which the error was detected

S: Terminates processing.

O: After determining the error cause and error number and correcting the error, re-execute the pdlogunld command.

KFPS01303-E E+L

HiRDB file aa....aa error, errno=bb....bb, HiRDB file name=cc....cc

An error occurred during access to an unload log file created in a HiRDB file system area.

aa....aa: Error detail:

close: File close error

create: Fire creation error

expand: File expansion error

fstat: File information acquisition error

open: File open error

read: File read error

write: File write error

bb....bb: Error code

For details on the error codes, see 5.1 Error codes returned from HiRDB file system access requests.

cc....cc: Name of the unload log file in which the error occurred

If the path name of the unload log file exceeds 150 characters, the last 150 characters of the unload log file path name are output.

S: Terminates processing.

O: Refer to the error code to eliminate the cause of the error, then re-execute the command.

KFPS01362-I L

Log block reading started, type=aaa(bb....bb), read start point=cc....cc, dd....dd, ee....ee, ff....ff, gg....gg

Reading of the system log has started.

aaa: File type

sys: System log file

bb....bb: HiRDB server name

cc....cc: File group name of the system log file at read startup

dd....dd: Run ID of the system log at read startup

ee....ee: User run ID of the system log at read startup

ff....ff: Generation number of the system log at read startup

gg....gg: Block number of the system log at read startup

S: Continues processing.

KFPS01363-I L

Log block reading completed, type=aaa(bb....bb), read end point=cc....cc, dd....dd, ee....ee, ff....ff, gg....gg

Reading of the system log has finished.

aaa: File type

sys: System log file

bb....bb: HiRDB server name

cc....cc: File group name of the system log file at read completion

dd....dd: Run ID of the system log at read completion

ee....ee: User run ID of the system log at read completion

ff....ff: Generation number of the system log at read completion

gg....gg: Block number of the system log at read completion

Note: If no log blocks are input, ******** is displayed for cc....cc, dd....dd. ee....ee, ff....ff, and gg....gg.

S: Continues processing.

KFPS01380-I E

Usage: pdlogucat [-k std|csv] unload_log_file_name

The usage of the pdlogucat command is displayed. This is output if there is an error in the command format.

S: Terminates processing.

KFPS01390-I L

Unable to expand sys(aa....aa) log file, file group=bb....bb, system A/B=c, reason=dddd

The system log file cannot be expanded.

aa....aa: HiRDB server name

bb....bb: File group name of the system log file

c: System classification

a: System A

b: System B

dddd: Reason code

S: Continues processing.

O: Take corrective action by referring to the operator action that corresponds to the appropriate reason code in the following table.

Action

Take corrective action by referring to the HiRDB administrator action that corresponds to the appropriate reason code in the following table.

Reason code
Explanation
Operator action
HiRDB administrator action

101
A memory shortage occurred. As a result, this system log file will no longer be expanded.
--
Check the required amount of memory again.

205
The disk is full.
--
Free up disk space as necessary.

209
An I/O error occurred. As a result, this system log file will no longer be expanded.
Refer to the messages output before and after this message, identify the cause of the error, and then take corrective action.
To allow the system log file to be expanded, take one of the following actions:

Execute the pdlogcls command to close the system log file.

Execute the pdfmkfs -a command to re-create HiRDB file system area.

Execute the pdloginit command to re-create the system log file.

221
A lock segment shortage occurred. As a result, that system log file will not be expanded.
--
Revise the number of lock segments specified for OS system startup.

1690
The HiRDB file system area that contains this system log file cannot be expanded (this HiRDB file system area was created by specifying the pdfmkfs command without the -a option). As a result, this system log file will no longer be expanded.
--
To allow the system log file to be expanded, take one of the following actions:

Execute the pdlogcls command to close the system log file.

Execute the pdfmkfs -a command to re-create HiRDB file system area.

Execute the pdloginit command to re-create the system log file.

1691
The initial size of the system log file exceeds the maximum expansion size specified in the pd_log_auto_expand_size operand. As a result, this system log file will no longer be expanded.
Use the pdfls command to check the number of records of corresponding system log files.
Check the following specification values, and revise them if necessary.

-n option of pdloginit command

Maximum expansion size of pd_log_auto_expand_size operand

1692
The maximum capacity of the system log file has been reached. As a result, this system log file will no longer be expanded.
--
If necessary, revise the total capacity and generation number of the system log file.

1694
The maximum expansion capacity of the system log file has been reached. As a result, this system log file will no longer be expanded.
--
If necessary, revise the maximum expansion size specified in the pd_log_auto_expand_size operand.

Legend:

--: Not applicable.

KFPS01391-I L

Sys(aa....aa) log files expansion bb....bb, {output file name=cc....cc|expanded size=dd....dd}

Starts or terminates automatic extension of the system log file. Displays cc....cc and dd....dd when starting or terminating automatic extension, respectively.

aa....aa: HiRDB server name

bb....bb: Processing type

start: Processing start

complete: Processing termination

cc....cc: Status information file name of the system log file

When automatic extension starts, the status information file of the system log file is output under %PDDIR%\spool\pdjnlinf\.

dd....dd: Number of expanded records

When multiple file groups automatically expand, the sum of the number of records for each expanded file group is displayed.

If the number of expanded records is 1,000,000,000 or greater, K is added, and the numerical values obtained with the following formula are displayed.

sum of number of records of each expanded file group 1000

S: Continues processing.

KFPS01392-W L

Unable to use sys(aa....aa) log files expansion, reason code=bbbb

The system log file automatic extension facility cannot be applied on this server.

aa....aa: HiRDB server name

bbbb: Reason code

S: Continues processing.

Action

Take action according to the reason code, as listed below:

Reason code | Explanation | HiRDB administrator action
1693 | N is specified in the pd_large_file_use operand, so the automatic extension facility has been disabled. | Either specify Y in the pd_large_file_use operand or omit the specification.

KFPS01393-E L

Unable to expand sys(aa....aa) log file, file group=bb....bb, code=cccc

An attempt was made to expand the system log file. However, expansion was not possible for one of the following reasons, and processing was interrupted.
(1) If the KFPS01390-I message was output prior to this message:

The error cause is displayed in message KFPS01390-I.

(2) If the KFPS01390-I message was output prior to this message:

Input / output processing to the system log file was centralized, for a reason such as the execution of an update transaction.

A communication error occurred.

A memory shortage occurred.

aa....aa: HiRDB server name

bb....bb: System log file group name

cccc: HiRDB internal code

S: Terminates abnormally.

Action

If the KFPS01390-I message was output prior to this message, take the action indicated in that message.

If the KFPS01390-I message was not output, take corrective action according to When a HiRDB (unit) terminates abnormally due to a system log file shortage in the HiRDB Version 9 System Operation Guide.

KFPS01800-I L

Now starting HiRDB unit aaa

Indicated HiRDB unit is being started.

aaaa: Unit identifier

S: Resumes HiRDB system startup processing.

KFPS01801-E E+L

Unable to start HiRDB unit due to improper operational environment. reason code=aa....aa

A HiRDB unit cannot be started, because its operating environment has not been set up.

aa....aa: Cause of the startup error

S: Cancels HiRDB startup processing.

Action

Take the following actions, and then start HiRDB. Contact the customer support center if a reason code other than the following is output:

Reason code
Cause
Action

ENV_PDDIR
The environment variable PDDIR is not set, or the directory it resides in cannot be referred to.
Set environment variable PDDIR.

MEMORY
There is a process private memory or shared memory shortage.
See the descriptions for SHM_EINVAL, SHM_ENOMEM, or SHM_ENOSPC.

PAUSE
An error occurred such that HiRDB processing could not continue, and the process server process was suspended.
Refer to the message output immediately before this message in the command input window and the event log (in UNIX, syslogfile). Alternatively, refer to the corrective actions in message KFPS00715-E.

PROGRAM
There are no prerequisite programs.
Install the prerequisite programs.

RPL_FILE
There is no data linkage file for HiRDB Datareplicator, the user does not have access privileges, or the content is invalid.
See the KFPS01889-E message output immediately before this message to recover from the error in the data linkage file for HiRDB Datareplicator.
Representative error factors and actions:

function-value = SYSTEM CALL(stat) ERROR, error = 2
There is no data linkage file.
If there is an error in the value specified in the pd_rpl_hdepath operand, which is the name of the HiRDB Datareplicator directory where data is to be extracted, modify the pd_rpl_hdepath operand, and then restart HiRDB. If the disk to be used for the data linkage file is unmounted, remount the file and restart HiRDB Datareplicator and HiRDB. If there is no data linkage file, synchronize to the target database, re-create the data linkage file, and then restart HiRDB Datareplicator and HiRDB.

function-value = SYSTEM CALL(open) ERROR, error = 13
The user does not have access privileges to the data linkage file. Check your access privileges to the data linkage file. If you do not have access privileges, establish access privileges, and then restart HiRDB Datareplicator and HiRDB.

function-value = FILE ERROR
The data linkage file is invalid. Synchronize to the target database, re-create the data linkage file, and then re-execute HiRDB Datareplicator and HiRDB.

RPL_INSTALL
Possible causes:

An error such as a failure on the HiRDB Datareplicator installation disk prevents access to the HiRDB Datareplicator installation directory.

The HiRDB addressing mode and the HiRDB Datareplicator addressing mode do not match.

HiRDB Datareplicator is not installed.

Check the following items and take appropriate action:

Check if an error such as a failure on the HiRDB Datareplicator installation disk on a server machine with the unit that output this message prevents access to the HiRDB Datareplicator installation directory. If an error is found, eliminate the cause, and then re-execute.

Check if the addressing mode of the unit that output this message and the address mode of HiRDB Datareplicator match. If they do not match, replace HiRDB Datareplicator with a HiRDB Datareplicator that has the same address mode as the HiRDB addressing mode.

Check if HiRDB Datareplicator is installed on the server machine containing the unit that output this message. If HiRDB Datareplicator is not installed, install it, and then re-execute.

RPL_STOP
HiRDB Datareplicator suspended data linkage to HiRDB.
Find the cause of data linkage being stopped and eliminate the problem. Then, start HiRDB Datareplicator. For details about how to locate the cause, see the HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide.

SETUP
In UNIX, the system is not set up. In Windows, the HiRDB service has stopped.
In UNIX, use the pdsetup command to set up HiRDB.
In Windows, the HiRDB service might not be started. Start the service, then restart HiRDB.

SHM_EINTR
A signal was received during the shared memory securing process.
Check the cause of the signal, take appropriate action, and then restart HiRDB.

SHM_EINVAL
In UNIX
The shared memory size exceeded the system limit.
In Windows
The size of the installation drive is insufficient, so work files for shared memory could not be allocated.
In UNIX
Increase the maximum segment size in system shared memory, and then re-create the kernel.
In Windows
On the HiRDB installation drive, allocate sufficient free space for the shared memory.

SHM_EMFILE
The number of open files exceeded the number of file tables the system can open.
Decrease the number of open files or increase the number of file tables the system can open and re-create the kernel.

SHM_ENOMEM
In UNIX
Memory equal to the shared memory size was not found in the system.
In Windows
Consider the following causes:

There is insufficient memory in the system to equal the size of the shared memory.

If a paging file was allocated at the location where the shared memory was allocated, the HiRDB service was not started.

In UNIX
Increase system memory.
In Windows
A KFPO00107-E or KFPO00113-E message was output before this message was output. Refer to the explanation given in the KFPO00107-E or KFPO00113-E message and take appropriate action.

SHM_ENOSPC
In UNIX
The number of shared memory identifiers exceeds the maximum defined in the system.
In Windows
The installation drive does not contain a disk area to allocate only the shared memory.
In UNIX
Decrease the number of shared memory buffers or increase the maximum number of shared memory identifiers and re-create the kernel.
In Windows
A KFPO00107-E or KFPO00113-E message was output before this message was output. Refer to the explanation given in the KFPO00107-E or KFPO00113-E message and take appropriate action.

SHM_EOVER
The shared memory size exceeded 2 GB.
Detail code:

lck: Lock server

trn: Transaction control

jnl: Log server

tjl: Transaction log server

aud: Security audit

controlNo display: Unit controller

32 bit mode
See the section on formulas for calculating shared memory used by unit controllers in the HiRDB Version 9 Installation and Design Guide, and change the definition values to make the size of the shared memory for all unit controllers less than 2 GB.

lck
Decrease the value of the pd_max_access_tables, pd_max_users, pd_max_bes_process, pd_max_dic_process, pd_max_reflect_process_count, pd_ha_max_act_guest_servers, pd_lck_hash_entry, pd_lck_pool_size, pd_lck_pool_partition, pd_fes_lck_pool_size, pd_fes_lck_pool_partition, or pd_max_open_holdable_cursors operand.

trn
Decrease the value of the pd_max_users, pd_max_bes_process, pd_max_dic_process, pd_max_reflect_process_count, or pd_ha_max_act_guest_servers operand. Alternatively, decrease the number of front-end servers and the number of back-end servers.

jnl
Decrease the value of the pd_log_rec_leng, pd_log_max_data_size, pd_log_write_buff_count, pd_stj_buff_size, pd_max_users, pd_max_reflect_process_count, pd_ha_max_act_guest_servers, pdlogadfg -d sys, pdlogadfg -d spd, or pdlogadpf -d spd operand. Alternatively, decrease the number of servers in the unit with the error.

tjl
Decrease the value of the pd_log_rec_leng, pd_log_max_data_size, pd_log_rollback_buff_count, pd_max_users, pd_max_bes_process, pd_max_dic_process, pd_max_reflect_process_count, or pd_ha_max_act_guest_servers operand.

aud
Decrease the value of the pd_aud_async_buff_size or pd_aud_async_buff_count operand.

64 bit mode

jnl
See the section on formulas for calculating shared memory used by unit controllers in the HiRDB Version 9 Installation and Design Guide, and change the definition values to make the size of the shared memory for each server less than 2 GB. For HiRDB/Parallel Server, calculate using 1 as the value for number-of-servers-in-unit+D and number-of-FES-in-unit.

SHM_CALC ***
An internal conflict occurred during calculation of the shared memory size. *** indicates the HiRDB internal information.
Save the files under %PDDIR%\spool, save the event log (in UNIX, syslogfile), and contact the customer support center.

VERSION
The operating system version does not match.
Replace the current version of the operating system with the correct version.

AHA_INSTALL
HiRDB Advanced High Availability is not set up.
HiRDB Advanced High Availability is necessary when using the standby less system switchover facility. Either introduce HiRDB Advanced High Availability or delete the pd_ha_agent operand.

AHA_VR
The system definition specifies that the standby-less system switchover (effects distributed) facility be used, but the version of the HiRDB Advanced High Availability that is set up in the server machine that allocated the unit that output the message is invalid.
Take one of the following actions:

See the KFPS05620-I message, and check the version of the HiRDB Advanced High Availability that has been set up. If the version is incorrect, set up the correct version of HiRDB Advanced High Availability and re-execute.

Reconsider the use of the standby-less system switchover (effects distributed) facility.

NONALTSVUNIT
Can only be executed by an alternate BES unit.
Execute using an alternate BES unit.

NRF_INSTALL
A recovery-unnecessary front-end server is set (there is a front-end server with the -k stls option specified in the pdstart operand), but HiRDB Non Recover FES is not specified on the server machine with the unit that output the message.
To set a recovery-unnecessary front-end server, HiRDB Non Recover FES is required. Introduce HiRDB Non Recover FES, or remove the pdstart operand with the -k stls option.

DRL_INSTALL
In the system definition pd_rise_pairvolume_combination operand, syssync is specified, but HiRDB Disaster Recovery Light Edition is not set up in the server of the unit that output the message.
Take one of the following actions:

Determine whether HiRDB Disaster Recovery Light Edition is installed, and if it is not installed, install it.

Determine whether HiRDB Disaster Recovery Light Edition is set up in the HiRDB working directory, and if it is not set up, execute the pdopsetup command to set it up.

Reconsider whether Real Time SAN Replication with the log-only synchronous method is to be used. If Real Time SAN Replication with the log-only synchronous method is not to be used, specify other than syssync in the system definition pd_rise_pairvolume_combination operand.

RECOVERY
The possible causes are as follows:

You executed the command pdstart -r -t, and then executed the command pdstart -r -t [-q] on the standby system of a unit running with the shared resource automatic activation facility enabled.

You executed the command pdstart -r -t in a standby-less system switchover (1:1) configuration, and then executed the command pdstart -q -c on a unit running with the shared resource automatic activation facility enabled.

If the running HiRDB system has already been started with the command pdstart -r, execute recovery processing on the running system. If the running HiRDB system was started normally, terminate the running HiRDB system normally, and then restart by executing the command pdstart -r -t.

Note

If the reason code is RPL_STOP or RPL_FILE, the KFPS04624-I message showing the server name is output before this message (KFPS01801-E) for each server in which the error occurred.

KFPS01802-E E

Unable to start HiRDB unit because another HiRDB with the same ID operating

Specified HiRDB unit cannot be started, because a HiRDB with the same HiRDB identifier is running.

S: Cancels HiRDB startup processing.

P: Restart after the current HiRDB has terminated. Or, change the HiRDB identifier and restart.

KFPS01803-I L

HiRDB unit aaaa start mode determined. start mode: bb....bb

The unit startup mode was selected.

aaaa: Unit identifier

bb....bb: Startup mode:

R: Restart

R(P): Restart after planned termination

S: Normal startup

S: Resumes processing.

KFPS01812-E E+L

Error occurred while starting server aa....aa. reason code=bb....bb

An error occurred while starting server aa....aa.

aa....aa: Name of the server resulting in the error

bb....bb: Cause of the error

COMMUNICATION: Inter-process communication error occurred.

CONFIGURATION: Error occurred during definition analysis.

EXIST: Server with the same name or service group name is already running.

FORK FAILED: Server startup failed.

LOCK: Lock processing failed.

MAX PROCESSES: Number of processes exceeded the specified maximum.

MEMORY: Memory shortage occurred.

NO RPC ENVIRONMENT: RPC environment has not been started.

NO SCHEDULER: Scheduler is engaged in termination processing or is inactive.

NO SERVER: Server terminated (normally or abnormally).

NO SERVICE PRODUCER: Process server process has not been started.

PRC ERROR: Error occurred in process server process.

SCD NOT UP: Scheduler process has not been started.

SERVER DOWN: Server terminated abnormally.

SHARED MEMORY: Shared memory could not be secured.

STOPPING NOW: Server is now terminating.

VERSION INVALID: Version is invalid.

S: Continues HiRDB processing. However, terminates HiRDB processing in cases such as HiRDB startup where the HiRDB process can no longer run.

Action

Eliminate the cause of the error and restart the server.

CONFIGURATION: Check the definition.

COMMUNICATION: Check the cause of the network error.

FORK FAILED: Check the amount of memory (pd_sds_shmpool_size, pd_dic_shmpool_size, pd_bes_shmpool_size, SHMMAX, for example) and the number of processes (pd_process_count, pd_max_server_process, for example).

MAX PROCESSES: Check the maximum number of server processes defined in the system common definition.

MEMORY: In UNIX, check the real memory size or the swap area size. In Windows, check the Windows real memory size or the virtual memory size.

NO RPC ENVIRONMENT: Check if pd_rpc_open() has been issued.

NO SERVER: If the server terminated abnormally, check the cause.

PRC ERROR: Take the same action as for COMMUNICATION or VERSION INVALID.

SERVER DOWN: Check the cause of abnormal termination of the server.

SHARED MEMORY: Check the messages output to the event log (in UNIX, syslogfile) before or after this error occurred, and take appropriate action. If this problem recurs, contact the customer support center.

VERSION INVALID: Check the versions of the libraries and processes.

KFPS01813-I L

Server aa....aa started[ on unit bbbb]

Server aa....aa has been placed in online mode by unit bbbb. This is output on unit bbbb when the server is activated by the unit that is applying the standby-less system switchover (effects distributed) facility.

aa....aa: Name of the server whose startup has been completed

bbbb: Unit identifier of the server activation target unit

S: Resumes HiRDB processing.

KFPS01814-I L

HiRDB unit aaaa previous operation not terminate normally; perform normal start

Attempt was made to start HiRDB normally, but HiRDB had not terminated normally at the previous session.

aaaa: Unit identifier

S: Starts HiRDB forcibly.

KFPS01815-E E+L

Error occurred in OS while executing aa....aa. function value=bb....bb, errno=cc....cc

An error occurred in a system function in the operating system.

aa....aa: Name of the system call or subroutine resulting in abnormal termination

bb....bb: Return value of the system call or subroutine resulting in abnormal termination

cc....cc: Value of errno set during abnormal termination

S: Cancels processing.

Action

Check the value of errno and refer to errno.h or to the applicable OS manual to eliminate the cause of the error. For representative errors, see 4.3 System call return codes.

KFPS01818-E E

Stops activating server aa....aa because the server not in halt state

Server startup was cancelled, because an active server was specified.

aa....aa: Name of active server

S: Cancels server startup processing.

O: Check the name of the server to be started.

KFPS01819-I L

Server aa....aa. failed information. process ID=bb....bb, C-PID=cc....cc(dd....dd), TIME=eeffgg, PROGRAM=hh....hh

This message provides additional information concerning termination of a server process. This message is not displayed if the server is not connected to a client or if this is an internal server used by HiRDB.

aa....aa: Name of the terminated server

bb....bb: Process ID at the terminated server

cc....cc: Process ID of the client (a UAP or a utility) that was connected to a server process. However, in the following cases, 0 is displayed:

A server process that is not connected to a client

A server process that is connected to a client linked to a client library version prior to 04-00

A server process that is connected to a Type 4 JDBC Driver

dd....dd: IP address of the client (a UAP or a utility) that was connected to a server process. In the case of a server process that is not connected to a client, 0.0.0.0 is displayed.

eeffgg: Time (hour, minute, second) the service request was accepted; for a server process that was not connected to a client, 999999 is displayed.

hh....hh: UAP identification information (this is the UAP name specified in PDCLTAPNAME in the client environment definition. If PDCLTAPNAME is not set, Unknown is displayed. For a utility, the name of the utility command is displayed. If the UAP was running on a utility server process or the UAP identification information cannot be obtained due to an error, this information may be left blank)

S: Cancels server startup processing.

O: Check the name of the server to be started.

Action

Use this message to investigate the cause of the error indicated by the error message output before this message.

KFPS01820-E E+L

Server aa....aa failed. process ID=bb....bb, service group name=cc....cc, run mode=dd....dd, critical state=e, critical mask=ff....ff, end state=gg....gg, server type=hhh

Server aa....aa was terminated.
When using the facility for changing a process down message when canceling a transaction (the pd_cancel_down_msgchange operand in the system definition is set to Y or omitted), message KFPS01852-W is output instead of message KFPS01820-E. For details, see Facility for changing the process-down message when a transaction is cancelled in the HiRDB Version 9 System Operation Guide.
Note that the process termination statuses listed below are examples. A process termination status other than these might appear.

Value of gg....gg
Explanation

007f
0009
A request to forcibly terminate the server process was received. If the pdcancel command was executed, this message was output. Based on the messages that were output before or after this message, investigate the reason that the process received a forcible termination request (including executing the pdcancel command) and take any appropriate action. However, if during execution of a UAP or utility related processes or the units on which the related processes exist abnormally terminate, no other messages except this message are output.

0003
0083
A request to forcibly terminate the server process was received. Investigate the reason the process received a forcible termination request from the status of the executed transaction and the messages output before and after this message. Then, take appropriate action.

0006
0086
0100
0200
0300
0400
0800
Abnormal termination was due to an abnormality detected during processing. Investigate the cause of the abnormal termination from the messages output before and after this message, and take appropriate action.

8000
Due to a memory shortage, process activation failed or the process terminated abnormally. Take one of the following actions:

Reduce the number of other processes running on the same server machine.

Increase the swap area.

Increase the real memory.

In Windows, another possibility is that a desktop heap shortage has occurred. See the HiRDB Version 9 Installation and Design Guide, and then revise the value specified for the desktop heap.

c000
A connect system call was issued; however, a connection was not established because the destination system was down or there was a network failure.

c100
The second and subsequent SQL response transmissions could not be sent because either the destination system was down or there was a network failure.

c200
During a transaction in which control was held by the HiRDB client, a timeout was detected by the HiRDB client environment definition PDSWAITTIME.

c300
An error occurred at the remote system during communication processing; the remote communication socket was closed.

c400
If the client had control and no transaction was being processed, a timeout was detected by the client environment definition PDSWATCHTIME. Or, a timeout was detected in the pd_watch_pc_client_time set in the HiRDB system while connecting a Windows edition of the HiRDB client.

c500
Acquisition of special file (FIFO) failed during server startup.

c600
The possible causes are as follows:

The maximum number of transactions that can be processed concurrently by HiRDB has been exceeded.

There is a server in new transaction scheduling suppressed status.

Use the command pdls -d svr to identify the server in new transaction scheduling suppressed status and eliminate the cause of the error. If there is no server in new transaction scheduling suppressed status, many rollbacks might have occurred. In that case, wait for the rollbacks to be completed, and then re-execute the UAP.

c700
Abnormal termination of the client that requested the SQL statement was detected during execution of the SQL statement by the HiRDB server.

c800
SQL request transmission failed due to a network failure between the server and the system manager.

c900
The second and subsequent SQL request receptions could not be received because a network failure occurred between the source and the system manager.

d000
Because the parent process was forcibly terminated during processing of a transaction, the child process was forcibly terminated.

d100
Server processing was canceled because UAP processing did not terminate within the monitoring time limit set in the PDSWAITTIME, PDSWATCHTIME, or PDCWAITTIME client environment definition. Alternatively, related server processing was canceled because the pdcancel command was executed.

d200
The maximum number of transactions that can be processed concurrently by a UAP, or an XDS client of a UAP, under the OLTP environment has been exceeded. Because many rollbacks might have occurred, wait for the rollbacks to be completed, and then re-execute the UAP.

d300
An error was detected, but the HiRDB server process was terminated without outputting troubleshooting information because the specification of the pd_dump_suppress_watch_time operand was in effect.

d500
An error occurred during transaction completion processing.

d600
The HiRDB server process made a transaction branch request to a server that is stopped, or is in the process of stopping or switching over. As a result, the HiRDB server process was forcibly terminated.

d700
The HiRDB server process made a transaction branch request to a server that is in the process of starting up or switching over (a switchover target). As a result, the HiRDB server process was forcibly terminated.

d800
A front-end server process failed in its attempt to connect to and retransmit a rollback request to a back-end server or dictionary server within the rollback instruction retransmission time limit specified in the pd_trn_rollback_watch_time operand. As a result, the front-end server process terminated abnormally.

000f
ff00
The HiRDB server process was forcibly terminated using the pdkill command (in UNIX, the OS kill command).

008b
An operating system stack overflow may have occurred during HiRDB operation. The following lists the causes and actions for a stack overflow:
Cause 1
Consider the following causes:

A user-defined routine that issues many calls or repeats them infinitely was executed

A column defined using a nesting of user-defined data types or many inheritances was specified in an SQL statement

There are too many nesting levels of IF or WHILE statements or scalar functions

Action for cause 1

Consider the above SQL causes and take action if possible.

Consider the value of the maxssiz kernel parameter, and increase the stack size.

Cause 2
Stack extension failed due to an operating system memory shortage.
Action for cause 2
Terminate unneeded programs, and increase the free memory area.

aa....aa: Name of the terminated server

bb....bb: Process ID of the terminated server

cc....cc: Service group name of the terminated server

However, for some server processes, there is no service group name. In that case, spaces are displayed.

dd....dd: Internal information

e:

N: Not on critical status

Y: On critical status

As HiRDB shares information among multiple processes, it references and updates the management table in the shared memory. If a process updating the shared memory terminates abnormally, the table information will lose integrity, and subsequent processing by other processes cannot be performed. For this reason, forcible termination in this type of processing space (referred to as the critical space) should be restricted as much as possible. If a failure occurs because abnormal termination in this space could not be suppressed, terminate HiRDB, and the integrity of the table information will recover when it is restarted.

ff....ff: Critical information

gg....gg: Process termination status returned with wait(2)

hhh: Server type (*** is displayed for any server other than a HiRDB server)

S: Terminates processing at the server resulting in the error and restarts the server, if necessary.

Action

gg....gg is c800:

Use the pdls command to determine if the status information of the unit of the relevant server became STOP(A). If the status information became STOP(A), a network failure may have occurred between the unit and the system manager. Stop the unit with the pdstop -z command, determine the cause of the network failure, and take appropriate action. Then, restart the unit.

gg....gg is c900:

Check whether a KFPS01820-E message was displayed where gg....gg is "c800" in the transmission source. If one was displayed, investigate the reason for the transmission source stopping, and take action.

gg....gg is d600 or d700:

Check the status of the server.

If the server is in the process of stopping, wait for it to finish stopping, and then start the server and re-execute the transaction.

If the server is in the process of starting, wait for the server to finish starting, and then re-execute the transaction.

If the server is in the process of switching over, wait for the server to finish switching over, and then re-execute the transaction.

Other than the above:

Refer to the message that was output before this message or to the troubleshooting information (dump, trace, etc.) to check the cause of the server termination, and take appropriate action. Then, restart the server, if necessary. Troubleshooting information is not output if gg....gg is c000, c100, c200, c300, c400, c500, c600, c700, c800, c900, d000, d100, d200, d300, d500, d600, d700, or d800.

KFPS01821-E E+L

Unable to continue HiRDB unit processing because serious error occurred; stops HiRDB unit aaaa

HiRDB is being terminated because an error occurred and HiRDB processing cannot be resumed.

aaaa: Unit identifier

S: Upon termination of HiRDB, restarts HiRDB if possible.

O: Eliminate the cause of the error on the basis of the message that was output before this message. Restart HiRDB, if necessary.

KFPS01823-E E+L

System version invalid; stops unit startup

Because the system version is invalid, the unit is being terminated.

S: Cancels unit startup processing.

Action

Check the versions of library and server and restart.

KFPS01824-E E+L

HiRDB ID invalid; stops unit startup

An invalid HiRDB identifier was specified in the definition or no HiRDB identifier was specified.

S: Cancels unit restart processing.

O: Specify the correct HiRDB identifier and restart HiRDB.

KFPS01826-I L

HiRDB dir = aa....aaHiRDB vrs = bb....bbunit run ID = cc....ccHiRDB ID = ddddunit ID = eeee

Displays the environment in which the unit is being started normally. In the case of a unit restart, the previous environment is displayed.

aa....aa: HiRDB directory name

bb....bb: HiRDB version

If HiRDB is in the 64-bit mode, (64) is displayed after the version number.

When using a POSIX library version, (POSIX) is displayed after the version number.

Example: HiRDB version 07-00, POSIX library version, and 64-bit mode HiRDB:

'07-00(64)(POSIX)'

cc....cc: Unit run ID (if the pdstart -r command was used, 00....00 is displayed)

dddd: HiRDB identifier

eeee: Unit identifier

S: Resumes processing.

O: Check the execution environment.

KFPS01827-E E

Unit ID invalid; stops unit startup

An invalid unit identifier was specified in the definition, or no unit identifier was specified.

S: Cancels unit startup processing.

O: Specify the correct unit identifier in the unit control information definition and restart HiRDB.

KFPS01828-E E+L

System definition parameter aa....aa missing; stops unit startup

An operand required in the HiRDB system definition is missing.

aa....aa: Name of the operand required in the HiRDB system definition

S: Terminates abnormally.

Action

Add the required operand and restart HiRDB.

KFPS01829-E E

aa....aa invalid; stops unit startup

aa....aa for unit restart processing does not match the information used during normal startup.

aa....aa:

HiRDB dir:

HiRDB directory

HiRDB ID:

HiRDB identifier

Master file name:

First HiRDB file name in the master directory RDAREA

System Version:

System version

Unit ID:

Unit identifier

Server Number:

Number of servers

Utility exec mode:

Utility execution mode

S: Terminates abnormally.

Action

Revise the items indicated as the cause in aa....aa, and restart HiRDB.

System Version:

HiRDB version

HiRDB ID:

The pd_system_id operand of the system common definition

HiRDB dir:

The -d option of the pdunit operand of the system common definition

Unit ID:

The pd_unit_id operand of the unit control information definition

Master file name:

The pd_master_file_name operand of the system common definition

Server Number:

Number of pdstart operands specified in the system common definition or pd_mlg_msg_log_unit operands in the system common definition

Utility exec mode:

The pd_utl_exec_mode operand of the system common definition

KFPS01830-I L

Server aa....aa recovery process start

Recovery processing has started during a HiRDB server restart.

aa....aa: Server name

S: Resumes processing.

KFPS01831-I L

Server aa....aa recovery process end

Recovery processing during a HiRDB server restart has been completed.

aa....aa: Server name

S: Resumes processing.

KFPS01832-I E+L

Data replication restart. unit ID = aa....aa, reason code = bb....bb

HiRDB Datareplicator linkage has been restarted.

aa....aa: Unit identifier

bb....bb: Reason for restarting HiRDB Datareplicator linkage:

FORCE:

HiRDB Datareplicator linkage was established in the previous session, but HiRDB was started by the pdstart -i command.

STATUS:

Initialization or error occurred in the file for data linkage by HiRDB Datareplicator or in a HiRDB system status file.

S: Terminates HiRDB Datareplicator linkage and then restarts it.

Action

If necessary, initialize the file for data linkage by HiRDB Datareplicator and re-create the target database.

KFPS01833-E E+L

Cancels processing because the same command running

Another process is running the same command. This message might be output if the same command is executed immediately after this command terminates abnormally.
Also, if the standby-less system switchover (effects distributed) facility is being used and the pdstbegin operand is specified, this message might be output when the unit or server is started.

S: Terminates processing.

O: Revise the options specified in the command, and re-execute the command.

Action

After the command process terminates, re-execute the command. If the command terminates abnormally, wait a brief period before re-executing the command.

If this message was output when a unit or server using the standby-less system switchover (effects distributed) facility was started, use the pdls -d stj command to determine whether statistical information was output. If statistical information was not output, use the pdstbegin command to output statistical information.

KFPS01833-I E+L

Unable to continue data replication. unit ID=aaaa, reason code=bb....bb

The system was unable to continue HiRDB Datareplicator linkage.

aa....aa: Unit identifier

bb....bb: Reason for discontinuing HiRDB Datareplicator linkage:

DEFINITION:

HiRDB Datareplicator linkage was established in the previous session, but N was specified in the pd_rpl_init_start operand of the system common definition.

RPL_FILE:

An error occurred in the file for data linkage by HiRDB Datareplicator.

RPL_STATUS:

The file for data linkage by HiRDB Datareplicator was initialized.

S: Terminates data linkage and resumes HiRDB startup processing.

Action

To re-execute HiRDB Datareplicator linkage, eliminate the cause of the error, synchronize the target HiRDB, then execute the pdrplstart command to restart HiRDB Datareplicator linkage.

If HiRDB is to be terminated but HiRDB Datareplicator linkage is to be always established, specify Y in the pd_rpl_init_start operand in the system common definition.

If the reason code is RPL_STATUS or RPL_FILE, the KFPS04624-I message showing the server name is output before this message (KFPS01833-I) for each server in which the error occurred.

KFPS01834-E E+L

Error occurred in status file while data, duplication unit ID=aaaa reason code=bb....bb

Error was detected in the status file while using the HiRDB Datareplicator linkage facility.

aaaa: Unit identifier

bb....bb: Reason code:

COMMUNICATION: Inter-process communication error occurred

SERVER NOT UP: Status server process has not been started

I/O ERROR: I/O error occurred

OTHER: Other error occurred

S: Terminates HiRDB.

Action

Eliminate the cause of the error on the basis of the message that was output before this message.

KFPS01835-E E+L

Error found in system configuration for fall-back operation. reason code=aa....aa

The system definition regarding reduced activation operation contains an error.

aa....aa: Reason code

UNIT ID ERROR unit-identifier:

The unit identifier coded in the pd_start_skip_unit operand is not found in the system configuration.

DUPLICATE UNITID:

The same unit identifier cannot be specified multiple times in the pd_start_skip_unit operand.

MGR UNIT NOT SKIPPED:

A unit in which the System Manager is located cannot be specified in the pd_start_skip_unit operand.

DIC UNIT NOT SKIPPED:

A unit in which the Dictionary Server is located cannot be specified in the pd_start_skip_unit operand.

NECESSARY ONE FES FOR FALL-BACK:

Reduced activation operation requires one or more active front-end servers.

NECESSARY ONE BES FOR FALL-BACK:

Reduced activation operation requires one or more active back-end servers.

S: Terminates processing.

Action

Check the specification of the pd_start_level and pd_start_skip_unit operands and restart HiRDB.

KFPS01836-W E+L

Fall-back operation ignored, because of restarting with "pdstart aa"

When operating HiRDB with reduced activation, the aa option cannot be specified with the pdstart command. Specification of the reduced activation mode is ignored.

aa: pdstart command option

For details about pdstart command options, see the manual HiRDB Version 9 Command Reference.

S: Resumes processing.

Action

To perform reduced activation:

Execute the pdstart command without specifying the aa option.

To activate while specifying the aa option:

If a unit cannot be started, place it in startable status.

KFPS01837-I E+L

Unit startup skipping for fall-back operation. unit ID=aa....aa

The HiRDB system is started on a reduced activation basis by skipping the HiRDB unit indicated by the unit identifier.

aa....aa: Unit identifier

S: Resumes processing.

KFPS01838-W E+L

Fall-back operation ignored, because no startup skip HiRDB unit

This system configuration does not contain any units that can be skipped; the reduced activation operation mode is ignored.

S: Resumes processing.

Action

Change the pd_start_level operand in the system common definition to 0 (do not apply the reduced activation mode). To start the HiRDB on a reduced activation basis, change to a reduced-startup-capable system configuration by assigning front-end and back-end servers to multiple units.

KFPS01839-E E+L

Error found in system configuration for pd_system_expand_unit. unit=aaaa, reason code=bb....bb

The specification of the pd_system_expand_unit operand is invalid.

aaaa: Unit identifier

However, if bb....bb (reason code) is FES UNIT or BES UNIT, **** is displayed.

bb....bb: Reason code

UNIT ID ERROR:

The unit identifier described in the pd_system_expand_unit operand is not included in the system configuration.

DUPLICATE UNIT ID:

Identical unit identifiers were described multiple times in the pd_system_expand_unit. The same unit identifier cannot be described in this operand more than once.

MGR UNIT:

The unit with the system manager is specified in the pd_system_expand_unit operand.

DIC UNIT:

The unit with the dictionary server is specified in the pd_system_expand_unit operand.

FES UNIT:

Units with front-end servers exist in HiRDB when expansion units are excluded (all basic units).

BES UNIT:

Units with back-end servers exist in HiRDB when expansion units are excluded (all basic units).

S: Terminates processing.

Action

Perform one of the following actions as applicable, and then re-execute the pdconfchk command or HiRDB start processing:

If bb....bb (reason code) is UNIT ID ERROR or DUPLICATE UNIT ID:
Re-examine the pd_system_expand_unit operand specification and eliminate the cause of the error.

If bb....bb (reason code) is different from those mentioned above:
Re-examine the system configuration and eliminate the cause of the error.

KFPS01840-I L

Now terminating HiRDB unit aaaa

HiRDB is being terminated.

aaaa: Unit identifier

S: Resumes HiRDB processing.

KFPS01841-I S

HiRDB unit aaaa terminated, mode=bb....bb

HiRDB unit aaaa terminated. The termination mode is bb....bb.

aaaa: Unit identifier

bb....bb: Termination mode:

FORCE: Forced termination

NORMAL: Normal termination

PLAN: Planned termination

S: Terminates HiRDB processing.

KFPS01842-I L

Now terminating server aa....aa

Server is being terminated.

aa....aa: Name of the server being terminated

S: Resumes HiRDB processing.

KFPS01843-I S

Server aa....aa terminated

Server has been terminated.

aa....aa: Name of the terminated server

S: Resumes HiRDB processing.

KFPS01844-E E+L

Error occurred while terminating server aa....aa. reason code=bb....bb

An error occurred during server termination processing. Either the server could not be terminated, or the server abnormally terminated during termination processing.

aa....aa: Name of the server resulting in the error

bb....bb: Cause of the error:

ABNORMAL:

pdstop command was used to terminate HiRDB, but a server had not terminated normally.

ABORT:

Server terminated abnormally (pdstop).

ABORTING:

Server abnormal termination processing (pdstop -s) is underway.

COMMUNICATION:

Inter-process communication error occurred.

CRITICAL:

Forced termination has been placed on hold due to critical status.

EXIT:

System is inactive (there is no server), or termination processing is underway.

MEMORY:

Memory shortage occurred.

PROTOCOL:

pd_rpc_mainloop cannot be issued.

STARTING: Server is starting.

S: Resumes HiRDB processing.

O: Check whether there are servers that are not terminated. If there are servers that are not terminated, eliminate the cause of the error and terminate the servers again. Note that only forced termination (pdstop -s -f or pdstop -f) may be accepted, depending on the previous termination status.

KFPS01845-E E+L

Commands unable to enter because HiRDB inactive

Commands cannot be entered because HiRDB is inactive.

S: Terminates the entered command.

KFPS01846-E E+L

Unable to terminate the unit normally; some servers forced to terminate

The system cannot be terminated normally, because a server was terminated forcibly.

S: Terminates the command.

O: Restart the server indicated as ABNORMAL in the KFPS01844-E message and terminate it normally. Or, terminate the system forcibly.

KFPS01847-E E+L

Unable to terminate the unit; some servers being started or terminated

The system cannot be terminated, because a server is engaged in startup or termination processing.

S: Terminates the command.

O: Wait until the server startup or termination processing has been completed. Or, enter the pdstop -f command.

KFPS01849-W S+L

Now waiting for termination of server aa....aa

The system is waiting for termination of a server.

aa....aa: Name of the server for which the system is waiting for termination

S: Places system termination on hold until the displayed server has terminated.

O: Terminate the displayed server.

KFPS01850-I S

HiRDB system terminated. mode=aa....aa

The HiRDB system terminated. The termination mode is aa....aa.

aa....aa: Termination mode:

NORMAL: Normal termination

PLAN: Planned termination

FORCE: Forced termination

S: Terminates processing.

In the following cases, it is possible that a unit that is not the system manager did not terminate, even though this message was output:

The pdstop command did not terminate normally

Message KFPS05121-E or KFPS05227-W was output to the event log (in UNIX, syslogfile) on the unit where the system manager resides

Action

Before the next time HiRDB starts, check the event log (in UNIX, syslogfile) of the unit that is not the system manager to see whether message KFPS01841-I was output. If message KFPS01841-I was not output, the unit has not terminated. Take corrective action according to any other messages that were output.

KFPS01851-E E+L

Server aa....aa initialization error occurred; return code=bb....bb

A server initialization error occurred.

aa....aa: Server name in the HiRDB/Single Server or HiRDB/Parallel Server (front-end server)

bb....bb: Error code

S: In the case of a HiRDB/Single Server, terminates abnormally; in the case of the front-end server, sets the status displayed by the pdls command to SUSPEND.

Action

For a HiRDB/Single Server, re-execute the pdstart command; for a HiRDB/Parallel Server, execute the pdstart -a command.

KFPS01852-W E+L

Server aa....aa failed. process ID=bb....bb, service group name=cc....cc, run mode=dd....dd, critical state=e, critical mask=ff....ff, end state=gg....gg, server type=hhh

Server aa....aa stopped.
This message is output when you are using the facility for changing a process down message when canceling a transaction (by specifying Y in the pd_cancel_down_msgchange operand in the system definition), and the server stops for one of the reasons listed below. If you are not using the facility for changing a process down message when canceling a transaction, message KFPS01820-E is output rather than this message.

Client allocation was accompanied by a forcible termination request, causing the HiRDB server executing the transaction to terminate. (This applies to UAPs that use DBPARTNER or DABroker to access HiRDB and UAPs that use ODBC to access HiRDB. This also includes cases where the applicable UAP is stopped by pressing Ctrl+C on the keyboard.)

A UAP failed, causing the HiRDB server process executing the transaction to terminate. (If the XA interface is being used, this message is not changed.)

The pdcancel command was executed, causing the HiRDB server process executing the transaction to terminate (including utility server processes).

When control is on the HiRDB client side, a client environment definition PDSWAITTIME timeout was detected during a transaction, causing the HiRDB server process to terminate.

When control is on the HiRDB client side, a client environment definition PDSWATCHTIME timeout was detected not during a transaction, or when connected to a Windows edition HiRDB the system definition pd_watch_pc_client_time operand timeout was detected, causing the HiRDB server process to terminate.

The pdfgt command was executed, forcibly terminating the transaction and causing the HiRDB server process to terminate.

The facility for monitoring the free area for the system log file was used to specify safe in the system definition pd_log_remain_space_check operand, and the log size exceeded the threshold value, causing the HiRDB server process to terminate.

When a HiRDB server process failed due to an error, the server process terminated to perform transaction and utility recovery. (The server process that failed due to an error does not affect this message.)

For HiRDB/Parallel Server, when a unit was forcibly terminated, a unit shut down, or a system switchover occurred, the HiRDB server process terminated so another unit could perform transaction and utility recovery.

aa....aa: Terminated server name

bb....bb: Terminated server ID

cc....cc: Service group name of terminated server

However, for some server processes, there is no service group name. In that case, spaces are displayed.

dd....dd: Internal information

e:

N: Not in critical status

Y: In critical status

ff....ff: Critical information

gg....gg: Process termination status returned by wait(2) (for a HiRDB command, **** is displayed). For details, see KFPS01820-E.

hhh: Server type (if other than a HiRDB server, *** is displayed)

S: Reactivates the user server process as necessary. Does not terminate HiRDB (for HiRDB/Parallel Server, the unit) at this time.

O: If put is specified in the pd_cancel_dump operand, the error information is output. If the error information is not required, delete it.

KFPS01853-W E

Hostname = aa....aa, unable to execute cc....cc command, unit state not bb....bb

The system was unable to execute the entered command because the unit was not on status bb....bb at host aa....aa.

aa....aa: Name of the host where the system was unable to execute the command

bb....bb: Status in which command can be entered:

OFFLINE: Offline status

ONLINE: Online status

cc....cc: Name of the entered command

S: Terminates the command.

O: Reenter the command after the system or unit status is displayed. The pdstart command cannot be executed while the unit is active (or engaged in startup processing); the pdstop command cannot be executed while the unit is inactive (or engaged in termination processing). Check that the unit is inactive or active, as applicable, before entering the command.

This message is displayed when the unit status does not meet the command's execution requirements. This is similar to message KFPS01863-E, and whichever message is output, both the HiRDB processing and corrective action by the operator are the same.

KFPS01854-E E+L

Unable to start standby,online unit notup.

The running system unit did not start when the rapid system switchover facility was used to start the standby system.

S: Terminates HiRDB processing.

Action

Check if the running system unit started normally. When the running system unit starts normally, ACTIVE is displayed in STATUS of the pdls command execution results or the KFPS05210-I or KFPS05110-I message is output.

When using Hitachi HA Toolkit Extension, check if service processing for Hitachi HA Toolkit Extension started. If the running system unit started without service processing starting, both systems were started as standby systems. For details on how to start service processes, see the manual Hitachi HA Toolkit.

KFPS01855-E E+L

Unable to stop alternate server or original server aa....aa

The standby less system switchover facility cannot independently terminate alternate BES and normal BES.

aa....aa: Name of alternate BES or normal BES

S: Terminates processing.

Action

To stop alternate BES or normal BES, terminate the alternate BES unit or the normal BES unit.

KFPS01856-E E+L

Unable to stop server aa....aa by force ,server not bb....bb

Because server aa....aa is not bb....bb, it cannot be forcibly terminated.

aa....aa: Server name

bb....bb: Error cause

IN HAGROUP: Target standby-less system switchover (effects distributed) facility

ONLINE: Online

S: Terminates processing.

Action

Based on the cause of the error, take appropriate action.

Error cause is IN HAGROUP
Servers for which the standby-less system switchover (effects distributed) facility does not apply cannot be forcibly terminated. Revise the command option specification. To stop the server, execute a normal termination (pdstop -s command).

Error cause is ONLINE
The server may already be stopped. Execute the pdls command to check the running status of the server.

KFPS01857-E E+L

Operand combination invalid, operand=aa....aa

The combination of operands aa....aa specified in the system definition is invalid. If there are multiple invalid combinations in the system definition, this message is output multiple times.

aa....aa: Invalid combination of operand names

{pd_lock_uncommited_delete_data, pd_indexlock_mode|

pd_max_tmp_table_rdarea_no, pd_max_rdarea_no|

pd_max_tmp_table_rdarea_no, pd_max_temporary_object_no}

S: If this message is output during execution of the pdstart command, start processing terminates abnormally. After that, message KFPS00715-E is output with reason code=20, and HiRDB enters PAUSE status (the restarting of the process server process is suspended).

If this message was output during execution of the pdconfchk command, command processing terminates.

Action

Refer to the manual HiRDB Version 9 System Definitions to check consistency between operands, and then revise the specified value for each operand. Then, re-execute the command. Also, if this message is output during execution of the pdstart command, execute the pdconfchk once, check whether this message is output, and then re-execute the pdstart command.

KFPS01860-E E

Command format aa....aa invalid

Indicated command is invalid.

aa....aa: Format of the command:

pdstop [-f]: System termination command

pdstop [-f] -s server_name: Server termination command

pdstart: System startup command

pdstart -s server_name: Server startup command

S: Terminates the command.

O: Reenter the command.

KFPS01861-E E

Error occurred during command execution. reason code=aa....aa

A command error occurred.

aa....aa: Nature of the command error:

COMMUNICATION:

Inter-process communication error occurred.

DEFINE FILE:

Definition file error occurred.

INITIALIZING:

Command cannot be accepted because startup processing requested by pdstart is underway (reenter the command after HiRDB startup is completed).

MEMORY:

Memory shortage occurred.

PARAM:

Argument is invalid.

RPL STATUS:

HiRDB Datareplicator linkage startup or termination processing failed.

SERVER NAME LEN:

Length of the server name is invalid.

SHARED MEMORY:

Shared memory access failed.

STATUS:

Server addition or deletion failed.

TIMEOUT:

System initialization processing did not terminate within the specified time, or an invalid system definition was detected at the system server.

UTILITY:

The command cannot be received because the utility is running. Wait for the utility to terminate, and then re-execute the command.

S: Terminates the command.

O: Eliminate the cause of the error and reenter the command.

pdstop -s command:

Check for any server that has not terminated. Only the pdstop -s -f or pdstop -f command may be accepted, depending on the previous termination status.

SHARED MEMORY:

This message may be output when an operation command is entered while the system startup process is running. If necessary, re-execute the command.

TIMEOUT:

Perform the following procedure:

If HiRDB start processing continues, ignore this message except for the unit(s) displayed in the additional information of this message when 1 is specified to the pd_start_level operand in the system definition.

If the following conditions hold after this message is output, execute the pdstop -f command:
The pdstart command did not terminate and is not responding.
The command pdls -d ust shows a unit in STARTING status for an extended period of time.#

If an error message or a warning message is output to the event log (in UNIX, syslogfile) of the unit where the system manager resides before or after this message was output, follow the actions given in that message.

If an error message or a warning message is output to the event log (in UNIX, syslogfile) of the unit indicated in the additional information of this message before or after this message was output, follow the actions given in that message.

Increase the value specified in the pd_start_time_out operand.

Re-execute the pdstart command.

If the pdstart command outputs this message again after performing step 6, repeat steps 1 through 6.

#

Check whether a previously-executed pdstart command terminated abnormally, or was stopped using the OS's kill command or by a similar means.

RPL STATUS:

Take action on the basis of the message that was output immediately before.

COMMUNICATION:

Eliminate the cause of the error according to the description in Table 4-1 Frequently occurring causes and required action for RPC-related errors, and then re-execute the command.

KFPS01862-E E+L

Enter server name

Asks that a server name be entered.

S: Terminates the command.

O: Reenter the command with a server name entered as the command argument.

KFPS01863-E E

Hostname=aa....aa, unable to execute cc....cc command, unit state not bb....bb

Because the unit status at host aa....aa is not bb....bb, the command cannot be executed.

aa....aa: Name of the host at which the command could not be executed

bb....bb: Status in which the command can be executed:

OFFLINE: Offline

ONLINE: Online

cc....cc: Name of the entered command

S: Terminates the command.

O:

Reenter the command after the system or unit status is displayed. The pdstart command cannot be executed while the unit is active (or engaged in startup processing); the pdstop command cannot be executed while the unit is inactive (or engaged in termination processing). Check that the unit is inactive or active, as applicable, before entering the command.

On a system switchover configuration unit, if this message was output during execution of the pdstart command, the unit might be waiting for a running system to start. Use the HA monitor monshow command to check the status of the unit, and then take action depending on its state.

This message is displayed when the unit status does not meet the command's execution requirements. This is similar to message KFPS01853-W, and whichever message is output, both the HiRDB processing and corrective action by the operator are the same.

KFPS01864-E E+L

Timeout occurred during execution of command aa....aa

A command resulted in a timeout.

aa....aa: Command name:

pdstop: Termination command

S: Terminates the command.

Action

Determine the cause of the abnormal termination, and then restart HiRDB. In UNIX, if a dump was output to the core file, save the dump.

KFPS01865-E L

Server failed: cancels execution of aa....aa command

Server terminated abnormally, so command processing is being cancelled.

aa....aa: Name of the entered command

pdstop: System termination command

S: Terminates the command.

Action

Determine the cause of the abnormal termination, and then restart HiRDB. In UNIX, if a dump was output to the core file, save the dump.

KFPS01866-E E+L

Server aa....aa specified twice

The same name was specified more than once in a list of input commands.

aa....aa: Duplicated server name

S: Terminates the command.

O: Delete the duplicated name from the list of input commands and reenter the commands.

KFPS01867-E E

Unable to continue processing because shared memory unused

Because shared memory cannot be used, processing cannot continue.

S: Terminates the command.

O: Check whether or not the system is active and reenter the command.

KFPS01868-E E+L

Server name aa....aa invalid

Invalid server name was found.

aa....aa: Invalid server name

S: Terminates the command.

O: Correct the command argument and reenter the command.

KFPS01869-E E

Unable to accept the command because the unit failed or not installed

Because the system has not been installed or the system is inactive, the command cannot be accepted.

S: Terminates the command.

O: Check whether or not the system is active and reenter the command.

KFPS01870-E E+L

Unable to analyze the definition file due to insufficient memory

A memory shortage occurred in a process during definition file analysis processing.

S: Cancels definition file analysis processing.

Action

Reduce either the number of processes or the amounts of memory available to other processes and restart HiRDB.

KFPS01871-E E+L

Communication error occurred. server name=aa....aa, return code=bb....bb

A communication error occurred.

aa....aa: Name of the server resulting in the error

bb....bb: Return value set when error control return occurred

S: Cancels the corresponding server processing.

O: Eliminate the cause of the error on the basis of the message output before this message, then restart HiRDB, if necessary.

KFPS01872-I L

HiRDB is placed in the standby state

HiRDB has been placed in standby status.

S: Resumes processing.

KFPS01873-E L

HA monitor has been stopped

The HA monitor or the Hitachi HA Toolkit Extension is currently stopping.

S: Terminates abnormally.

O: Start the HA monitor or the Hitachi HA Toolkit Extension, and then restart HiRDB.

KFPS01874-E L

Cannot connect to HA monitor. reason=aa....aa

Connection cannot be established with the HA monitor or the Hitachi HA Toolkit Extension.

aa....aa: Reason that a connection could not be established with the HA monitor or the Hitachi HA Toolkit Extension

HA NOEXIST: The HA monitor or the Hitachi HA Toolkit Extension was not found or is inactive.

PDDIR LEN: The length of the character string set in the PDDIR environment variable exceeded the maximum.

DUPLICATE: An attempt was made to start another server with the same name.

S: Terminates abnormally.

O: Restart HiRDB after correcting the error.

KFPS01875-E L

System error detected during communication with HA monitor. error code=aaaa, detail code=bbbb

System error was detected during the HA monitor or Hitachi HA Toolkit Extension communication processing.

aaaa: Return code for the HA monitor or Hitachi HA Toolkit Extension

bbbb: Detail return code from the HA monitor or Hitachi HA Toolkit Extension

S: For units for which the standby-less system switchover facility is applicable, stops the server. Abnormally terminates any others.

Action

See the HA monitor or Hitachi HA Toolkit Extension message that was output before or after this message, and take appropriate action as indicated in the message. If no the HA monitor or Hitachi HA Toolkit Extension message was output, contact the customer support center.

KFPS01877-I L

HiRDB stop request issued from HA monitor; stops HiRDB. reason=aa....aa

HiRDB will be terminated because a HiRDB termination request was issued from the HA monitor or the Hitachi HA Toolkit Extension.

aa....aa: HiRDB's internal termination cause code (maintenance information)

S: Terminates abnormally.

O: See the HA monitor or Hitachi HA Toolkit Extension message.

KFPS01878-I L

HiRDB restart request issued from HA monitor; stops HiRDB temporarily. reason=aa....aa

HiRDB will be terminated temporarily because a HiRDB restart request was issued from the HA monitor or the Hitachi HA Toolkit Extension. If the HA monitor is being used, the running system unit was activated before the unit terminated.

aa....aa: HiRDB's internal termination cause code (maintenance information)

S: Takes one of the following actions, depending on the startup method used after termination:

Automatic startup: Terminates HiRDB, then starts it automatically.

Manual startup: Terminates HiRDB.

O: If manual startup is used after termination, enter the pdstart command to restart HiRDB.

If the HA monitor is being used, when the running system unit is started, it is possible that a KFPS01878-I or KFPS00715-E message will be output and the start will fail. If the running system unit cannot be started, use the following procedure to start it:

Determine whether the unit is stopped using the HA monitor's monshow command. (When the monshow command is executed, stopped systems are not displayed. If the status of a unit is displayed, this indicates that the unit is not stopped.)

Use the pdrpause command to restart the HiRDB process server process.

Use the pdstart command to start the running system unit.

KFPS01879-I L

HiRDB standby state released, status=aa

Standby status of HiRDB was released.

aa: HiRDB status code (maintenance information)

S: Continues processing.

KFPS01880-W E

Statistics already output stopped

The output of statistics information is already stopped.

S: Ignores the command that was entered.

O: Check whether statistics information is being output. Re-execute the pdstend command as necessary. To determine whether statistics information is being output, execute the pdls -d command.

When adding or changing specifications for the statistics information to be output to the statistics log file, use either the pdstbegin or pdstend command to specify the contents of the statistics information to be added or changed, and then execute the command.

KFPS01881-I E+S

Usage: pdstbegin{[-k statistics_type [,statistics_type]....] [-m time_interval] [-x host_name [,host_name]....] [-a| -s server_name[,server_name].... ] [-w]}

Displays the format of pdstbegin and pdstend commands.

KFPS01882-E E

Command argument invalid

A command argument is invalid. Or, an unnecessary argument was specified in the command.

S: Cancels command processing.

O: Correct the command argument and reenter the command.

KFPS01883-E E

Cancels processing because the same command running

This message is output in the following two cases:

The same command process is already running. This message might be output if a command is re-entered immediately after the command terminates abnormally.

This message might be output when a unit or server is started when both of the following conditions are satisfied:

The standby-less system switchover (effects distributed) facility is used

The pdstbegin operand is specified

S: If 1, terminates the command processing.

If 2, continues the command processing.

O: If 1, wait for the executing command process to terminate, and then re-enter the command. If the command terminates abnormally, re-enter the command after a while.

If 2, use the pdls -d stj command to determine whether output of the current statistical information has started. If output of statistical information has not started, execute the pdstbegin command to start the output of statistical information.

KFPS01884-E E

Statistics already output

Statistical information has already been output to the statistics log file.

S: Ignores the entered command.

O: To determine whether statistics information is being output, execute the pdls -d stj command. When adding or changing specifications for the statistics information to be output to the statistics log file, use either the pdstbegin or pdstend command to specify the contents of the statistics information to be added or changed, and then execute the command.

KFPS01885-E E

Cancels the comand because shared memory for statistics in server aa....aa unable to be allocated

Allocation of shared memory needed to obtain statistical information for server aa....aa failed, so the command's processing is being cancelled.

aa....aa: Name of the server for which allocation of shared memory was attempted

S: Cancels command processing.

O: Reenter the pdstbegin command without creating a statistics log file for the corresponding server.

KFPS01886-W R+S

Cancels system active statistics log output. reason code=aa....aa

System activity statistical information cannot be output to the log.

aa....aa: Reason code:

MAX PROCESSES:

The maximum number of server processes that can be started at the same time in HiRDB has been exceeded.

S: Resumes processing.

This statistical information will be output the next time system activity statistical information is output. This error does not affect HiRDB's current online activity.

Action

If MAX PROCESSES is displayed in the reason code, the specified maximum number of concurrently activated server processes (the pd_max_server_process operand) may be too small. Re-evaluate the specified value of the pd_max_server_process operand, and then set the correct value.

KFPS01888-W E+L

Too small aa....aa. pd_max_users assumed. server=bb....bb

Value specified in pd_max_bes_process or pd_max_dic_process was less than the value of pd_max_users in the system common definition. The system assumes the value of pd_max_users.

aa....aa: Name of the definition for which the value of pd_max_users was assumed:

pd_max_bes_process:

Maximum number of startup processes in the back-end server

pd_max_dic_process:

Maximum number of startup processes in the dictionary server

bb....bb: Server name

S: Resumes processing.

Action

Check the value specified for the corresponding pd_max_bes_process or pd_max_dic_process.

KFPS01889-E E+L

Error occurred in HiRDB Datareplicator while executing aa....aa. server ID=bb....bb, function value=cc....cc, errno=dddd

Error occurred in HiRDB Datareplicator linkage.

aa....aa: Name of abnormally terminated subroutine

bb....bb: Server name

cc....cc: Reason code set by the abnormally terminated subroutine:

INTERNAL ERROR:

Error occurred during internal processing.

SEQUENCE ERROR:

Error was detected in the function issuance order.

PARAMETER ERROR:

Argument was invalid.

FILE ERROR: HiRDB-Datareplicator-directory-name:

File for data linkage was invalid (up to 64 characters of the directory name are displayed).

SYSTEM CALL (system-call-name) ERROR:

System call error occurred.

FILE LOCK ERROR

A reference privilege or update privilege could not be acquired for the data linkage file.

dddd: errno value specified by the abnormally terminated subroutine

S: Suspends HiRDB Datareplicator linkage if HiRDB is starting. Continues HiRDB Datareplicator linkage if the pdls -d rpl command is running or if HiRDB is operating.

Action

If the reason code is FILE ERROR or SYSTEM CALL ERROR, check the Datareplicator execution environment of HiRDB and HiRDB Datareplicator. If the pdls -d rpl command was executed during system switchover of the unit, this message may be output. Re-execute the command after the system switchover is complete.

Also, if this message is output while HiRDB is running, refer to the event log (in UNIX, syslogfile) or execute the pdls -d rpl command to check the data linkage status. If the KFPS05141-I message is not output, data linkage was not interrupted, so you do not need to recover data linkage. If any other reason code is displayed, contact the customer support center.

KFPS01890-I L+S

Statistics: ID=aa....aa, number of events=bb....bb, average=cc....cc, max=dd....dd, min=ee....ee

Displays statistical information about an event.

aa....aa: Event ID

bb....bb: Number of times this event occurred

cc....cc: Average value of the event

dd....dd: Maximum value of the event

ee....ee: Minimum value of the event

S: Terminates the command.

KFPS01891-E E+L

Invalid value for variable aa....aa in definition file.

An operand specification value in the HiRDB system definition contains an error.
aa....aa: Name of the HiRDB system definition operand

S: Terminates the HiRDB startup processing.

Action

Review the value specified in the aa....aa operand and start HiRDB.

KFPS01892-E E

aa....aa invalid; stops unit startup. server ID=bb....bb, old value=cc....cc, new value=dd....dd

The unit cannot be restarted because a specification value in operand aa....aa was changed.
The value of operand aa....aa cannot be changed after abnormal termination or forced termination.

aa....aa: Name of the HiRDB system definition operand

bb....bb: Server name

if aa....aa is a system common definition operand or a unit control information definition operand, ******** is displayed.

cc....cc: Old value of operand aa....aa

dd....dd: New value of operand aa....aa

S: Terminates startup processing for the unit.

Action

Take a corrective actions according to the information displayed in aa....aa:

Displayed as pd_max_users:

Reset the value of the pd_max_users operand to the previous value (the value of cc....cc) and restart the unit.

Displayed as pd_max_bes_process or pd_max_users:

Take action according to the following table:

Condition | Action
pd_max_bes_process operand omitted | Reset the value of the pd_max_users operand to the previous value (the value of cc....cc) and restart the unit.
pd_max_bes_process operand specified | cc....cc > pd_max_users | Reset the value of the pd_bes_process operand to the previous value (the value of cc....cc) and restart the unit.
cc....cc pd_max_users | Reset the values of the pd_max_users and pd_max_bes_process operands to the previous value (the value of cc....cc) and restart the unit.

Note

When changing the value of the pd_max_bes_process operand, determine which server definition is to be changed on the basis of the server name indicated in bb....bb.

Displayed as pd_max_dic_process or pd_max_users

Take action according to the following table:

Condition | Action
pd_max_dic_process operand omitted | Reset the value of the pd_max_users operand to the previous value (the value of cc....cc) and restart the unit.
pd_max_dic_process operand specified | cc....cc > pd_max_users | Reset the value of the pd_max_dic_process operand to the previous value (the value of cc....cc) and restart the unit.
cc....cc pd_max_users | Reset the values of the pd_max_users and pd_max_dic_process operands to the previous value (the value of cc....cc) and restart the unit.

When pd_max_list_users is displayed:

Return the value of the pd_max_list_users operand to what it was before the change (value cc....cc). Then, restart the unit.

When pd_max_list_count is displayed:

Return the value of the pd_max_list_count operand to what it was before the change (value cc....cc). Then, restart the unit.

When pd_max_reflect_process_count is displayed:

Return the value of the pd_max_reflect_process_count operand to what it was before the change (value cc....cc). Then, restart the unit.

When pd_ha_max_act_guest_servers is displayed:

Return the value of the pd_ha_max_act_guest_servers operand to the value before the change (value of cc....cc). Then, restart the unit.

KFPS01893-E E

Error occurred during pd_ha_restart_failure command execution

The command specified in the pd_ha_restart_failure operand of the unit control information definition cannot be started or it terminated abnormally.

S: Terminates unit startup processing

Action

Check the command and the definition.

Either enter the pdstart command and restart the unit or switchover systems.

KFPS01894-I L

Master_file_name = aa....aa

Displays the environment of a normally started unit (for a restarted unit, displays its previous environment).

aa....aa: First HiRDB file name in the master directory RDAREA

S: Resumes processing.

O: Check the execution environment.

KFPS01895-E E

Error found in system definition, file=aa....aa, line=bb....bb, option=c

An error was found in the indicated definition.

aa....aa: Definition file name

bb....bb: Line number

c: Option name

S: Terminates abnormally.

O: Contact the HiRDB system administrator.

Action

Correct the error in the definition file and re-execute HiRDB.

KFPS01896-E E+L

Error found in system configuration. reason code=aa....aa

An error was found in the specification of an operand related to system configuration specified in the HiRDB system definition.

aa....aa: Reason code

S: Terminates abnormally.

Action

Take action according to the reason code, and then start HiRDB.

Reason code
Action

CURRENT PDDIR ERR directory-name
The HiRDB directory name specified in the environment variable PDDIR and the HiRDB directory specified in the -d option of the pdunit operand do not match. Make the HiRDB directory names match.
Note that the displayed directory name is the HiRDB directory name specified in the -d option, and that a maximum of only 63 characters are displayed.

CURRENT UNIT ID ERR unit-identifier

The unit identifier specified in the -u option of the pdstart operand and the unit identifier specified in the -u option of the pdunit operand do not match. Make the unit identifiers match.

The unit identifiers specified in the -u option of the pdstart operand were duplicated. Take action to resolve the unit identifier duplication in the system.

DUPLICATE DIC
Multiple DICs are specified in the -t option of the pdstart operand. Specify only one DIC in the system.

DUPLICATE HOSTNAME host-name
The host name specified in the -x or -c option of the pdunit operand is the same as the host name specified in the -x or -c option of another pdunit operand.
Specify a different host name in the -x and -c options of each pdunit operand.

DUPLICATE HOSTNAME unit-identifier
The host names specified in the -x option and -c option of the pdunit operand were duplicated. Specify the host name of the primary system in the -x option and specify the host name of the secondary system in the -c option. Specify different host names for the primary system and secondary system. When not using the system switchover facility, do not specify the -c option.

DUPLICATE MGR
Multiple MGRs are specified in the -t option of the pdstart operand. Specify only one MGR in the system.

DUPLICATE PDDIR directory-unit-identifier
HiRDB directories specified in the -d option of the pdunit operand were the same. For mutual system switchover configurations, specify a different HiRDB directory for each unit.
Windows does not distinguish between upper case and lower case letters, so errors occur when HiRDB directory names differ only in the case of the letters in the name.

DUPLICATE SERVER ID server-name
The server names specified in the -s option of the pdstart operand were the same. Take action to resolve the server name duplications in the system. Windows does not distinguish between upper case and lower case letters, so errors occur when HiRDB directory names differ only in the case of the letters in the name.

DUPLICATE UNIT ID unit-identifier
The unit identifiers specified in the -u option of the pdunit operand were the same. Take action to resolve the unit identifier duplications in the system.

FES SAME UNIT
Multiple front-end servers were defined in the same unit. Only one front-end server can be defined in a unit.

INVALID Datareplicator environment
The execution environment of HiRDB Datareplicator is invalid. Check the execution environment of HiRDB Datareplicator.

MISSING pdunit host-name

If the pdunit operand is specified:

The host name specified in the -x option of the pdstart operand, or the unit identifier specified in the -u option of the pdstart operand, are not specified in the pdunit operand. Specify the host name or unit identifier in the pdunit operand. Note that this is case sensitive (uppercase and lowercase letters are distinguished).

If the pdunit operand is omitted:

The standard host name is not specified in the pdstart -x option. Specify the standard host name in the pdstart -x option (if the pdunit operand is omitted, the pdstart -u option cannot be specified).

NEED TO SPECIFY pd_rpl_hdepath
The pd_rpl_hdepath operand is not specified. When using HiRDB Datareplicator, specify the extracted HiRDB Datareplicator directory in the pd_rpl_hdepath operand.

NEED TO SPECIFY pdunit
-c host-name
The -c option of the pdunit operand was not specified. Specify this option for system switchovers that do not inherit IP addresses.
On a unit using standby-less system switchover (effects distributed), this message is sometimes output if N is specified in the pd_ha_ipaddr_inherit operand of the system common definition or unit control information definition. In this case, omit the pd_ha_ipaddr_inherit operand.
If the system contains units using standby-less system switchover (effects distributed) and switchover units that do not inherit IP addresses, omit the pd_ha_ipaddr_inherit operand in the system common definition and the pd_ha_ipaddr_inherit operand in the unit control information definition on the units using standby-less system switchover (effects distributed), and specify N in the pd_ha_ipaddr_inherit operand in the unit control information definition on the switchover units that do not inherit IP addresses.

NO BES
There is no back-end server specification. The system requires at least one back-end server. Re-evaluate specification of the -t option in the pdstart operand.

NO DIC
There is no directory server specification. The system requires at least one directory server. Re-evaluate specification of the -t option in the pdstart operand.

NO FES
There is no front-end server specification. The system requires at least one front-end server. Re-evaluate specification of the -t option in the pdstart operand.

NO MGR
There is no system manager specification. The system requires one system manager. Re-evaluate specification of the -t option in the pdstart operand.

OUT OF SYSTEM
The host name of the host that executes HiRDB was not specified in the -x option of the pdunit operand. Re-evaluate the specification of the -x option in the pdunit operand.

SDS SAME UNIT
Multiple single servers were defined in the same unit. Re-evaluate the specification of the pdstart operand.

UNABLE TO SPECIFY pdunit -c unit-identifier
The -c option of the pdunit operand can be specified only when using a system switchover facility that does not inherit IP addresses. Delete the -c option when it does not apply.

UNKNOWN HOSTNAME host-name (/etc/hosts) unit-identifier
The host name specified in the pdunit operand cannot be resolved. Change the host name specified in the pdunit operand, or else add it to the hosts file or register it on a DNS so that the name will be resolved. If a DNS is used, this reason code message is output even if the DNS is set correctly. In this case, ignore the message. In HiRDB Single Server, **** might be output as the unit identifier.

INVALID pdcltgrp client-group-name
The group name specified in the -g option of the pdcltgrp operand is invalid. Re-evaluate the specification of the -g option. For details about client groups, see the HiRDB Version 9 System Operation Guide.

NUMBER OF pdcltgrp EXCEEDS THE LIMIT
The number of user-specified pdcltgrp operand specifications exceeded 10. Reduce the number of specifications to 10 groups or less.

EXCEEDED pd_max_users
The total number of minimal-guarantee connections for each client group specified by the pdcltgrp operand exceeded the value of the pd_max_users operand. Either decrease the total number of minimal-guarantee connections or increase the value of the pd_max_users operand.

DUPLICATE pdcltgrp client-group-name
The client group name specified by the pdcltgrp operand was duplicated. Take action to resolve the client group name duplication.

NUMBER OF SERVER EXCEEDS THE LIMIT
The number of servers exceeded the limit of servers in a unit (34). Re-evaluate the specification of the pdunit operand and reduce the number of servers defined in a unit.

UNABLE TO SPECIFY pd_ha_agent
An error was found in the preconditions for using the rapid system switchover facility. Specify the following operands to use the rapid system switchover facility:

pd_ha = use

Do not specify pd_ha_unit

pd_ha_ipaddr_inherit = N

pd_ha_acttype = server

If the standby-less system switchover or standby-less system switchover (effects distributed) is used, the following operands must be specified. Check the contents specified for each operand.

pd_ha = use

pd_ha_unit is not specified.

pd_ha_acttype = server

INVALID pd_max_users_wrn_pnt operand
An error was found in the specification of the pd_max_users_wrn_pnt operand. Specify a value in the specifiable range.

INVALID pd_aud_file_wrn_pnt operand
An error was found in the specification of the pd_aud_file_wrn_pnt operand. Specify a value in the specifiable range.

NUMBER OF CONNECT USERS EXCEEDS THE LIMIT
The sum of the values specified in the pc_max_users operand and the pd_max_reflect_process_count operand (considered to be 0 if no value is specified) exceeds the maximum that can be specified in the pd_max_users operand. Take corrective action so that this sum is equal to or less than the maximum that can be specified in the pd_max_users operand.

NUMBER OF PROCESSES EXCEEDS THE LIMIT, server = server-name

The applicable server is a back-end server:
The sum of the values specified in the pd_max_bes_process operand and the pd_max_reflect_process_count operand (considered to be 0 if no value is specified) exceeds the maximum that can be specified in the pd_max_bes_process operand. Take corrective action so that this sum is equal to or less than the maximum that can be specified in the pd_max_bes_process operand.

The applicable server is a dictionary server:
The sum of the values specified in the pd_max_dic_process operand and the pd_max_reflect_process_count operand (considered to be 0 if no value is specified) exceeds the maximum that can be specified in the pd_max_dic_process operand. Take corrective action so that this sum is equal to or less than the maximum that can be specified in the pd_max_dic_process operand.

NEED TO SPECIFY pd_rise_pairvolume_combination
There is no specification of the pd_rise_pairvolume_combination operand. If Y is specified in the pd_rise_use operand, specify the pd_rise_pairvolume_combination operand.

NEED TO SPECIFY pd_hostname
There is no pd_hostname operand specification. If Y is specified in the pd_rise_use operand, specify the pd_hostname operand.

INVALID pd_mode_conf
The specification of the pd_mode_conf operand is invalid. If Y is specified in the pd_rise_use operand, specify MANUAL1 or MANUAL2 in the pd_mode_conf operand.

INVALID pd_dbsync_point
The specification of the pd_dbsync_point operand is invalid.
If hybrid or syssync is specified in the pd_rise_pairvolume_combination operand, commit cannot be specified in the pd_dbsync_point operand.

NEED TO SPECIFY pd_rise_fence_level
There is no specification of the pd_rise_fence_level operand. If Y is specified in the pd_rise_use operand and sync, hybrid, or syssync is specified in the pd_rise_pairvolume_combination operand, the pd_rise_fence_level operand must be specified.

INVALID KIND
The specification of the -k option of the pdstart operand in the system common definition is invalid. Alternatively, multiple function names are specified in the -k option. Revise the -k option.

INVALID pdstart -k stls
The specification of the -k option of the pdstart operand in the system common definition is invalid. Possible causes are as follows:

A server other than a front-end server is specified in the pdstart -t operand.

The operand pdstart -k stls is specified on a unit where there is a server other than a front-end server.

Make sure that the operand pdstart -k stls is not specified for a server on a unit that also holds a server other than a front-end server.

INVALID pdstart -c
The alternate BES name specified in the system common definition pdstart -c operand is invalid. Revise the alternate BES name specified in the system common definition pdstart -c operand. This reason code may be accompanied by maintenance information.

INVALID pdstart -t
A server other than a back-end server was defined on the unit specified in the system common definition pdstart -c operand. A server other than a back-end server cannot be defined on a unit specified in the pdstart -c operand. Revise the pdstart -c operand specification and the server type on the alternate BES unit. This reason code may be accompanied by maintenance information.

INVALID HiRDB port: error about host-name:host-name
Different port numbers (the -p option of the pd_name_port operand or pdunit operand) are specified for the normal BES unit and the alternate BES unit where the standby-less system switchover facility is applied.
For units using standby-less system switchover, specify the same HiRDB port number (the -p option of the pd_name_port operand or pdunit operand) on the normal BES unit and alternate BES unit.

INVALID scd port: error about host-name:host-name
Different scheduler port numbers (the -s option of the pd_scd_port operand or pdunit operand) are specified for the normal BES unit and the alternate BES unit where the standby-less system switchover facility is applied.
For units using standby-less system switchover, specify the same scheduler port number (the -s option of the pd_scd_port operand or pdunit operand) on the normal BES unit and alternate BES unit.

INVALID tm port: error about host-name:host-name
Different transaction server port numbers (the -t option pd_trn_port operand or pdunit operand) are specified for the normal BES unit and the alternate BES unit where the standby-less system switchover facility is applied.
For units using standby-less system switchover, specify the same transaction server port number (the -t option of the pd_trn_port operand or pdunit operand) on the normal BES unit and alternate BES unit.

NO SERVER IN HAGROUP UNIT unit-identifier
There is no primary system server among the units in the HA group. Define primary system server.

INVALID SERVER IN UNIT unit-identifier
There is a server other than a back-end server defined among the units of an HA group or in normal BES units for which server was specified in the pd_ha_agent operand. Define only back-end servers among the units of an HA group or in normal BES units for which server was specified in the pd_ha_agent operand.

INVALID pd_ha_agent unit-identifier
For the units in an HA group, activeunits was not specified in the pd_ha_agent operand. Specify activeunits in the unit control information definition pd_ha_agent operand of the unit specified in the pdhagroup -u operand.

NEED TO SPECIFY pdstart -g: server-name
There is no HA group specification among the servers of the units in an HA group. Specify the HA group identifier that the unit belongs to in the pdstart -g operand for the servers in the units specified in the pdhagroup -u operand.

INVALID pdstart -g: server-name
The servers of the units in the HA group are not included in the same HA group as the unit. Specify the HA group identifier that the unit belongs to in the pdstart -g operand for the servers in the units specified in the pdhagroup -u operand.

INVALID pdhagroup -u unit-identifier
The unit specified in the pdhagroup -u operand was not defined in the pdunit -u operand. Revise the specification of the pdhagroup -u operand and the pdunit -u operand.

INVALID HiRDB port: error about HA group-identifier
The HiRDB port numbers (the -p option of the pd_name_port operand or pdunit operand) of the units in an HA group are different.
Specify the same HiRDB port number (the -p option of the pd_name_port operand or pdunit operand) for all units in the HA group.

INVALID scd port: error about HA group-identifier
The scheduler port numbers (the -s option of the pd_scd_port operand or pdunit operand) of the units in an HA group are different.
Specify the same scheduler port number (the -s option of the pd_scd_port operand or pdunit operand) for all units in the HA group.

INVALID trn port: error about HA group-identifier
The transaction server port numbers (the -t option pd_trn_port operand or pdunit operand) of the units in an HA group are different.
Specify the same transaction server port number (the -t option pd_trn_port operand or pdunit operand) for all units in the HA group.

INVALID pdunit -d: error about HA group-identifier
The HiRDB directories of the units in the HA group are different. Specify the same HiRDB directory in the pdunit -d operand for all units in the HA group.

UNABLE TO SPECIFY pdstart -g server-name
The pdstart -g operand was specified for servers in units not included in the HA group. The pdstart -g operand can only be specified for servers in units specified in the pdhagroup -u operand. Revise the pdhagroup -u operand and the pdstart operand.

NEED TO ADD unit-identifier TO pdhagroup -u
Units for which activeunits was specified in the pd_ha_agent operand were not specified in the pdhagroup -u operand, and activeunits is specified in the unit control information definition pd_ha_agent operand of units not included in the HA group. Revise the pdhagroup -u operand and the pd_ha_agent operand.

UNABLE TO SPECIFY pd_ha_max_act_guest_servers
The pd_ha_max_act_guest_servers operand was specified for units not included in the HA group. The pd_ha_max_act_guest_servers operand can be specified only for units specified in the pdhagroup -u operand. Revise the pdhagroup -u operand and the pd_ha_max_act_guest_servers operand.

UNABLE TO SPECIFY SAME SYSTEM pdstart -c, pdstart -g
A server with the pdstart -c operand specified and a server with the pdstart -g operand specified are mixed within the same system. The standby-less system switchover (1:1) cannot be mixed in the same system with the standby-less system switchover (effects distributed). Revise the pdstart operand.

INVALID pd_rpl_reflect_mode operand
The specification of the pd_rpl_reflect_mode operand is invalid.
With HiRDB/Single Server, uap cannot be specified in the pd_rpl_reflect_mode operand. Refer to the manual HiRDB Datareplicator Version 8, revise the transaction reflection formula, and revise the system common definition pd_rpl_reflect_mode operand.

INVALID pd_hostname
The host name specified in the pd_hostname operand cannot be converted to an IP address. Check the following items, and correct any error:

Error in the hosts file setting

Invalid privilege to the hosts file

Setting error in the file that contains the DNS or NIS settings (nsswitch.conf, resolv.conf, etc.)

Invalid privilege to the file that contains the DNS or NIS settings (nsswitch.conf, resolv.conf, etc.)

Also, if DNS or NIS is being used, a communication error might occur with the DNS server or NIS server.

INVALID pd_aud_max_generation_size
The specification of the pd_aud_max_generation_size operand is invalid.
In the pd_aud_max_generation_size operand, specify a value sufficient to store at least one audit trail record. For the maximum length of audit trail records, see the description of the pd_aud_max_generation_size operand in the manual HiRDB Version 9 System Definition.

INVALID pd_aud_async_buff_size
The specification of the pd_aud_async_buff_size operand is invalid.
In the pd_aud_async_buff_size operand, specify a value greater than the maximum audit trail record size. For the maximum length of audit trail records, see the description of the pd_aud_max_generation_size operand in the manual HiRDB Version 9 System Definition.

DUPLICATE pdhagroup -g HA group-identifier
The HA group identifier specified in the -g option of the pdhagroup operand is the same as the HA group identifier specified in the -g option of another pdhagroup operand.
In the pdhagroup -g operand of each HA group, specify a HA group identifier that is unique in the system.

DUPLICATE pdhagroup -u unit-identifier
The unit identifier specified in the -u option of the pdhagroup operand is the same as the unit identifier specified in the -u option of another pdhagroup operand.
Take action to resolve the unit identifier duplications in different HA groups.

UNABLE TO SPECIFY SAME UNIT pdxds, 1:1 standby-less
The pdxds operand and 1:1standby-less system switchover are mixed within the same system.
XDS and 1:1standby-less system switchover cannot be mixed in the same system. Revise the pdxds, pd_ha_agent, and pd_ha_unit operands in the system common definition.

UNABLE TO SPECIFY SAME UNIT pdxds, effects distributed standby-less
The pdxds operand and standby-less system switchover (effects distributed) are mixed within the same system.
XDS and standby-less system switchover (effects distributed) cannot be mixed in the same system. Revise the pdxds, pd_ha_agent, and pd_ha_unit operands in the system common definition.

UNABLE TO SPECIFY SAME SYSTEM pdxds, real time SAN replication
The pdxds operand and Real Time SAN Replication are mixed within the same system.
XDS and Real Time SAN Replication cannot be mixed in the same system. Revise the pdxds and pd_rise_use operands in the system common definition.

DUPLICATE pdxds -s XDS-server-name
The XDS server name in the pdxds -s operand is duplicated.
In the pdxds -s operand in the system common definition, specify an XDS server name that is unique in the system.

DUPLICATE pdstart -s, pdxds -s XDS-server-name
The XDS server name in the pdxds -s operand is the same as the server name in the pdstart -s operand.
In the pdxds -s operand in the system common definition, specify an XDS server name that is different from the server name in the pdstart -s operand.

INVALID SERVER pdxds -r server-name
The server name in the pdxds -r operand does not exist in the pdstart operand.
Specify the server name in the pdstart -s operand in the pdxds -r operand in the system common definition.

KFPS01897-E E

Error found in system definition. file=aa....aa, line=bb....bb

An error was found in the indicated definition.

aa....aa: Definition file name

bb....bb: Line number

S: Terminates abnormally.

Action

Correct the definition file and re-execute HiRDB.

KFPS01898-E E+L

Error occurred while starting server, server ID=aa....aa, server type=bbb, reason code=cc....cc

An error occurred while starting a HiRDB server.

aa....aa: Server name

bbb: Type of server

cc....cc: Cause:

CONFIGURATION:

Error occurred during definition analysis.

SERVER INIT ERROR:

Error occurred during initialization of the HiRDB server.

SERVER START ERROR:

Error occurred during activation of a server process.

S: CONFIGURATION displayed as the cause:

Resumes processing.

SERVER INIT ERROR or SERVER START ERROR displayed as the cause:

Terminates the unit abnormally.

Action

For errors that occurred during definition analysis, correct the content of the definition file and use the server start command to start the server on which the error occurred. If the error occurs when initializing the HiRDB server or activating a server process, take action according to the messages outputbefore or after this message.

KFPS01899-E E

Error occurred while initializing server, server ID=aa....aa, server type=bbb, reason code=cc....cc

An error occurred while initializing a HiRDB server.

aa....aa: Server name

bbb: Type of server

cc....cc: Cause:

CONFIGURATION: Error occurred during definition analysis.

S: Terminates abnormally.

Action

Correct the error in the definition file and re-execute HiRDB.

KFPS01902-E E

Unable to start message log service due to insufficient memory

The message log server process cannot be started due to insufficient process private area.

S: Cancels processing.

Action

Terminate any unneeded processes and restart HiRDB.

KFPS01903-E E

Unable to start message log service due to communication failure

The message log server process cannot be started due to a communication error.

S: Cancels processing.

Action

If an error is found in the access privileges or settings defined in the hosts file, correct the hosts file. Check for the cause of the communication error, eliminate the cause, and then restart HiRDB.

The port number specified in the -m option of the pd_mlg_port operand or pdunit operand might be the same as the port number of another definition or program. If they are the same, revise the values in the port number settings so that they are not duplicated, and then restart HiRDB.

KFPS01910-I E+L

Message log file changed over from aa....aa to bb....bb

The message log obtained after this message will be output to the indicated message log file.

aa....aa: Name of the current message log file#

bb....bb: Name of the new message log file#

Note

To retain multiple generations of the message log file, save the current message log file immediately after output of this message.

#: The message log file name is displayed by the absolute path. If the path exceeds 89 characters, only the last 89 characters are displayed.

S: Resumes processing.

KFPS01911-E E+L

Error occurred while preprocessing message log file aa....aa

An error occurred in the message log file due to the cause indicated in the KFPO00107-E message (reporting a start or open system call error) that was output before this message.

aa....aa: Name of the message log file resulting in the error

The message log file name is displayed by the absolute path. If the path exceeds 165 characters, only the last 165 characters are displayed.

S: Cancels processing.

Action

Eliminate the cause of the message log file error and restart HiRDB.

KFPS01912-E E+L

Error occurred while opening message log file aa....aa

A message log file open error occurred due to the cause indicated in the KFPO00107-E message (reporting an open system call error) that was output before this message.

aa....aa: Name of the message log file resulting in the error

The message log file name is displayed by the absolute path. If the path exceeds 171 characters, only the last 171 characters are displayed.

S: Cancels processing.

Action

Eliminate the cause of the message log file error and restart HiRDB.

KFPS01913-E E

Error occurred during message log file changeover; message log output destination changed to standard error output

An error occurred during message log file swapping. The output destination of the message log is being changed to the standard error.

S: Changes the output destination of the message log to standard error, and then continues processing.

Action

Check the KFPS01912-E message output before this message for the cause of the error and correct the error so that the message log file can be opened.

KFPS01914-E E

I/O error occurred in message log file aa....aa; message log output destination changed to standard error output

Because an I/O error occurred in log file aa....aa, the message log output destination was changed to the standard error.

aa....aa: Name of the message log file resulting in the error

S: Changes the output destination of the message log to standard error, and then continues processing.

Action

Check the cause of the I/O error (such as a full disk) and correct the error.

KFPS01915-I E+L

Message log output destination changed from standard error output to message log file aa....aa

A message log file was opened successfully (by retry), and the message log output destination was changed from the standard error to the message log file.

aa....aa: Name of the message log file after change

The message log file name is displayed by the absolute path. If the path exceeds 131 characters, only the last 131 characters are displayed.

S: Changes the message log output destination to the message log file and resumes processing.

KFPS01920-E E+L

Unable to handle program version aa....aa that requested message log output in this system. request source process ID=bb....bb

The version of the message log service function that is being used by the program that issued the message log output request does not match the version of the message log server process. For this reason, the message log output request cannot be accepted.

aa....aa: Version of the message log service function that is being used by the program that issued the message log output request

bb....bb: Process ID of the source requesting output of message log

S: Resumes processing.

Action

If the program requesting output of message log is a system program, contact the customer support center.

KFPS01921-I L

"Extended SYSLOG function" applied, func=aa....aa, code=bb

The extended syslog facility is applied.

aa....aa: Facility that applies one of the following

High-availability: Improved reliability of the syslogfile

High-availability and Code conversion: syslogfile with improved reliability and syslogfile character encoding conversion (converts SJIS to UTF-8)

bb: Detail code

01: The character encoding# used by HiRDB is not SJIS.

02: The character encoding# used by HiRDB is SJIS.

03: The character encoding conversion of syslogfile cannot be used for one of the following reasons:

The Hitachi encoding conversion has not been installed.

The Hitachi encoding failed to initialize. Memory may be insufficient.

04: The character encoding# that HiRDB uses is SJIS. However, because the extended syslog facility does not support a character encoding conversion facility, syslogfile character encoding conversion cannot be used.

#

The character encoding that HiRDB uses is a character code classification in which the -c option of the pdsetup command is specified.

S: Continues processing.

Action

If you want to use syslogfile character encoding conversion and you are on an OS that supports it, detail codes and actions are shown below.

Detail code
Action

01
02
No action is necessary.

03

If Hitachi encoding conversion has not been installed:

Stop HiRDB, install Hitachi encoding conversion, and then restart HiRDB.

If Hitachi encoding conversion has been installed:

If there is a memory shortage, resolve it and then restart HiRDB.

For situations other than those described above, stop HiRDB, install Hitachi encoding conversion, and then restart HiRDB. If you still have problems, contact the customer support center.

04
If you use syslogfile character encoding conversion, stop HiRDB, install the extended syslog facility that supports the character encoding conversion facility, and then restart HiRDB.

KFPS01933-E E

Unable to output message aa....aa due to invalid parameter

Message log cannot be output, because a parameter is invalid for the message log service function.

aa....aa: Serial number assigned to the message ID of the message log that cannot be output

S: Resumes processing.

Action

Record this message log and the message ID of the message log that could not be output, and contact the customer support center.

KFPS01943-E E

Unable to output message aa....aa due to invalid parameter

Message log cannot be output, because a parameter is invalid for the message log service function.

aa....aa: Message ID of the message log that cannot be output

S: Resumes processing.

Action

Record this message log and the message ID of the message log that could not be output, and contact the customer support center.

KFPS01944-E E

Unable to output message aa....aa; invalid parameter for message log service

Message log aa....aa cannot be output, because a parameter is invalid for the message log service function.

aa....aa: Message ID of the message log that cannot be output

S: Resumes processing.

Action

Record this message log and the message ID of the message log that could not be output, and contact the customer support center.

KFPS01945-E E+L

failed in output of log message to JP1; output to JP1 is restrained. maintenance info: aa....aa

Output to the Job Management Partner 1 event server was suppressed because log message output to the Job Management Partner 1 event server failed.

aa....aa: Maintenance information

S: Suppresses output to the Job Management Partner 1 event server.

P: Contact the HiRDB administrator.

Action

If messages must be output to the Job Management Partner 1(Job Management Partner/Base or Job Management Partner/System Event Service) event server, investigate the cause of the failed connection and eliminate it.

KFPS01946-I S+L

Restarts log message output to JP1.

Output of log messages to the Job Management Partner 1 event server was restarted because log message output to the Job Management Partner 1 event server succeeded.

S: Resumes processing.

KFPS01947-E E+L

I/O error occurred during output of log message to JP1. maintenance info: aa....aa

An I/O error occurred when a log message was being output to the Job Management Partner 1 event server.

aa....aa: Maintenance information

S: Resumes processing.

P: Contact the HiRDB administrator.

Action

If messages must be output to the Job Management Partner 1 (Job Management Partner/Base or Job Management Partner/System Event Service) event server, investigate the cause of the failed connection and eliminate it.

KFPS01948-E E+L

Unable to connect to event server of JP1

A connection to the Job Management Partner 1 event server cannot be established.
There is a specification to notify Job Management Partner 1 of HiRDB events (Y is specified in the pd_jp1_use operand), but a connection could not be established with the Job Management Partner 1 event server.

S: Resumes processing.

Action

If message output to the Job Management Partner 1 (Job Management Partner/Base or Job Management Partner/System Event Service) event server is necessary, investigate the cause of the failed connection and eliminate it. If this is not necessary, specify not to notify Job Management Partner 1 of HiRDB events (specify N in the pd_jp1_use operand), and restart HiRDB.

KFPS01950-I E+S

Usage: pdcat [-ab] [-c E |W |I |Q] [-x host name] [-d start date] [-t start time] [-T stop time] [-n record number] [message log file name]

Displays the format of the pdcat command. This message is output when a specified command option or argument is invalid.

O: If a command option or argument is invalid, reenter the command specified correctly.

KFPS01951-E E

Insufficient memory

A shortage occurred in the process private area while executing a message log service function command.

S: Cancels processing.

Action

Terminate any unneeded process.

KFPS01952-E E

Error occurred during message log service. maintenance information= aa....aa

The message log service function resulted in an error.

aa....aa: Maintenance information

S: Cancels processing.

Action

Record this message and contact the customer support center.

KFPS01953-E E

Failed in obtaining message log file storage directory

The system failed to obtain the message log file storage directory.

S: Cancels processing.

O: Set the PDDIR environment variable and re-execute.

KFPS01954-E E

Unable to open message log file aa....aa

The indicated message log file cannot be opened, because it was not found or the read privilege has not been defined for the message log file.

aa....aa: Name of message log file

S: Cancels open processing for the corresponding message log file.

O: Take appropriate action and re-execute.

Action

If the read privilege has not been defined for the corresponding message log file, define the privilege.

KFPS01955-E E

I/O error occurred in message log file aa....aa

An error occurred in the message log file due to the cause indicated by the KFPO00107-E message that was output before this message.

aa....aa: Message log file name

S: Cancels processing.

Action

Eliminate the cause of the message log file error and re-execute.

KFPS01956-E E

I/O error occurred in message log file aa....aa

Processing of the indicated file was cancelled due to a disk I/O error.

aa....aa: Name of message log file

S: Cancels all types of processing involving the corresponding file.

KFPS01957-E E

File aa....aa is not a message log file

File aa....aa is not a message log file.

aa....aa: Name of the file that was to be processed

S: Aborts processing involving the applicable file.

KFPS01958-E E

Unable to handle the version (aa....aa) of the message log file (bb....bb) in this command

The system failed to obtain the last update time because the applicable message log file was not found, or for some similar reason.

aa....aa: Name of message log file

bb....bb: Version number of the message log file

S: Cancels all types of processing involving the corresponding file.

Action

Contact the customer support center.

KFPS01959-E E

No message log to output

There is no message log to be output.

KFPS01968-E E

Unable to find message log file (aa....aa)

Specified file was not found.

aa....aa: Name of specified file

S: Ignores the specified file and resumes processing.

Action

Record this message and contact the customer support center.

KFPS01971-E E

Communication failure occurred

Command cannot be executed due to a communication error.

S: Cancels processing.

Action

Refer to the message that was output immediately before this message to check the cause of the communication error, and correct the error.

KFPS01972-E E

Message log server inactive or terminated

Because the message log server is not active or is engaged in termination processing, an entered command cannot be executed.

S: Cancels processing.

Action

Start HiRDB with the pdstart command.

KFPS01973-E E

Versions of message log server and command are different

A command cannot be executed, because its version does not match the version of the message log server.

S: Cancels processing.

Action

Check the HiRDB installation method for an error.

KFPS01974-E E

Real-time output function active

The realtime output function is active.

KFPS01975-E E

Real-time output function inactive

The realtime output function is not active.

KFPS01976-E E

Unable to set environmental variable aa....aa

Environment variable aa....aa has not been set.

aa....aa: Name of the environment variable that has not been set

S: Cancels processing.

O: Set the environment variable and re-execute.

KFPS01977-E E

Name server inactive; unable to execute command

A command cannot be executed, because the name server is not active.

Action

Start HiRDB with the pdstart command.

KFPS01978-E E

Invalid command argument

A command argument is missing, or too many command arguments were specified.

S: Cancels command processing.

O: Reenter the command according to the command usage displayed immediately after this message log.

KFPS01979-E E

Mandatory option flag not specified or option flags specified in incorrect combination

A required option flag is missing, or the combination of option flags is invalid.

S: Cancels command processing.

O: Reenter the command according to the command usage displayed immediately after this message log.

KFPS01980-E E+S

*** Unable to output message (aa....aa) due to memory shortage; component (bbb) ****

Message log cannot be output due to a memory shortage.

aa....aa: Message ID of the message log that cannot be output

bbb: Name of the component that issued the message log output request

S: Resumes processing.

Action

Terminate any unneeded processes. Check the appropriate message according to the message ID cross-reference table and the message ID:

Component name | First 4 digits of message ID
bac, cpy, jar, rec | KFPR
bpp, cit, cpp | KFPZ
dbh | KFPH
dfc | KFPB
dic | KFPD
dsa, sta | KFPK
exp, int, mod | KFPX
goi, ric | KFPN
ios | KFPI
osl | KFPO
lod, rld | KFPL
sqa | KFPA
utl | KFPU
Other | KFPS

KFPS01981-E E+S

*** Unable to output message (aa....aa) due to memory shortage; component (bbb) ****

Message log cannot be output due to a memory shortage or communication error.

aa....aa: Serial number assigned to the message ID of the message log that cannot be output

bbb: Name of the component that issued the message log output request

S: Resumes processing.

Action

Terminate any unneeded processes. Check the appropriate message according to the message ID cross-reference table and the message ID:

Component name | First 4 digits of message ID
bac, cpy, jar, rec | KFPR
bpp, cit, cpp | KFPZ
dbh | KFPH
dfc | KFPB
dic | KFPD
dsa, sta | KFPK
exp, int, mod | KFPX
goi, ric | KFPN
ios | KFPI
osl | KFPO
lod, rld | KFPL
sqa | KFPA
utl | KFPU
Other | KFPS

KFPS01983-E E+S

*** Unable to output message (aa....aa) due to message log file version different; component (bbb) ****

Message log cannot be output, because the version of the message log file does not match the version of the program that issued the request.

aa....aa: Serial number assigned to the message ID of the message log that cannot be output

bbb: Name of the component that issued the message log output request

S: Resumes processing.

Action

Relink the executed program. Check the appropriate message according to the message ID cross-reference table and the message ID:

Component name | First 4 digits of message ID
bac, cpy, jar, rec | KFPR
bpp, cit, cpp | KFPZ
dbh | KFPH
dfc | KFPB
dic | KFPD
dsa, sta | KFPK
exp, int, mod | KFPX
goi, ric | KFPN
ios | KFPI
osl | KFPO
lod, rld | KFPL
sqa | KFPA
utl | KFPU
Other | KFPS

KFPS01984-E E+S

*** Unable to output message(aa....aa) due to message log file not found; component (bbb) ****

Message log cannot be output, because the message log file was not found.

aa....aa: Serial number assigned to the message ID of the message log that cannot be output

bbb: Name of the component that issued the message log output request

S: Resumes processing.

Action

Ensure that the PDDIR environment variable has been specified correctly. Check the appropriate message according to the message ID cross-reference table and the message ID:

Component name | First 4 digits of message ID
bac, cpy, jar, rec | KFPR
bpp, cit, cpp | KFPZ
dbh | KFPH
dfc | KFPB
dic | KFPD
dsa, sta | KFPK
exp, int, mod | KFPX
goi, ric | KFPN
ios | KFPI
osl | KFPO
lod, rld | KFPL
sqa | KFPA
utl | KFPU
Other | KFPS

KFPS01985-E E+S

*** Unable to output message (aa....aa) due to message log file I/O error; component (bbb) ****

Message log cannot be output, because an I/O error occurred in the message log file.

aa....aa: Serial number assigned to the message ID of the message log that cannot be output

bbb: Name of the component that issued the message log output request

S: Resumes processing.

Action

Check the appropriate message according to the message ID cross-reference table and the message ID:

Component name | First 4 digits of message ID
bac, cpy, jar, rec | KFPR
bpp, cit, cpp | KFPZ
dbh | KFPH
dfc | KFPB
dic | KFPD
dsa, sta | KFPK
exp, int, mod | KFPX
goi, ric | KFPN
ios | KFPI
osl | KFPO
lod, rld | KFPL
sqa | KFPA
utl | KFPU
Other | KFPS

If the error cannot be corrected by the user, record this message and the ID serial number of the message that could not be output and contact the customer support center.

KFPS01986-E E+S

*** Unable to output message (aa....aa) due to message log file access denied; component (bbb) ****

Message log cannot be output, because no access privilege has been defined for the message log file.

aa....aa: Serial number assigned to the message ID of the message log that cannot be output

bbb: Name of the component that issued the message log output request

S: Resumes processing.

Action

If there is no read permission for the message log file, provide read permission. If there is no retrieval permission for the directories on the message log file path, provide retrieval permission. Check the appropriate message according to the message ID cross-reference table and the message ID:

Component name | First 4 digits of message ID
bac, cpy, jar, rec | KFPR
bpp, cit, cpp | KFPZ
dbh | KFPH
dfc | KFPB
dic | KFPD
dsa, sta | KFPK
exp, int, mod | KFPX
goi, ric | KFPN
ios | KFPI
osl | KFPO
lod, rld | KFPL
sqa | KFPA
utl | KFPU
Other | KFPS

KFPS01989-E E

Unable to make message log file: file (aa....aa) version error. file=bb....bb, command=cc....cc

Message log file cannot be created, because the entered command cannot process this version of the message log file (which is later than the command's version).

aa....aa: Name of the file resulting in the error

bb....bb: File version

cc....cc: Command version

S: Cancels command execution.

Action

Record this message and contact the customer support center.

KFPS01990-E E+S

*** Unable to output message (aa....aa) due to parameter too many; component (bbb) ****

Message log cannot be output due to an invalid parameter.

aa....aa: Serial number assigned to the message ID of the message log that cannot be output

bbb: Name of the component that issued the message log output request

S: Resumes processing.

Action

Check the appropriate message according to the message ID cross-reference table and the message ID:

Component name | First 4 digits of message ID
bac, cpy, jar, rec | KFPR
bpp, cit, cpp | KFPZ
dbh | KFPH
dfc | KFPB
dic | KFPD
dsa, sta | KFPK
exp, int, mod | KFPX
goi, ric | KFPN
ios | KFPI
osl | KFPO
lod, rld | KFPL
sqa | KFPA
utl | KFPU
Other | KFPS

If the error cannot be corrected by the user, record this message and the ID serial number of the message that could not be output and contact the customer support center.

KFPS01991-E E+S

*** Unable to output message (aa....aa) due to parameter not enough; component (bbb) ***

Message log cannot be output due to an invalid parameter.
aa....aa: Serial number assigned to the message ID of the message log that cannot be output
bbb: Name of the component that issued the message log output request

S: Resumes processing.

Action

Check the appropriate message according to the message ID cross-reference table and the message ID:

Component name | First 4 digits of message ID
bac, cpy, jar, rec | KFPR
bpp, cit, cpp | KFPZ
dbh | KFPH
dfc | KFPB
dic | KFPD
dsa, sta | KFPK
exp, int, mod | KFPX
goi, ric | KFPN
ios | KFPI
osl | KFPO
lod, rld | KFPL
sqa | KFPA
utl | KFPU
Other | KFPS

If the error cannot be corrected by the user, record this message and the ID serial number of the message that could not be output and contact the customer support center.

KFPS01992-I E+S

*** Unable to output message (aa....aa) due to message too long; component (bbb) ***

A message was truncated, because the edited message length exceeded the maximum length.

aa....aa: Serial number assigned to the message ID of the message log that cannot be output

bbb: Name of the component that issued the message log output request

S: Resumes processing.

Action

Record this message and the ID serial number of the message that could not be output and contact the customer support center.

KFPS01993-E E+S

*** Unable to output message (aa....aa) due to invalid argument; component (bbb) ***

Message log cannot be output due to an invalid parameter.

aa....aa: Serial number assigned to the message ID of the message log that cannot be output

bbb: Name of the component that issued the message log output request

S: Resumes processing.

Action

Check the appropriate message according to the message ID cross-reference table and the message ID:

Component name | First 4 digits of message ID
bac, cpy, jar, rec | KFPR
bpp, cit, cpp | KFPZ
dbh | KFPH
dfc | KFPB
dic | KFPD
dsa, sta | KFPK
exp, int, mod | KFPX
goi, ric | KFPN
ios | KFPI
osl | KFPO
lod, rld | KFPL
sqa | KFPA
utl | KFPU
Other | KFPS

This message may be output with a KFPA message ID if an attempt was made to re-execute the FETCH statement after an error occurred when the FETCH statement was executed during UAP processing. In such a case, correct the UAP.

If the error cannot be corrected by the user, record this message and the ID serial number of the message that could not be output and contact the customer support center.

KFPS01996-E E+S

*** Unable to output message (aa....aa) due to message not found; component (bbb) ***

Message log cannot be output, because the message log file does not contain a message log.

aa....aa: Serial number assigned to the message ID of the message log that cannot be output

bbb: Name of the component that issued the message log output request

S: Resumes processing.

Action

Check the appropriate message according to the message ID cross-reference table and the message ID:

Component name | First 4 digits of message ID
bac, cpy, jar, rec | KFPR
bpp, cit, cpp | KFPZ
dbh | KFPH
dfc | FKPB
dic | KFPD
dsa, sta | KFPK
exp, int, mod | KFPX
goi, ric | KFPN
ios | KFPI
osl | KFPO
lod, rld | KFPL
sqa | KFPA
utl | KFPU
Other | KFPS

If the error cannot be corrected by the user, record this message and the ID serial number of the message that could not be output and contact the customer support center.

KFPS02101-I L

pd_spd_syncpoint_skip_limit is too small,assumed limit 2,server=aa....aa

Either 1 was specified in the pd_spd_syncpoint_skip_limit operand of the aa....aa server or the result of the autocalculation was less than 2. 2 is assumed in the pd_spd_syncpoint_skip_limit operand, and processing resumes.

aa....aa: Server name

S: Continues processing.

Action

When 1 is specified in the pd_spd_syncpoint_skip_limit operand, correct the specified value. If this message was output by autocalculation, see the description of the skipped effective synchronization point dump monitoring facility in the HiRDB Version 9 System Operation Guide to determine whether or not to stop using autocalculation.

KFPS02102-E E+L

Unable to start syncpoint dump service aa....aa. reason code=bb....bb

The synchronization point dump service cannot be started on the aa....aa server.

aa....aa: Server name

bb....bb: Reason code

The table below lists the reason codes and the actions to be taken.

S: Terminates HiRDB.

Action

Take action appropriate to the reason code, as listed below, and restart HiRDB:

Reason code
Explanation
Action
Remarks

6
Shared memory pool too small to process the request
Contact the customer support center.
--

8
77
88
Memory shortage
Check the utilization status of the process private area and shared memory.

9
Analysis information file open error
Check the synchronization point dump file-related definitions.

10
105
Unresumable error during analysis processing

15
36
Network error
Check the cause of the error, take appropriate action, then restart the system.

24
Definition read failure
Take action appropriate to the message that was output before.

28
Memory shortage
Check the utilization status of the process private area and shared memory.

33
34
Internal conflict in name service function
Contact the customer support center.

35
Timeout
Check the cause of the error, take appropriate action, then restart the system.

37
Unable to use the name service function
Check the server execution status with a HiRDB command.

38
50
79
Inter-process communication error
Check the cause of the error, take appropriate action, then restart the system.

41
Status file I/O error

43
Unable to allocate work area
Check the utilization status of the process private area and shared memory.

44
Insufficient buffer sectors
Check the server definition.

45
Unable to allocate the requested size of records (insufficient status file capacity)

47
Inactive status server
Check the execution status of the status server with a HiRDB command.

52
Swapping error
Check the cause of the error, take appropriate action, then restart the system.

72
Status write error

73
Status read error

74
Definition analysis error
Refer to the KFPU message output immediately before, and take the appropriate action. If no message was output, contact the customer support center.

76
Internal file write error
Check the cause of the error, take appropriate action, then restart the system.

89
Duplicated definition file name
Check the server definition, correct the error, then restart the system.

92
File open error
Check the cause of the error, take appropriate action, then restart the system.
Details of the error are displayed in the KFPS-02122-W message.

94
Analysis error
Check the definition file, correct the error, then restart the system.
--

104
In UNIX:
Insufficient message queue
In Windows:
The size of the installation drive is insufficient.
In UNIX:
Reconfigure the kernel (change the value of the msgmni message-related parameter).
In Windows:
On the HiRDB installation drive, allocate sufficient free space for the shared memory.

119
The specification values of the normal synchronization point dump file in the system definition for a transaction execution site and a log application site do not match.
Revise the specification values of the normal synchronization point dump file in the system definition for the transaction execution site and the log application site.

120
The synchronization point dump file in use does not exist.
Take the action indicated in the KFPS02181-E message.

--: Not applicable

KFPS02103-I L

Assumed pd_spd_syncpoint_skip_limit, value=aa....aa, server=bb....bb

The value specified in the pd_spd_syncpoint_skip_limit operand was automatically calculated so that HiRDB restart processing does not take too long. Another possibility is that the result of the automatic calculation exceeded 100,000, so the value specified in the pd_spd_syncpoint_skip_limit operand is assumed to be 100000.

aa....aa: Specification value calculated automatically

bb....bb: Server name

S: Continues processing.

Action

Refer to Monitoring UAP status (skipped effective synchronization point dump monitoring facility) in the HiRDB Version 9 System Operation Guide, and investigate whether or not to stop automatic calculation.

KFPS02104-W L

Unable to recover the previous syncpoint dump service status from status file; continues recovery processing without status file, reason code=aa....aa

The previous synchronization point dump could not be restored from the status file. Recovery will be resumed without a status file.

aa....aa: Reason code

The table below lists the reason codes and the actions to be taken.

S: Starts the server normally, but does not collect a synchronization point dump because restart from the system log is not possible.

Action

Take action appropriate to the reason code, as listed below:

Reason code | Explanation | Action
46 | Status record required for recovery does not exist. | Check the server definition.
90 | Invalid status file contents
93 | Invalid resource run ID | Check the definition as to whether it is the same as the one used during previous HiRDB session.

KFPS02105-W L

Error occurred while terminating syncpoint dump service; continutes processing.reason code=aa....aa

An error occurred while terminating the synchronization point dump service, but processing is continuing.

aa....aa: Reason code

S: Resumes processing.

Action

Take action appropriate to the reason code, as listed below:

Reason code
Explanation
Action

28
Process private area cannot be allocated.
Shared memory is insufficient.
Check the utilization status of the process.
private area and shared memory.

35
Timeout occurred.
Check the cause of the error, take appropriate action, then restart the system.

36
Network error occurred.

37
Name service function cannot be used.
Check the server execution status with a HiRDB command.

38
Inter-process communication error occurred.
Check the cause of the error before the next startup, take appropriate action, then restart the system.

KFPS02110-E L

Process-specific area found insufficient while performing syncpoint dump service for aa....aa service.

A process private area shortage occurred during execution of synchronization point dump service on the aa....aa server.

aa....aa: Server name

S: Terminates HiRDB.

Action

Check the utilization status of the process private area and restart HiRDB.

KFPS02111-E L

Error occurred while performing syncpoint dump service for aa....aa service.reason code=bb....bb function: cc....cc

An error occurred during synchronization point dump acquisition on the aa....aa server.

aa....aa: Server name

bb....bb: Reason code

cc....cc: Name of the function resulting in the error

S: Terminates abnormally.

Action

Take a corrective action by referring to the list of reason codes and restart HiRDB. If necessary, collect error information and contact the customer support center.

Reason code
Explanation
Action

4
Shared memory cannot be accessed.
Contact the customer support center.

11
Argument is invalid.

12
Function issuance sequence error occurred.

13
Fatal or unexpected error occurred.
See -303 in 4.1 Detail codes for RPC-related errors.

14
Memory shortage occurred.
Check the memory usage.

15
Network error occurred.
Check the cause of the error with the procedure listed below and take appropriate action:

Check the server machine connection status with an OS command.

Check the execution status of each server with a HiRDB command.

16
Transfer timeout occurred.

17
Input parameter length exceeded the maximum.

18
Returned response is too long to fit in the area at the calling source.

19
Specified service function has not been registered.

20
Server is being terminated.

21
Process that provides the specified service function was not found.

22
25
Unexpected error occurred.

23
RPC environment is not active.

26
Name information retrieval error occurred.
Contact the customer support center.

27
Specified argument is invalid.

28
Process private area cannot be allocated. Shortage occurred in the shared memory.
Check the utilization status of the process private area and shared memory.

29
Versions do not match between function and shared memory or between function and server.
Check the cause of the error with the following procedure, and take appropriate action:

Check the server machine connection status with an OS command.

Check the execution status of each server with a HiRDB command.

30
33
34
Internal conflict was detected in the name service function.
Contact the customer support center.

31
Function parameter error occurred.
Check the cause of the error with the following procedure, and take appropriate action:

Check the server machine connection status with an OS command.

Check the execution status of each server with a HiRDB command.

32
Function issuance sequence error occurred.

35
Timeout occurred.
Check the cause of the error, take appropriate action, then restart the system.

36
Network error occurred.

37
Name service function cannot be used.
Check the server execution status with a HiRDB command.

38
79
Inter-process communication error occurred.
Check the cause of the error before the next startup, take appropriate action, then restart the system.

39
Status is invalid (the server is inactive, engaged in abnormal termination, or engaged in forced termination).

80
84
86
87
Specified array size exceeds the defined maximum size.
Contact the customer support center.

81
82
Area cannot be allocated.
Check the memory usage.

83
Error occurred during data conversion.
Contact the customer support center.

85
Text received from function is too short to set in arguments.

109
110
A timeout was detected during database buffer sweep-out processing.
Save the maintenance data under %PDDIR%\spool and contact the customer support center, then restart the system.

111
112
A timeout occurred during database buffer synchronization processing.

KFPS02112-W L

Minor error occurred while analyzing definitions for syncpoint dump service. file being analyzed:aa....aa, record number=bb....bb, reason code=cc....cc

A minor error occurred while analyzing definitions for the synchronization point dump service.

aa....aa: Name of the definition file being analyzed

bb....bb: Number of the record that had the error

cc....cc: Reason code that shows the contents of the error

S: Ignores the pdlogadfg or pdlogadpf operand definition statement that was in error, and starts the synchronization point dump service or continues restart processing (operates as though there were no definition statement).

Action

Refer to the following reason code list, and revise the definition related to the synchronization point dump service.

Reason code
Explanation
Action

411
There is an error in the -a option specification of the pdlogadpf operand.

The length of the path specified in the -a option exceeds the maximum number of characters.

The length of the HiRDB file name specified in the -a option exceeds the maximum (30 characters).

As necessary, stop the system, revise the definition, and restart.

412
There is an error in the -b option specification of the pdlogadpf operand (when duplexed synchronization point dump is used).

The length of the path specified in the -b option exceeds the maximum number of characters.

The length of the HiRDB file name specified in the -b option exceeds the maximum (30 characters).

KFPS02113-E L

Error occurred while analyzing definitions for syncpoint dump service. server=aa....aa, reason code=bb....bb, cc....cc

An error occurred during analysis of the system definition related to a synchronization point dump file.

aa....aa: Server name

bb....bb: Reason code

cc....cc: The following value is displayed, on the basis of the reason code:

If the reason code is UNMATCH_DEFINITION
definition=dd....dd
dd....dd: Name of the operand with an unmatched definition

If the reason code is UNMATCH_FILEGROUP
filegroup=ee....ee
ee....ee: Unmatched logical file name

If the reason code is UNDEFINE_FILEPATH
filegroup=ff....ff
ff....ff: Logical file name for which no physical file name is defined

S: Continues processing.

Action

Take action on the basis of the reason code.

Reason code
Explanation
Action

UNMATCH_DEFINITION
The value specified in the dd....dd operand differs between the transaction execution site and the log application site.
Set the value specified in the dd....dd operand for the log application site to match the value of the dd....dd operand for the transaction execution site.

UNMATCH_FILEGROUP
A secondary synchronization point dump file group that matches the primary synchronization point dump file group is not defined for the log application site, or a secondary synchronization point dump file group that corresponds to a primary synchronization point dump file group that is not defined for the transaction execution site is defined for the log application site.
Make all of the log application site secondary synchronization point dump file group names match the transaction execution site primary synchronization point dump file groups.

UNDEFINE_FILEPATH
A secondary synchronization point dump file that corresponds to a primary synchronization point dump file group is not defined for the log application site.
Define all secondary synchronization point dump files required to start the log application site.

KFPS02114-E L

File error occurred while getting information while getting information necessary for aa....aa service recovery.

A file error occurred while collecting the information required for recovery of server aa....aa.

aa....aa: Name of the server resulting in the error

S: Terminates HiRDB.

Action

Check both the error messages that were output before this message and the file status, then restart HiRDB.

KFPS02115-E L

File error occurred while getting syncpoint dump for aa....aa service

A file error occurred while collecting a synchronization point dump for server aa....aa.

aa....aa: Name of the server resulting in the error

S: Terminates HiRDB.

Action

Check both the error messages that were output before this message and the file status, then restart HiRDB.

KFPS02118-I L

Syncpoint dump file group aa....aa for bb....bb service has been opened

A synchronization point dump file for the bb....bb server was opened.

aa....aa: File group name of the synchronization point dump file

bb....bb: Server name

S: Resumes processing.

KFPS02119-I L

Syncpoint dump file group aa....aa for bb....bb service has been closed

A synchronization point dump file for the bb....bb server was closed.

aa....aa: File group name of the synchronization point dump file

bb....bb: Server name

S: Resumes processing.

KFPS02122-W L

Error occurred while opening syncpoint dump file group for aa....aa service.file group name: bb....bb,reason code=cccc

An error occurred while opening a synchronization point dump file group for server aa....aa.

aa....aa: Name of the server resulting in the error

bb....bb: Name of the file group resulting in the error

cccc: Reason code (the table below lists the reason codes and the actions to be taken)

S: Resumes processing.

Action

Take action appropriate to the reason code, as listed below:

Reason code
Explanation
Action

59
File status flag is invalid.
Contact the customer support center.

61
The HiRDB file name is invalid.
Check and, if necessary, revise the server definition.

62
A synchronization point dump file was not created in the HiRDB file system area for system files.
Create a synchronization point dump file in the HiRDB file system area for system files.
If Real Time SAN Replication is used, make the path to reference the synchronization point dump file on the remote site the same as on the main site. For a log application site, confirm that the path specified in the pdlogadpf -d ssp operand matches the path of the secondary synchronization point dump file created in the preparation for log application.

63
A synchronization point dump file could not be found.

64
File system versions do not match.
Check the HiRDB execution environment.

65
File system lock error occurred.

66
Shortage occurred in file system lock segments.
Check the memory usage.

67
107
Number of file systems opened exceeded the maximum.
Either close unneeded files or check the maximum number of files that can be opened and re-create the kernel, if necessary.

68
There is no access privilege for the corresponding HiRDB file system area.
Modify the access privileges for the corresponding HiRDB file system area using OS commands (chmod, for example).

69
There is no access privilege for the corresponding file.
Modify the access privileges for the HiRDB file system area where the corresponding file is stored using OS commands (chmod, for example).

70
File system I/O error occurred.
Check the cause of the I/O error and take appropriate action.

71
Memory shortage occurred in the file system.
Check the memory usage.

88
Memory shortage
Check the usage of the process private area.

92
File test error occurred (synchronization point dump file has not been initialized or is being used by another server or HiRDB).
Check the cause of the error with the following procedure, and take appropriate action:

Re-evaluate the pdlogadpf operand of the synchronization point dump file or the system common definition.

Initialize the HiRDB file system area for the synchronization point dump file, and then re-execute.

97
Invalid size
Check the size of the synchronization point dump file.

98
I/O error
Check the cause of the I/O error and take appropriate action.

106
Invalid file name
Consider the following causes:

An invalid character is specified in the file name.

The length of the HiRDB file name exceeds the maximum (30 characters).

Check the file name specified in the server definition or the command operand.

108
Unregistered file name maximum
Use the pdlogadpf command to register the file name corresponding to the target file group.

121
The possible causes are as follows:

An attempt was made to open a synchronization point dump file created in a HiRDB file system area that exceeds 2 GB, but N is specified in the pd_large_file_use operand.

An attempt was made to open a synchronization point dump file created in a HiRDB file system area created with the pdfmkfs -a command, but N is specified in the pd_large_file_use operand.

Specify Y for the pd_large_file_use operand, or omit the specification.

KFPS02123-W L

Error occurred while closing syncpoint dump file group for aa....aa service.file group name: bb....bb,reason code=cccc

An error occurred while a synchronization point dump file on the aa....aa server was being closed.

aa....aa: Name of the server on which the error occurred

bb....bb: File group name of the synchronization point dump file in which the error occurred

cccc: Reason code

S: Continues processing.

Action

Take appropriate action according to the reason code.

Reason code | Explanation | Action
66 | Insufficient file system lock segments | Check the memory usage.
70 | File system I/O error | Check the cause of the I/O error and take appropriate action.
71 | File system memory shortage | Check the memory usage.
91 | Error occurred in both the A system and B system. | See the KFPS4321-W message just output and take appropriate action.
205 | Internal conflict in program | Contact the customer support center.

KFPS02124-W L

Error occurred while reading from syncpoint dump file for aa....aa service.file name: bb....bb,generation number=cc....cc,reason code=dddd

An error occurred while reading a synchronization point dump file for server aa....aa.

aa....aa: Name of the server resulting in the error

bb....bb: File group name of the synchronization point dump file in which the error occurred

cc....cc: Generation number resulting in the error

dddd: Reason code

S: Continues processing.

Action

If the KFPS04323-W message is output immediately before this message, take action according to the KFPS04323-W message. If the KFPS04323-W message is not output immediately before this message, take appropriate action according to the reason code.

Reason code
Explanation
Action

1
Record requested for input is outside the file area.
Contact the customer support center.

70
I/O error occurred.
Check the cause of the error and take appropriate action.

71
Memory is insufficient.
Review the memory requirements. If there is a problem, take corrective action such as increasing the amount of memory or reducing the number of resident processes. If this fails to resolve the problem, contact the customer support center.

201
203
206
208
Input error was detected in the synchronization point dump file.
Contact the customer support center.

KFPS02125-W L

Error occurred while writing to syncpoint dump file for aa....aa service.file group name:bb....bb,generation number=cc....cc.reason code=dddd

An error occurred when a synchronization point dump file on the aa....aa server was being written to.

aa....aa: Name of the server resulting in the error

bb....bb: File group name of the synchronization point dump file in which the error occurred

cc....cc: Generation number resulting in the error

dddd: Reason code

S: Continues processing.

Action

If the KFPS04322-W message is output immediately before this message, take action according to the KFPS04322-W message. If the KFPS04322-W message is not output immediately before this message, take action appropriate to the reason code, as listed below:

Reason code
Explanation
Action

1
Record requested for input is outside the file area.
Contact the customer support center.

70
I/O error occurred.
Check the cause of the error and take appropriate action.

71
Memory is insufficient.
Review the memory requirements. If there is a problem, take corrective action such as increasing the amount of memory or reducing the number of resident processes. If this fails to resolve the problem, contact the customer support center.

95
The requested number of records cannot be written into the synchronization point dump file.
Contact the customer support center.

202
204
207
209
Output error was detected in the synchronization point dump file.

KFPS02126-E L

Number of file groups is insufficient for aa....aa service.number of available file groups=bb....bb,number of guaranteed generations=cc....cc

There is a shortage of synchronization point dump files on the aa....aa server. The number of synchronization point dump files on the aa....aa server did not satisfy the condition guaranteed-generation-count + 1.

aa....aa: Server name

bb....bb: Number of available synchronization point dump file groups

cc....cc: Number of guaranteed generations

S: Cancels collection of synchronization point dump for server aa....aa.

Action

Refer to the following messages that were output before this message to check the cause of the error:

KFPS02122-W

KFPS02124-W

KFPS202127-W

KFPS02127-W L

Unable to use syncpoint dump file for aa....aa service due to insufficient file capacity,file group name=bb....bb,system A/B=c,file capacity=dd....dd,size needed for syncpoint dump=ee....ee

A synchronization point dump file for server aa....aa cannot be used due to insufficient size.

aa....aa: Server name

bb....bb: File group name

c: System type (a: A system, b: B system)

dd....dd: Capacity of synchronization point dump files (record count)

ee....ee: Requested record count of synchronization point dump files

S: Continues processing.

Action

Change the synchronization point dump file capacity for the system displayed in c. See the requested record count indicated in ee....ee.

KFPS02128-E E

Server name aa....aa specified with this command is invalid.

An invalid server name (aa....aa) was specified in a command.

aa....aa: Server name

S: Cancels command execution.

O: Enter the correct server name and re-execute the command.

KFPS02129-E E

Syncpoint dump file group name aa....aa specified with this command is invalid.

The synchronization point dump file name specified by the command is invalid.

aa....aa: File group name

S: Cancels command execution.

O: Correctly enter the file group name of the synchronization point dump file, and then re-execute the command.

KFPS02131-E E

-g option specified with this command is invalid.

The -g option is invalid in a command.

S: Cancels command execution.

O: Specify the -g option correctly and re-execute the command.

KFPS02132-E E

Stops command processing due to error. reason code=aa....aa

Command processing was cancelled due to an error.
aa....aa: Reason code indicating the nature of the error

S: Cancels command execution.

Action

Check the error message in the message log file and take appropriate action.

Reason code
Explanation
Action

2
Parameter error occurred in a shared memory function.
Contact the customer support center.

3
Request segment size is greater than the pool size for the entire shared memory.

4
Attempt was made to share a segment allocated by another process, but the segment has not been allocated.
Check the execution status of the log/synchronization point dump service function with a HiRDB command and reenter the command in the online mode.

5
Function execution sequence error occurred.

6
Size of shared memory pool is insufficient
Contact the customer support center.

7
Shared memory pool lock processing failed.

11
Argument is invalid.

12
Function input sequence error occurred.

13
Fatal or unexpected error occurred.
See -303 in 4.1 Detail codes for RPC-related errors.

14
Memory shortage occurred.
Check the memory usage. Check the cause of the error using the following procedure and take appropriate action:

Check the server machine connection status with an OS command.

Check the execution status of each server with a HiRDB command.

15
Network error occurred.

16
Transfer timeout occurred.

18
Length of input parameter exceeds the maximum.

18
Returned response is too long to fit in the area at the calling source.

19
Specified service function has not been registered.

20
Server is being terminated.

21
Process that provides the specified service function was not found.
Check the cause of the error using the following procedure and take appropriate action:

Check the server machine connection status with an OS command.

Check the execution status of each server with a HiRDB command.

22
25
Unexpected error occurred.

23
RPC environment is not active.

26
Name information retrieval error occurred.
Contact the customer support center.

27
Specified argument is invalid.

28
Process private area cannot be allocated.
Check the memory usage.

29
Versions do not match between function and shared memory or between function and server.
Check the cause of the error using the following procedure and take appropriate action:

Check the node connection status with an OS command.

Check the execution status of each server with a HiRDB command.

31
Function parameter error occurred.

32
Function input sequence error occurred.

35
Timeout occurred.

36
Network error occurred.

37
Name service function cannot be used.

40
Specified key value already exists.
Check the server definition or initialization.

41
I/O error occurred.
Check the cause of the I/O error and take appropriate action.

42
Offset + length is outside the allocated area.
Contact the customer support center.

43
Work area cannot be allocated.
Check the memory usage.

44
There are not enough buffer sectors.
Check the server definition.

45
Requested number of records cannot be allocated (insufficient status file size).

46
No record has the corresponding key value.
Contact the customer support center.

47
Server for executing the status service function is not active.
Check the server execution status with a HiRDB command.

48
Offset is outside the allocated area.
Contact the customer support center.

49
Parameter format is invalid.

50
Inter-process communication error occurred.
Check the server execution status with a HiRDB command.

51
Requested size is invalid.
Contact the customer support center.

52
Swapping error occurred.
See -1039 in 4.2 Detail codes for system-related errors, and take appropriate action. Then, start HiRDB.

53
Protocol version error occurred.
Contact the customer support center.

54
Size is different from an existing key value.

80
84
86
87
Specified array size exceeds the defined maximum size.

81
82
Area cannot be allocated.
Check the memory usage.

83
Error occurred during data conversion.
Contact the customer support center.

85
Text received from function is too short to set in arguments.

96
Internal conflict was detected in program.

97
Invalid file error occurred.
Check the size of the synchronization point dump file. Check the cause of the I/O error and take appropriate action.

98
I/O error occurred.

KFPS02135-E L

File group name aa....aa specified in definition file bb....bb is already defined in definition file cc....cc

File group name bb....bb specified in definition file aa....aa has already been defined in definition file cc....cc.

aa....aa: Name of the erroneous definition file

bb....bb: File group name

cc....cc: Name of the definition file containing the specified file group name

S: Resumes analysis processing and cancels unit startup processing upon termination of analysis processing.

Action

Correct the duplicated file group name.

KFPS02137-E L

Physical file name aa....aa specified in definition file bb....bb is already defined in definition file cc....cc.

File name bb....bb specified in definition file aa....aa has already been defined in definition file cc....cc.

aa....aa: Name of the erroneous definition file

bb....bb: Physical file name

cc....cc: Name of the definition file containing the specified file name

S: Resumes analysis processing and cancels unit startup processing upon termination of analysis processing.

Action

Correct the duplicated file name.

KFPS02139-E L

Definition file aa....aa contains commands with deleted file group name bb....bb

File group name bb....bb that was deleted from the definition during normal startup was found in definition file aa....aa at the time of synchronization point dump restart.

aa....aa: Name of the erroneous definition file

bb....bb: File group name

S: Resumes analysis processing and cancels unit startup processing upon termination of analysis processing.

Action

Restore the deleted definition generation so that the same information is used as when the system was started normally.

KFPS02141-E L

File group name aa....aa specified with pdlogadfg is already defined in definition file bb....bb. record number=cc....cc

File group name bb....bb specified in pdlogadfg in definition file aa....aa has already been specified in the same definition.

aa....aa: Name of the erroneous definition file

bb....bb: File group name

cc....cc: Record number in the erroneous definition file

S: Resumes analysis processing and cancels unit startup processing upon termination of analysis processing.

Action

Correct the duplicated file group name.

KFPS02143-E L

Physical file name aa....aa specified with pdlogadpf is already defined in definition file bb....bb. record number=cc....cc

The file name is specified in the pdlogadpf operand more than once.

aa....aa: File name that is specified more than once

bb....bb: File name of the server definition in which the error occurred

cc....cc: Record number in the definition file in which the error occurred

S: Terminates processing.

Action

Correct the file name that is specified more than once.

KFPS02144-E L

pdlogadfg does not specify file group name in definition file aa....aa. record number=bb....bb

A file group name is missing in pdlogadfg specified in definition file aa....aa.

aa....aa: Name of the erroneous definition file

bb....bb: Record number in the erroneous definition file

S: Resumes analysis processing and cancels unit startup processing upon termination of analysis processing.

Action

Check the information specified in the definition file and correct the error.

KFPS02145-E L

pdlogadpf does not specify file group name in definition file aa....aa.record number=bb....bb

A file group name is missing in pdlogadpf specified in definition file aa....aa.

aa....aa: Name of the erroneous definition file

bb....bb: Record number in the erroneous definition file

S: Resumes analysis processing and cancels unit startup processing upon termination of analysis processing.

Action

Check the information specified in the definition file and correct the error.

KFPS02147-E L

pdlogadpf does not specify physical file name in definition file aa....aa.record number=bb....bb

The pdlogadpf operand does not specify a synchronization point dump file name.

aa....aa: File name of the server definition where the error occurred

bb....bb: Record number in the definition file where the error occurred

S: Terminates processing.

Action

Take one of the following actions:

If the synchronization point dump file is not duplicated, determine whether the -a option is specified in the pdlogadpf -d spd or pdlogadpf -d ssp operand.

If the synchronization point dump file is duplicated, determine whether the -a and -b options are specified in the pdlogadpf -d spd or pdlogadpf -d ssp operand.

KFPS02148-E L

File group name specified with pdlogadpf not defined in definition file aa....aa.record number=bb....bb

The file group name bb....bb was defined in the pdlogadfg operand but was not defined in the pdlogadpf operand.

aa....aa: Name of the erroneous definition file

bb....bb: Record number in the definition file where the error occurred

S: Resumes analysis processing and cancels unit startup processing upon termination of analysis processing.

Action

Check the following items in the pdlogadfg operand and the pdlogadpf operand for definition file aa....aa.

Is file group name bb....bb correct?

After file group name bb....bb was defined in the pdlogadfg operand, was it defined in the pdlogadpf operand?

KFPS02149-E L

Number of pdlogadfg -d bbb commands with ONL is insufficient in definition file aa....aa

When a synchronization point dump was started, the number of pdlogadfg -d bbb specifications with ONL specified in the system definition was insufficient. (number-of-guaranteed-valid-generations+1).

aa....aa: Name of the erroneous definition file

bbb: File type

spd: Synchronization point dump file

ssp: Secondary synchronization point dump file

S: Resumes analysis processing and cancels unit startup processing upon termination of analysis processing.

Action

Check the information specified in the definition file and correct the error.

KFPS02153-E E+L

Number of pdlogadfg -d bbb commands exceeds the limit in definition file aa....aa

The number of pdlogadfg -d bbb specifications exceeds the limit.

aa....aa: Name of the erroneous definition file

bbb: File type

spd: Synchronization point dump file

ssp: Secondary synchronization point dump file

S: Cancels unit startup processing.

Action

Revise the number of pdlogadfg -d bbb specifications to a maximum of 60.

KFPS02154-E L

More than one pdlogadpf -d ccc command is specified for pdlogadfg -g bb....bb in definition file aa....aa

More than one pdlogadpf -d ccc was specified for pdlogadfg -g bb....bb.

aa....aa: Name of the erroneous definition file

bb....bb: File group name for which pdlogadpf was specified more than once

ccc: File type

spd: Synchronization point dump file

ssp: Secondary synchronization point dump file

S: Cancels unit startup processing.

Action

Ensure that only one pdlogadpf is specified for each file group indicated in pdlogadfg.

KFPS02155-E E+L

Number of pdlogadpf -d bbb commands exceeds the limit in definition file aa....aa

The number of pdlogadpf -d bbb specifications exceeds the limit.

aa....aa: Name of the erroneous definition file

bbb: File type

spd: Synchronization point dump file

ssp: Secondary synchronization point dump file

S: Cancels unit startup processing.

Action

Check the information specified in the definition file and correct the error.

KFPS02156-E L

Pdlogadpf -d ccc is not specified for pdlogadfg -g bb....bb in definition file aa....aa

The pdlogadfg -g bb....bb has no corresponding pdlogadpf -d ccc.

aa....aa: Name of the erroneous definition file

bb....bb: File group name specified with pdlogadfg

ccc: File type

spd: Synchronization point dump file

ssp: Secondary synchronization point dump file

S: Cancels unit startup processing.

Action

Check the information specified in the definition file and correct the error.

KFPS02157-E L

Shared memory error occurred while starting or terminating syncpoint dump service.reason code=aa....aa, function=bb....bb

A shared memory error occurred while starting or terminating the synchronization point dump service function.

aa....aa: Reason code

bb....bb: Name of the function resulting in the error

S: Cancels unit startup processing.

Action

Take action appropriate to the reason code, as listed below:

Reason code | Explanation | Action
4 | Shared memory cannot be accessed. | Contact the customer support center.
6 | Size of shared memory pool is too small to process the request.

KFPS02158-E L

Error occurred in status file while starting or terminating syncpoint dump service. reason code=aa....aa, function=bb....bb

A status file error occurred while starting or terminating the synchronization point dump service function.

aa....aa: Reason code

bb....bb: Name of the function resulting in the error

S: Cancels unit startup processing.

Action

Take action appropriate to the reason code, as listed below:

Reason code | Explanation | Action
41 | I/O error occurred. | Check the cause of the I/O error and take appropriate action.
43 | Work area cannot be allocated. | Check the memory usage.
44 | There are not enough buffer sectors. | Check the server definition.
45 | Requested number of records cannot be allocated (insufficient status file).
47 | Status server is not active. | Check the server execution status with a HiRDB command.
50 | Inter-process communication error occurred. | Check the cause of the error, take appropriate action,
52 | Swapping error occurred. | then restart the system.

KFPS02159-E L

Memory found insufficient while starting or terminating syncpoint dump service.

A memory shortage occurred while starting or terminating the synchronization point dump service function.

S: Cancels unit startup processing.

Action

Check the memory for any excess resources and release unneeded resources. Or, check the defined shared memory size, take appropriate action, then restart.

KFPS02160-E L

Error occurred in system service call while starting or terminating syncpoint dump service. reason code=aa....aa, function=bb....bb

An error occurred while starting or terminating the synchronization point dump service function.

aa....aa: Reason code

bb....bb: Name of the function resulting in the error

S: Cancels unit startup processing.

Action

Take action appropriate to the reason code, as listed below:

Reason code | Explanation | Action
72 | Status file write error occurred. | Check the cause of the error and take appropriate action.
73 | Status file read error occurred.
74 | Server definition analysis error occurred. | Check the corresponding server definition, correct the error, then restart the system.
75 | Server terminated abnormally during normal termination or planned shutdown. Or, server is engaged in abnormal termination processing. | Check the cause of the error and take appropriate action.
77 | Memory shortage occurred. | Check the memory usage.
78 | Attempt was made to terminate the server forcibly, but the server was on critical status. | Check the cause of the error and take appropriate action.
79 | Inter-process communication error occurred.

KFPS02167-W E

File group specified with the command is already open.

The file group specified in a command is already open.

S: Cancels command execution.

O: Enter the pdlogls command to check the file status.

KFPS02168-W E

File group specified with the command is already closed.

The file group specified in a command is already closed.

S: Cancels command execution.

O: Enter the pdlogls command to check the file status.

KFPS02169-E E

Failure to open syncpoint dump file.

The system failed to open a synchronization point dump file.

S: Cancels command execution.

O: Enter the pdlogls command to check the file status. Also, refer to the KFPS02122-W message that was output to the message log file to check the cause of the error.

KFPS02170-E E

Failure to close syncpoint dump file. reason code=aa....aa

The system failed to close a synchronization point dump file.

aa....aa: Reason code

S: Cancels command execution.

O: Check the reason code and take appropriate action:

Reason code | Explanation | Action
91 | Error occurred in the file system. | Refer to the KFPS02123-W message output to the log file to check the cause of the error and take appropriate action.
99 | Close request was issued for a valid file. | Enter the pdlogls command to check the status of the corresponding file.
100 | Close request was issued for a file being input or output. | Enter the pdlogls command to make sure that the most recent synchronization point dump file points to the current log, then re-execute the command.

KFPS02171-E E

Unable to perform command processing because there is not enough memory to allocate work area.

Command cannot be executed, because a work area cannot be allocated.

S: Cancels command execution.

Action

Check for excess memory resources and release any unneeded resource. Or, check the shared memory size specified in the definition, take appropriate action, then reenter the command.

KFPS02172-I E

There is no information to be displayed about syncpoint dump file.

There is no synchronization point dump file information to be displayed.
There is no synchronization point dump file information to be displayed by the pdlogls command.

S: Terminates command processing.

O: Check whether the system is in the online mode. Or, check the server execution status and reenter the command.

KFPS02173-E L

Status file error occurred during syncpoint dump processing. reason code=aa....aa

A status file error occurred during synchronization point dump processing.

aa....aa: Reason code

S: Cancels unit startup processing.

Action

See the reason code list and take appropriate action. Then re-start HiRDB. If it is necessary to contact the customer support center, obtain data on the error information and then contact the customer support center.

Reason code | Explanation | Action
40 | Specified key value already exists. | Check the server definition or initialization.
41 | I/O error occurred. | Check the cause of the I/O error and take appropriate action.
42 | Offset + length is outside the allocated area. | Contact the customer support center.
43 | Work area cannot be allocated. | Check the memory usage.
44 | There are not enough buffer sectors. | Check the server definition.
45 | Requested number of records cannot be allocated (insufficient status file size).
46 | No record has the corresponding key value. | Contact the customer support center.
47 | Status server is inactive. | Check the server execution status with a HiRDB command.
48 | Offset is outside the allocated area. | Contact the customer support center.
49 | Parameter format is invalid.
50 | Inter-process communication error occurred. | Check the server execution status with a HiRDB command.
51 | Requested size is invalid. | Contact the customer support center.
52 | Swapping error occurred. | See -1039 in 4.2 Detail codes for system-related errors, and take appropriate action. Then, start HiRDB.
53 | Protocol version error occurred. | Contact the customer support center.
54 | Size is different from an existing key value.

KFPS02174-E L

Contents of syncpoint dump file for aa....aa service are invalid,file group name=bb....bb

The content of the synchronization point dump file is invalid.

aa....aa: Server name

bb....bb: File group name of the synchronization point dump file where the error occurred

S: Continues processing.

Action

Re-create the synchronization point dump file of bb....bb.

KFPS02176-I L

No syncpoint dump file available for next acquisition.

No file is available for the next synchronization point dump.

Action

Open a reserve file to provide the file for the next synchronization point dump.

KFPS02177-I L

Number of syncpoint dump files is not enough for aa....aa service recovery; opens all files.

There are not enough synchronization point dump files to recover server aa....aa. The system opens all files.

aa....aa: Server name

KFPS02178-E E+L

Unable to acquire syncpoint dump for assuring syncpoint failure in remote site, server name=aa....aa, group=bb....bb, reason code=cc....cc

The RDAREA on a remote site for a synchronization point of cannot be acquired.
An inconsistency may have occurred in the data transmitted from server aa....aa that output this message to the remote site due to the Real Time SAN Replication not working correctly. If HiRDB is started on the remote site in this condition, HiRDB cannot start, the data lacks integrity, or the data is corrupt.

aa....aa: Name of the server for which a synchronization point dump could not be acquired

bb....bb: Name of the pair logical volume group that detected the error

cc....cc: Reason code

S: Suspends synchronization point acquisition processing if the protection mode (the value specified in the pd_rise_fence_level operand) is data. Resumes synchronization point acquisition processing if the protection mode is never.

Action

Refer to the list of reason codes, and take appropriate action. If HiRDB is running, remove the data inconsistency between the main site and the remote site by taking appropriate action, and then execute the pdlogsync command for server aa....aa and acquire the synchronization point dump.

Reason code
Explanation
Action

115
116
117
118
119
During server aa....aa synchronization point dump acquisition processing, the system was waiting for group bb....bb update data copy processing, but the wait failed.
See the KFPS04680-E or KFPS01815-E message displayed immediately before, investigate the cause of the error, and take appropriate action.

KFPS02179-I L

Syncpoint dump acquisition opportunities for aa....aa service were skipped.number of skip=bb....bb, log generation number=cc....cc factor code=ddd-ee

There was an opportunity to acquire a synchronization point dump, but because the last synchronization point dump was still processing, the synchronization point dump acquisition opportunity for server aa....aa was ignored.

aa....aa: Server name

bb....bb: Total number of synchronization point dump opportunities that were ignored

Even if synchronization point dumps have been collected, depending on the timing, synchronization point dump collection opportunities might be ignored. In such a case, 0 is displayed.

cc....cc: Log generation number whose synchronization point dump opportunity was ignored

ddd: Cause code indicating the reason for ignoring the synchronization point dump opportunity (this code indicates the HiRDB internal status; the user need not know the code)

ee: Detail code for the ignored synchronization point dump opportunity

S: Continues processing.

Action

This message is output in the following cases:

The system log file swap interval is short.

Execution of the UAP transaction is slow relative to the synchronization point dump acquisition interval.

Due to deferred write processing, synchronization point dump collection is slow.

If this message is output repeatedly, take the following action on the basis of the factor code:

factor code = A01-01
Take action as indicated in the section on the tuning of synchronization point dump processing when deferred write processing is applicable in the manual HiRDB Version 9 System Operation Guide.

factor code = A01-02
Transactions that were not completed when the last synchronization point dump was acquired are still not complete. The cause is the slow execution of the UAP transactions relative to the synchronization point dump acquisition interval. Take corrective action according to message KFPS04374-I, output immediately after this one. If this message is output again, even after taking these actions, take the actions below under Factor code other than the above.

Factor code other than the above
Increase the value of the pd_log_sdinterval operand. Alternatively, take measures to increase the size of the system log file. If this message continues to be repeatedly output, revise the UAP. Consider shortening the execution time per transaction by splitting the slow transactions into multiple transactions.

Also, even if this message is output, if there is sufficient system log file space prepared for the swap target, this will not be a hindrance to continuing online or restarting. However, it may take time to restart HiRDB.

KFPS02181-E L

Unable to find syncpoint dump file for aa....aa service recovery.

There is no synchronization point dump file for recovering server aa....aa.
If Real Time SAN Replication with the log-only synchronous method is used and a log application site HiRDB outputs this message, this indicates that no secondary synchronization point dump files are required for preparation for log application of server aa....aa. Consider the following causes:

There is an error in the path name or file name of the secondary synchronization point dump file specified in the pdlogadpf -d ssp operand.

The secondary synchronization point dump file specified in the pdlogadpf -d ssp operand does not exist.

The secondary synchronization point dump file specified in the pdlogadpf -d ssp operand cannot be accessed.

Preparation for log application was not completed correctly, because there is no pdlogadfg -d spd operand that specifies the same file group name as the pdlogadpf -d ssp operand.

aa....aa: Server name

S: Outputs the KFPS02102-E message and terminates HiRDB.

Action

Check the error message output before this message, make sure that the same synchronization point dump file is used that was used during the previous online session, then restart HiRDB.

If Real Time SAN Replication with the log-only synchronous method is used and a log application site HiRDB outputs this message, take the following actions:

Determine whether there is an error in the path name or file name of the secondary synchronization point dump file specified in the pdlogadpf -d ssp operand, and correct the error.

Investigate the reason that the secondary synchronization point dump file specified in the pdlogadpf -d ssp operand cannot be accessed, correct the error, perform preparation for log application, and restart HiRDB. For details about preparation for log application, see the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide.

If there is no pdlogadfg -d spd operand that specifies the same file group name as the pdlogadpf -d ssp operand, verify that the file group name specified in the pdlogadpf -d ssp operand is correct.

KFPS02182-E L

Insufficient memory. size=aa....aa, area type:bb....bb

A memory shortage occurred.

aa....aa: Size of area that was to be allocated

bb....bb: Type of area resulting in the memory shortage

S: Terminates HiRDB.

Action

If the unit terminated abnormally when the error occurred at the startup of a user server (executed by specifying the -s option of the pdstart command) that is not a back-end server using the standby-less system switchover (effects distributed) facility, specify server in the pd_shmpool_control operand in the system common definition, and then restart the unit. Otherwise, check the system definition, take appropriate action, and then restart HiRDB.

KFPS02183-I S+L+R

Syncpoint dump for aa....aa has been acquired to file group bb....bb. log file information:cc....cc,dd....dd,ee....ee. start time=ff....ff, end time=gg....gg

Synchronization point dump for server name aa....aa was collected in bb....bb.

aa....aa: Server name

bb....bb: File group of destination synchronization point dump file

cc....cc: Log file group name

dd....dd: Log file generation number

ee....ee: Log file block number

ff....ff: Synchronization point dump collection starting time (hh:mm:ss)

gg....gg: Synchronization point dump enabling completion time (hh:mm:ss)

S: Resumes processing.

KFPS02184-E E

Unable to close the file group because number of file groups is insufficient.

Specified file group cannot be closed, because there are not enough file groups.
If the specified file group is closed, the number of synchronization point dump file groups would be less than the number of guaranteed-valid generations + 1.

S: Cancels command execution.

O: Enter the pdlogls command to check the file status.

KFPS02185-I L

aa....aa service is recovered with syncpoint dump of file group bb....bb.

Server aa....aa was recovered from a synchronization point dump in file group bb....bb.

aa....aa: Server name

bb....bb: File group name

KFPS02186-W L

aa....aa service could not recovered with effective syncpoint dump.

Server aa....aa cannot be recovered from a valid synchronization point dump.

aa....aa: Server name

S: Attempts to recover the server from previous synchronization point dump generations that can be read.

Action

Check the guaranteed-valid generations to determine why they cannot be read and take appropriate action.

KFPS02187-I L

Number of syncpoint dump files is not enough for aa....aa service; continues syncpoint dump processing with file reduced mode

Operation has switched to the reduced mode, because there are not enough synchronization point dump files for server aa....aa.

aa....aa: Server name

Action

Refer to the message that was output before this message to check the cause.

KFPS02188-I L

Number of syncpoint dump files is enough for aa....aa service; continues syncpoint dump processing with normal mode

Operation has switched to the normal mode, because the specified number of synchronization point dump files were allocated for server aa....aa.

aa....aa: Server name

S: Resumes processing.

KFPS02189-W L

Take measure; syncpoint dump service for aa....aa service is file reduced mode

The synchronization point dump service function for server aa....aa is in the reduced operation mode; appropriate action should be taken immediately.

aa....aa: Server name

S: Resumes processing.

Action

Refer to the message that was output before this message to check the cause.

KFPS02190-E L

Number of pdlogadfg -d bbb commands with ONL exceeds the limit in definition file aa....aa

The number of pdlogadfg -d bbb specifications with ONL specified exceeds the limit.

aa....aa: File name of the server definition where the error occurred

bbb: File type

spd: Synchronization point dump file

ssp: Secondary synchronization point dump file

S: Terminates the HiRDB system.

Action

Limit the number of operands (pdlogadfg -d spd or ssp) with ONL specified in the server definition files to 30, and restart HiRDB.

KFPS02191-E E

-b option specified with this command is invalid.

An error was found in the specification of the -b option (B system). The -b option was not specified, even though the synchronization point dump file was duplicated. Or, the -b option was specified, even though the synchronization point dump file was not duplicated.

S: Terminates processing.

Action

Check the specification (whether or not the synchronization point dump file is duplicated) of the pd_spd_dual operand, and then re-execute the command.

KFPS02192-W E

File group specified with the command is already allocate

A file has already been allocated to the file group specified in a command.

S: Cancels command execution.

Action

Check the file group for which the physical file is to be allocated and re-execute the command.

KFPS02193-E E

Physical file name aa....aa specified with this command is invalid,system A/B=b

An error was found in the synchronization point dump file name specified by the command.

aa....aa: File name

If the file name exceeds 148 characters, the last 148 characters of the file name are output.

b: System type (a: A system, b: B system)

S: Terminates processing.

Action

Consider the following causes. Check the file name specified in the option, then re-execute the command.

The file path name exceeds the maximum number of characters.

The length of the HiRDB file name exceeds the maximum (30 characters).

The specified file name is in use by the file group of another synchronization point dump file.

KFPS02194-I L

Syncpoint dump file group cc....cc for aa....aa service has been allocated physical file bb....bb

The synchronization point dump file was allocated to server aa....aa.

aa....aa: Server name

bb....bb: File group name

cc....cc: File name

If the file name exceeds 122 characters, the last 122 characters of the file name are output.

S: Terminates processing.

KFPS02195-W E+L

Minor error occured while analyzing definitions for syncpoint dump service, file being analyzed: aa....aa, record number=bb....bb, reason code=cc....cc

An error occurred while analyzing the definition of synchronization point dump service function.

aa....aa: Name of definition file being analyzed

bb....bb: Erroneous record number

cc....cc: Reason code indicating the nature of the error:

408: The pdlogadfg operand is invalid (-d option may be missing)

409: The pdlogadpf operand is invalid (-d option may be missing)

S: Resumes processing.

Action

Correct the definition and restart HiRDB, if necessary.

KFPS02196-W L

Server name conflict with status-file. server=aa....aa

Although one of the following server name operations was performed with the pdstart operand of the system common definition, the server name conflicts with the status file because the status file was not initialized:

Server name change

Server name addition

Server name deletion

Server name specification sequence change

aa....aa: Server name

S: Allocates a new status file area and resumes processing. If sufficient space is not available for the status file, the unit terminates.

O: The next time the unit terminates normally, initialize the status file as described in the following table:

Change | Status file to be initialized
Change of pdstart server name | Initialize the status file of the corresponding server.
Addition, deletion, or server name specification sequence change in pdstart | Initialize all status files in the corresponding unit.

KFPS02200-E E+L

Unable to provide transaction log service for aa....aa service. reason code=bbbb

The transaction log service function cannot be provided to server aa....aa.

aa....aa: Server name

bbbb: Reason code

S: Terminates HiRDB abnormally.

Action

Take action appropriate to the reason code, as listed below, and restart HiRDB:

Reason code | Explanation | Action
0001 | Process private area shortage | Reduce the number of processes and restart HiRDB. If the same error recurs, contact the customer support center.
0100 | Shared memory shortage | Contact the customer support center.
1001 | Status file write failure | If an error message has been issued before this message, take action appropriate to that message. Otherwise, contact the customer support center.

KFPS02210-E E+L

Insufficient memory. size= aa....aa bytes, area type=bb....bb

A memory shortage occurred.

aa....aa: Size of area that was to be allocated

bb....bb: Type of area resulting in the memory shortage:

DYNAMIC_SHMPOOL: Dynamic shared memory

PROCESS: Process private area

STATIC_SHMPOOL: Static shared memory

S: Cancels processing.

Action

Memory shortage occurred in dynamic shared memory:

Check the values specified in the definition file, take appropriate action, then re-execute.

Memory shortage occurred in process private area:

Check the number of processes, take appropriate action, then re-execute.

Memory shortage occurred in static shared memory:

If the unit terminated abnormally when the error occurred at the startup of a user server (executed by specifying the -s option of the pdstart command) that is not a back-end server using the standby-less system switchover (effects distributed) facility, specify server in the pd_shmpool_control operand in the system common definition, and then restart the unit.

Otherwise, try re-executing at a later time.

If the same error recurs, contact the customer support center.

KFPS02220-E E+L

Unable to recover transaction due to log error

A transaction could not be recovered because an invalid log was detected during HiRDB full recovery or log application processing.
Possible reasons are as follows:

The system log file was damaged.

An invalid system log file was used to execute full recovery of HiRDB.

The paircreate or pairresync command was executed to perform formatting and copying of the pair volume that stores the system log files.

S: Terminates processing.

O: Take the following actions:

Transaction execution site, or if Real Time SAN Replication with the log-only synchronous method is not used
Check the log file and eliminate the cause of the error. To recover the transaction, restart HiRDB.

Log application site
Confirm that the status of the pair volume is PAIR, and then restart HiRDB. If HiRDB cannot be started, perform preparation for log application, and then restart HiRDB.

If a site takeover for disasters has occurred, see the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide.

KFPS02235-I L

Transaction branch in recovery. server=aa....aa,TRNGID=bb....bb,TRNBID=cc....cc,block number=dd....dd,last block number=ee....ee

Rollback processing is in progress.

aa....aa: Name of server

bb....bb: Global identifier of the transaction

cc....cc: Branch identifier of the transaction

dd....dd: Block number (hexadecimal) of the system log being loaded

ee....ee: System log block number (hexadecimal) that was previously output by message KFPS02235-I (if message KFPS02235-I is first output, the block number of the rollback start point)

S: Continues processing.

KFPS02240-W L

aa....aa recovery to last commit point bbbb/cc/dd ee:ff:gg, TRNGID=hh....hh, TRNBID=ii....ii, PROGRAM=jj....jj, INFO_FILE=kk....kk

Server aa....aa recovered the database to the commit point at bbbb/cc/dd ee:ff:gg.

aa....aa: Name of the server that performed the database recovery

bbbb: Date of the most recent commit (year)

cc: Date of the most recent commit (month)

dd: Date of the most recent commit (day)

ee: Time of the most recent commit (hour)

ff: Time of the most recent commit (minute)

gg: Time of the most recent commit (second)

hh....hh: Global identifier of the transaction of the most recent commit

ii....ii: Branch identifier of the transaction of the most recent commit

jj....jj: Value of PDCLTAPNAME of the transaction of the most recent commit (for a utility, "****" is displayed)

kk....kk: Path name of the recovered transaction information file (if the path name of the transaction information file is longer than 54 characters, only the last 54 characters are output)

S: Continues processing.

Action

Check the date and time of the commit and whether recovery could be made to the most recent database from the transaction information file. For details about how to check the transaction information file, see the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide. If recovery could not be made to the most recent database, re-execute the update of the non-recovered data.

KFPS02254-E E+L

Unable to start transaction log service. reason code=aaaa

The error indicated by the reason code occurred while starting the transaction log service function; this function cannot be started.

aaaa: Reason code

S: Terminates HiRDB abnormally.

Action

Take action appropriate to the reason code, as listed below, and restart HiRDB:

Reason code
Explanation
Action

0001
Process private area shortage
Reduce the number of processes and restart HiRDB. If the same error recurs, contact the customer support center.

0100
Shared memory shortage
Contact the customer support center.

0200
Error during definition analysis startup processing
If an error message has been issued before this message, take action appropriate to that message. Otherwise, contact the customer support center.

0201
Analysis error in system common definition or unit control information definition

0300
Communication error
See 4.1 Detail codes for RPC-related errors, and take appropriate action.

0301
Timeout

0600
Server information failed to be registered in the name service function.
If an error message was output before this message, take the action indicated in the message.
If no error message was output, contact the customer support center.

1000
Status file read error

1001
Status file write error

1002
Status file allocation failure

KFPS02255-E E+L

Error occurred while terminating transaction log service; continues processing. reason code=aaaa

The error indicated by the reason code occurred while terminating the transaction log service function, but the system is resuming termination processing.

aaaa: Reason code

S: Terminates HiRDB abnormally.

Action

Take action appropriate to the reason code, as listed below, before the next HiRDB startup:

Reason code | Explanation | Action
0001 | Process private area shortage | Reduce the number of processes and restart HiRDB. If the same error recurs, contact the customer support center.
0100 | Shared memory shortage | Contact the customer support center.
0601 | Service information failed to be deleted from the name service function | If an error message has been issued before this message, take action appropriate to that message. Otherwise, contact the customer support center.
1001 | Status file write error
1003 | Status file release error

KFPS02256-E E+L

Unable to continue transaction log service.reason code=aaaa

The system log I/O service for the transaction cannot be continued.

aaaa: Reason code:

2000: Synchronization point dump I/O service cannot be used.

2001: Start time for synchronization point dump I/O service is incorrect.

2003: I/O processing for synchronization point dump file is disabled.

S: Terminates HiRDB abnormally.

O: If the following message related to the synchronization point dump I/O service was output before or is output after this message, take action appropriate to that message, then re-execute the service:

KFPS021xx-y (where xx is 00 to 99 and y is E, W, or I)
If there is no message related to the synchronization point dump I/O service, contact the HiRDB administrator.

Action

Refer to the message log and check whether an error message for an error other than one related to the synchronization point dump I/O service was output. After the cause of the error is identified, take appropriate action, then re-execute the service. If the above does not apply, contact the customer support center.

KFPS03302-E E+L

Unable to start interval service. reason code=aaaa

The interval service function cannot be started.

aaaa: Reason code:

200: Communication error

300: Memory shortage

400: Shared memory shortage

500: System error

600: Status (file) error

700: adm error

S: Terminates processing.

O: Contact the system administrator, take action appropriate to the reason code, then restart the HiRDB system.

Action

Take action appropriate to the reason code.

KFPS03700-E R

Error occurred in XA interface, func=aa....aa, reason=bb....bb, code=cc....cc

An XA interface error occurred.

aa....aa: Name of the function resulting in the error

bb....bb: Character string indicating the type of error

Character string | Error type
SVR PROC | Error occurred at HiRDB server during transaction settlement processing.
SQL ERR | Error occurred during SQL processing.
CLT ENV | Error occurred while setting the environment to use the XA interface.
RPC INIT | Error occurred during initialization of communication environment.
RPC CALL | Error occurred during communication.
TRN OPEN | Error occurred while a communication path was being secured during transaction recovery processing.
TRN CMIT | Error occurred at HiRDB server during transaction recovery processing (commit).
TRN ROLB | Error occurred at HiRDB server during transaction recovery processing (rollback).
TRN WAIT | Error occurred at HiRDB server while monitoring termination of transaction recovery processing.
TRN RCV | Error occurred at HiRDB server while collecting unsettled transaction information.
AX FUNC | Error occurred during transaction startup or restart processing.
AX TRID | Transaction ID was invalid during transaction startup or restart processing.
TXA OPEN | Error occurred during opening of the resource manager.
TXA STAT | An error occurred during transaction start/restart (while a multi-thread for support of the XA interface was being used).
TXA CLOS | Error occurred during closing of the resource manager.
TXA ENV | Error occurred during linkage with the transaction manager.

cc....cc: Code indicating the cause of the error

S: Resumes processing.

P or O: Take action appropriate to the code indicating the cause of the error:

Type of error
Code showing the cause of the error
Explanation
Action

SVR PROC
-902
Rollback occurred erroneously.
Contact the customer support center.

SQL CODE
SQLCODE
See the explanation of the corresponding SQL code.
Check the corresponding SQL code and take appropriate action.

CLT ENV
-1
A value other than 0 or 1 is specified in the client environment definition PDXAMODE.
Specify 0 or 1 in the client environment definition PDXAMODE. For details on PDXAMODE, see the HiRDB Version 9 UAP Development Guide.

-10
The value specified in the client environment definition is incorrect.
See the HiRDB Version 9 UAP Development Guide, and check whether the value specified for the client environment definition is correct.

TXA CLOS
-6
The transaction migration settings are different for the transaction manager and the HiRDB client.
Make the settings match for the transaction manager and the HiRDB client. Set the HiRDB client transaction migration in the client environment definition PDXAMODE. For details on transaction migration, see the HiRDB Version 9 Installation and Design Guide.

RPC INIT
-2403
Initialization failed.
The server may not be active. Check the server status.

-2415
HiRDB server is inactive.

RPC CALL
-2404
Memory shortage occurred.
A network error may have occurred; or, the server may not be active. Check the network status or server status.

-2406
-2418
Network error occurred.

-2407
Transfer timeout occurred.

-2410
-2411
-2414
-2415
HiRDB server is inactive.

-2412
-2413
-2432
HiRDB server is engaged in termination processing.

-2416
System error occurred at HiRDB server.

-2417
Memory shortage occurred at HiRDB server.

-2420
HiRDB server is being started.

-2431
Number of connections to the HiRDB server exceeded the maximum number of concurrent connections.

TRN OPEN
-99
HiRDB server is starting.
Possible causes are a network error or the HiRDB server not starting. Check the network status or HiRDB server status.

100
Connection established to standby HiRDB system.
Check if a running system host name is specified in the client environment variable HiRDB_PDHOST for the OLTP product.
If a running system host name is specified, check to be sure the version of HiRDB Client is not 06-02-/A or earlier. If HiRDB Client is version 06-02-/A or earlier, this error code is sometimes output when a unit is in the primary system and that system is a standby system. In this case, upgrade HiRDB Client to version 06-02-/B or later. If you cannot upgrade right away, switch the primary system unit from a standby system to a running system.

TRN CMIT
TRN ROLB
TRN WAIT
TRN RCV
-4
Error occurred during host-to-host communication.
The server may not be active. Check the server status.

-6
Rollback occurred erroneously.
Contact the customer support center.

-7
Applicable transaction was not found in the HiRDB system.
The applicable transaction was independently determined by the HiRDB system. Check the status of the OLTP transaction.

100
Connection established to a standby HiRDB system.
Check if a running system host name is specified in the client environment variable HiRDB_PDHOST for the OLTP product.
If a running system host name is specified, check to be sure the version of HiRDB Client is not 06-02-/A or earlier. If HiRDB Client is version 06-02-/A or earlier, this error code is sometimes output when a unit is in the primay system and that system is a standby system. In this case, upgrade HiRDB Client to version 06-02-/B or later. If you cannot upgrade right away, switch the primary system unit from a standby system to a running system.

AX FUNC
-1
Error occurred in OLTP.
Check the status of OLTP.

-3
Issuance sequence is invalid.
Application program may not be receiving the transaction service. Check the application program.

AX TRID
-1
Data is invalid in transaction ID.
Check the status of OLTP.

-2
Transaction ID was not specified.

TXA OPEN
-2
The number of concurrent connections per process has exceeded the maximum number of concurrent transactions.
Check the maximum number of concurrent transactions. Set the maximum number of concurrent transactions using the client environment definition PDTXACANUM.

-3
Connection could not be established with the HiRDB server using a multi-threaded XA interface.
Upgrade the HiRDB version so that connection can be established with the HiRDB server using a multi-threaded XA interface.

TXA STAT
-2
The number of transactions that can be processed concurrently in a single process has exceeded the maximum.
Check the maximum number of transactions that can be processed concurrently, which is specified in the PDTXACANUM client environment definition.

-3
Cannot connect to HiRDB server using a multi-thread that supports the XA interface.
Upgrade the HiRDB server version so that it can be connected using a multi-thread that supports the XA interface.

TXA ENV
-1
When connecting to HiRDB using a data source in standard advanced mode from Cosminexus, the settings are ignored because the XA Open String of the Cosminexus data source is undefined or the format is invalid. Also, the client environment definition PDUSER is not set.
Check the setting of the Cosminexus data source XA Open String and the client environment definition PDUSER.

-2
When connecting to HiRDB from OpenTP1/Server Base Enterprise Option, the setting is ignored because the character string used by the xa_open function is not set or the format is invalid. Also, the client environment definition PDUSER is not set.
Check the setting of the OpenTP1/Server Base Enterprise Option xa_open function character string and the client environment definition PDUSER.

KFPS04128-I E

Usage: pdlogadpf -d spd [-s server_name] -g file_group_name -a physical_file_name

Displays the format of the pdlogadpf command for a HiRDB/Single Server. This message is output when the specified command format is invalid.

KFPS04128-I E

Usage: pdlogadpf -d spd -s server_name -g file_group_name -a physical_file_name

Displays the format of the pdlogadpf command for a HiRDB/Parallel Server. This message is output when the specified command format is invalid.

KFPS04160-E E

Specification of aa option required.

Required option is missing.

aa: Option name

S: Terminates processing.

Action

Specify the required option and re-execute.

KFPS04161-E E

Argument of aa option is invalid.

An option argument is missing or its specification is invalid.

aa: Option name

S: Terminates processing.

Action

Specify the correct option and re-execute.

KFPS04162-W E

Unable to specify aa option. ignored.

An invalid option was specified (the system ignored the option).

aa: Option name

S: Resumes processing.

Action

Delete the invalid option.

KFPS04163-E E

Specified hostname conflicts with the server name.

Specified host name is different from the host name for the specified HiRDB server.

S: Terminates processing.

Action

Either omit the host name or specify the correct host name for the HiRDB server.

KFPS04164-E E

Server name must be equal to SDS's name for single server.

For HiRDB/Single Servers, the server name must be the same as the single server's name.

S: Terminates processing.

Action

For HiRDB/Single Servers, either omit the server name or specify the correct HiRDB server name.

KFPS04165-E E

Hostname must be equal to SDS hostname for single server.

For HiRDB/Single Servers, the host name must be the same as the single server's host name.

S: Terminates processing.

Action

For HiRDB/Single Servers, either omit the host name or specify the correct host name.

KFPS04170-E E

Failed to open (unload) log file(aa....aa). reason code=bbbbbb.

A log file or unload log file failed to open.

aa....aa: File name

If the file name exceeds 163 characters, the last 163 characters of the file name are output.

bbbbbb: Return value of pdi_ofl_open() or p_f_ios_open()

S: Continues processing.

KFPS04171-E E

Unable to get server name because specfication of 'pdstart' operand is invalid in system definition file.

The server name cannot be obtained, because the pdstart operand in the system common definition is invalid.

S: Terminates processing.

Action

Correct the pdstart operand specification and re-execute.

KFPS04172-E E

Unable to execute command due to failure of aa....aa system call(command), code=bb....bb

A command cannot be executed due to an error in system call (command) aa....aa.
This message is output when activation of an internal command called by the log command fails.

aa....aa: System call or command resulting in the error:

{exec | fork | rsh rcp | tempnam | open}

bb....bb: Internal code for the system call or the rsh return value

If tempnam or open is output in aa....aa, the errno value is output.

S: Terminates processing.

Action

In UNIX:

If tempnam or open is output in aa....aa, refer to errno.h or the applicable OS manual to eliminate the cause of the error based on the errno value, and then re-execute the command once recovery from the error is complete. The cause of the error is in the directory specified in the environment variable TMPDIR (if the environment variable TMPDIR is not specified, the cause of the error is in the directory $PDDIR/tmp), or in a file that begins with the prefix plcmd in that directory. For typical errno examples, see 4.3 System call return codes.

If exec, fork, or rsh rcp is output in aa....aa, revise the environment variables or HiRDB system definition, and then retry the operation.

In Windows:

If tempnam or open is output in aa....aa, check the mnemonic in the OS's errno definition file or refer to the applicable OS manual to eliminate the cause of the error based on the errno value, and then re-execute the command once recovery from the error is complete. The cause of the error is in the directory specified in the environment variable TMP or TEMP (if environment variables TMP and TEMP are not specified, the cause of the error is in the directory %PDDIR%\tmp), or in a file that begins with the prefix plcmd in that directory. For typical errno examples, see 4.3 System call return codes.

If exec, fork, or rsh rcp is output in aa....aa, revise the environment variables or HiRDB system definition, and then retry the operation.

KFPS04173-E E

Specified hostname invalid in 'pdstart' operand

The host name specified in the pdstart operand of the system common definition is not valid.

S: Terminates processing.

O: Correct the system common definition and re-execute.

Action

Correct the host name specification in the pdstart operand of the system common definition.

KFPS04178-E E

Unable to specify aa option

The aa option cannot be specified.

aa: Option name

S: Terminates processing.

O: Re-execute the command without specifying the aa option.

KFPS04179-E E

Unit ID aaaa is invalid

The unit identifier specified in the command option is invalid.

aaaa: Unit identifier

S: Terminates processing.

O: Check whether unit aaaa belongs to the standby-less system switchover (effects distributed) HA group. If it does not belong to the HA group, specify the unit identifier of a unit that belongs to the HA group, then re-execute the command.

KFPS04200-E E

(Specification of aa option required.)

A required option is missing.

aa: Option name

S: Terminates processing.

Action

Add the required option and re-execute.

KFPS04201-E E

Argument of aa option is invalid.

An option argument is missing or invalid.

aa: Option name

S: Terminates processing.

Action

Specify the correct option and re-execute.

KFPS04202-E E

One of aa....aa options must be specified.

One of the listed options must be specified.

aa....aa: List of options (separated by the comma)

S: Terminates processing.

Action

Specify one of the options and re-execute.

KFPS04203-E E

Only of aa....aa options can specified.

Only one of the listed options can be specified.
This message is output when lock options are specified.

aa....aa: List of options (separated by the comma)

S: Terminates processing.

Action

Specify only one of the options and re-execute.

KFPS04204-E E

Specified hostname conflicts with the server name.

Specified host name does not match the host name for the specified HiRDB server.

S: Terminates processing.

Action

For a HiRDB server, either omit the host name or specify the correct host name for the HiRDB server.

KFPS04205-E E

Server name must be equal to SDS's name for single server.

For HiRDB/Single Servers, the server name must be the same as the single server's server name.
Because a HiRDB/Single Server consists of only one HiRDB server, specification of a server name can be omitted. This message is output when the specified server name is not the defined single server's server name.

S: Terminates processing.

Action

For HiRDB/Single Servers, either omit the server name or specify the correct HiRDB server name.

KFPS04206-E E

Hostname must be equal to SDS hostname for single server.

For HiRDB/Single Servers, the host name must be the single server host name.
Because a HiRDB/Single Server consists of only one host, specification of a host name can be omitted. This message is output when the specified host name is not the local host name.

S: Terminates processing.

Action

For HiRDB/Single Servers, either omit the host name or specify the correct host name.

KFPS04207-E E

Unable to get server name because specfication of 'pdstart' operand is invalid in system definition file.

The server name cannot be obtained, because the pdstart operand in the system common definition is invalid.

S: Terminates processing.

Action

Correct the pdstart operand specification in the system common definition and re-execute.

KFPS04208-E E

Unable to execute command due to failure of aa....aa system call (command), code=bb....bb

A command cannot be executed due to an error in system call (command) aa....aa.
This message is output when activation of an internal command called by the status log command fails.

aa....aa: System call or command resulting in the error:

{exec | fork | rsh | tempnam | open}

bb....bb: Internal code for the system call or the rsh return value

If tempnam or open is output in aa....aa, the errno value is output.

S: Terminates processing.

Action

In UNIX:

If tempnam or open is output in aa....aa, refer to errno.h or the applicable OS manual to eliminate the cause of the error based on the errno value, and then re-execute the command once recovery from the error is complete. The cause of the error is in the directory specified in the environment variable TMPDIR (if the environment variable TMPDIR is not specified, the cause of the error is in the directory $PDDIR/tmp), or in a file that begins with the prefix pscmd in that directory. For typical errno examples, see 4.3 System call return codes.

If exec, fork, or rsh is output in aa....aa, revise the environment variables or system definition file and the re-execute.

In Windows:

If tempnam or open is output in aa....aa, check the mnemonic in the OS's errno definition file or refer to the applicable OS manual to eliminate the cause of the error based on the errno value, and then re-execute the command once recovery from the error is complete. The cause of the error is in the directory specified in the environment variable TMP or TEMP (if environment variables TMP and TEMP are not specified, the cause of the error is in the directory %PDDIR%\tmp), or in a file that begins with the prefix pscmd in that directory. For typical errno examples, see 4.3 System call return codes. If exec, fork, or rsh is output in aa....aa, revise the environment variables or system definition file and the re-execute.

KFPS04209-E E

Specified hostname invalid in 'pdstart' operand.

The host name specified in the pdstart operand of the system common definition is not valid.

S: Terminates processing.

O: Correct the system common definition and re-execute.

Action

Correct the host name specification in the pdstart operand of the system common definition.

KFPS04210-E E

Unit ID aaaa is invalid

The unit identifier specified in the command option is invalid.

aaaa: Unit identifier specified in the command option

S: Terminates processing.

O: Specify the unit identifier of the running system unit of the HiRDB server specified in the command option, and then re-execute the command.

KFPS04211-E E

Unable to specify aa option

The aa option cannot be specified.

aa: Name of the option that cannot be specified

S: Terminates processing.

O: Re-execute the command without specifying the aa option.

KFPS04320-W L

Failure to open syncpoint dump file for aa....aa service,file group name=bb....bb,system A/B=c,reason code=dddd

An attempt to open a synchronization point dump file failed. The file could not be opened.

aa....aa: Server name

bb....bb: File group name of the synchronization point dump file

c: System type (a: A system, b: B system)

dddd: Reason code

S: Continues processing.

Action

Take action according to the reason code.

Reason code
Description
Action

59
File status flag is invalid.
Contact the customer support center.

61
The HiRDB file name is invalid.
Check and, if necessary, revise the server definition.

62
No synchronization point dump file was created in the HiRDB file system area for system files.
Create a synchronization point dump file in the HiRDB file system area for system files.
If Real Time SAN Replication is used, make the path to reference the synchronization point dump file on the remote site the same as on the main site. For a log application site, confirm that the path specified in the pdlogadpf -d ssp operand matches the path of the secondary synchronization point dump file created in the preparation for log application.

63
No synchronization point dump file was found.

64
File system versions do not match.
Re-evaluate the HiRDB execution environment.

65
File system locking error occurred.

66
Shortage of file system lock segments.
Re-evaluate the amount of memory used.

67
107
The maximum was exceeded when opening the file system.
Close unnecessary files or re-evaluate the open file limit. Re-create the kernel if necessary.

68
There is no access privilege for the corresponding HiRDB file system area.
Modify the access privileges for the corresponding HiRDB file system area by using an OS command (chmod, for example).

70
File system I/O error.
Check for the cause of the I/O error, and then take appropriate action.

71
There is a shortage of file system memory.
Re-evaluate the amount of memory used.

88
Memory shortage.
Re-evaluate the usage status of the process private area.

92
A file detection error occurred. (Either the file was not initialized as a synchronization point dump file or is a synchronization point dump file in use by another server or HiRDB system.)
To check for the error cause:

Re-evaluate the pdlogadpf operand of the synchronization point dump file or the system common definition.

Initialize the HiRDB file system area for use by synchronization point dump files, and then re-execute.

97
Invalid size.
Re-evaluate the size of the synchronization point dump file.

98
I/O error.
Check for the cause of the I/O error, and then take appropriate action.

106
Invalid file name.
Consider the following causes:

An invalid character was used in the file name.

The HiRDB file name length exceeded the maximum (30 characters).

Re-evaluate the file name specified by the server definition or command operand.

108
File name is not registered.
Use the pdlogadpf command to register a file name corresponding to the applicable file group.

121
The possible causes are as follows:

An attempt was made to open a synchronization point dump file created in a HiRDB file system area that exceeds 2 GB, but N is specified in the pd_large_file_use operand.

An attempt was made to open a synchronization point dump file created in a HiRDB file system area created with the pdfmkfs -a command, but N is specified in the pd_large_file_use operand.

Specify Y for the pd_large_file_use operand, or omit the specification.

KFPS04321-W L

Failure to close syncpoint dump file for aa....aa service,file group name=bb....bb,system A/B=c,reason code=dddd

An attempt to close a synchronization point dump file failed. The file could not be closed.

aa....aa: Server name

bb....bb: File group name of the synchronization point dump file

c: System type (a: A system, b: B system)

dddd: Reason code

S: Continues processing.

Action

Take action according to the reason code.

Reason code
Description
Action

66
Shortage of file system lock segments.
Re-evaluate the amount of memory used.

70
File system I/O error.
Check for the cause of the I/O error, and then take appropriate action.

71
There is a shortage of file system memory.
Re-evaluate the amount of memory used.

106
File system path error.
Consider the following causes:

An invalid character was used in the path name.

The HiRDB file name length exceeded the maximum (30 characters).

Determine if the file name specification is valid.

205
A program internal conflict was detected.
Contact the customer support center.

KFPS04322-W L

Failure to write to syncpoint dump file for aa....aa service,file group name=bb....bb,system A/B=c,reason code=dddd

An attempt to write a synchronization point dump file failed. The file could not be written.

aa....aa: Server name

bb....bb: File group name of the synchronization point dump file

c: System type (a: A system, b: B system)

dddd: Reason code

S: Continues processing.

Action

Take action according to the reason code.

Reason code
Description
Action

1
A record output request that exceeded the file area was issued.
Contact the customer support center.

70
File system I/O error.
Check for the cause of the I/O error, and then take appropriate action.

71
Memory is insufficient.
Review the memory requirements. If there is a problem, take corrective action such as increasing the amount of memory or reducing the number of resident processes. If this fails to resolve the problem, contact the customer support center.

95
A synchronization point dump file for the requested number of records could not be written into a file.
Contact the customer support center.

202
204
207
209
An error was detected while a synchronization point dump file was being output.

KFPS04323-W L

Failure to read from syncpoint dump file for aa....aa service,file group name=bb....bb,system A/B=c,reason code=dddd

An attempt to read a synchronization point dump file failed. The file could not be read.

aa....aa: Server name

bb....bb: File group name of the synchronization point dump file

c: System type (a: A system, b: B system)

dddd: Reason code

S: Continues processing.

Action

Take action according to the reason code.

Reason code
Description
Action

1
A record input request that exceeded the file area was issued.
Contact the customer support center.

70
An I/O error occurred.
Check for the cause of the error, and then take appropriate action.

71
Memory is insufficient.
Review the memory requirements. If there is a problem, take corrective action such as increasing the amount of memory or reducing the number of resident processes. If this fails to resolve the problem, contact the customer support center.

201
203
206
208
An error was detected while a synchronization point dump file was being input.
Contact the customer support center.

KFPS04370-W L

Syncpoint dump file is already closed,system A/B=a

The synchronization point dump file is already closed.

a: System type (a: A system, b: B system)

S: Terminates processing.

Action

Execute the pdlogls -d spd -e command and check the status of the synchronization point dump file.

KFPS04371-W L

Syncpoint dump file is already opened,system A/B=a

The synchronization point dump file is already open.

a: System type (a: A system, b: B system)

S: Terminates processing.

Action

Execute the pdlogls -d spd -e command and check the status of the synchronization point dump file.

KFPS04372-I L

Syncpoint dump file for aa....aa service has been opened,file group name=bb....bb,system A/B=c

A synchronization point dump file was opened for the aa....aa server.

aa....aa: Server name

bb....bb: File group name of the synchronization point dump file

c: System type (a: A system, b: B system)

S: Continues processing.

KFPS04373-I L

Syncpoint dump file for aa....aa service has been closed,file group name=bb....bb,system A/B=c

A synchronization point dump file was closed for the aa....aa server.

aa....aa: Server name

bb....bb: File group name of the synchronization point dump file

c: System type (a: A system, b: B system)

S: Continues processing.

KFPS04374-I L

Syncpoint skip inf. SERVER=aa....aa,TRNCNT=bb....bb,TGID=cc....ccdd....dd,TBID=cc....ccee....ee,PID=ff....ff,C-PID=gg....gg(hh....hh),TIME=ii....ii,PROGRAM=jj....jj

This message provides maintenance information when a synchronization point dump acquisition opportunity is ignored or synchronization point dump activation processing is not completed because transactions that were not completed at the time of the last synchronization point dump acquisition are still not complete.
If factor code in the KFPS02179-I that was output immediately before this message is A01-02, this message outputs the following information:

The number of uncompleted transactions

Information about the first uncompleted database update transaction

Normally, information about the first uncompleted database update transaction is output in this message, unless the corresponding transaction is completed while its information is being acquired, in which case its transaction information is not output. In this case, **** is output as the transaction information.
If the client connected to the HiRDB server (UAP) is an application complying with X/Open, or the XDS client, message KFPS04375-I is output after this one.

aa....aa: Name of server

bb....bb: Number of uncompleted transactions

Outputs the number of uncompleted database update transactions. If the uncompleted database update transactions are all completed while the information is being acquired, 0 is displayed.

cc....cc: HiRDB system identifier, or unit identifier

Outputs information about the first uncompleted database update transaction. If the corresponding transaction is completed while the information is being acquired, **** is output.

dd....dd: Global transaction number

Outputs information about the first uncompleted database update transaction. No information is output if the corresponding transaction is completed while the information is being acquired.

ee....ee: Transaction branch number

Outputs information about the first uncompleted database update transaction. No information is output if the corresponding transaction is completed while the information is being acquired.

ff....ff: Process ID of the HiRDB server that was processing the transaction as an extension of the processing of the UAP or utility

Outputs information about the first uncompleted database update transaction. If the corresponding transaction is completed while the information is being acquired, **** is output.

gg....gg: Process ID of the HiRDB client (a UAP or a utility) that was connected to a server process

If the server process is one of the following, 0 is displayed:

A server process that is not connected to a client

A server process that is connected to a client linked to a client library version prior to 04-00

A server process that is connected to a Type 4 JDBC Driver

Outputs information about the first uncompleted database update transaction. If the corresponding transaction is completed while the information is being acquired, **** is output.

hh....hh: IP address of the HiRDB client (a UAP or a utility) that was connected to a server process

In the following cases, 0.0.0.0 is displayed:

A server process that is not connected to a client

If the client library for linking to the UAP is prior to version 04-00

Outputs information about the first uncompleted database update transaction. If the corresponding transaction is completed while the information is being acquired, **** is output.

ii....ii: Date and time of the first database update transaction (yyyy/mm/dd hh:mm:ss)

Outputs information about the first uncompleted database update transaction. If the corresponding transaction is completed while the information is being acquired, **** is output.

jj....jj: UAP identification information

Outputs the UAP name specified in PDCLTAPNAME in the client environment definition.

If PDCLTAPNAME is not set, Unknown is displayed.

For a utility, the name of the utility command is displayed.

Outputs information about the first uncompleted database update transaction. If the corresponding transaction is completed while the information is being acquired, **** is output. However, in the following cases, this information might be left blank:

The UAP was running as a utility server process.

The UAP identification information cannot be obtained due to an error.

S: Continues processing.

Action

When the number of uncompleted transactions is 0:

Because all uncompleted transactions were completed immediately before this message was output, no action is required.

When the number of uncompleted transactions is 1:

Based on the transaction information that was output, check whether the transactions have been uncompleted for an extended period, and then execute the commit or cancel as necessary.

When the number of uncompleted transactions is 2 or more:

Execute the command pdls -d trn, check whether the transactions have been uncompleted for an extended period, and then execute the commit or cancel as necessary.

KFPS04375-I L

Syncpoint skip inf2. SERVER=aa....aa,TMID=bbbb,XID=cc....cc,dd....dd,ENVGRP=eeee

If the client connected to the HiRDB server (UAP) is an application complying with X/Open, or an XDS client, this message is output following message KFPS04374-I.

aa....aa: Name of server

bbbb: OLTP identifier of the connected OLTP (HiRDB_PDTMID or PDTMID in the client environment definition)

This information is output if the client connected to the HiRDB server process (UAP) is an application complying with X/Open, or an XDS client. If no OLTP identifier is specified, **** is output. If an XDS client is used, HRDB is output.

cc....cc,dd....dd:

One of the following is output:

The transaction identifier assigned by OLTP
This information is output when the client (UAP) connected to the HiRDB server process is an application complying with X/Open and the OLTP is OpenTP1 or TPBroker for C++.

The transaction identifier assigned by XDS
This information is output when the client (UAP) connected to the HiRDB server process is an XDS client.

eeee: Environment variable group identifier assigned by OLTP

If the client (UAP) connected to the HiRDB server process is an application complying with X/Open and the multi-connection facility is used, this information is output. If the multi-connection facility is not used, **** is output.

S: Continues processing.

Action

See the description of message KFPS04374-I.

KFPS04602-W L

Unable to create pd_tmp_directory directory,unit ID : aaaa, directory : bb....bb

The specified directory could not be created in the pd_tmp_directory operand.

aaaa: Unit identifier

bb....bb: Specified directory name in the pd_tmp_directory operand

S: Because the directory specified in the pd_tmp_directory operand cannot be created, a directory is assumed, and processing continues. For details about assumed directories, refer to message KFPS04643-I.

O: Contact a HiRDB administrator.

Action

To use directories other than those assumed by HiRDB, reset the specifications for the pd_tmp_directory operand. Note that if specifications are changed, the work file remains in the directory that it was in prior to the change. If you do not need it, delete it.

KFPS04603-W E+L

Specified pd_tmp_directory directory not exist,unit ID : aaaa, directory : bb....bb

The directory specified in the pd_tmp_directory operand or environment variable TMP (In UNIX: TMPDIR) cannot be referenced.

aaaa: Unit identifier

bb....bb: Specified directory in the operand or environment variable

S: Because the specified directory cannot be referenced, a directory is assumed, and processing continues. For details about assumed directories, refer to message KFPS04643-I.

O: Contact a HiRDB administrator.

Action

To use directories other than those assumed by HiRDB, reset the specifications. Note that if the specifications are changed, the work file remains in the directory that it was in prior to the change. If you do not need it, delete it.

KFPS04604-W E+L

Invalid value for variable pd_tmp_directory,reason code=aa....aa

The value specified in the pd_tmp_directory operand is invalid.

aa....aa: Reason code

NOT_ABSOLUTE_PATH: The specified value is not an absolute path.

INVALID PATH: The specified value is not a valid path name.

S: Because the directory specified in the pd_tmp_directory operand is invalid, a directory is assumed, and processing continues. For details about assumed directories, refer to message KFPS04643-I.

O: Contact a HiRDB administrator.

Action

To use directories other than those assumed by HiRDB, reset the specifications for the pd_tmp_directory operand. Note that if the specifications are changed, the work file remains in the directory that it was in prior to the change. If you do not need it, delete it.

If the reason code is INVALID_PATH, specify the following directory in the pd_tmp_directory operand. Specify a different directory name.

In UNIX: / (root directory)

In Windows: Directly under the drive (for example, C:\)

KFPS04605-W L

Unable to specify aa....aa operand, ignored

A definition that cannot be specified for the platform was specified.

aa....aa: Ignored definition

S: Ignores the specified definition and continues processing

Action

Delete the corresponding definition from the definition file and start HiRDB.

KFPS04606-W L

Unable to connect to event server of JP1

The system common definition specifies linkage with Job Management Partner 1 (pd_jp1_use=Y or pd_jp_event_level=2), but connection cannot be established with the Job Management Partner 1 event server.

S: Continues processing.

Action

If it is necessary that events be output to Job Management Partner/Integrated Manager, investigate the cause of the connection failure and eliminate it. Job Management Partner/Integrated Manager or Job Management Partner/Base may not be installed.

If it is not necessary that events be output to Job Management Partner/Integrated Manager, specify N in the pd_jp1_use operand and restart HiRDB.

KFPS04607-I L

Data replication restart, server ID=aa....aa, reason code=bb....bb

Linkage with the HiRDB Datareplicator was restarted.

aa....aa: Server name

bb....bb: Reason that linkage with the HiRDB Datareplicator was restarted

FORCE: During the previous session, linkage was established with the HiRDB Datareplicator, but HiRDB was started with the pdstart -i command

STATUS: One of the following reasons:

An error occurred in the HiRDB Datareplicator data linkage file, or it was initialized.

An error occurred in the status file used by the server, or it was initialized.

S: Stops and then restarts linkage with the HiRDB Datareplicator.

Action

If necessary, initialize the HiRDB Datareplicator data linkage file or re-create the target database.

KFPS04608-W L

Unable to continue data replication, server ID=aa....aa, reason code=bb....bb

Linkage with the HiRDB Datareplicator could not be maintained.

aa....aa: Server name

bb....bb: Reason that linkage with the HiRDB Datareplicator could not be maintained

DEFINITION: During the previous session, linkage was established with the HiRDB Datareplicator, but N was specified in the pd_rpl_init_start operand

RPL_FILE: An error occurred in the HiRDB Datareplicator data linkage file

RPL_STATUS: The HiRDB Datareplicator data linkage file was initialized

S: Stops the linkage with the HiRDB Datareplicator, and continues server activation processing.

Action

To re-execute linkage with the HiRDB Datareplicator, eliminate the cause of the error, synchronize with the target HiRDB, and use the pdrplstart command to restart linkage with the HiRDB Datareplicator. Also, if HiRDB is stopped and linkage with the HiRDB Datareplicator is already established, specify Y in the pd_rpl_init_start operand.

KFPS04609-E L

Error occurred in status file while data replication, server ID=aa....aa, reason code=bb....bb

An error was detected in the status file during linkage with the HiRDB Datareplicator.

aa....aa: Server name

bb....bb: Reason code

COMMUNICATION: Inter-process communication error

SERVER NOT UP: Status server process has not started

I/O ERROR: I/O error

OTHER: Other error

S: Abnormally terminates.

Action

Eliminate the cause of the error on the basis of the message output before this message.

KFPS04611-I E+S

Usage: pdmemsv [{-d | -s}]

The specification format of the pdmemsv command option is invalid.

S: Terminates processing.

O: Reenter correctly the specified command.

KFPS04612-E E

Error occured in execution, reason code=aa....aa

The pdmemsv command cannot be executed because of error code aa....aa.

aa....aa:

ALREADY:

The attempted operation has already been executed.

INSTALL_DIR:

This command cannot be executed in the environment under the installation directory.

NO_DIR:

A required directory cannot be found.

NO_LIBS:

The environment has been damaged.

NOT_SINGLE:

The server is not a HiRDB/Single Server.

NOT_PARALLEL

The server is not a HiRDB/Parallel Server.

PDDIR:

The PDDIR environment variable cannot be found.

PERMISSION:

The person who executed the command is not a superuser.

SETUP:

HiRDB is running.

VERSION:

The installed HiRDB and the HiRDB in $PDDIR are different versions. Or, the necessary load module was deleted by the pdlodsv command.

S: Terminates processing.

O: Take action appropriate to the cause, as described below:

PDDIR:

Change the PDDIR environment variable setting to the HiRDB environment to be operated with this command.

PERMISSION:

Execute the command as a superuser.

SETUP:

Keep the files needed for execution and execute pdsetup -d.

VERSION:

Check if the versions of the installed HiRDB and the HiRDB in $PDDIR are the same. When a load module required by the pdlodsv command was deleted, reinstall HiRDB with the same version as the HiRDB in the HiRDB directory.

Other:

Check whether the setting for the PDDIR environment variable is correct. If it is correct, contact the HiRDB administrator.

Action

Check whether the installed HiRDB and the HiRDB in $PDDIR have the same version. The HiRDB in $PDDIR requires system files; check that the necessary files have not been deleted during pdsetup -d execution.

KFPS04614-I L+S

Usage:aa....aa

The command option specification format is invalid.

aa....aa: Command in which option specification is invalid:

pdopsetup command:

pdopsetup [-d] -k option HiRDB_home_directory

pdadmvr command:

pdadmvr [-s| -c]

pdlodsv command:

pdlodsv [-r kind]

S: Terminates processing.

Action

Re-execute the command according to the command usage method.

KFPS04615-E E

Specified HiRDB option already setup, option=aaa, version=bb....bb

Version bb....bb option program product was already embedded into the HiRDB directory specified by the pdopsetup command.

aaa: Option program product

sti: HiRDB Staticizer Option

aha: HiRDB Advanced High Availability

nrf: HiRDB Non Recover FES

drl: HiRDB Disaster Recovery Light Edition

acl: HiRDB Accelerator

bb....bb: Version of option program product

S: Terminates processing.

Action

Check the version of the option program product embedded in the specified HiRDB directory and the version of the installed option program product. To embed the version of the installed option program product, execute the pdopsetup -d command, and then execute the pdopsetup command.

KFPS04616-E E

Specified HiRDB option not setup, option=aaa

An attempt to delete failed because the option program product is not embedded in the HiRDB directory specified by the pdopsetup -d command.

aaa: Option program product

sti: HiRDB Staticizer Option

aha: HiRDB Advanced High Availability

nrf: HiRDB Non Recover FES

drl: HiRDB Disaster Recovery Light Edition

acl: HiRDB Accelerator

S: Terminates processing.

Action

Check if the HiRDB directory specified by the pdopsetup command is correct.

KFPS04617-E E

HiRDB option not installed, PP=aa....aa

A HiRDB option program product is not yet installed.

aa....aa: Name of option program product:

HiRDB Staticizer Option

HiRDB Advanced High Availability

HiRDB Non Recover FES

HiRDB Disaster Recovery Light Edition

HiRDB Accelerator

S: Terminates processing.

Action

Install the HiRDB option program product and re-execute the command.

KFPS04618-I S

HiRDB option setup complete, func=aa....aa, option=bbb, version=cc....cc

A HiRDB option program product was either installed or removed.

aa....aa: Function type:

add: Install

delete: Remove

bbb: Option program product:

sti: HiRDB Staticizer Option

aha: HiRDB Advanced High Availability

nrf: HiRDB Non Recover FES

drl: HiRDB Disaster Recovery Light Edition

acl: HiRDB Accelerator

cc....cc: Version of option program product

S: Terminates processing.

KFPS04619-E S+R

Unable to execute aa....aa command due to HiRDB unit not offline or not terminate normally

The HiRDB unit is not stopped; command aa....aa cannot be executed.
aa....aa: Name of the command
S: Terminates processing.

Action

It is possible that HiRDB was still running (including startup or termination processing) when the command was executed. The command cannot be executed under those conditions.

If HiRDB is running, use the pdstop command to stop HiRDB and then re-execute the command. Otherwise, activate HiRDB, use the pdstop command to stop HiRDB, and then re-execute the command.

UNIX edition only
Even if HiRDB is stopped, the pdplgset and pdopsetup commands cannot be entered if HiRDB terminated abnormally or was forcibly terminated by the pdstop -f command.

KFPS04620-I L

Server aa....aa information. Process ID=bb....bb. System event=0xcccccccc dddddddd eeeeeeee. User event=0xffffffff. SYS_CALL=0xgggggggg.

This is server information.

aa....aa: Server name

bb....bb: Process ID

cccccccc: System event information 1 (internal code)

dddddddd: System event information 2 (internal code)

eeeeeeee: System event information 3 (internal code)

ffffffff: User event information (internal code)

gggggggg: System call code information (internal code)

S: Resumes processing.

Action

This information is in addition to a KFPS01820-E message that was output before this message. Take a corrective action based on the server name and the KFPS01820-E message that is associated with the process ID.

KFPS04621-E L

Caution: Server aa....aa (process ID=bb....bb) killed by user request

A HiRDB server process was stopped because of a user request issued from outside HiRDB. User requests issued from outside HiRDB include the following:

In UNIX:

OS's kill command was executed. This message is applicable to SIGTERM, SIGKILL, SIGQUIT, and SIGABRT signals only.

Java Virtual Machine sent a signal when a Java stored procedure or Java stored function was being used. This message is applicable to SIGTERM, SIGKILL, and SIGABRT signals only.

The facility for parallel output of system logs was applied, even though the aio library was not installed or was not configured correctly.

In Windows:

The pdkill command was executed.

aa....aa: Server name of the stopped process

bb....bb: Process ID at the server

S: Continues processing.

O: If the core file was output in a UNIX edition of HiRDB, contact the HiRDB administrator.

Action

In UNIX:

Take one of the following actions:

Determine whether the OS's kill command was executed.

Check if the facility for parallel output of system logs was in use (parallel was specified in the pd_log_dual_write_method operand) while the aio library was not installed or was not enabled. For details about the facility for parallel output of system logs, see the HiRDB Version 9 Installation and Design Guide.

In Windows:

Determine whether the pdkill command was executed.

KFPS04622-E E+L

Invalid user name, user=aa....aa; bb....bb processing

aa....aa is an invalid authorization identifier.

aa....aa: Authorization identifier

bb....bb: System action:

stops: Stops processing.

continues: Continues processing using the executing user's log-in account (during pdinit execution only).

S: Performs the bb....bb processing.

O: Re-execute the utility, as appropriate.

Action

If this message was output when pdinit was executing, revise the authorization identifier and then re-execute. The following names cannot be used for the authorization identifier:

Name more that 8 bytes long

Name that does not begin with a single-byte character (upper- or lower-case letter)

Name containing a character string other than single-byte characters (upper- or lower-case letters) and single-byte numbers

HiRDB, MASTER, ALL, and PUBLIC (reserved words that cannot be used as authorization identifiers)

KFPS04623-E E+L

Invalid password, user=aa....aa; bb....bb processing

The password for authorization identifier aa....aa is invalid.

aa....aa: Authorization identifier

bb....bb: System action:

stops: Stops processing.

S: Performs the bb....bb processing.

O: Re-execute the utility, as appropriate.

Action

If this message is output during pdinit execution, check and correct the password if necessary and re-execute. The following names cannot be used as passwords and must be changed:

Name more that 30 bytes long

Name that does not begin with a single-byte character (upper- or lower-case letter)

Name containing a character string other than single-byte characters (upper- or lower-case letters) and single-byte numbers

KFPS04624-I E+L

Data replication already stopped, unit ID=aaaa, server ID=bb....bb

An error was detected in the data linkage file of the HiRDB Datareplicator or in the server in which a data linkage stoppage occurred. This message is displayed for each server in which an error occurred.

aaaa: Unit identifier

bb....bb: Server name

S: Stops data linkage and continues with HiRDB startup.

Action

Take the actions indicated by the KFPS01833-I and KFPS01801-E messages, which follow this message.

KFPS04625-E L

Error found in system configuration, reason code=aa....aa

An operand specified in the system common definition or unit control information definition is invalid.

aa....aa: Reason code:

SPECIFIED pd_spool_cleanup_level:

An error was found in the specification of the pd_spool_cleanup_level operand.

SPECIFIED pd_spool_cleanup_interval_level:

An error was found in the specification of the pd_spool_cleanup_interval_level operand.

S: Terminates processing.

Action

Correct the operand and restart HiRDB.

KFPS04626-E S

Unable to remove aa....aa, reason code=bb....bb

Load module aa....aa cannot be deleted.

aa....aa: Load type:

POSIX: POSIX library version of HiRDB

bb....bb: Reason code:

USING: This load module cannot be deleted because it is being used.

REMOVED: This load module has already been deleted.

RUNNING: pdsetup command is executing.

S: Terminates processing.

Action

If the reason code is RUNNING, wait for the pdsetup command to terminate and then re-execute.

KFPS04627-E L

HiRDB Datareplicator extraction process not in progress, because error occurred in HiRDB Datareplicator access communication file. unit ID=aaaa, server ID=bb....bb.

The HiRDB Datareplicator data linkage extraction process did not run because access to the data linkage file failed.

aaaa: Unit identifier

bb....bb: Server name

S: Continues processing.

Action

Check the reason why access to the data linkage file failed, and then take appropriate action. You can check the KFPS01889-E message output immediately before this message for the reason access failed.

When function value of the KFPS01889-E message is SYSTEM CALL(stat) ERROR and errno is 2:

The data linkage file could not be found. To re-create a data linkage file, you must use HiRDB Datareplicator to initialize the data linkage file.

To re-create a data linkage file:

Use the pdrplstop command to terminate data linkage processing.

For nontarget system logs, use HiRDB Dataextractor or HiRDB Datareplicator data linkage facility to restore consistency between data linkage extraction and target databases.

Execute the hdestart -i command that HiRDB Datareplicator provides, re-create the data linkage file, and then initialize.

Use the pdrplstart command to start the data linkage process.

When errno of the KFPS01889-E message is 13:

The user has no access privileges to the data linkage file. Request that the HiRDB administrator change access privileges so you can access the data linkage file.

When function value of the KFPS01889-E message is FILE LOCK ERROR:

HiRDB Datareplicator may have exclusive ownership of the data linkage file. Check the execution status of HiRDB Datareplicator.

KFPS04628-W E+L

Data replication stopped, please check.

Data linkage to HiRDB Datareplicator stopped. Check the reason why data linkage stopped.

S: Continues processing.

Action

Check the reason why data linkage to HiRDB Datareplicator stopped. If there is a problem, use the data linkage recovery facility of HiRDB Dataextractor or HiRDB Datareplicator to restore consistency between the data linkage extraction database and the target database.

KFPS04629-I E+L

Command failed on online unit, command=aa....aa, hostname=bb....bb; Retrying on standby unit

Because execution of command aa....aa on running system unit host bb....bb failed, the command was executed on a standby unit.

aa....aa: Command name

bb....bb: Host name

S: Continues processing.

Action

If the command that was re-executed by the standby system unit terminates normally, ignore the error issued by the running system unit. Note that the running system and standby system referred to here are statuses that are determined by the HiRDB system, and may differ from the actual systems. If an error occurs on both the running system and the standby system, check the actual system status, and then take action according to the error message output by the running system unit.

KFPS04643-I L

Assumed aa....aa default value=bb....bb on unit cccc

Assumed default value bb....bb of definition operand aa....aa in unit cccc.

aa....aa: Definition operand name

pd_max_server_process (maximum number of concurrently active server processes)

pd_tmp_directory (name of work file output directory)

bb....bb: Default value of the definition operand

cccc: Unit identifier

S: Continues processing.

Action

When an insufficient maximum number of concurrently active server processes is detected during operation, re-estimate the specified operand value, specify a value greater than the default value, and then restart HiRDB.

If using the default value of the pd_tmp_directory operand causes problems, change the value specified in the pd_tmp_directory operand.

KFPS04644-I L

Assumed aa....aa default value=bb....bb on server cc....cc

The default value bb....bb is assumed for operand aa....aa on server cc....cc.

aa....aa: Operand name

pd_bes_shmpool_size (shared memory size for back-end server)

pd_dic_shmpool_size (shared memory size for dictionary server)

pd_sds_shmpool_size (shared memory size for a single server)

bb....bb: Default value of the operand (bytes)

cc....cc: Server name

S: Continues processing.

Action

If a shared memory shortage was detected during operation, re-estimate the value of the specification. Specify a value larger than the default (value of bb....bb) and restart HiRDB.

KFPS04645-I L+S

pdprgcopy ended, return code=aa

The pdprgcopy command terminated.

aa: Return code

0: The pdprgcopy command terminated normally.

8: The pdprgcopy command terminated with an error.

S: Terminates processing.

Action

If the return code is 8, refer to the error message that is output to standard error or to the event log (in UNIX, syslogfile), and eliminate the cause of the error. Then, re-execute the command.

KFPS04646-I L+S

pdprgrenew ended, return code=aa

The pdprgrenew command terminated.

aa: Return code

0: The pdprgrenew command terminated normally.

8: The pdprgrenew command terminated with an error. HiRDB is returned to its pre-update version.

12: The pdprgrenew command terminated with an error. An error occurred during processing to return HiRDB to its pre-update version. HiRDB stopped.

S: Terminates processing.

Action

Based on the return code, take the following action:

If the return code is 8:

Refer to the error message that is output to standard error or to the event log (in UNIX, syslogfile), and eliminate the cause of the error. Then, re-execute the command.

HiRDB operates even after the command termination if HiRDB was running when the command was executed. If HiRDB was inactive when the command was executed, HiRDB remains inactive even after command termination.

If the return code is 12:

See the KFPS04647-I message output immediately before this message, check which processing the error occurred, take appropriate action, and then re-execute the pdprgrenew command. Take one of the following actions:

If SYS_SUSPEND or SYS_RESUME is displayed in the KFPS04647-I message:
If there is a HiRDB process, use the pdstop -f command to forcibly terminate HiRDB, and then execute the pdprgrenew -b command. If there is no HiRDB process, execute the pdprgrenew -b command.

If RECOVER_REPLACE, RECOVER_BACKUP, or RECOVER_SYS_SUSPEND is displayed in the KFPS04647-I message:
Refer to the error message that is output to standard error or to the event log (in UNIX, syslogfile), eliminate the cause of the error, and then execute the pdprgrenew -b command.

KFPS04647-I L+S

pdprgrenew aa....aa started

The pdprgrenew command started aa....aa processing.

aa....aa: Processing contents

Processing contents (aa....aa) | Explanation
SYS_SUSPEND | HiRDB processing is suspended internally.
BACKUP | A backup of the active HiRDB is being acquired.
REPLACE | HiRDB is being replaced with an updated version.
SYS_RESUME | HiRDB has been restarted with an updated version.
RECOVER_REPLACE | This recovery process is performed when an error occurs. The updated version of HiRDB is returned to the update directory.
RECOVER_BACKUP | This recovery process is performed when an error occurs. HiRDB is returned to its pre-update version.
RECOVER_SYS_SUSPEND | This recovery process is performed when an error occurs. The pre-update version of HiRDB is restarted.

S: Continues processing.

KFPS04648-E E+L

Error occurred in pdprgrenew command, unit ID=aaaa, reason code=bb....bb

An error occurred during execution of the pdprgrenew command.

aaaa: Unit identifier

If an error occurred before the unit identifier was obtained, **** is displayed.

bb....bb: Reason code

Reason code (bb....bb) | Explanation
permission error | The user executing the command is not a HiRDB administrator.
renew directory not exist | The renew directory was not found in the HiRDB directory.
renew_bak directory exist | The renew_bak directory was found in the HiRDB directory.
rename error | An error occurred in the program update process rename() system call.
transactions exist | The pdprgrenew command waited for transactions to terminate, but execution of the command was suspended because some transactions were still active even 15 minutes later.
offline units exist | Some inactive units remain in the system.
offline servers exist | Some inactive servers remain.
utility be executing | A HiRDB utility is currently running. The pdprgrenew command cannot be executed while a utility is running.
replication mode unmatch | When using the HiRDB Datareplicator linkage facility, the specification of the pd_rpl_init_start operand and the run status do not match.
pdprgrenew -b be unnecessary | The pdprgrenew -b command was executed, but no operation was performed because executing the pdprgrenew -b command is not necessary.
sys_info error | An error occurred during system information (registry, setup information) operations.
service start error | An error occurred during HiRDB service start processing.
service stop error | An error occurred during HiRDB service stop processing.
MSCS-info error | An error occurred during MSCS or MSFC information collection.
MSCS online error | An error occurred while an MSCS or MSFC resource was online.
MSCS offline error | An error occurred while an MSCS or MSFC resource was offline.
resident RDAREA exists | There is an in-memory RDAREA.
expand unit exists | An expansion unit is specified in the pd_system_expand_unit operand in the system common definition.

S: Continues processing.

Action

Take action according to the reason code.

permission error:

Request that the HiRDB administrator execute the pdprgrenew command.

renew directory not exist:

Execute the pdprgcopy command, and then re-execute the pdprgrenew command.

renew_bak directory exist:

Either delete the renew_bak directory in the HiRDB directory or change the name of the directory, and then re-execute the pdprgrenew command.

rename error:

This error occurs if the renew directory under the HiRDB directory containing the updated HiRDB that was copied with the pdprgcopy command is not in the same file system as the HiRDB directory (bin, lib, etc.) that is currently running under the HiRDB directory. Update so that the required directories exist in the same file system, and then re-execute the pdprgrenew command.

If the directory is on the same file system, the OS's rename() system call failed. OS messages might be output to the event log (in UNIX, syslogfile). Eliminate the cause of the error, use the pdprgrenew -b command to return HiRDB to its previous state before being updated, and then re-execute the pdprgrenew command.

transactions exist:

Check that there are no long-term transactions running, wait for the currently running transactions to terminate, and then re-execute the pdprgrenew command.

offline units exist or offline servers exist:

Activate all HiRDB units and servers, and then re-execute the pdprgrenew command.

utility be executing:

After the HiRDB utility terminates, re-execute the pdprgrenew command.

replicator mode unmatch:

Reconcile the specification of the pd_rpl_init_start operand with that of the operating status, then re-execute the pdprgrenew command.

pdprgrenew -b be unnecessary:

Execute the pdprgrenew -b command only after the KFPS04646-I message outputs a return code of 12 and the pdprgrenew command has terminated.

sys_info error:

Determine whether regedit.exe or another program is accessing the registry, or whether the HiRDB installation environment file (Setup.ini) is open, and then handle the error as described in Operation when an error occurs during installation under Updating to HiRDB update version in the HiRDB Version 9 Installation and Design Guide.

service start error:

Check the event log (in UNIX, syslogfile) to determine the reason that the service did not start, and eliminate the cause of the error. If the service is still starting, wait for the service to start or stop, and then handle the error as described in Operation when an error occurs during installation under Updating to HiRDB update version in the HiRDB Version 9 Installation and Design Guide.

service stop error:

Check the event log (in UNIX, syslogfile) to determine the reason that the service did not stop, and eliminate the cause of the error. If the service is still stopping, wait for the service to start or stop, and then handle the error as described in Operation when an error occurs during installation under Updating to HiRDB update version in the HiRDB Version 9 Installation and Design Guide.

MSCS-info error:

Check the event log (in UNIX, syslogfile), eliminate the cause of the error, and then handle the error as described in Operation when an error occurs during installation under Updating to HiRDB update version in the HiRDB Version 9 Installation and Design Guide.

MSCS online error:

Check the event log (in UNIX, syslogfile) to determine the reason that the MSCS or MSFC resource did not go online, eliminate the cause of the error, and then handle the error as described in Operation when an error occurs during installation under Updating to HiRDB update version in the HiRDB Version 9 Installation and Design Guide.

MSCS offline error:

Check the event log (in UNIX, syslogfile) to determine the reason that the MSCS or MSFC resource did not go offline, eliminate the cause of the error, and then handle the error as described in Operation when an error occurs during installation under Updating to HiRDB update version in the HiRDB Version 9 Installation and Design Guide.

resident RDAREA exists:

Release the RDAREA from in-memory allocation, and then re-execute the pdprgrenew command.

expand unit exists:

The pdprgrenew command cannot be executed. Terminate HiRDB normally, and then update to HiRDB update version.

KFPS04649-E E+L

Error occurred in pdprgcopy command, unit ID=aaaa, reason code=bb....bb

An error occurred during execution of the pdprgcopy command.

aaaa: Unit identifier

If an error occurred before the unit identifier was obtained, **** is displayed.

bb....bb: Reason code

permission error:

The user executing the command is not the HiRDB administrator.

invalid version:

HiRDB could not be updated because the version number and the revision number do not match.

invalid addressing mode:

The addressing modes between the running HiRDB and the update replacement version HiRDB do not match.

invalid version different between units:

The HiRDB version differs between units.

no space disk:

The required disk space is not available.

renew directory exist:

The renew directory already exists under the HiRDB directory.

invalid HiRDB server type:

The HiRDB server type (HiRDB/Single Server or HiRDB/Parallel Server) of the HiRDB currently running and the update replacement version HiRDB do not match.

install directory:

For UNIX, the directory specified as the argument of the pdprgcopy command is the HiRDB installation directory.

For Windows, the directory specified as an argument of the pdprgcopy command is the directory installed by Program Maintenance Setup.

copy error:

An error occurred while copying a file.

delete error:

An attempt to delete the renew directory under the HiRDB directory failed because an error occurred during execution of the pdprgcopy command.

sys_info error:

An error occurred during system information (registry, setup information) operations.

S: Terminates processing.

Action

Take action according to the reason code.

permission error:

Request that the HiRDB administrator execute the pdprgcopy command.

invalid version:

The HiRDB system currently running cannot be replaced by the replacement update version HiRDB if the version numbers and revision numbers do not match. Install an update version HiRDB with the same version number and revision number, and then re-execute the pdprgcopy command.

invalid addressing mode:

The HiRDB system currently running can only be replaced by the replacement update version if both are in the same addressing mode. Install the update version HiRDB in the same addressing mode as the HiRDB system currently running, and then re-execute the pdprgcopy command.

invalid version different between units:

Install the same version of the replacement update HiRDB system for all units.

no space disk:

In the HiRDB directory, secure the free disk space that is required for the update version HiRDB, and then re-execute the pdprgcopy command.

install directory:

For UNIX, if the HiRDB directory and the installation directory are the same directory, the current version of the HiRDB system cannot be replaced by the update version. If the HiRDB directory and the installation directory are different directories, specify the HiRDB directory in an argument of the pdprgcopy command, and then re-execute.

For Windows, specify the installation directory of the update version HiRDB, then re-execute the command.

renew directory exist:

Either change the name of the renew directory under the HiRDB directory or delete the renew directory, and then re-execute the pdprgcopy command.

invalid HiRDB server type:

The HiRDB system currently running can only be replaced by the replacement update version if both have the same HiRDB server type (HiRDB/Single Server or HiRDB/Parallel Server). Install the update version HiRDB system with the same server type as the HiRDB system currently running, and then re-execute the pdprgcopy command.

communication error occurred:

Check for the cause of the communication error, take appropriate action, and then re-execute the command.

copy error:

OS messages might be output to the event log (in UNIX, syslogfile). Check for the cause of the copy process failure, eliminate the cause, and then re-execute the pdprgcopy command.

delete error:

Refer to the error message output before this message, and eliminate the cause of the error. Then, delete the renew directory under the HiRDB directory and re-execute the pdprgcopy command.

sys_info error:

Determine whether regedit.exe or another program is accessing the registry, or whether the HiRDB installation environment file (Setup.ini) is open, and then handle the error as described in Operation when an error occurs during installation under Updating to HiRDB update version in the HiRDB Version 9 Installation and Design Guide.

KFPS04650-I L

Trouble shoot file and temporally file delete aa....aa. system ID=bbbb, unit ID=cccc

Deletion of the troubleshooting information file under %PDDIR%\spool and the temporary file under %PDDIR%\tmp has started or finished.

aa....aa: Processing content

started: Deletion processing has started

completed: Deletion processing has finished

bbbb: HiRDB identifier

cccc: Unit identifier

S: Continues processing.

KFPS04651-W E+L

Message log server restarted

This message indicates that the message log server was restarted. From the time the message log server terminates abnormally to the time its restart is complete, HiRDB messages are not output to the message log file (%PDDIR%\spool\pdlog1 or pdlog2). Messages are output to the event log (in UNIX, syslogfile) of the server unit that is the source of the messages. However, in some cases messages might not be output to the event log (in UNIX, syslogfile). For currently active UAPs, commands, and utilities, this does not present a problem.

S: Continues processing.

KFPS04652-E E+L

Pdstop command failed,reason=aa....aa

The pdstop command could not be executed because another operation command was currently running.

aa....aa: Reasons for the command not executing:

RPL_STARTING: Linkage with HiRDB Datareplicator is currently starting up.

RPL_STOPPING: Linkage with HiRDB Datareplicator is currently terminating.

S: Terminates processing.

Action

Wait for other operation commands to terminate, and then re-execute the pdstop command.

KFPS04653-E L+S

Unable to stop unit aaaa with alternate servers, reason=bb....bb

The alternate BES unit or an alternate facility could not be stopped because of the status of the alternate facility in the standby less system switchover facility.

aaaa: Unit identifier of the unit that could not be stopped.

If the pdstop -z -c command was executed, **** might be displayed.

bb....bb: Reason code

S: Terminates processing.

Action

Take action according to the reason code listed in the following table.

Reason code | Description | Action
STARTING | An alternate facility is currently being prepared. | Re-execute the stop command.
SBY_STARTING | An alternate facility is currently being prepared as a standby server. | Re-execute the stop command after the KFPS01872-I message is output.
SBY_TERM | An alternate standby system is currently being stopped. | Re-execute the stop command.
SBY_RELEASE | Execution of an alternate facility using system switchover is currently being prepared. | Re-execute the stop command after the KFPS05110-I message is output.
ACT_STARTING | An alternate facility is currently being prepared as a running server.
STOPPING | An alternate facility is currently being stopped. | Re-execute the stop command after the KFPS01841-I message is output.
ONLINE | Alternate processing is currently in progress. | Operation cannot be stopped quickly when alternate processing is in progress. When executing the system reconfiguration command or replacing the current HiRDB with an update version, return the system to normal status, and then execute.
OFFLINE | Already corrected. | The alternate BES unit is already stopped.
NONALTSVUNIT | The unit is not an alternate BES unit. | Execute the command using the alternate BES unit.

KFPS04654-W L

Unable to continue alternate service for unit aaaa because of dying alternate server unit bbbb

The currently running alternate facility stopped because the alternate BES unit terminated.

aaaa: Unit identifier of a normal BES unit

bbbb: Unit identifier of an alternate BES unit

S: Terminates processing.

Action

When the alternate BES unit has taken over the server functioning of the normal BES unit, system switchover occurs once the normal BES unit completes standby. If system switchover does not occur, execute the pdstart -q command on the normal BES unit.

KFPS04655-E L

Unable to continue HiRDB server aa....aa processing because serious error occurred

Processing cannot continue in server aa....aa due to an error.

aa....aa: Server name

S: Terminates processing.

Action

Check the error message output before this message, and eliminate the cause of the error. If necessary, restart the server.

KFPS04660-I L

Pdchgconf started

The system reconfiguration command (pdchgconf) has started.

S: Continues processing.

KFPS04661-I L

Pdchgconf terminated. return code=aa

The system reconfiguration command (pdchgconf) has terminated.

aa: Return code

0: System reconfiguration processing terminated normally.

8: System reconfiguration processing terminated in an error.

S: Terminates processing.

Action

If the return code is 8, see the error message output to standard error or the message log to eliminate the cause of the error. Then, re-execute the command.

KFPS04662-E L

Unable to execute pdchgconf, because aa....aa

The system reconfiguration command (pdchgconf) could not be executed.

aa....aa: Reason code

S: Terminates processing.

Action

Take action according to the reason code listed in the following table.

Reason code
Action

transactions exist
A transaction or utility has been running for 15 minutes. Check if any transactions or utilities require long operation time, and then re-execute the command.

offline units exist
Some inactive units were found. Start all units, and then re-execute the command.

offline servers exist
Some inactive servers were found. Start all servers, and then re-execute the command.

change of configuration invalid (pd_system_id)
The pd_system_id operand could not be changed. Return the specified value of this operand to the original value, and then re-execute the command.

change of configuration invalid (pd_master_file_name)
The pd_master_file_name operand could not be changed. Return the specified value of this operand to the original value, and then re-execute the command.

communication error occurred
A communication error occurred. Check for the cause of the communication error, take appropriate action, and then re-execute the command.

pdrplstop executing
The pdrplstop command is currently running. After the pdrplstop command terminates, re-execute the command.

only for pdrstr and pdcopy mode
Use the pdstart -r command to start the HiRDB system. Re-execute the command after normal starting or resuming.

Online DB Reorganization executing
Updatable online reorganization is running. Terminate updatable online reorganization, and then re-execute the command.

replication mode unmatch
The operating status of linkage with HiRDB Datareplicator does not match the definition. Make the operating status linkage with HiRDB Datareplicator match the definition, and then re-execute the command.

change of configuration invalid (unit status file:bbbb,cc....cc)
The definition of a status file for a unit that cannot be changed was changed. bbbb is the unit identifier and cc....cc is the name of the status file where the error occurred. Return the specified value for this operand to its original value, and then re-execute the command.

change of configuration invalid (server status file:dd....dd,ee....ee)
The definition of a status file for a server that cannot be changed was changed. dd....dd is the server name and ee....ee is the name of the status file where the error occurred. Return the specified value for this operand to its original value, and then re-execute the command.

change of configuration invalid (log file:ff....ff,gg....gg)
The definition of a system log file that cannot be changed was changed. ff....ff is the server name and gg....gg is the file group name of the system log file where the error occurred. Return the specified value for this operand to its original value, and then re-execute the command.

change of configuration invalid (sync point dump file:hh....hh,ii....ii)
The definition of a synchronization point dump file that cannot be changed was changed. hh....hh is the server name and ii....ii is the file group name of the synchronization point dump file where the error occurred. Return the specified value for this operand to its original value, and then re-execute the command.

configuration change failed
An attempt to change the HiRDB system definition failed.
Action:

Fix the cause of the error. If the disk space under the HiRDB directory is full, secure disk space. If you do not have write privileges to a system shared definition file, request that the HiRDB administrator grant write privilege to this file. If a communication error occurred, eliminate the cause.

Check the status of the HiRDB system definition for all units. If the status is not the pre-modification status, recover the HiRDB system definition from %PDDIR%\conf\backconf.

Because HiRDB is inactive, start HiRDB, and then re-execute the command.

disk change failed
The disk was disconnected or connection failed.
Action:

Disconnect the disk and check the content of the connection shell. If you do not have shell execution privileges, request execution privileges from the HiRDB administrator.

Check the status of the HiRDB system definition for all units. If the status is not the pre-modification status, recover the HiRDB system definition from %PDDIR%\conf\backconf.

Check the disk connection status.

If the HiRDB system is inactive, start HiRDB, and then re-execute the command.

change of configuration directory invalid
The directory is invalid. Check the %PDDIR%\conf\chgconf directory for each unit of the HiRDB system, and then re-execute the command.

change of configuration directory not exist
The directory does not exist. Check the %PDDIR%\conf\chgconf directory for each unit of the HiRDB system, and then re-execute the command.

HiRDB Advanced High Availability not setup
HiRDB Advanced High Availability is not set up. When using the system reconfiguration command, set up HiRDB Advanced High Availability.

unable to skip offline unit
Because the value of the pd_mode_conf operand is AUTO, recovery-unnecessary FES units that have stopped are ignored, and the command cannot be executed. Start the stopped units, and then re-execute the command.

change of configuration invalid (pdstart -k stls)
For recovery-unnecessary FES units that have stopped, specification of the pdstart operand with the -k stls option cannot be changed. Start the stopped units, and then re-execute the command.

resident RDAREA exists
Release the RDAREA from in-memory allocation, and then re-execute the command.

XDS exists
There is a running XDS. Stop all running XDS units, and then re-execute the command.

expand unit exists
Because an expansion unit is specified in the pd_system_expand_unit operand in the system common definition, the system configuration cannot be changed by the pdchgconf command while HiRDB is running. Terminate HiRDB normally, and then change the system configuration.

KFPS04663-W L

Now waiting for termination of transaction or utility

The system manager is currently awaiting termination of a transaction or utility.
This message might be output repeatedly when a transaction or utility does not terminate for a long time.

S: Continues processing.

Action

When giving priority to execution of the pdchgconf or pdtrnqing commands, check currently running transactions and utilities using the pdls -d trn or pdls -d prc command, and then cancel them using the pdcancel command. When giving priority to executing transactions and utilities, no action is required.

KFPS04664-I L

Configuration change processing aa....aa. unit:bbbb

The system reconfiguration command (pdchgconf) was used to change the system definition.

aa....aa: Processing content

start: Changing of the system definition has started.

end: Changing of the system definition has finished.

recover: Undoing of the changes to the system definition has started.

bbbb: Unit identifier

S: Continues processing.

KFPS04665-W E

Changing definition file skipped in pdchgconf, unit ID=aaaa, reason code=bb....bb

The pdchgconf command did not update the system definition file on unit aaaa.

aaaa: Unit identifier of the unit for which the system definition file was not updated

bb....bb: Reason that the system definition file was not updated

communication error occurred: A communication error occurred. An error may have occurred in the network, each machine, unit, or server.

S: Continues processing.

Action

Before restarting unit aaaa, replace the system definition files under %PDDIR%\conf and %PDCONFPATH% with the system definition file after the update.

communication error occurred is displayed in bb....bb: This is the reason for the communication error from the system manager unit to unit aaaa. Check that there was no network failure and that the remote shell execution privilege has been granted, and take action appropriate to the cause of the error.

KFPS04666-I J

System configuration changed

The system definition may have been changed. This message is output when Job Management Partner/Integrated Manager is notified of an event.

S: Continues processing.

KFPS04667-I L

Transaction and connect pause process start.unit=aa....aa

Unit aa....aa transaction queuing started.

aa....aa: Unit identifier

S: Continues processing.

KFPS04668-I L

Transaction and connect pause process ended.unit=aa....aa

Unit aa....aa transaction queuing terminated.

aa....aa: Unit identifier

S: Continues processing.

KFPS04669-I L

Transaction and connect pause process released.unit=aa....aa

Unit aa....aa transaction queuing was released.

aa....aa: Unit identifier

S: Continues processing.

KFPS04670-E E+L

Error occurred while releasing HiRDB standby state

An abnormality was detected during standby release processing; or HiRDB normal startup processing was executed on a HiRDB in standby status. In this case, the standby system HiRDB cannot start normally.

Consider the following causes:

User server hot standby is applied, and Hitachi HA Toolkit Extension is used:

Before the Hitachi HA Toolkit Extension service process was activated (using the hateserve command), HiRDB was started using the pdstart command. If HiRDB is started before the Hitachi HA Toolkit Extension service process is activated, HiRDB will start in standby status, and activation of the Hitachi HA Toolkit Extension service process performs standby release processing.

After starting the standby system HiRDB, start the running system HiRDB normally. At this time, startup of the running system HiRDB will fail, and a system switchover will occur.

An attempt was made to stop the running system HiRDB:

After a normal termination or a planned termination was confirmed, a system switchover occurred due to CPU error or service slowdown.

S: Outputs an abort code (Psadhf0), and terminates the process.

Action

User server hot standby is applied, and Hitachi HA Toolkit Extension is used:

If the pdstart command was executed before activation of the Hitachi HA Toolkit Extension service process, execute pdstart after the Hitachi HA Toolkit Extension service process has been activated; or specify the HiRDB activation command in the Hitachi HA Toolkit Extension server definition statement actcommand operand. If the pdstart command is executed from a shell, make sure that the shell operates in the same way after the Hitachi HA Toolkit Extension service process has activated.

After taking measures to correct the failed startup of the running system HiRDB, restart the running system HiRDB.

An attempt was made to stop the running system HiRDB:

In UNIX
Take measures to correct the failed termination of the running system HiRDB.
When HiRDB is restarted, startup processing might be interrupted in the following circumstance: If the HA monitor is being used as the cluster software, and the HA monitor single system is in shutdown status, the HA monitor might not be able to determine whether a system is the running system or the standby system. In that case, it is necessary to execute the following HA monitor commands to make the system the running system:
Use the monshow command to confirm that the server status is *SBY* (waiting for the running server to start up).
Use the monact command to notify the HA monitor that this is the running server.

In Windows
Take measures to correct the cause of the failed termination of the running system HiRDB.

KFPS04680-E E+L

Error occurred in Real_Time_SAN_Replication, reason code=aa....aa, command=bb....bb, group=cc....cc

An error occurred in a RAID Manager command.

aa....aa: Code

bb....bb: Name of the RAID Manager command that caused the error

cc....cc: Name of the pair logical volume group

S: Continues processing.

Action

Take action based on the following codes:

Code (aa....aa) | Explanation | HiRDB administrator action
SYSTEMCALL | RAID Manager command bb....bb call failed. | See the table SYSTEMCALL actions below, and take the action appropriate to the values of errno and value indicated in the KFPS01815-E message output immediately before this message.
ERRORRETURN[dd....dd] | RAID Manager command bb....bb caused an error. The error code of the RAID Manager command is dd....dd. The pair logical volume group that corresponds to execution of the command is cc....cc. | See the RAID Manager manual, and take the action appropriate to the error code. Use the code displayed in dd....dd, and see the table ERRORRETURN actions below for typical codes.
GETRESULTFAILED | Result acquisition of RAID Manager command bb....bb failed. | There may be a shortage of free disk space in the HiRDB directory, or a memory error. Consider the free disk area and free memory area, and increase the amount of free area.
TIMEOUT | Pair logical volume group update wait processing has exceeded the maximum wait time. | Check the RAID Manager and HORC running status, check the reason that the subvolume reflection of the pair logical volume group displayed in cc....cc was delayed, and take appropriate action. For details on investigating the cause and appropriate actions, see the RAID Manager and HORC manuals.
BROKEN | In pair logical volume group update wait processing, the pair in the volume group was broken. | Check the reason that the pair in the pair volume group was broken, and take appropriate action. For details on investigating the cause and appropriate actions, see the RAID Manager manual.
CHANGED | In pair logical volume group update wait processing, the synchronization status of the volume group was temporarily released and was then resynchronized. | Check the reason that the pair in the pair volume group was broken, and take appropriate action. For details on investigating the cause and appropriate actions, see the RAID Manager manual.

SYSTEMCALL actions

errno
Value
Explanation
Action

Ignored
0
The process was cancelled during command execution.
Determine the reason for the cancellation (excluding intended cancellation), and take appropriate action.

126
There is no command execution privilege.
Request that the HiRDB administrator grant the RAID Manager administrator privilege.

127
The command was not installed in the default path.
If the RAID Manager is not installed, install it. Confirm that the RAID Manager commands are located under /usr/bin, and if not, reinstall the RAID Manager.

11
Any
The total number of processes being executed by a single user exceeds the maximum for the system.
In UNIX:
Increase the value of the following operating system parameters (kernel parameters):

HP-UX: maxuprc or nproc

Solaris: maxuprc or max_nprocs

AIX: maxuproc or the number of fixed licenses

Linux: MAX_TASKS_PER_USER or NR_TASKS

If these measures do not correct the problem, contact the customer support center.
In Windows:
Contact the customer support center.

12
Any
Consider the following causes:

Due to a swap area shortage, new processes cannot be generated

There are too many processes, or some processes are consuming a large amount of memory

If there is a swap area shortage, extend the area. If the area cannot be extended, stop unneeded processes. If some of the processes are consuming a large amount of memory, consider whether the processes can be stopped temporarily.

13
Any
There is an error in the command access privilege.
Check the command access privilege.

ERRORRETURN actions

Value of dd....dd
Explanation
Action

EX_COMERR
Communication with RAID Manager failed.
Check that the RAID Manager instance is running and that the specification of the HORCMINST operand is correct.

EX_ATTHOR
Unable to connect to the RAID Manager instance.
Take the following actions:

Check that the RAID Manager instance is running.

Check that the specification of the HORCMINST operand is correct.

Check that the pair volume configuration definition is correct.

EX_ENOENTEX_ENOGRP
The group specified by cc....cc does not exist.
Take the following actions:

Check that the specification of the HORCMINST operand is correct.

Check that the pair volume configuration definition is correct.

EX_INVVOL
The status of the group specified by cc....cc is invalid.
Check the attributes and status of each pair volume included in cc....cc, and ensure that the attributes and status of all pair volumes match.
Also ensure that the attributes and status of all pair volumes are correct.

KFPS04681-E E

aa....aa invalid; stops unit startup. server ID=bb....bb, old value= cc....cc, new value= dd....dd

The unit cannot be restarted because the value specified in aa....aa operand has been changed. The value of aa....aa operand cannot be changed after an abnormal termination, forced termination, or planned termination.

aa....aa: Operand that does not match the specified value

pd_rise_use

pd_rise_pairvolume_combination

pd_rpl_reflect_mode

pdstart -k

pd_system_expand_unit

bb....bb: Server name

If aa....aa operand is the system common definition or the unit control information definition, "********" is displayed.

cc....cc: Value of aa....aa operand before the change

If an expansion unit was added to the pd_system_expand_unit operand, **** is displayed.

dd....dd: Value of aa....aa operand after the change

If the expansion unit specified in the pd_system_expand_unit operand was deleted, **** is displayed.

S: Terminates processing.

Action

If aa....aa is something other than pd_system_expand_unit:

Return the value of aa....aa operand to its value before the change (cc....cc), and restart the unit.

If aa....aa is pd_system_expand_unit:

Because some units might be in the process of starting, execute the command pdls -d ust on each unit to check the status of the unit. If the status of the unit is STARTING, use the pdstop -z command to terminate the unit. Make sure that all the units have terminated, and then change the value specified in the pd_system_expand_unit operand. After that, restart the units.

Note that the value before the change (the value in cc....cc) and the value after the change (the value in dd....dd) are displayed for each unit.

KFPS04682-E E+L

Unable to specify Real_Time_SAN_Replication, because of using aa....aa

Some facilities cannot be used when Real Time SAN Replication with the log-only synchronous method is used.

aa....aa: Facility name

Staticizer Option: Inner replica facility

S: Terminates processing.

Action

If Real Time SAN Replication with the log-only synchronous method is used, revise the system definition so as not to use the facility indicated in the message.

If the facility indicated in the message is to be used together with Real Time SAN Replication with the log-only synchronous method, set the pd_rise_pairvolume_combination operand to other than syssync. If the facility is to be used without Real Time SAN Replication, set the pd_rise_use operand to N.

After revising the system definition, restart HiRDB.

KFPS04683-I L

HiRDB unit aaaa start on standby site

A log application site unit was started.

aaaa: Unit identifier

S: Continues processing.

KFPS04684-E E

Unable to execute aa....aa, because bb....bb

Due to reason bb....bb, the aa....aa command could not be executed.

aa....aa: Command name (including options)

bb....bb: Reason code

S: Terminates processing.

Action

Refer to the reason code, and determine whether the executed command and its options are appropriate. Also, if necessary, take the following actions. Refer to the section on operations when an error has occurred in the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide.

Reason code (bb....bb)
Explanation
HiRDB administrator action

HiRDB Disaster Recovery Light Edition not set up
HiRDB Disaster Recovery Light Edition is not set up.
If Real Time SAN Replication with the log-only synchronous method is used, also use HiRDB Disaster Recovery Light Edition.

Real_Time_SAN_Replication mode is not system_log synchronized
Some operands required for Real Time SAN Replication with the log-only synchronous method might not have been specified.
If Real Time SAN Replication with the log-only synchronous method is used, specify Y in the system common definition pd_rise_use operand, and specify syssync in the pd_rise_pairvolume_combination operand.

necessary to execute pdriseset
The site was not set up using the pdriseset command.
Execute the pdriseset command, and set up the transaction execution site or the log application site.

this system is Real_Time_SAN_Replication primary site
The command cannot be executed on a transaction execution site.
If it is possible to switch to a log application site, execute the pdriseset -S command.

this system is Real_Time_SAN_Replication standby site
The command cannot be executed on a log application site.
Execute commands that can be executed on a log application site.
To start HiRDB on a log application site, use the pdstart -l command.
To stop HiRDB on a log application site, use the pdstop -l command or the pdstop -f command.
If it is possible to switch to a transaction execution site, execute the pdriseset -P command.

this system is not Real_Time_SAN_Replication standby site
The command can only be executed on a log application site.
Ensure that the commands and options to be executed can be executed on a site other than a log application site.

unit being started
The command cannot be executed because a unit is in startup processing.
The unit that was the cause of the error and its status are displayed in a KFPS05223-I message.
Use pdls -d svr to check the unit's status, and, if necessary, restart the stopped unit.

unit being terminated
The command cannot be executed because a unit is in shutdown processing.

unit terminated abnormally
The command cannot be executed because a unit terminated abnormally or was terminated using the pdstop -f command.

execution in process
The command cannot be executed because the pdrisedbto command is executing.
If multiple pdrisedbto commands were executed, wait for any executing pdrisedbto command to terminate.
The site inheritance status can be checked using the pdls -d ris command.

KFPS04685-E E

Status subfiles only initialized, aa....aa

All status subfiles are in initial status.
Consider the following causes:

In the preparation for log application, the log application site's status subfiles were not created according to the correct procedure.

The log application site's current status subfiles were deleted.

aa....aa:

unit=bbbb

Unit status file for unit bbbb

unit=bbbb, server=cc....cc

Server status file for server cc....cc on unit bbbb

bbbb: Unit identifier

cc....cc: Server name

S: Continues processing.

Action

Ensure that there was no error in the procedure for preparation for log application, and then re-execute preparation for log application.

Execute preparation for log application in order to start the log application site HiRDB.

KFPS04686-I L

HiRDB unit aaaa database take over terminated

Unit aaaa was terminated, and database inheritance from the transaction execution site terminated.

aaaa: Unit identifier

S: Terminates processing.

KFPS04687-I L+S

Real_Time_SAN_Replication information : status=aa....aa

The site status of Real Time SAN Replication with the log-only synchronous method is displayed.

aa....aa: Site status

primary: Execution

standby: Log application

ready: Ready

initial: Initial

If the site status cannot be determined, **** is displayed.

S: Continues processing.

Action

Site status other than ****
There is no problem.

Site status is ****
Take one of the following actions:
If using a system switchover configuration, check the system where the command was executed, and execute the pdriseset command from the primary system.
If this message was output when the pdriseset command was executed on the primary system, review the value of the unit control information definition pd_hostname operand.
If the pd_hostname operand contains a specification other than the standard host name of the primary system, specify the standard host name of the primary system.
If this message was output when using a configuration other than a system switchover configuration, contact the customer support center.

KFPS04688-I L+S

Site status set to aa....aa from bb....bb

The site status was reset.

aa....aa: Site status that was reset

primary: Execution

standby: Log application

initial: Initial

bb....bb: Site status before resetting

ready: Ready

primary: Execution

standby: Log application

initial: Initial

S: Continues processing.

KFPS04689-W E+L

aa....aa ignored, reason=bb....bb

Due to reason code bb....bb, specification of the facility indicated by aa....aa was ignored.

aa....aa: Facility name

Non_Recover_FES: Recovery-unnecessary front-end server

System switchover facility: System switchover facility

Security Audit: Security audit facility

Statistical information: Statistical information

HiRDB Datareplicator: HiRDB Datareplicator linkage facility

bb....bb: Reason code

standby site: Operates as a log application site

S: Continues processing.

Action

If Real Time SAN Replication with the log-only synchronous method is being used on a log application site, the facility indicated in aa....aa becomes invalid. For details, see the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide.

KFPS04690-Q S

The state of site changed to aa....aa. (y/n)

This is a message inquiring whether to change the site status to aa....aa.

aa....aa:

primary: Execution

standby: Log application

initial: Initial

S: Continues processing.

Action

To change the site status, enter y or Y; to leave the site status unchanged, enter n or N. If any other letter is entered, or if only the return key is entered, n is assumed.

KFPS04691-I L+S

Pdrisedbto terminated, return code=a

Database inheritance terminated.

a: Return code

0: Terminated normally.

4: Database inheritance has terminated for some of the servers.

8: Terminated in an error.

S: Terminates processing.

Action

If the return code is 8, refer to the message output before this message, and take action.

If the return code is 4, take one of the following actions:

To perform database inheritance for all servers
Refer to the message output before this message, eliminate the cause of the error from the server for which inheritance failed, use the pdstart -l command to start HiRDB, and then re-execute the pdrisedbto command.

To invalidate database inheritance for some of the servers, and to perform site switchover
Refer to the section on site switchover in the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide, and continue with site switchover.

KFPS04692-W S

pdrisechk command executed with standby system

Because the pdrisechk command was executed on a standby system in a system switchover configuration, the site status could not be determined correctly.

S: Continues processing.

Action

If this message was output when the pdrisechk command was executed on the primary system, revise the value specified for the unit control information definition pd_hostname operand. If other than the standard host name of the primary system is specified in the pd_hostname operand, specify the standard host name of the primary system.

If the pdrisechk command was executed on the standby system, there is no problem. Check the results of the pdrisechk command execution.

KFPS04693-E E+L

Host name specified in pd_security_host_group definition invalid, reason code=aa....aa, hostname=bb....bb

Invalid host name specified in the pd_security_host_group operand of the system common definition:

aa....aa:

INVALID: An invalid host name or a host name that cannot be resolved has been specified.

DUPLICATE: The host name is a duplicate.

LENGTH OVER: Exceeds the limit for the length of the host name (256 characters).

bb....bb: Invalid host name:

The host name, IP address or FQDN is displayed. If the number of characters exceeds the maximum of 100, only the first 100 characters are displayed.

S: Terminates system definition analysis processing, and then terminates HiRDB start processing.

Action

Take corrective action according to the reason code, and then re-start HiRDB.

INVALID:

If the host name is invalid:
Specify the correct host name.

Other servers:
The host name has not been resolved. If you are not using the DNS server, record the host name in the hosts file. If you are using the DNS server, record the host name in the DNS server file.

DUPLICATE:

Specify a unique host name.

LENGTH OVER:

Specify a host name that does not exceed 256 characters.

KFPS04694-E E

Unable to create temporary file, dir=aa....aa, func=bb....bb, errno=cc....cc

Creation of temporary files failed.

aa....aa: Temporary file creation directory

If the directory name length is 141 bytes or longer, an ellipsis (...) is output at the front of the name and then the last 137 bytes are output.

If a directory where temporary files are created cannot be identified, NULL is output.
Directories in which temporary files are created depend on environment variable TMPDIR in UNIX and environment variable TMP or TEMP in Windows. If NULL is output, revise the environment variable.

bb....bb: OS function in which the error occurred

tempnam: tempnam function

open: open function

cc....cc: errno value of the OS function

S: Terminates processing.

Action

Investigate the errno value, refer to error.h or the OS documentation, and eliminate the cause of the error. For representative errnos, see 4.3 System call return codes.

KFPS04695-I L

Now starting HiRDB expand unit aaaa

The expansion unit aaaa is starting up.

aaaa: Unit identifier

S: Continues processing.

KFPS05001-I E+S

Usage: pdls {[-d {act [-s server_name]
aud [-U user_id]
ha [{-u unit_id | -s server_name}] [-a]|
lck {[-a] [-s server_name]|[-p [-e]]|[-T [-R]]}|
mem|
org [-u unit_id] [-s server_name] [-a]|
prc [-a|-s server_name] [-c] [-C [-H]]|
ris [-u unit_id] [-s server_name] [-a]|
rpc [-a]|
rpl [-j] [-u unit_id] [-s server_name]|
scd [-a|-s server_name]|
stj [-s server_name]|
sts [{-x host_name|-u unit_id}]
[{-n logical_file_name|-f physical_file_name|-a|-l|-p}]|
sts -s server_name
[{-n logical_file_name|-f physical_file_name|-a|-l|-p}]|
svr [-a [-b]]|
trn [-t TRNGID][-{a|c}][-s server_name] [-C [-H]]
ust [-a] [-C [-H]]}]|
[-a [-b]]}

The specification format of a pdls command option is invalid.

S: Terminates processing.

O: Re-executer the command correctly for a HiRDB/Single Server.

KFPS05001-I E+S

Usage: pdls {[{-d act [-s server_name] [-x host_name[,host_name]...|-u unit_id[,unit_id]...]
aud [-u unit_id] [-U user_id]|
ha [{-u unit_id | -s server_name}] [-a]|
lck {[-a] [-s server_name]|[-p [-e]]|[-T [-R]]} [-x host_name[,host_name]...|-u unit_id[,unit_id]...]|
mem [-x host_name[,host_name]...|-u unit_id[,unit_id]...]|
org [-s server_name] [-a] [-x host_name[,host_name]...|-u unit_id[,unit_id]...]|
prc [-a|-s server_name] [-c] [-C [-H]] [-x host_name[,host_name]...|-u unit_id[,unit_id]...]|
ris [-u unit_id] [-s server_name] [-a]|
rpc [-a]|
rpl [-j] [-u unit_id] [-s server_name]|
scd [-a|-s server_name] [-x host_name[,host_name]...|-u unit_id[,unit_id]...]|
stj [-s server_name] [-x host_name[,host_name]...|-u unit_id[,unit_id]...]|
sts {-x host_name|-u unit_id}
[{-n logical_file_name|-f physical_file_name|-a|-l|-p}]|
sts -s server_name
[{-n logical_file_name|-f physical_file_name|-a|-l|-p}]|
svr [-a [-b]] [-x host_name[,host_name]...|-u unit_id[,unit_id]...]|
trn [-t TRNGID][-{a|c}][-s server_name] [-C [-H]] [-x host_name[,host_name]...|-u unit_id[,unit_id]...]
ust [-a] [-C [-H]]}]|
[-a [-b]] [-x host_name[,host_name]...|-u unit_id[,unit_id]...]}

The specification format of a pdls option is invalid.

S: Terminates processing.

O: Re-execute the command correctly for a HiRDB/Parallel Server.

KFPS05002-I S

Usage: pdinit -d statement_control_file_name [-u authorization_identifier [-p password]]

The specification format of a pdinit option is invalid.

S: Terminates processing.

Action

Re-execute the utility correctly.

KFPS05003-I S

Usage: pdmod -a statement_control_file_name

The specification format of a pdmod option is invalid.

S: Terminates processing.

Action

Re-execute the utility correctly.

KFPS05005-I L+S

Usage: pdstart [{-i|-r [-t]|-l|dbdestroy}]

The specification format of a pdstart command option is invalid.

S: Terminates processing.

Action

Re-execute the command correctly for a HiRDB/Single Server.

KFPS05005-I L+S

Usage: pdstart [{-i|-r [-t]|-l|dbdestroy}] | [-x host_name|-u unit_id] [-r [-t]|-l|dbdestroy] | [[-x host_name|-u unit_id] -s server_name] | [-a [-s FES_name]] | [-q [-r [-t]|-l]] | [-q -c] | [-R [-t]]

The specification format of a pdstart command option is invalid.

S: Terminates processing.

Action

Re-execute the command correctly for a HiRDB/Parallel Server.

KFPS05006-I S

Usage: pdstop [-P [-d]|-f [-d|-q]|[-d]|-l [-d]]

The specification format of the pdstop command option is invalid.

S: Terminates processing.

Action

Re-execute the command correctly for a HiRDB/Single Server.

KFPS05006-I S

Usage: pdstop [{[-x host_name|-u unit_id][-s server_name][-d]|-P [-d]|-f [-x host_name|-u unit_id][-s server_name][-d]|-z [-d|-q|-c|-s server_name]|-l [-d]}]

The specification format of a pdstop command option is invalid.

S: Terminates processing.

Action

Re-execute the command correctly for a HiRDB/Parallel Server.

KFPS05007-I S

System definition check ended. return code = a

The pdacunlck command terminated with return code a.

a: Return code:

0: Normal termination

8: Error termination (an argument was invalid or an error was output in the execution results of the pdconfchk command)

S: Terminates processing.

Action

If the return code is not 0, check the execution results of the pdconfchk command and correct the error.

KFPS05008-I S

Usage: pdcancel {-U |-u uap_name[-i process_id] |-i process_id -d}

The specification format of a pdcancel command option is invalid.

S: Terminates processing.

Action

Re-execute the command correctly for a HiRDB/Single Server.

KFPS05008-I S

Usage: pdcancel {-x host_name| -X unit_id} {-U| -u uap_name [-i process_id]| -i process_id -d}

The specification format of a pdcancel command option is invalid.

S: Terminates processing.

Action

Re-execute the command correctly for a HiRDB/Parallel Server.

KFPS05009-I S

Usage: pdcat {[-a | -b | -ab] [-c importance_code[,importance_code]....] [-y yyyymmdd] [-t hhmmss] [-T hhmmss] [-n record_number] [file_name] | -d sts {[-x host_name|-u unit_id]|-s server_name} -f full_path_name [-v] [-e] }

The specification format of a pdcat command option is invalid.

S: Terminates processing.

O: Re-execute the command correctly for a HiRDB/Single Server.

KFPS05009-I S

Usage: pdcat {[-x host_name|-u unit_id] [-a | -b | -ab ] [-c importance_code[,importance_code]....] [-y yyyymmdd] [-t hhmmss] [-T hhmmss] [-n record_number] [file_name] | -d sts {-x host_name|-u unit_id|-s server_name} -f full_path_name [-v] [-e] }

The specification format of a pdcat command option is invalid.

S: Terminates processing.

O: Re-execute the command correctly for a HiRDB/Parallel Server.

KFPS05011-I S

Usage: pddump [-f rpc_trace_file_name]

The specification format of a pddump command option is invalid.

S: Terminates processing.

O: Re-execute the command correctly for a HiRDB/Single Server.

KFPS05011-I S

Usage: pddump {-x host_name |-u unit_id} [-f rpc_trace_file_name]

The specification format of a pddump command option is invalid.

S: Terminates processing.

O: Re-execute the command correctly for a HiRDB/Parallel Server.

KFPS05012-I E+L+S

Usage: pdconfchk [-d directory_name] [-n][-l]

The specification format of a pdconfchk command option is invalid.

S: Terminates processing.

Action

Re-execute the command correctly for a HiRDB/Single Server.

KFPS05012-I E+L+S

Usage: pdconfchk [-d directory_name] [-n] [-l] [-u unit_id]

The specification format for the pdconfchk command option is invalid.

S: Terminates processing.

Action

Re-execute the command correctly for a HiRDB/Parallel Server.

KFPS05015-I E

Usage: pdstjswap [-x host_name| -u unit_id]

The specification format of a pdstjswap command option is invalid.

S: Terminates processing.

P: Re-execute the command correctly for a HiRDB/Single Server.

KFPS05015-I E

Usage: pdstjswap {-x host_name| -u unit_id}

The specification format of a pdstjswap command option is invalid.

S: Terminates processing.

P: Re-execute the command correctly for a HiRDB/Parallel Server.

KFPS05016-I S

Usage: pdstbegin [-k statistics_type [, statistics_type]....] [-m time_interval] [-a |-s server_name [, server_name]...][-w]}

The specification format of a pdstbegin command option is invalid.

S: Terminates processing.

Action

Re-execute the command correctly for a HiRDB/Single Server.

KFPS05016-I S

Usage: pdststart [-k statistics_type [,statistics_type]....] [-m time_interval] [-x host_name |-u unit_id] [-a |-s server_name [, server_name]...][-w]}

The specification format of a pdststart command option is invalid.

S: Terminates processing.

Action

Re-execute the command correctly for a HiRDB/Parallel Server.

KFPS05017-I S

Usage: pdstend [-k statistics_type[, statistics_type]....] [-a| -s server_name[, server_name]...][-w]

The specification format of the pdstend command option is invalid.

S: Terminates processing.

Action

Re-execute the command correctly for a HiRDB/Single Server.

KFPS05017-I S

Usage: pdstend [-k statistics_type[, statistics_type]....][-x host_name|-u unit_id][-a|-s server_name[, server_name]...][-w]

The specification format of the pdstend command option is invalid.

S: Terminates processing.

Action

Re-execute the command correctly for a HiRDB/Parallel Server.

KFPS05018-I S

Usage: pdchgconf

The specification format of the pdchgconf command option is invalid.

S: Terminates processing.

Action

Re-execute the command correctly.

KFPS05019-I E+L

Usage: pdopen {-r RDAREA[,RDAREA ...]|-r ALL}[-q generation_number]

The specification format of the pdopen command option is invalid.

S: Terminates processing.

Action

Re-execute the command correctly.

KFPS05020-I E+L

Usage: pdclose {-r RDAREA[,RDAREA ...]|-r ALL}[-q generation_number]

The specification format of a pdclose command option is invalid.

S: Terminates processing.

Action

Re-execute the command correctly.

KFPS05021-I E+L

Usage: pdhold {-r RDAREA[,RDAREA ...]|-r ALL}[-q generation_number] {[-c]|[-i]|[-b[-w][-u]]|[-s]}

The specification format of a pdhold command option is invalid.

S: Terminates processing.

Action

Re-execute the command correctly.

KFPS05022-I E+L

Usage: pdrels {-r RDAREA[,RDAREA ...]|-r ALL}[-q generation_number][-o]

The specification format of the pdrels command option is invalid.

S: Terminates processing.

Action

Re-execute the command correctly.

KFPS05023-I E+L

Usage: pddbls { { { -r RDAREA[,RDAREA...] | -r ALL | -s server_name[,server_name...] } [ -{ l | a } ] [-{ b | o } ] [ -m ] [-x[-y]] [-M] [-D] [-T] } | { { -q generation_number | -C } [ - { l | a } ] [ -m ] [-x[-y]] [-M] [-D]} }

The specification format of a pddbls command option is invalid.

S: Terminates processing.

Action

Re-execute the command correctly.

KFPS05024-I S+L

Usage: pdrplstart

The specification format of the pdrplstart command is invalid.

S: Terminates processing.

Action

Re-execute the command correctly.

KFPS05025-I S+L

Usage: pdrplstop

The specification format of the pdrplstop command is invalid.

S: Terminates processing.

Action

Re-execute the command correctly.

KFPS05026-I E

Usage: pdndls [-w HiRDB_ID] [-x host_name]

The specification format of the pdndls command is invalid.

S: Terminates processing.

O: Re-execute the command correctly.

KFPS05028-I S

Usage: pdchprc [-p resident_process_count[,max_process_count]]

The specification format of the pdchprc command is invalid.

S: Terminates processing.

P: Re-execute the command correctly for a HiRDB/Single Server.

KFPS05028-I S

Usage: pdchprc {-a |-s server_name} [-p resident_process_count[,max_process_count]]

The specification format of the pdchprc command is invalid.

S: Terminates processing.

P: Re-execute the command correctly for a HiRDB/Parallel Server.

KFPS05029-I S

Usage: dcspool [-i] [-d day_count] [-k { all|dump } ]

An option is specified in an invalid format in the pdspool command.

S: Terminates processing.

O: Re-execute the command correctly.

KFPS05030-I S

Remove following files

Deletes the following files.

S: Continues processing. Following this message, HiRDB outputs a list of path names of the files to be deleted, minus the path %PDDIR%\spool.

KFPS05031-E E

An error occurred due to aa....aa

A command's internal function resulted in an error.

aa....aa: Cause of the error

S: Terminates processing.

Action

Contact the customer support center.

KFPS05032-E E

RPC error, return code=aa....aa

An RPC communication error occurred.

aa....aa: RPC error code

S: Terminates processing.

Action

See 4.1 Detail codes for RPC-related errors to eliminate the cause of the error, and re-execute the command. If the same error recurs, contact the customer support center.

KFPS05033-E E+L

Internal function error, func=aa....aa, return code=bb....bb

Command's internal processing resulted in an error.

aa....aa: Name of the function resulting in the error

bb....bb: Detail code for the system-related error

S: Terminates processing.

Action

See 4.2 Detail codes for system-related errors to eliminate the cause of the error. If the error cannot be corrected by the user, contact the customer support center.

KFPS05034-E E

System call error, func=aa....aa, return code=bb....bb, errno=cc....cc

A system function error occurred. This message displays the function name resulting in the error, the function's return code, and errno.

aa....aa: Function name

bb....bb: Return code

cc....cc: errno value

S: Terminates processing.

O: Check the error indicator value, refer to errno.h and to the applicable OS manual to eliminate the cause of the error, then re-execute.

Action

Eliminate the cause of the error and execute the command.

KFPS05035-E E+L

Unable to start command; insufficient memory on PROCESS

A shortage occurred in the process private area.

S: Terminates processing.

Action

Check System call = malloc and Mnemonic = ENOMEM in 4.3 System call return codes to investigate the cause of the error, and take appropriate action.

KFPS05036-E E

aa....aa receive data incorrect

RPC reception result is invalid for command aa....aa.

aa....aa: Command name

S: Terminates processing.

Action

There may be a communication error or a memory shortage. If an error message was output before this message, take action as indicated in that message. If this message is output again, even with these actions, contact the customer support center.

KFPS05037-E E

Enter command in manager node

A command was entered to a host that is not the system manager.

S: Terminates processing.

O: Enter the command on the server machine where the system manager is located.

KFPS05038-E E

Remote procedure call error occurred

A communication error occurred.

S: Terminates processing.

Action

If an error message was output before this message, take action as indicated in that message. If no message was output, contact the customer support center.

KFPS05039-E E+L

Unable to access shared memory

Shared memory cannot be accessed.

S: Terminates processing.

Action

HiRDB shared memory may have been deleted. If HiRDB shared memory was deleted, contact the customer support center.

Otherwise, eliminate the cause of the error according to the detail message already output. If no detail message was output, contact the customer support center.

If you are using the Windows edition of HiRDB/Parallel Server, this message may be output immediately after a value is entered with the pdstart command. In this case, a system definition may be invalid, so re-evaluate the system definitions based on the messages output to the event log.

KFPS05040-E E+L

Unable to start command due to HiRDB status off line

A command was entered while HiRDB was inactive.

S: Terminates processing.

Action

Activate HiRDB before executing the command.

KFPS05041-E E+L

Incorrect server name specified

The server name specified in a command option is invalid. The name of a server that was not defined as a HiRDB server was specified, or the name of a server that was not the target of the command was specified.

S: Terminates processing.

Action

Check the server name, and re-execute the command.

KFPS05042-E E

Incorrect hostname or unit id specified

The host name specified in a command parameter has not been defined as a HiRDB host name.

S: Terminates processing.

Action

Specify a host name that has been defined as a HiRDB host name and execute the command.

KFPS05043-E E

Unable to execute aa....aa command from bb....bb to cc....cc

A command cannot be executed at a remote host.

aa....aa: Command name

bb....bb: Local host name (standard host name of the host that executed the command)

If no standard host is required, ******** is displayed.

If the standard host name exceeds 32 characters, only the first 32 characters are displayed.

cc....cc: Remote host name

If the remote host name exceeds 32 characters, only the first 32 characters are displayed.

S: Terminates processing.

Action

Take the following action:

Check if it is permitted to use the same user ID to log in from the local host to the remote host.

If c-shell is used as the login shell, check PDDIR specified for $HOME/.cshrc for an error (in UNIX).

If this message is displayed when the pdconfchk command was executed, and if the host name of the reserve system is displayed in cc....cc in the message, the host name specified in the pd_hostname operand or in the -x option of the pdstart operand may be incorrect. Check that the standard host name of the running system is specified in the pd_hostname operand. Also, check that the correct host name is specified in the -x option of the pdstart operand.

KFPS05044-E E

Communication error occurred, function=aa....aa, errno=bb....bb

Communication error occurred while reporting abnormal termination of a utility.

aa....aa: Name of the function resulting in the error

bb....bb: errno

S: Terminates processing.

Action

Check the error indicator value, eliminate the cause of the error, then re-execute the utility, if necessary. If the same error message is reissued, contact the customer support center.

KFPS05045-E E+L

No server in this unit

No server is defined for the unit from which the command was entered.

S: Terminates processing.

Action

If the command was entered from the wrong unit, execute the command on the correct unit. Otherwise, terminate the unit, add the server definition, then re-execute the command.

KFPS05045-E E

No dictionary server

No dictionary server is defined.

S: Terminates processing.

Action

Check the system common definition for the dictionary server definition.

Dictionary server defined:

Re-execute the processing. If the same message is reissued, contact the customer support center.

Dictionary server undefined:

Define the dictionary server.

KFPS05046-E E

Dictionary already initialized

A dictionary has already been initialized.

S: Terminates processing.

Action

To initialize a dictionary, either use the pdfmkfs command to re-create the HiRDB file area for the master directory RDAREA or enter the pdstart -i command after system startup.

KFPS05047-E L

Command aa....aa failed, process ID=bb....bb

An operation command or utility command process terminated abnormally.

aa....aa: Command name

bb....bb: Process ID

S: Resumes processing.

Action

Refer to the message troubleshooting information (dump, trace, etc.) that was output before this message and to the message for the corresponding server to check the cause of the abnormal termination, then take appropriate action. If the error cannot be corrected, contact the customer support center.

KFPS05048-Q E+L

Fall-back operation will be started, do you really want to proceed? (y/n)

When the HiRDB system performs reduced activation by specifying the pd_start_skip_unit operand, the system waits for operator confirmation.

S: Resumes processing.

O: Preceding this message, the system displays a KFPS01837-I message indicating the unit identifier on which the reduced activation operation is to be skipped. Check the message and reply y to perform the reduced activation operation, and n to skip it. If n is indicated, the system cancels the HiRDB startup processing.

KFPS05049-Q S

DB recovery from backup required when restarting with "pdstart -dbdestroy", (n/3), do you really want to proceed ?(y/n)

When pdstart dbdestroy is used to restart HiRDB, database recovery with the database recovery utility becomes necessary, and the system asks whether forced startup should actually be executed. This message is output three times; if the y response is entered all three times, the system executes forced restart. If any other response is entered, the system cancels forced restart and terminates. pdstart dbdestroy should be entered only when HiRDB cannot be started with pdstart; pdstart should always be used first to restart HiRDB. If HiRDB cannot be restarted, take appropriate action, as described below:

Enter pdstart -r to restart HiRDB.

Recover the master directory RDAREA, make a backup, then terminate the HiRDB system.

Enter pdstart dbdestroy to start HiRDB forcibly.

Recover RDAREAs that were updated since the previous HiRDB startup or since the pdclose command was entered, make a backup, then release the shutdown status.

S: Waits for a response.

Action

To execute forced startup:

Enter y as the response to all messages that are output.

To cancel forced startup:

Enter any character other than y as the response.

KFPS05050-Q S

DB will be initialized when restarting with "pdstart -i", do you really want to proceed ?(y/n)

When HiRDB is started with the pdstart -i command, all databases must be re-created; the system therefore asks whether HiRDB should actually be started in the initialization mode.
If y is entered as the response, the system resumes startup in the initialization mode; if any character other than y is entered as the response, the system cancels startup and terminates.
To start HiRDB without initializing the database, enter the pdstart command.

S: Waits for a response.

Action

To reinitialize the database, enter y as the response.

To cancel database reinitialization, enter any character other than y as the response.

KFPS05051-E E+L

Unable to cancel process due to status critical

The process cannot be cancelled because the process status is critical.

S: Terminates the command.

O: Re-execute the command if necessary.

KFPS05052-E E

Unable to cancel process due to HiRDB status busy

Cancellation of the process failed because the HiRDB workload is high.

S: Terminates the command.

O: Re-execute the command, if necessary.

KFPS05053-E S

Unable to specify manager node

The system manager server machine (host) cannot be specified in a command parameter.

S: Terminates processing.

Action

Enter the command to the system manager server machine.

KFPS05054-E E

Same UAP name process exists, Specify server process id

There is more than one UAP process with the UAP name specified in the pdcancel command.

S: Terminates processing.

Action

Re-execute the command specifying the process ID.

KFPS05055-E E

No such process

One of the following occurred:

The process specified in the pdcancel command was not found.

The specified process terminated immediately before the pdcancel command was entered.

An attempt was made to cancel a HiRDB system control process by entering the pdcancel command with the -d option specified. (in UNIX)

S: Terminates processing.

O:

If the intended process is still active, re-execute the command with its process ID specified or the correct UAP name specified.

To execute a pdcancel command that specifies the -d option, specify the process ID of the front-end server, back-end server, dictionary server, single server, or utility server (in UNIX).

KFPS05056-E E

Unable to stop MGR unit with "-z" option

The pdstop command with the -z option specified cannot be executed at the system manager (MGR).

S: Terminates processing.

O: To terminate the system manager, specify the pdstop command without any option specified or with the -f option specified, and terminate the HiRDB system.

KFPS05057-W E

Unable to find server process

The HiRDB/Single Server process specified in the pdcancel command was not found.

S: Terminates processing.

Action

Check if the process specified in the option for cancellation exists, and re-execute the command specifying the correct option, if necessary.

KFPS05057-W E

Unable to find front end server process

The front-end server process for a HiRDB/Parallel Server whose cancellation was requested by the pdcancel command was not found.

S: Terminates processing.

Action

Check if the process specified in the option for cancellation exists, and re-execute the command specifying the correct option, if necessary.

KPS05058-E S

Dictionary being initialized

pdinit is already executing.

S: Terminates processing.

KFPS05059-E S

Usage: aa....aa

The command option specification format is invalid.

aa....aa: Command format

S: Terminates processing.

Action

Check the command usage in the manual HiRDB Version 9 Command Reference, and re-execute.

KFPS05060-E S

Unable to execute aa....aa because bb....bb

The aa....aa command cannot be executed.

aa....aa: Command name

bb....bb: Reason code

file not found: The setup file does not exist.

setup file is invalid: The setup file is invalid.

S: Terminates processing.

Action

file not found
Check that the path name of the setup file specified in the aa....aa command is correct.

setup file is invalid
There is an error in the contents of the setup file specified in the aa....aa command. Revise the contents of the setup file and re-execute the command.

KFPS05061-E E

Too long path name with aa....aa and directory_name

The pathname of the HiRDB system definition file in the directory specified by the -d option of the pdconfchk command is too long.

aa....aa:

PDDIR: Storage location of the unit control information definition file

PDCONFPATH: Storage location of HiRDB system definition files other than the unit control information definition file

S: Terminates processing.

Action

Take one of the following actions:

If aa....aa is PDDIR:
Re-evaluate the length of the path name of the %PDDIR%\conf\ subdirectory so that it is no more than 220 bytes.

If aa....aa is PDCONFPATH (in UNIX):
If the PDCONFPATH operand is specified in the unit control information definition, re-evaluate so that the total length of the shared directory and the subdirectory path name is no more than 220 bytes. If the PDCONFPATH operand is not specified in the unit control information definition, re-evaluate so that the length of the $PDDIR/conf/ subdirectory is no more than 220 bytes.

If aa....aa is PDCONFPATH (in Windows):
Revise the path name of the %PDDIR%\conf\subdirectory to 220 bytes or less.

KFPS05062-W E

Unmatched PDCONFPATH between system definition file and environment variable

The value of the PDCONFPATH operand (%PDDIR%\conf is assumed if no value is specified) in the unit control information definition file and the value of the PDCONFPATH environment variable when executing pdconfchk do not match. The pdconfchk command uses the value of the PDCONFPATH operand in the unit control information definition file.

S: Continues processing.

Action

Re-evaluate the value of the PDCONFPATH environment variable.

KFPS05063-E S

Unable to stop normally because unit terminated abnormally

HiRDB cannot be terminated normally, because a unit was terminated abnormally or forcibly by the pdstop -f command.

S: Resumes processing.

Action

Use the pdls command to determine which unit terminated abnormally or was stopped by the pdstop -f command, start the unit, then terminate it normally with the pdstop command. Or, terminate the unit forcibly with the pdstop -f command.

If Real Time SAN Replication with the log-only synchronous method is used:

Transaction execution site
Use the pdls command to determine which units terminated abnormally or were terminated using the pdstop -f command, restart the units, and then use the pdstop command to perform normal termination. Alternatively, use the pdstop -f command to terminate them forcibly.

Log application site
Use the pdls command to determine which units terminated abnormally or were terminated using the pdstop -f command, start the units, and then use the pdstop -l command to perform normal termination. Alternatively, use the pdstop -f command to terminate them forcibly.

KFPS05064-E S

Unable to stop HiRDB normally because unit being started

HiRDB cannot be terminated normally, because a unit is engaged in startup processing.

S: Resumes processing.

Action

Re-execute the pdstop command after HiRDB system startup is completed. Or, terminate HiRDB forcibly with the pdstop -f command.

KFPS05065-E S

Unable to stop HiRDB normally because unit being terminated

HiRDB cannot be terminated normally, because a unit is engaged in termination processing.

S: Resumes processing.

Action

Re-execute the pdstop command after unit termination is completed. Or, terminate HiRDB forcibly with the pdstop -f command.

KFPS05066-E E+L

Error found while analyzing system common definition file

An error was detected while analyzing the operands in the system common definition.

S: Terminates processing.

Action

Correct the information specified in the system common definition and re-execute.

KFPS05067-E E

Unable to start server due to dictionary server is inactive

Front-end server or back-end server cannot be started because the dictionary server is inactive.

S: Terminates processing.

Action

If the dictionary server can be used, start the dictionary server and re-execute.

KFPS05068-E S

Unable to stop aa....aa normally due to existence of half status unit

aa....aa cannot be terminated normally, because a unit has been shut down.

aa....aa: Termination type:

HiRDB: System

unit: Unit

server: Server

S: Resumes processing.

Action

To terminate, enter the pdstop -f command.

KFPS05069-W S

Unable to stop unit due to error occurred while terminating

A unit cannot be terminated because an error occurred during termination processing.
Or, the unit has already terminated.

S: Resumes processing.

Action

If a KFPS05222-E message was output immediately before, take action as indicated in that message. If the pdstop -f command was used, the unit may already be stopped, so check the message that was output immediately before.

If other than the above, check the unit that cannot be terminated from the message immediately before, and stop the unit using the pdstop -f or pdstop -z command.

If it cannot be terminated forcibly, contact the customer support center.

KFPS05070-E S

Unable to stop unit normally due to error occurred while terminating

A unit cannot be terminated normally, because an error occurred during termination processing.

S: Resumes processing.

Action

Terminate the unit forcibly with the pdstop -f command. If it cannot be terminated forcibly, contact the customer support center.

KFPS05071-E S

Unable to stop server due to error occurred while terminating

A server cannot be terminated normally, because an error occurred during termination processing. Or, the server is already stopped.

S: Resumes processing.

Action

Terminate the server forcibly with the pdstop -f command. If it cannot be terminated forcibly, contact the customer support center.

If a stop command is issued for a server that has already stopped, this message may be output. In this case, ignore this message.

If a message indicating the reason that the server to be stopped could not be stopped was output to the event log (in UNIX, syslogfile) of the unit on which the server is running, refer to that message.

KFPS05072-W E+L

HiRDB system termination process (mode=aa....aa) execution exceeds bb minutes

The shutdown processing of HiRDB has not terminated after bb minutes.

aa....aa: Termination mode

"PLAN": Planned termination

"NORMAL": Log application site termination

bb: Elapsed time (in minutes)

S: Terminates the pdstop command, and continues termination processing.

Action

Take one of the following actions:

Take no action if the planned shutdown process is to be held until the current utility or transaction terminates.

Use the pdcancel command to cancel the current utility or transaction if the planned shutdown process is to proceed by cancelling the current utility or transaction. When the utility or transaction is cancelled, HiRDB proceeds with the planned shutdown process.

(In UNIX:) If the pdcancel command cannot cancel the transaction, remove the relevant process using the OS's kill command with the -6 option specified, terminate the unit forcibly, save the data under $PDDIR/spool, and contact the customer support center.

(In Windows:) If the pdcancel command cannot cancel the transaction, remove the relevant process using the pdkill command, terminate the unit forcibly, save the data under %PDDIR%\spool, and contact the customer support center.

If this message was output during termination of a log application site, the termination processing probably caused the error. Use the pdstop -f command to terminate HiRDB forcibly, investigate the cause of the error by reviewing messages output before this message, and eliminate the cause of the error. For the primary causes of errors and recovery procedures, see the section on operations when an error occurs with the log-only synchronous method in the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide. After removing the cause of the error, perform preparation for log application, and restart the log application.

KFPS05073-E E

Environmental variable aa....aa nothing

Environment variable aa....aa has not been set up.

aa....aa: Environment variable

S: Continues or terminates processing, depending on how the HiRDB environment variables have been set up.

Action

Check whether or not all environment variables required by HiRDB have been set up. Set up any needed environment variables and re-execute the command.

KFPS05074-E S

Unable to stop normally, use pdstop command with "-f" option

The system cannot be terminated normally because an error occurred during termination processing.

S: Terminates processing.

O: If a process is engaged in UAP or utility execution, re-execute the pdstop command after the process terminates. In other cases, terminate the system forcibly with the pdstop -f command.

Action

If the system cannot be terminated, contact the customer support center.

KFPS05075-E E

Unable to execute command, command=aa....aa, return code=bb....bb, errno=cc....cc

A shell command to be executed within a command failed.

aa....aa: Command to be executed

bb....bb: Command's return code

cc....cc: Error number

S: Terminates processing.

Action

Eliminate the cause of the command failure and re-execute the command, if necessary. If this error message is output repeatedly, contact the customer support center.

KFPS05076-E L

Unable to start this unit with "-i" option

A utility special unit could not be started with the pdstart -i command.
For HiRDB/Parallel Servers, the -i option cannot be specified when starting at the unit level.

S: Terminates processing.

Action

Start HiRDB/Single Servers using the pdstart command. Alternatively, specify the -r or dbdestroy option with the pdstart command to activate HiRDB/Single Servers.

When reinitializing using a HiRDB/Parallel Server, stop the system, and then start the system using the pdstart -i command. To start a unit, either specify the pdstart -x option alone, specify it with the -r option (pdstart -x -r), or specify it with the -dbdestroy option (pdstart -x -dbdestroy).

KFPS05077-E E

Unable to execute remote shell command, hostname=aa....aa

The command cannot be executed for a remote host (in UNIX, remote shell).

aa....aa: Remote host name (in UNIX, host name)

S: Terminates processing.

Action

Take one of the following actions:

In UNIX
Check if the remote shell execution privilege has been granted for the corresponding remote host and re-execute, if necessary.

In Windows
Determine whether the same user ID has privilege to log on to the remote host from the local host, and, if necessary, re-execute. If using HiRDB/Parallel Server or if using HiRDB/Single Server with a system switchover facility, a connection with the remote shell is required. Check if the settings are still valid. For details, see the section on OS environment file settings in the HiRDB Version 9 Installation and Design Guide.

KFPS05078-I L

Unable to recognize HiRDB system initialization completion

The pdstart command could not confirm completion of system initialization processing.

S: Continues processing.

Action

Database Initialization Utility not running:

Check whether a KFPS05201-Q message has been output. If it has been output, the system is waiting for the input of the pdinit command, in which case the pdinit command should be executed. System initialization processing is resumed after the processing of the utility has terminated. After a while, enter the pdls command to check the system status. The pdls command can also be used to determine whether or not the system is waiting for the input of the pdinit command.

A HiRDB version upgrade command not running:

Check whether a KFPS05203-Q message has been output. If it has been output, the system is waiting for the input of the pdvrup command, in which case the pdvrup command should be executed. System initialization processing is resumed after the processing of the pdvrup command has terminated. After a while, enter the pdls command to check the system status.

When there is no request for the input of an HiRDB version upgrading command in the Database Initialization Utility:

Because the server startup is taking time, wait a while and enter the pdls command to check the system status.

If the system initialization processing has not terminated, check the message for other causes of the problem. If the cause of the problem cannot be determined, contact the customer support center.

The pdstart command is failing to terminate normally:

Specify the pdstart command completion wait time in the pd_system_complete_wait_time operand. If the completion wait time is increased, the pdstart command terminates normally.

When the system switchover facility is used and the standby system is activated:
The standby system unit may be waiting for the running unit to initialize because the running system unit has not yet initialized. Use the pdls command and the HA monitor or Hitachi HA Toolkit Extension commands to check the status of the running system unit. If the running system unit was not initialized, eliminate the cause of the initialization error and reinitialize the running system unit.

When the system switchover facility is used and the running system is activated:
The system may be waiting for activation of the running system unit or it may be activated as the standby system unit. Check the system status using the pdls command and the HA monitor or the Hitachi HA Toolkit Extension commands. If it is not activated as the running system unit, activate it as the running system unit using the HA monitor (Hitachi HA Toolkit Extension) commands or cluster software.

KFPS05079-E E

Dictionary not initialized, unable to start server

A dictionary has not been initialized by the pdinit command, but an attempt was made to start the server with the pdstart command.

S: Terminates processing.

Action

Initialize the dictionary and re-execute, if necessary.

KFPS05080-Q S

Uap name=aa....aa, uap start time=bb....bb, server process id=cc....cc,cancel process? (y/n)

If a UAP name is specified in the pdcancel command and the command is executed, this message outputs the UAP name, the UAP start time, and the server process ID, and then awaits user response to determine whether to cancel the process.
If the -d option is specified in the pdcancel command and the command is executed, this message outputs the server process ID, and then awaits user response to determine whether to cancel the process.

aa....aa: UAP name (if the pdcancel command was executed with the -d option specified, ******** is displayed)

bb....bb: UAP startup time (if the pdcancel command was executed with the -d option specified, 999999 is displayed)

cc....cc: ID of the process subject to cancellation processing

S: Resumes processing.

O: To continue cancellation processing, enter y; to cancel the processing, enter n.

KFPS05081-Q S

Cancel all server process? (y/n)

Asks the operator whether or not all single server processes on a HiRDB/Single Server are to be canceled.

S: Resumes processing.

Action

To continue cancellation processing, enter y (yes); to cancel the processing, enter n (no).

KFPS05081-Q S

Hostname=aa....aa, cancel all front end server processes? (y/n)

Asks the operator whether or not all front-end server processes being executed on the specified host are to be canceled.

aa....aa: Host name

S: Resumes processing.

Action

To continue cancellation processing, enter y (yes); to cancel the processing, enter n (no).

KFPS05082-Q S

Utility server name=aa....aa, process id=bb....bb, cancel process? (y/n)

When a utility is cancelled by the pdcancel command, the system displays the utility server name and process ID and asks the operator whether or not cancellation processing is to be continued.

aa....aa: Utility server name

bb....bb: Utility server process ID

S: Resumes processing.

Action

To continue cancellation processing, enter y (yes); to cancel the processing, enter n (no).

KFPS05083-E E

aa....aa terminated, due to server process abnormal end

A remote server process terminated abnormally during execution of a utility or operation command.

aa....aa: Command name

S: Terminates processing.

Action

If a server process was terminated by pdstop or pdcancel, contact the customer support center.

KFPS05084-E E

Invalid option argument specified, option argument=aa....aa

An invalid option argument was specified in a command.

aa....aa: Option argument

S: Terminates processing.

Action

Correct the option argument and re-execute, if necessary.

KFPS05087-E E

Unable to execute aa....aa command because bb....bb

The aa.....aa command could not be executed because the system did not have a system switchover configuration.

aa....aa: Command name

pdls -d ha

pdstop -f -q (HiRDB/Single Server)

pdstop -z -q (HiRDB/Parallel Server)

bb....bb: Reasons the command cannot be executed:

pd_ha is not 'use': This system does not have a system switchover configuration.

pd_ha is not 'use' or pd_ha_unit is 'nouse': This system or unit does not have a system switchover configuration.

S: Terminates processing.

Action

Check that use is specified in the pd_ha operand. Or, check that nouse is specified in the pd_ha_unit operand.

KFPS05090-E L

Unable to execute pdndls command

The pdndls command cannot be executed.

S: Terminates processing.

O: Re-execute the command after creating a multi-node-configuration definition file.

KFPS05091-E L

Incorrect HiRDB ID specified

Undefined HiRDB identifier was specified in a command parameter.

S: Terminates processing.

O: Check the multi-node-configuration definition file or option definitions for the correct HiRDB.

KFPS05092-E E

Error occurred

Error was detected during execution of pdndls command.

S: Resumes processing.

O: Check the detail information that is displayed after this message, then take appropriate action.

KFPS05093-E E

Error found while analyzing pdmnd definition file

The pdndls command cannot be executed.

S: Terminates processing.

O: Check the contents of the multi-node-configuration definition file.

KFPS05094-E E

System error, func= aa....aa, code= bb....bb, detail=cc....cc, call func=dd....dd, line=ee....ee

An error was detected in the internal processing of a HiRDB-embedded support function.

aa....aa: Name of the function in which the error occurred

bb....bb: Error code

cc....cc: Error detail code

dd....dd: Call-originating file name (internal information)

ee....ee: Call-originating line number (internal information)

S: Terminates processing.

O: Take one of the following actions:

When HiRDB-embedded support function is not used
This command can be executed only when a HiRDB-embedded support function is used.

When HiRDB-embedded support function is used
Referencing the operation model setup file failed. Check the status of this file. Or, check that the PDEMBDIR environment variable has been set up correctly.

Action

See 4. Error Detail Codes and take appropriate action. If the cause is unknown, save the contents of this message, the files under %PDDIR%\spool, and a backup of the event log (in UNIX, syslogfile), and contact the customer support center.

KFPS05095-E E

Unable to execute command, user=aa....aa

The command that user aa....aa entered could not be executed.

aa....aa: Log in user name of the user entering the command

S: Terminates processing.

O:

Re-evaluate the log in the user environment of the user who entered the command. For command details or the error cause, see the KFPS05043-E or KFPS05077-E message output immediately before this message.

KFPS05096-I S+L

Usage: pdpfresh [-s server_name] [-{f | c} ]

The option specification format of the pdpfresh command is invalid.

S: Terminates processing.

Action

Correct the option specification, and then re-execute.

KFPS05097-E S

Unable to stop normally during Online DB Reorganization

An attempt to terminate normally failed because updatable online reorganization is not complete.

S: Terminates processing.

Action

Correct the option specification, and then re-execute.

O:

Execute the pdls -d org command to check if discrepancies application processing of online reorganization is complete. If it is complete, re-execute the pdstop command to terminate normally. If the HiRDB system is terminated before discrepancies application processing of online reorganization is complete, execute either a planned stop (pdstop -P) or forced termination (pdstop -f).

KFPS05098-I S

Usage: pdprgrenew [-b] HiRDB_home_directory

The specification format of the pdprgrenew command option is invalid.

S: Terminates processing.

Action

Correct the option specification and re-execute.

KFPS05099-I S

Usage: pdprgcopy HiRDB_home_directory

The specification format of the pdprgcopy command option is invalid.

S: Terminates processing.

Action

Correct the option specification and re-execute.

KFPS05100-E L

Error occurred in HiRDB unit starting process,reason code=aa

The unit cannot be started due to an error during unit startup processing.

aa: Reason code:

10: Definition analysis error

20: Communication error

30: Area shortage

40: Shared memory shortage

S: Terminates abnormally.

Action

Take an appropriate action according to the reason code. If the error cannot be corrected, contact the customer support center.

Reason code | Explanation | Action
10 | Definition analysis error. | See the message output immediately before, check whether there is an error in the HiRDB system definition, and correct the error.
20 | A communication error occurred. | See the message output immediately before, check the cause of the communication error, and eliminate it.
30 | An area (memory) shortage occurred. | Execute the startup process after other processes have terminated, or revise the size of the swap area, then re-execute.
40 | A common memory shortage occurred. | Consider whether the estimate of the common memory size is correct. If the estimate is correct, contact the customer support center.

KFPS05101-E L

HiRDB unit definition parameter analysis error

An error occurred while analyzing the HiRDB unit definition parameters.

S: Terminates abnormally.

Action

Contact the customer support center.

KFPS05102-E L

Insufficient memory on STATIC_SHMPOOL, size=aa....aa

A shared memory allocation error occurred.

aa....aa: Size (in bytes) of the area that was to be allocated

S: Terminates processing.

Action

Save the files under %PDDIR%\spool for this unit, save the event log (in UNIX, syslogfile), and contact the customer support center.

KFPS05110-I S+L

HiRDB unit aaaa initialization process complete

Initialization of HiRDB unit aaaa has been completed.

aaaa: Unit identifier

S: Resumes processing.

KFPS05111-E L

Error occurred in HiRDB unit aaaa termination process. mode=bb....bb, reason code=cc....cc

Error occurred during termination processing at HiRDB unit aaaa.
If the termination mode is PLAN, or if Real Time SAN Replication is used for a log application site that is terminating with a termination mode of NORMAL, all units other than unit aaaa are terminated forcibly.

aaaa: Unit identifier

bb....bb: Termination mode:

NORMAL: Normal termination

PLAN: Planned termination

FORCE: Forced termination

cc....cc: Reason code:

COMMUNICATION: System manager communication error

INTERNAL ERROR: Internal processing error

S: Terminates abnormally.

Action

Check the messages that were output before this message, correct the error, then restart the system.

(Planned termination or normal termination of a log application site when Real Time SAN Replication is used)

Check that all units have terminated, then restart the system.

If there is an active unit, terminate it either by entering the pdstop -f command from the system manager unit or by logging directly into the unit and entering the pdstop -z command, and then restart the system.

The method for determining termination status is to refer to each unit's event log (in UNIX, syslogfile); if any of the following messages is output, the unit is terminated:

KFPS01821-E message

System manager unit: KFPS01850-I message (termination mode = FORCE)

For a unit that is not the system manager: KFPS01841-I message (termination mode = FORCE)

If the cause is unknown, save the files under %PDDIR%\spool for this unit, save the event log (in UNIX, syslogfile), and contact the customer support center.

KFPS05112-I L

Some servers did not startup,please check

Some HiRDB servers may not be active (although they are on startup completed status as a HiRDB unit).

S: Resumes processing.

Action

Check the server status with the pdls command. If a server is on HELD status, the database must be recovered. If a server is on STOP status, eliminate the cause of the startup error and restart the server.

KFPS05113-E L

Error occurred in HiRDB unit aaaa starting process, reason code=bb....bb

An error occurred while starting Unit aaaa.
If the error code is 7, the unit cannot be restarted because planned termination processing is underway. The system forcibly terminates all units.
If the error code is 11, the unit cannot be restarted because there are units in termination processing on the log application site. All units are terminated forcibly.
If the error code is 12, the unit cannot be restarted because there are units performing database inheritance. All units are terminated forcibly.

aaaa: Unit identifier

bb....bb: Error code:

S: If the error code is 1-6, 8, 9, or 10, the unit is terminated abnormally.

If the error code is 7, 11, or 12, all units are terminated forcibly.

Action

The following shows the error codes and their appropriate actions:

Error code
Error contents
Action

1
Internal processing error
Save the files under %PDDIR%\spool for this unit, save the event log (in UNIX, syslogfile), and contact the customer support center.

2
Communication error
Check whether the system manager unit is stopped. If the system manager unit is stopped, check the cause of the system manager unit being stopped, and eliminate the error. Then, restart HiRDB. If the error occurred even when the system manager unit was active, there may be a network failure. See 4.1 Detail codes for RPC-related errors to investigate the error. If the cause is unknown, save the files under %PDDIR%\spool on the system manager unit and the unit that output the abort code, save the event log (in UNIX, syslogfile), and contact the customer support center.

3
Definition parameter error
A definition parameter specified for the unit may contradict the system manager unit definition or another unit definition. Check the server configuration and unit identifier for errors, correct any errors, then re-execute. For details, see the KFPS05215-W message.

4
Memory shortage
Execute after other processes terminate, or revise the size of the swap area, then re-execute.

5
Version mismatch
Save the files under %PDDIR%\spool for this unit, save the event log (in UNIX, syslogfile), and contact the customer support center.

6
Internal processing error

7
Status mismatch error with another unit
A unit in planned termination was detected. Check that all units have terminated, then restart the system. If there is an active unit, terminate it either by entering the pdstop -f command from the system manager unit, or by logging directly onto the unit and entering the pdstop -z command, and then restart the system.
The method for determining termination status is to refer to each unit's event log (in UNIX, syslogfile); if any of the following messages is output, the unit is terminated:

KFPS01821-E message

System manager unit: KFPS01850-I message (termination-mode=FORCE)

For a unit that is not the system manager: KFPS01841-I message (termination-mode=FORCE)

8
An activation waiting timeout occurred on a server to be used with standby-less system switchover (effects distributed)
Check the activation status of the server indicated in the KFPS05251-W message that was output immediately before using the HA monitor or the Hitachi HA Toolkit Extension, and then re-activate the units that abnormally terminated.

9
The contents of the system definition do not match between units
Check the KFPS05247-E message that was output immediately before, make the value of the pd_rpl_hdepath operand the same for each unit, and restart the units that abnormally terminated.

10
The activation mode does not match between units
Refer to the KFPS05247-E message output immediately before this message, read each unit's activation options, and then re-activate the abnormally terminated units.

11
Status mismatch error with another unit (during log application site termination processing)
A unit on the log application site in termination processing was detected. Confirm that all units have terminated, and then restart HiRDB. If there are still units that have not terminated, execute the pdstop -f command from the system manager unit, wait until they have terminated, and then restart HiRDB. The method for determining running status is to check each unit's event log (in UNIX, syslogfile). If a KFPS01821-E message is output (for HiRDB/Parallel Server, system manager unit, a KFPS01850-I message (termination-mode=FORCE); for a unit other than the system manager unit, a KFPS01841-I message (termination-mode=FORCE)), the unit is terminated.

12
Status mismatch error with another unit (during database inheritance)
A unit performing database inheritance was detected. Confirm that all units have terminated, and then restart HiRDB. If there are still units that have not terminated, execute the pdstop -f command from the system manager unit, wait until they have terminated, and then restart HiRDB. The method for determining running status is to check each unit's event log (in UNIX, syslogfile). If a KFPS01821-E message is output (for HiRDB/Parallel Server, system manager unit, a KFPS01850-I message (termination-mode=FORCE); for a unit other than the system manager unit, a KFPS01841-I message (termination-mode=FORCE)), the unit is terminated.

KFPS05114-E L

SDS server did not startup

The activation of the single server cannot be confirmed.

S: Terminates abnormally.

Action

Contact the customer support center.

KFPS05120-W L

Waiting for UAP and/or utility disconnect in HiRDB unit aaaa, current connect user count = bbb

The system is waiting for termination of a UAP or utility.

aaaa: Unit identifier of the unit waiting for termination

bbb: Number of connected users who are waiting for the termination of the UAP or utility

S:

Resumes processing while not allowing new users to connect to HiRDB. Holds the termination processing of HiRDB until the processing of the UAP or utility ends (15 minutes). Starts HiRDB termination processing upon termination of the UAP or utility.

Outputs detained information about the users connected to HiRDB to a connection user information file (%PDDIR%\spool\cnctusrinf). In addition, outputs the execution results of the following commands to a connection user detail file (cnctusrdtl under %PDDIR%\spool):

pdls -d act

pdls -d prc

pdls -d trn

For a HiRDB/Parallel Server, these files are output to the server machine in which the System Manager is located.

Alternatively, if a currently running UAP or utility stopped near the time this message is output, this information may not be included in the detail information for the servers connected to the HiRDB system.

O: Referring to the information output to the connection user information file (%PDDIR%\spool\cnctusrinf), determine which users are connected, and take corrective action. If you are still unsure which users are connected, refer to the connected user detail file (%PDDIR%\spool\cnctusrdtl) to determine this information, and take corrective action. For details on corrective actions, see the HiRDB Version 9 System Operation Guide.

Following is an example of output from the connection user information file:

Output example:

UNIT ID : M350(173420)
UID  PID    GID  SVID  TIME   PROGRAM
C-GRP  C-PID  C-IP
334  22118  300  fes1  173330 uap00
WS     22205  172.17.32.37

Explanation:

UNIT ID:

Displays the unit identifier and the time of creation of the cnctusrinf file (hhmmss).

UID:

Displays the user IDs of the users who are connected to HiRDB.

PID:

Displays the process IDs of the users who are connected to HiRDB.

GID:

Displays the group IDs of the users who are connected to HiRDB.

SVID:

Displays the server name of the server to which users are connected.

A space may be displayed after a HiRDB server process is started.

TIME:

Displays the time (hhmmss) when HiRDB accepted a service request. Displays the number 999999 for the server to which users are not connected.

PROGRAM:

Displays the value specified in the PDCLTAPNAME operand of the client environment definition. The default for the PDCLTAPNAME operand is Unknown.

For details on the PDCLTAPNAME operand, see the HiRDB Version 9 UAP Development Guide.

Displays ****** for a utility.

The symbol ****** may be displayed after a HiRDB server process is started.

C-GRP:

Displays the types (client group types) of users who are connected to HiRDB.

If a client group connection frame guarantee facility is used and a user-defined client group is defined, displays the name of the user-defined client group.

Displayed character string | User type
XA | Users who are connected to HiRDB using the X/Open XA interface
PC | Users who are connected to HiRDB from a PC client
WS | Users who are connected to HiRDB from a WS client
MF | Users who are connected to HiRDB from a mainframe-based client (including a VOS3 client)

C-PID:

Displays the process ID of the client.

C-IP:

Displays the IP address of the client.

Note

C-GRP, C-PID, or C-IP is not displayed in the following cases:

The UAP or utility is not executed on the client side (the UAP or utility is executed on the HiRDB system).

The version of the client that linked the UAP is earlier than HiRDB Version 4.0 04-00.

KFPS05121-E L

Unable to stop normally, UAP and/or utility remaining in HiRDB unit aaaa, current connect user count = bbb

The HiRDB system cannot be stopped because a UAP or utility is being executed.

aaaa: Unit identifier of unit executing the UAP or utility

bbb: Number of connected users who are executing the UAP or utility

S: Terminates termination processing.

O: Re-execute the pdstop command after UAP or utility processing ends. Use the pdls -d trn or pdls -d prc command to determine the users who are executing the UAP or utility.

KFPS05123-W L

Using resource for "aa....aa" operand reached bb....bb% [, cc....cc]

The resources for the system definition operand "aa....aa" have reached a warning value bb....bb.

aa....aa: Name of the system definition operand

bb....bb: Warning value (in percentage)

cc....cc: Additional information

S: Resumes processing.

Action

The additional information that is output and the corrective action to be taken vary with the name of the operand. Take action by referring to the following table. Some operand names do not output additional information.

System definition operand name aa....aa
Additional information cc....cc
Action

pd_max_users: Maximum number of concurrent connections
dd....dd/ee....ee, server = ff....ff

dd....dd: Number of connected users

ee....ee: Defined value

ff....ff: Front-end server name or single server name. The symbol '**....**' is output if a warning value is reached during the execution of one of the following utilities:

pdload

pdrorg

pddbst

pdgetcst

pdmod

Re-evaluate whether the value for pd_max_users is appropriate. If the value is not appropriate, change the value of the operand.

pd_max_access_tables: Maximum value for the sum of the number of tables and the number of sequence generators that one user can access concurrently in one transaction
dd....dd/ee....ee, server=ff....ff

dd....dd: Usage count

ee....ee: Definition count

ff....ff: Server name

ff....ff: Server name

Re-evaluate whether the value for pd_max_access_tables is appropriate. If the value is not appropriate, change the value of the operand.

pd_max_rdarea_no: Maximum number of RDAREAs
pd_max_file_no: Maximum number of HiRDB files comprising an RDAREA
dd....dd/ee....ee, server = ff....ff

dd....dd: Number of RDAREAs used

ee....ee: Number of definitions

ff....ff: Server name

Re-evaluate whether the value for pd_max_rdarea_no or pd_max_file_no is appropriate. If the value is not appropriate, change the value of the operand.

pdwork: Work table HiRDB file system area
dd....dd=ee....ee / ff....ff, file system = gg....gg (hh....hh)

dd....dd: Detail category#
capacity file count
expand count

ee....ee: Size of area used

ff....ff: Assigned amount

gg....gg: HiRDB file system area name

hh....hh: Server name

Re-evaluate whether the option specified by the pdfmkfs command is appropriate for the applicable work table HiRDB file system area. If the option is not appropriate, re-estimate the value of the operand, and then initialize the work table HiRDB file system area using the pdfmkfs command. Terminate the HiRDB system normally before executing the pdfmkfs command.

client-group connect users: Number of users in the free utilization frame at the time of client group specification
dd....dd/ee....ee, server = ff....ff

dd....dd: Number of users connected within the free utilization frame

ee....ee: Number of definitions

ff....ff: Front-end server or back-end server. A symbol **....** is output if a warning value is reached during the execution of any of the following utilities:
pdload
pdrorg
pddbst
pdgetcst
pdmod

Check whether the value of the minimum connection guarantee number for each client group, specified in the pdcltgrp operand, is appropriate.

When executing a large number of utilities or UAPs that do not belong to a client group, reduce the minimum connection guarantee number for each client group specified in the pdcltgrp operand, and increase the free utilization frame.

If the minimum connection guarantee number assigned to a client group is sufficient, reduce the minimum connection guarantee number for that client group specified in the pdcltgrp operand, and increase the free utilization frame.

pd_max_list_users: Maximum number of users who can create lists
dd....dd/ee....ee, server = ff....ff

dd....dd: Number used

ee....ee: Number defined

ff....ff: Server name

Check if the value specified in pd_max_list_users is appropriate. If not, re-estimate the appropriate value and specify it.

pd_max_list_count: Maximum number of lists one user can create
dd....dd/ee....ee, server = ff....ff

dd....dd: Number used

ee....ee: Number defined

ff....ff: Server name

Check if the value specified in pd_max_list_count is appropriate. If not, re-estimate the appropriate value and specify it. Before modifying system definitions, terminate HiRDB normally.

pd_aud_max_generation_num: Maximum number of audit trail tables
dd....dd/ee....ee/unit=ffff

dd....dd: Number of audit trail tables that cannot become the swap destination

ee....ee: Operand value

ffff: Unit identifier

Request that the auditor load the data in the audit trail files that are waiting for data loading.

Re-evaluate whether the value of the pd_aud_max_generation_num operand is appropriate. If the value is not appropriate, change the value of the operand.

#: If the detail category is capacity, the size of an area used or allocated is indicated in megabytes.

KFPS05124-W L

Number of connect users exceeded max users, server=aa....aa

The number of connections to HiRDB exceeded the maximum number of concurrent connections (value of the pd_max_users operand).

aa....aa: Name of the server on which the number of concurrently connected users was detected

S: Resumes processing.

O: Re-execute the command after other users have terminated.

P: Re-execute the command after other users have terminated.

Action

Check whether the value specified in the pd_max_users operand is appropriate. If not, re-estimate the specification value and change the value.

KFPS05125-E L

Unable to execute receiving RPC service, send unit=aaaa, reason code =bb....bb

Request from unit aaaa cannot be executed.

aaaa: Unit ID of the unit that sent the request

bb....bb: Reason code

STOPPED NRFUNIT: A message was received from a recovery-unnecessary FES unit that has stopped.

S: The SQL statement executed in response to the recovery-unnecessary FES that sent the request terminates with an error. This transaction will be invalidated.

Action

After checking the status of unit aaaa, recover from the error according to the reason code. If the reason code is STOPPED NRFUNIT, use the command pdls -d svr to check whether the status information of unit aaaa is STOP(A).

If the status information is STOP(A), there might be a network error between unit aaaa and the system manager. In that case, use the pdstop -z command to terminate unit aaaa, and then take action to investigate the cause of the network error. After taking corrective action, restart unit aaaa.

If the status information is something other than STOP(A), check other messages to eliminate to cause of the error.

KFPS05130-E L

Unable to execute command. except pdvrup

No commands can be executed while pdvrup is executing.

S: Terminates processing.

Action

Re-execute the command after system startup is completed.

KFPS05131-E L

Unable to execute aa....aa command. reason code=bbbb

Execution of command aa....aa failed.

aa....aa: Name of the command being executed

bbbb: Detail code (see 4.2 Detail codes for system-related errors)

S: Terminates processing.

O: Correct the cause of the error and re-execute the command as necessary. If this error message is output repeatedly, contact the customer support center.

KFPS05140-I E+L

Data replication started. unit=aaaa

HiRDB Datareplicator linkage has started.

aaaa: Unit identifier

S: Resumes processing.

KFPS05141-I E+L

Data replication stopped. unit=aaaa

HiRDB Datareplicator has stopped.

aaaa: Unit identifier

S: Resumes processing.

KFPS05142-W E+L

Unable to stop data replication, server=aa....aa, reason=bb....bb

Data linkage with HiRDB Datareplicator could not be stopped.

aa....aa: Server name

bb....bb: Reason code

S: Continues processing.

Action

Take appropriate action according to the reason code.

Reason code | Cause | Action
FILE LOCK ERROR | A reference privilege or update privilege could not be acquired for a data linkage file used by HiRDB Datareplicator. | HiRDB Datareplicator has exclusive ownership of the data linkage file. Investigate the cause, and then take appropriate action.
FILE OPEN ERROR | A data linkage file used by HiRDB Datareplicator could not be opened. | Either the data linkage file has been deleted or it could not be opened due to a disk error. Synchronize to the target database, re-create the data linkage file, and then restart HiRDB Datareplicator and HiRDB.

KFPS05160-I L+S

HiRDB unit aaaa initialization process complete on standby site

Unit start processing on the log application site has finished.

aaaa: Unit identifier

S: Continues processing.

KFPS05162-E L

Error occurred in HiRDB unit aaaa database take over process, reason code=bb....bb

An error occurred during database inheritance. All units are terminated forcibly.

aaaa: Unit identifier

bb....bb: Error code

COMMUNICATION: Error in communication with another unit

INTERNAL ERROR: Internal processing error

S: Terminates abnormally.

Action

Check the messages output before this message, eliminate the error, and start the log application site HiRDB. Ensure that all units have terminated, and then restart HiRDB.

If there are still units that have not terminated, either execute the pdstop -f command from the system manager unit or execute the pdstop -z command from the units that have not terminated, wait until they have terminated, and then restart the log application site HiRDB.

The method for determining running status is to check each unit's event log (in UNIX, syslogfile). If any of the following messages is output, the unit is terminated:

KFPS01821-E message

System manager unit: KFPS01850-I (termination-mode=FORCE)

Unit other than the system manager unit: KFPS01841-I (termination-mode=FORCE)

If the cause cannot be determined, collect the files under $PDDIR/spool for this unit, collect the event log (in UNIX, syslogfile), and contact the customer support center.

KFPS05170-E L

Server aa....aa recovery failed, abnormally terminated unit=bbbb

Server recovery processing failed due to abnormal termination of the indicated unit.

aa....aa: Name of the server whose recovery failed

bbbb: Identifier of the unit that terminated abnormally

S: Resumes processing.

Action

Collect the files under $PDDIR/spool for this unit, collect the event log (in UNIX, syslogfile), and contact the customer support center.

KFPS05171-E L

Process recovery failed,abnormally terminated process=aa....aa

Recovery processing failed due to abnormal termination of the indicated process.

aa....aa: ID of the process that terminated abnormally

S: Terminates abnormally.

Action

For the abnormally terminated process ID, 0 might be output.

If other than 0 is output, use the pdls -d prc command to determine whether the relevant process is still running. If it is not running, there is no problem. If it is running, collect the files under $PDDIR/spool for this unit, collect the event log (in UNIX, syslogfile), and contact the customer support center.

KFPS05172-E L

Unable to inform unit aaaa that process is abnormal, abnormal process=bb....bb

Indicated process terminated abnormally, but the indicated unit cannot be recovered.

aaaa: Unit identifier of the unit for which recovery processing could not be executed

bb....bb: ID of the process that terminated abnormally

S: Resumes processing.

Action

For the abnormally terminated process ID, 0 might be output.

Check the unit status because no error has occurred if the unit output in the message has not been started.

If the unit has been started, contact the customer support center.

KFPS05173-E L

Recovery failure because server aa....aa abnormally terminated, utility=bb....bb cc....cc

Unit recovery processing failed with abnormal termination of the server.

aa....aa: Name of the server that abnormally terminated (maximum 8 characters)

bb....bb: Process ID (maximum 10 characters) of the utility that failed in recovery that is related to the server that abnormally terminated

cc....cc: Internal service name used by HiRDB (maximum 16 characters)

S: Continues processing.

Action

Use the pdls -d prc -a command to check whether the process ID output by the message was retained. If it was not retained, there is no problem. If it was retained, use the pdls -d trn -a command to check the name of the executed utility, and check whether the execution time of the utility is long. For actions to take if the execution time is long, see the HiRDB Version 9 System Operation Guide.

KFPS05180-E L

System call/function error, call=aa....aa, code=bbb

A system call or function error occurred.

aa....aa: Name of the system call or function resulting in the error

bbb: Error code

S: If this message is output during system startup, when pdstop -x is executed, or when pdstop -u is executed, the command is terminated abnormally. If this message is issued as an extension of the pdstop command, the system terminates the command's processing.

Action

If the system call or function cannot be identified by the displayed error code, contact the customer support center.

Name of system call or function resulting in the error | Error code | Cause | Action
System | -1 | Total number of processes being executed exceeded the limit applicable to the system (in UNIX). | Increase the nproc parameter value of the OS.
Maximum number of processes that can be used by a user was exceeded (in UNIX). | Increase the maxuprc parameter value of the OS.
Physical memory shortage occurred. | Check that at least the necessary amount of memory has been allocated. If sufficient memory has been allocated, release unneeded resources.
Other | Other | -- | Contact the customer support center.

--: Not applicable

KFPS05190-E L

Communication error occurred, from host aa....aa to host bb....bb, processing code=ccc

An error occurred during communication from host aa....aa to host bb....bb.

aa....aa: Host name

bb....bb: Host name

ccc: Code being processed (HiRDB internal code)

S: Resumes processing or terminates abnormally, depending on the system status.

Action

If the host defined as the system manager (MGR) is not active, start it and then restart the HiRDB unit.

If a utility special unit is defined, the bb....bb host may not be active. If the host is not active, no error has occurred. Check whether the bb....bb host was active.

If this message is output in the following cases, confirm that the host indicated by bb....bb is operating.
A unit on which the standby-less system switchover (effects distributed) facility is being used terminates normally
A server on which the standby-less system switchover (effects distributed) facility is being used terminates normally
A unit on which the standby-less system switchover (effects distributed) facility is being used terminates forcibly
If the host indicated by bb....bb is not operating, this message can be ignored. If the host indicated by bb....bb is operating, check the server standby status of the unit indicated by bb....bb. If a running server that terminated under the above conditions is the unit indicated by bb....bb and is not in standby status, this message can be ignored. Otherwise, contact the customer support center.

Otherwise, contact the customer support center.

KFPS05191-E L

Communication error occurred, from host aa....aa to host bb....bb, processing code=ccc, reason code=dddd

An error occurred during communication from host aa....aa to host bb....bb.

aa....aa: Host name

bb....bb: Host name

ccc: Code being processed (HiRDB internal code)

dddd: Reason code (HiRDB internal code)

S: Resumes processing or terminates abnormally, depending on the system status.

Action

If the host defined as the system manager (MGR) is not active, start it and then restart the HiRDB unit.

If a network error has occurred, eliminate the cause of the error and restart the HiRDB unit.

Otherwise, contact the customer support center.

KFPS05192-E L

Communication error occurred, from utility to MGR/SDS unit, processing code=aaa

An error occurred during communication from the unit that executed the utility to either the system manager (MGR) or the unit defined as the single server (SDS).

aaa: Code being processed (HiRDB internal code)

S: Resumes processing or terminates abnormally, depending on the system status.

Action

Save the files under %PDDIR%\spool on the system manager unit and the unit that executed the utility, save the event log (in UNIX, syslogfile), and contact the customer support center.

KFPS05193-E E+L

Communication error occurred, to host aa....aa, processing code=bbb, reason code=cccc

An error occurred during communication to host aa....aa.
If the host name is ********, the error occurred during communication to either the system manager or the host defined as the single server.

aa....aa: Host name

bbb: Code being processed (HiRDB internal code)

cc: Reason code (HiRDB internal code)

S: Resumes processing or terminates abnormally, depending on the system status.

Action

Check whether a unit of host aa....aa is inactive. If this is the case, start the corresponding unit. If the corresponding unit is not running in reduced mode, ignore this message.

If this message is output even though the corresponding unit is running, a communication error has occurred. Take corrective action according to 4.1 Detail codes for RPC-related errors.

In cases other than the above, contact the customer support center.

KFPS05194-E L

Communication error occurred, to node MGR, processing code=aaa

Communication in a HiRDB unit failed (the displayed processing code is an HiRDB internal code).

aaa: Code being processed

S: Terminates abnormally.

Action

Save the files under %PDDIR%\spool on the system manager unit and this unit, save the event log (in UNIX, syslogfile), and contact the customer support center.

KFPS05195-E L

Communication error occurred, to node MGR,processing code=aaa, reason code=bbbb

An error occurred during communication to the server machine (MGR) at the HiRDB unit (the displayed reason code and processing code are HiRDB internal codes).

aaa: Code being processed

bbbb: Reason code

S: Terminates abnormally.

Action

Save the files under %PDDIR%\spool on the system manager unit and this unit, save the event log (in UNIX, syslogfile), and contact the customer support center.

KFPS05200-E L

Error occurred in HiRDB system starting process, reason code=aa

HiRDB cannot be started due to an error during HiRDB startup processing.

aa: Reason code:

10: Definition analysis error

20: Communication error

30: Memory shortage

40: Shared memory shortage

S: Terminates abnormally.

Action

Take action appropriate to the reason code. If the error cannot be resolved, save the files under %PDDIR%\spool on the system manager unit, save the event log (in UNIX, syslogfile), and contact the customer support center.

Reason code | Explanation | Action
10 | Definition analysis error. | See the message output immediately before, check whether there is an error in the HiRDB system definition, and correct the error.
20 | A communication error occurred. | See the message output immediately before, check the cause of the communication error, and eliminate it.
30 | An area (memory) shortage occurred. | Execute the startup process after other processes have terminated, or revise the size of the swap area, then re-execute.
40 | A common memory shortage occurred. | Consider whether the estimate of the common memory size is correct. If the estimate is correct, contact the customer support center.

KFPS05201-Q S+L

Dictionary not initialized; enter pdinit command

A dictionary has not been initialized in the HiRDB system. Initialize the dictionary by entering the pdinit command.

S: Waits until initialization of the dictionary by the pdinit -d command is completed.

Action

Enter the pdinit command. When the Windows edition is being used, execute the pdinit command with the Administrator privilege. In this case, root is the executor.

KFPS05202-E L

Insufficient memory on STATIC_SHMPOOL, size=aa....aa

A shared memory allocation error occurred.

aa....aa: Size (in bytes) of the area that was to be allocated

S: Terminates processing.

Action

Save the files under %PDDIR%\spool on the system manager unit, save the event log (in UNIX, syslogfile), and contact the customer support center.

KFPS05203-Q S+L

HiRDB version upped: enter pdvrup command

The system is waiting for the pdvrup command to be entered. Enter the command.

S: Waits for the pdvrup command to be entered.

Action

Enter the pdvrup command.

KFPS05205-E L

Error occurred while starting HiRDB control process, reason code=aa

Because an error occurred while starting the process server process, the system cannot be started.

aa: Reason code:

10: Definition analysis error

20: Communication error

30: Memory shortage

40: Shared memory shortage

S: Terminates abnormally.

Action

Take action appropriate to the reason code. If the error cannot be resolved, save the files under %PDDIR%\spool on the system manager unit, save the event log (in UNIX, syslogfile), and contact the customer support center.

Reason code
Explanation
Action

10
Definition analysis error.
See the message output immediately before, check whether there is an error in the HiRDB system definition, and correct the error.

20
A communication error occurred.
The port number specified in the -a option of the pd_alv_port or pdunit operand might be the same as the port number of another definition or program. If they are the same, change the values in the port number settings so that they are unique, and then restart.
Otherwise, determine the cause of the communication error and eliminate it by referring to the message that was output immediately before this one.

30
An area (memory) shortage occurred.
Execute the startup process after other processes have terminated, or revise the size of the swap area, then re-execute.

40
A common memory shortage occurred.
Consider whether the estimate of the common memory size is correct. If the estimate is correct, contact the customer support center.

KFPS05206-E L

Incompatible character code set for HiRDB unit aaaa, character code set=bb....bb, MGR unit character code set=cc....cc

bb....bb character codes at unit aaaa are incompatible with cc....cc character codes at the MGR unit. Therefore, the HiRDB system cannot be activated.

aaaa: Unit identifier

bb....bb: Character codes used at unit aaaa:

CHINESE: EUC Chinese kanji codes

CHINESE-GB18030: Chinese GB18030 codes

LANG-C: One-byte character codes

SJIS: Shift JIS codes

UJIS: EUC Japanese kanji codes

UTF-8: Unicode(UTF-8)

cc....cc: Character codes used at the MGR unit

S: Terminates abnormally.

Action

Take the following actions:

In UNIX
To unify the character code classifications, execute the pdsetup -d command, respond y at the prompt, and then specify the correct character code classification again using the pdsetup -c command.

In Windows
Unify the character code classifications. To unify the character code classifications, execute the pdntenv -c command.

KFPS05207-E L

Unable to start HiRDB system, some units exist whose version are not equal to that of MGR unit

The HiRDB system cannot be started because some units differ from the unit containing the system manager (MGR) in terms of one or more of the items listed below:

Version

Addressing mode (32-bit mode vs. 64-bit mode)

Load type (whether or not POSIX library version is being used)

S: Abnormally terminates.

P:

Take the following actions:

In UNIX
Based on message KFPS05209-I, set the same version, addressing mode, and load type for all units, and then start HiRDB.

In Windows
Based on message KFPS05209-I, set the same version and addressing mode for all units, and then start HiRDB.

KFPS05208-E L

Unable to start HiRDB system, abnormally terminated units exist

There is a unit that previously terminated abnormally, underwent a planned shutdown, or was terminated forcibly. Therefore, HiRDB cannot be started.

S: Abnormally terminates.

Action

Take the following actions:

In UNIX
Based on message KFPS05209-I, revert the version, addressing mode, and load type of all units (whether or not a POSIX library is used) to the previous version. After terminating normally in the previous version, upgrade HiRDB. For details about how to revert HiRDB to a previous version and how to upgrade HiRDB to a later version, see the HiRDB Version 9 Installation and Design Guide.

In Windows
Based on message KFPS05209-I, revert the version and addressing mode of all units to the previous version. After terminating normally in the previous version, upgrade HiRDB. For details about how to revert HiRDB to a previous version and how to upgrade HiRDB to a later version, see the HiRDB Version 9 Installation and Design Guide.

KFPS05209-I L

HiRDB version information, unit_id=aaaa, bb....bb, cc....cc

Displays information for HiRDB unit aaaa.

aaaa: Unit identifier

bb....bb: HiRDB version information:

version: HiRDB version

addressing mode: HiRDB addressing mode:

32: 32-bit mode

64: 64-bit mode

load: Displays the HiRDB load type. This information is displayed when using the HP-UX version (32-bit mode), the Solaris version, or the AIX version of HiRDB.

POSIX: POSIX library version

NO-POSIX: Non-POSIX library version

cc....cc: HiRDB version information at the previous termination:

stop status: Previous HiRDB termination mode:

A: Planned termination, forced termination, or unit abnormal termination

N: Normal termination

previous operation stop version: HiRDB version at the previous termination (if the status file is being initialized, ******** is displayed)

addressing mode: HiRDB addressing mode at the previous termination:

32: 32-bit mode

64: 64-bit mode

load: Displays the load type from the previous time HiRDB terminated. This information is displayed when using the HP-UX version (32-bit mode), the Solaris version, or the AIX version of HiRDB.

POSIX: POSIX library version

NO-POSIX: Non-POSIX library version

S: Terminates abnormally.

Action

Take corrective action by referring to message KFPS05207-E or KFPS05208-E that was output prior to this message.

In UNIX:

If message KFPS05207-E is output:
Based on message KFPS05207-E, set the version, addressing mode, and load type of all units to be the same, and then start HiRDB.

If message KFPS05208-E is output:
Based on message KFPS05208-E, return the version, addressing mode, and load type of all units to the previous version. After terminating normally in the previous version, upgrade HiRDB. For details about how to return to the previous version and upgrade the version, see the HiRDB Version 9 Installation and Design Guide.

In Windows:

If message KFPS05207-E is output
Based on message KFPS05207-E, set the version and addressing mode of all units to be the same, and then start HiRDB.

If message KFPS05208-E is output
Based on message KFPS05208-E, return the version and addressing mode of all units to the previous version. After terminating normally in the previous version, upgrade HiRDB. For details about how to return to the previous version and upgrade the version, see the HiRDB Version 9 Installation and Design Guide.

KFPS05210-I S+L

HiRDB system initialization process complete

Initialization of the HiRDB system has been completed.

S: Resumes processing.

KFPS05211-I L

Server aa....aa is ready to connect

The front-end server (FES) of a HiRDB/Parallel Server was terminated and then was started again. It is now ready to execute connect.

aa....aa: Server name

S: Resumes processing.

KFPS05212-E L

HiRDB aa....aa option information, unit_id=bbbb, version=cc....cc, previous operation stop version=dd....dd

Displays the version information of option program product aa....aa for HiRDB unit bbbb.

aa....aa: Option program product

Staticizer Option: HiRDB Staticizer Option

Advanced High Availability: HiRDB Advanced High Availability

Non Recover FES: HiRDB Non Recover FES

Disaster Recovery Light Edition: HiRDB Disaster Recovery Light Edition

Accelerator: HiRDB Accelerator

bbbb: Unit identifier

cc....cc: Additional program product version information:

The information is displayed in vv-rr format.

vv: Additional program product version

rr: Additional program product revision

If the version information displayed is 00-00, the additional program product is not included.

dd....dd: Additional program product version information from the previous time the unit terminated:

The information is displayed in vv-rr format.

vv: Additional program product version

rr: Additional program product revision

If the version is displayed as 00-00, it indicates that the option program product was not embedded.

S: Terminates abnormally.

Action

Take corrective action by referring to the message KFPS05207-E or KFPS05208-E that was output prior to this message.

In UNIX:

If the KFPS05207-E message is output:
Based on this message and the KFPS05212-E message, set the version, addressing mode, and load type for all units to be the same, and then start HiRDB.

If the KFPS05208-E message is output:
Based on this message and the KFPS05212-E message, restore the version, addressing mode, and load type for all units to the previous version. After terminating normally in the previous version, upgrade HiRDB.
For details on how to return the version to the previous version and upgrade the version, see the HiRDB Version 9 Installation and Design Guide.

In Windows:

If message KFPS05207-E is output
Refer to that message and to the KFPS05209-I message, set the same version and addressing mode for all units, then start HiRDB.

If message KFPS05208-E is output
Refer to that message and to the KFPS05209-I message, and return the version and addressing mode of all units to the previous version. After terminating normally in the previous version, upgrade HiRDB. For details about how to return values to the previous version and how to upgrade, see the manual HiRDB Version 9 Installation and Design Guide.

KFPS05213-E E+L

Unit aa....aa did not startup

When the system manager unit was starting, the start status of unit aa....aa could not be determined. For this reason, the system manager unit cannot start.

aa....aa: Unit identifier

S: Terminates abnormally.

Action

Take corrective action in the following order:

Check the status of unit aa....aa. The operating status of a unit can be checked with the command pdls -d ust.

Use the pdstop -z command to forcibly terminate the unit, unless the operating status of unit aa....aa is not one of the following:

ONLINE

STOP

PAUSE

In addition, make sure that the operating status of all units is either ONLINE or STOP.

Check for errors in unit aa....aa and take corrective action if an error occurred.

Refer to the syslog or pdlog of unit aa....aa and the system manager unit, investigate the cause of the error from the error messages, and then take corrective action.

If no error messages were output, investigate whether a network error occurred between the system manager unit and unit aa....aa, and if so take corrective action.

After taking corrective action, make sure that the operating status of all units is ONLINE or STOP, and then restart the system with the pdstart command.
Note that when unit aa....aa is one of the following units, it is not necessary to start the unit:

A unit for which reduced activation is specified

A recovery-unnecessary FES unit

A unit using standby-less system switchover (effects distributed)

KFPS05214-W E+L

Fall-back operation ignored, because of aa....aa

The HiRDB system cannot perform reduced activation. Ignores the reduced activation mode.

aa....aa: Reason code

HiRDB version upped: HiRDB has been upgraded.

dictionary not initialized: The dictionary is not yet initialized.

S: Resumes processing.

Action

If there are no units that cannot be started, no processing is required.

When upgrading HiRDB or initializing the dictionary, start all the units that make up the system.

KFPS05215-W L

HiRDB unit aaaa definition error, reason code=b

An error was detected in the unit definition.

aaaa: Unit identifier

b: Error code:

1: System ID is invalid.

2: Host name is invalid.

3: Unit identifier is invalid.

4: Required server is not defined.

5: Unnecessary server is defined.

9: Other error

S: Resumes processing.

Action

If the error code is 1 to 5, check the unit definition according to the displayed code and re-execute the unit. If the error code is 9, contact the customer support center.

KFPS05216-I E+L

Valid option for HiRDB system fall-back operation

The option for the reduced activation of the HiRDB system is specified.

S: Resumes processing.

KFPS05217-I E+L

Unit aa....aa did not startup; switches to fall-back operation

Because a unit was not started during HiRDB system activation, HiRDB is in reduced-startup mode.

aa....aa: Unit identifier

S: Resumes processing.

Action

Check the reason that the HiRDB unit did not start. After taking corrective action, clear the reduced status by starting the HiRDB unit.

KFPS05218-I E+L

All unit initialization completed; switches to normal operation

All HiRDB units have been started. The reduced status is cleared and normal operation resumes.

S: Resumes processing.

KFPS05219-I L

HiRDB initialization process complete; only for pdrstr and pdcopy

HiRDB startup by pdstart -r has been completed. Only pdrstr can be executed in this mode.

S: Resumes processing.

KFPS05220-I L

HiRDB system termination process started. mode=aa....aa

HiRDB system termination processing has begun.

aa....aa: Termination mode:

FORCE: Forced termination

NORMAL: Normal termination

PLAN: Planned termination

S: Resumes processing.

KFPS05221-E L

Error occurred in HiRDB system termination process. mode=aa....aa

An error occurred during HiRDB system termination processing.
If the termination mode is PLAN, or if Real Time SAN Replication is used for a log application site that is terminating with a termination mode of NORMAL, all units other than the system manager are terminated forcibly.

aa....aa: Termination mode:

NORMAL: Normal termination

PLAN: Planned termination

FORCE: Forced termination

S: Terminates abnormally.

Action

A termination error or communication error may have occurred at a unit other than the system manager unit. Check the messages output before this message, correct the error, then restart the system.

(Planned termination or normal termination of a log application site when Real Time SAN Replication is used)

Check that all units have terminated, then restart the system.

If there is an active unit, terminate it either by entering the pdstop -f command from the system manager unit or by logging directly into the unit and entering the pdstop -z command, then restart the system.

The method for determining termination status is to refer to each unit's event log (in UNIX, syslogfile); if any of the following messages is output, the unit is terminated:

KFPS01821-E message

System manager unit: KFPS01850-I message (termination-mode=FORCE)

For a unit that is not a system manager: KFPS01841-I message (termination-mode=FORCE)

If the cause is unknown, collect the files under %PDDIR%\spool on the system manager unit, collect the event log (in UNIX, syslogfile), and contact the customer support center.

KFPS05222-E L

Unable to terminate HiRDB unit aaaa due to communication error

Unit aaaa cannot be terminated due to a communication error.

aaaa: Unit identifier

S: Resumes processing.

Action

Use one of the following methods to terminate the unit:

From the unit containing the system manager, use the pdstop -x command to specify the appropriate host name

From the unit containing the system manager, use the pdstop -u command to specify the appropriate unit identifier

Log on directly to the appropriate unit and execute the pdstop -z command

If the HiRDB unit cannot be terminated by this command, contact the customer support center.

KFPS05223-I L

HiRDB unit aaaa inactive,status=bb

The status of HiRDB unit aaaa is bb.

aaaa: Unit identifier

bb: Status code:

10: Being started

15: Being started

16: Ready for database to be initialized with pdinit command

20: Unit startup completed

21: Front-end server startup completed

25: Being terminated

30: Terminated normally

31: Terminated forcibly

32: Terminated abnormally

33: Planned termination

40: Database is being shut down

S: Resumes processing.

Action

If the HiRDB unit cannot be terminated normally by the pdstop command, the system displays the cause and the unit status. To terminate the HiRDB unit when it cannot be terminated normally, enter the pdstop -f command.

If the pdrisedbto command terminates with an error or a warning, the status of the unit that caused the error is displayed. If there is an error, and if the pdrisedbto command is to be re-executed, use pdls -d svr to check the status of the unit, and then restart the stopped unit.

KFPS05224-E L

Error occurred while terminating MGR unit

An error occurred while terminating the unit where the system manager (MGR) is located.

S: Terminates abnormally.

Action

Collect the files under %PDDIR%\spool on the system manager unit, collect the event log (in UNIX, syslogfile), and contact the customer support center.

KFPS05225-E L

Error occurred while terminate HiRDB control process

An error occurred during termination processing of the process server process.
S: Terminates abnormally.

Action

Collect the files under %PDDIR%\spool on the system manager unit, collect the event log (in UNIX, syslogfile), and contact the customer support center.

KFPS05226-E L

Unable to terminate HiRDB server aa....aa

Server with server name aa....aa cannot be terminated.

aa....aa: Server name

S: Terminates processing.

Action

See the KFPS05180-E message and take appropriate action.

KFPS05227-W L

Now waiting for termination of HiRDB unit aaaa

The system is waiting for completion of termination processing at HiRDB unit aaaa.

aaaa: Unit identifier

S: Resumes processing.

Action

If the same message has been issued more than once with the same unit identifier, it may be taking a long time to terminate the unit for some reason or the unit may have terminated abnormally. Check the messages output before this message to determine the status of the HiRDB system.

Unit terminated abnormally:
Enter the pdstop -f command to forcibly terminate the HiRDB system.

Unit is taking a long time to terminate:
The following are possible reasons:
Transaction recovery processing is under way.
Communication error occurred.

KFPS05230-E S

Unable to stop aaaa normally because bbbb being cccc

Normal, planned, or forced termination could not be executed for aaaa because bbbb is engaged in cccc processing.

aaaa: Type of entity

{ HiRDB|unit|server }

bbbb: Type of entity

{ HiRDB|unit|server }

cccc: Processing:

started: Startup

terminated: Termination

S: Resumes processing.

O: Re-execute the pdstop command after bbbb startup or termination processing is completed. Or, terminate aaaa forcibly with the pdstop -f command. For HiRDB/Parallel Servers, forced termination cannot be executed using the pdstop -f -x host-name command or the pdstop -f -u unit-identifier command.

KFPS05231-E S

Unable to stop server due to server is inactive

The server cannot be stopped because it is inactive.

S: Resumes processing.

KFPS05232-E S

Unable to stop unit due to unit is inactive

The unit cannot be stopped because it is inactive or is already stopped.

S: Resumes processing.

KFPS05233-E S

Unable to stop HiRDB system normally due to user identifier remained

The HiRDB system cannot be terminated normally because a UAP or utility is executing or a transaction has not terminated.

S: Terminates processing.

O: Re-execute the pdstop command after the UAP or utility has terminated or the transaction has terminated.

To check the user causing this error, display user information by entering the pdls -d act command. Next, identify the user or transaction causing the error by checking the information displayed by the pdls -d prc or pdls -d trn command on the basis of the displayed user identification sequence number and process ID. If there is no applicable user or transaction, wait a while, then re-execute the command.

KFPS05234-E S

Unable to stop unit due to user identifier remained

The HiRDB unit cannot be terminated normally because a UAP or utility is executing or a transaction has not terminated.

S: Terminates processing.

O: Re-execute the pdstop command after the UAP or utility has terminated or the transaction has terminated.

To check the user causing this error, display user information by entering the pdls -d act command. Next, identify the user or transaction causing the error by checking the information displayed by the pdls -d prc or pdls -d trn command on the basis of the displayed user identification sequence number and process ID. If there is no applicable user or transaction, wait a while, then re-execute the command.

KFPS05235-E S

Unable to stop server due to user identifier remained

The HiRDB server cannot be terminated normally because a UAP or utility is executing or a transaction has not terminated.

S: Terminates processing.

O: Re-execute the pdstop command after the UAP or utility has terminated or the transaction has terminated.

To check the user causing this error, display user information by entering the pdls -d act command. Next, identify the user or transaction causing the error by checking the information displayed by the pdls -d prc or pdls -d trn command on the basis of the displayed user identification sequence number and process ID. If there is no applicable user or transaction, wait a while, then re-execute the command.

KFPS05236-E L+S

Unable to stop HiRDB system normally, because unit aaaa stop failed

The system was unable to perform a normal termination or a planned termination of HiRDB because termination processing of unit aaaa failed.

aaaa: Identifier of unit for which termination processing failed

S: Continues processing.

Action

Determine why termination processing of unit aaaa failed. Unit aaaa may be running. Execute the ps command to determine whether any HiRDB processes are executing, and if necessary use the pdstop -z command to forcibly terminate unit aaaa.

KFPS05237-E L

Unable to stop unit aaaa by force, reason code=bb....bb

The aa....aa unit cannot be forcibly terminated because of bb....bb.

aaaa: Unit identifier of the unit that could not be forcibly terminated.

bb....bb: Reason why termination was not possible

NOT RECOVERY:

The unit was not the HiRDB that was started by executing the pdstart -r command.

S: Continues processing.

Action

When you forcibly terminate non-MGR units that were started using the pdstart command without the -r option specified, execute the pdstop -z command in the unit to be forcibly terminated.

KFPS05240-E E+L

Pdrplstart command failed. reason=aa....aa

Error occurred while executing the pdrplstart command.

aa....aa: Character string indicating the type of error

SYSTEM INCOMPLETE:

System startup is not complete.

ANY UNIT INACTIVE:

The status of one or more units is inactive.

ANY BES INACTIVE:

The status of one or more back-end servers is inactive.

UTL UNIT: The system is unable to run on the UTL unit.

STARTED:

HiRDB Datareplicator linkage is already running.

PD_RPL_HDEPATH:

HiRDB Datareplicator linkage cannot run in the current environment.

TIMEOUT:

An execution time-out occurred.

STATUS WRITE ERROR:

Writing of the status file failed.

STOPPING NOW:

HiRDB Datareplicator linkage is being stopped.

EXTRACT STOPPED:

HiRDB Datareplicator extraction processing was interrupted.

S: Terminates processing.

Action

Take action appropriate to the type of error. If the displayed information is none of the character strings shown above, contact the customer support center.

Error indicator character string | Explanation | Action
SYSTEM INCOMPLETE | System startup was not completed. | Re-execute the command after system startup has been completed.
ANY UNIT INACTIVE | Some units were not on ACTIVE status. | Restart all inactive units and re-execute the command.
ANY BES INACTIVE | Some back-end servers were not on ACTIVE status. | Restart all inactive back-end servers and re-execute the command.
UTL UNIT | Requested processing cannot be executed at the UTL unit. | --
STARTED | HiRDB Datareplicator linkage was already executing. | --
PD_RPL_HDEPATH | HiRDB Datareplicator linkage cannot be executed in this environment. | Specify the pd_rpl_hdepath operand in the unit control information definition, restart HiRDB, then re-execute the command.
TIMEOUT | Execution timeout occurred. | Re-execute the command.
STATUS WRITE ERROR | Write error occurred in the status file. | Check that the pd_rpl_hdepath operand is specified correctly in the system common definition. Or, check that there is a file for data linkage.
STOPPING NOW | HiRDB Datareplicator linkage was terminating. | Re-execute the command after HiRDB Datareplicator linkage has terminated at all units.
EXTRACT STOPPED | Data extraction processing by HiRDB Datareplicator was cancelled. | Initialize the file for data linkage and re-execute the command.

--: Not applicable

KFPS05241-E E+L

Pdrplstop command failed, reason=aa....aa

An error occurred while the pdrplstop command was executing.

aa....aa: Error type

S: Terminates processing.

Action

Re-execute the pdrplstop command after taking one of the following actions. Contact the customer support center if an error type not described in the manual is output.

Error type
Error description
Action

UTL UNIT
Cannot be executed by a utility special unit.
The pdrplstop command cannot be executed on a utility special unit.

STOPPED
Replication with HiRDB Datareplicator already stopped.
The pdrplstop command cannot be executed because replication with HiRDB Datareplicator already stopped.

PD_RPL_HDEPATH
The pd_rpl_hdepath operand was not specified.
Specify the pd_rpl_hdepath operand. After starting the HiRDB system, re-execute the pdrplstop command.

TIMEOUT
Execution time was exceeded.
Re-execute the pdrplstop command.

STATUS WRITE
ERROR
An attempt to write the status file failed.
Check if the specification of the pd_rpl_hdepath operand is correct, and then re-execute the pdrplstop command. Alternatively, after checking that data linkage files exist, re-execute the pdrplstop command.

ANY UNIT
INACTIVE
There are inactive units.
Start inactive units, and then re-execute the pdrplstop command.

ANY BES
INACTIVE
There are inactive back-end servers.
Start inactive back-end servers, and then re-execute the pdrplstop command.

EXTRACTING
STATUS
Extraction processing of HiRDB Datareplicator is not complete.
See the KFPS05243-W message output before this message, and then take appropriate action.

FILE LOCK
ERROR
A reference privilege or update privilege could not be acquired for a data linkage file used by HiRDB Datareplicator.

FILE OPEN ERROR
A data linkage file used by HiRDB Datareplicator could not be opened.

COMMUNICATION
An inter-process communication error occurred.
Check for the cause of the network error on the unit where the communication error occurred.

BUSY
The command could not be executed because the service request destination server was processing.
See the KFPS05244-W message output immediately before this message, and then take appropriate action.

KFPS05242-I E+L

Accepted data replication stop request

HiRDB Datareplicator linkage termination request has been accepted.

S: Resumes processing.

KFPS05243-W E+L

Unable to stop data replication,server=aa....aa,reason=bb....bb

Data replication with HiRDB Datareplicator could not be stopped.

aa....aa: Server name

bb....bb: Reason code

S: Continues processing.

Action

Re-execute the pdrplstop command after taking the appropriate actions.

Reason code
Error description
Action

EXTRACTING
STATUS
Extraction processing by HiRDB Datareplicator is not complete.
Check all of the following items, and then re-execute the pdrplstop command:

Check if the hdestate command of HiRDB Datareplicator started the extraction process. If the extraction process is not running, start the extraction process, and then check item 2.

Check if extraction processing by HiRDB Datareplicator is complete. Extraction processing is complete if the following conditions are all met:

No transactions are active
Execute the pdls -d trn command to check for active transactions.

The system block number being extracted is the last block number of the current file
Execute the pdls -d rpl -j command to check the system log block number being extracted. Also, execute the pdlogls -d sys command to check the last block number of the current file.

BES INACTIVE
Inactive back-end server(s) found.
Start the inactive back-end server(s), and then re-execute the pdrplstop command.

FILE LOCK
ERROR
A reference privilege or update privilege could not be acquired for a data linkage file used by HiRDB Datareplicator.
HiRDB Datareplicator has exclusive ownership of the data linkage file. Investigate the cause, and then re-execute the pdrplstop command.

FILE OPEN ERROR
A data linkage file used by HiRDB Datareplicator.
Either the data linkage file has been deleted or it could not be opened due to a disk error. Synchronize to the target database, re-create the data linkage file, and then restart HiRDB Datareplicator and HiRDB.

KFPS05244-W E+L

Unable to stop data replication,unit=aaaa,reason=bb....bb

Data replication with HiRDB Datareplicator could not be stopped.

aaaa: Unit identifier

bb....bb: Reason code

S: Terminates processing.

Action

Take action according to the following table, and then re-execute the pdrplstop command.

Reason code | Error description | Action
UNIT INACTIVE | There are inactive units. | Start inactive units, and then re-execute the pdrplstop command.
COMMUNICATION | An inter-process communication error occurred. | Check for the cause of the network error on the unit where the communication error occurred.
PD_RPL_HDEPATH | The pd_rpl_hdepath operand was not specified. | Specify the pd_rpl_hdepath operand.
BUSY | The command could not be executed because the service request destination server is processing. | Re-execute the pdrplstop command.

KFPS05245-W E+L

Unit stopped for fall-back operation exists. Do not create target database from stopped unit,unit=aaaa

Some units were not started because of reduced activation. Do not re-create the target database based on the database of a unit that was not started because of reduced activation.

aaaa: Unit identifier

S: Continues processing.

KFPS05246-E L

Unable to start HiRDB system, because pd_rpl_hdepath not matched between units

HiRDB cannot be started, because aa....aa does not match between units.

aa....aa: Information that does not match between units

pd_rpl_hdepath: HiRDB Datareplicator working directory

start option: HiRDB startup mode

S: Terminates abnormally.

Action

aa....aa is pd_rpl_hdepath
Refer to the KFPS05247-E message, and match the value of the pd_rpl_hdepath operand of the unit using the standby-less system switchover (effects distributed) facility. Then, start HiRDB.

aa....aa is start option
If Real Time SAN Replication with the log-only synchronous method is used, depending on the site status of each site, match either the pdstart command or the pdstart -l command.

KFPS05247-E L

HiRDB unit information, unit_id = aaaa, bb....bb

Information on unit aaaa is displayed.

aaaa: Unit identifier

bb....bb: Unit information

pd_rpl_hdepath:

Value of the pd_rpl_hdepath operand (name of the HiRDB Datareplicator directory where data is extracted)

If this operand is omitted, (null) is displayed.

start option:dd....dd

dd....dd: Unit start status

"primary": Execution

"standby": Log application

S: Abnormally terminates.

Action

"pd_rpl_hdepath" is displayed

Set the value of the pd_rpl_hdepath operand to the same value for the units using the standby-less system switchover (effects distributed) facility. Then, start HiRDB.

"start option" is displayed

Make sure that the startup mode is the same for all units where Real Time SAN Replication with the log-only synchronous method is used.

KFPS05248-E L

Unable to start unit aaaa due to pd_ha_agent operand invalid

HiRDB cannot be started because the pd_ha_agent operand of unit aaaa is invalid. The value of the pd_ha_agent operand of unit aaaa may have been changed from the standby-less system switchover (effects distributed) facility to another system switchover facility.

aaaa: Unit identifier

S: Terminates processing.

Action

Check the value of the pd_ha_agent operand of unit aaaa. If the unit is using the standby-less system switchover (effects distributed) facility and the server abnormally terminated, the value of the pd_ha_agent operand cannot be changed. Specify activeunits in the pd_ha_agent operand, and start HiRDB.

KFPS05249-E L

aa....aa invalid; stops unit startup, unit_id = bbbb

During restart processing of unit bbbb, the contents of aa....aa did not match that for normal startup.

aa....aa: Error cause

pdhagroup: pdhagroup operand

bbbb: Unit identifier

S: Abnormally terminates.

Action

Check the value of the pdhagroup operand. If the system manager unit did not terminate normally, the pdhagroup operand cannot be changed. Return it to normal startup status, and start HiRDB.

KFPS05250-I L

Pdvrup command will be executed automatically

The pdvrup command will be activated automatically.

S: Continues processing.

KFPS05251-W L

Waiting for server start, server = aa....aa

The system is waiting for the server to start.

aa....aa: Name of the server that is waiting to start

S: Continues processing.

Action

On the standby-less system switchover (effects distributed) target unit, use the cluster software commands#¹ to check the status of the server indicated in the message.

If the server is not displayed for any unit:

Select the unit to start the running system server, and activate#² the server as the running system server.

If the server is waiting to be activated as the running server:

Activate#² the server as the running system server.

If there is a unit activating the running system server:

The wait is released as the server is activated. Nothing in particular is required.

If none of this is applicable, contact the customer support center.

#1: If the cluster software is HA monitor, enter the monshow command; if it is Hitachi HA Toolkit Extension, enter the hateshow command.

#2: If the cluster software is HA monitor, enter the monact command; if it is Hitachi HA Toolkit Extension, enter the command to activate the upper-level cluster software package (such as MC/ServiceGuard).

KFPS05260-I L+S

HiRDB system initialization process complete on standby site

Startup processing on the log application site HiRDB has finished.

S: Continues processing.

KFPS05261-W L

Database take over skipped, unit_id=aaaa, server=bb....bb

Database inheritance was skipped.

aaaa: Unit identifier

bb....bb: Server name

S: Continues processing.

Action

If switchover to a transaction execution site occurs when database inheritance was skipped, the data cannot be guaranteed on the server that output the message. Refer to the section on site switchover in the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide, and take the actions necessary to perform site switchover.

KFPS05262-E L

Error occurred in HiRDB unit aaaa database take over process, reason code=bb....bb

An error occurred during database inheritance. All units were terminated forcibly.

aaaa: Unit identifier

bb....bb: Error code

COMMUNICATION: Error in communication with another unit

STOP(A): STOP(A) Notification

INTERNAL ERROR: Internal processing error

S: Terminates abnormally.

Action

Ensure that all units have terminated, and then check the message that was output before this message. Eliminate the cause of the error, and then start the log application site HiRDB.

If there are still units that have not terminated, either execute the pdstop -f command from the system manager unit or execute the pdstop -z command from the units that have not terminated. After all units have terminated, start the log application site HiRDB.

The method for determining running status is to check each unit's event log (in UNIX, syslogfile). If any of the following messages is output, the unit is terminated:

KFPS01821-E message

System manager unit: KFPS01850-I (termination-mode="FORCE") message

Other than the system manager unit: KFPS01841-I (termination-mode="FORCE") message

If the cause cannot be determined, save the files under $PDDIR/spool for this unit, save the event log (in UNIX, syslogfile), and contact the customer support center.

KFPS05263-W L

Necessary to prepare for applying system log, reason=aa....aa

On the transaction execution site, aa....aa was executed. When aa....aa is executed, the following results might occur on the log application site:

The log application site fails to respond.

The log application site units shut down.

When a site switchover to the log application site is performed, data may be lost.

aa....aa: Operation performed on the transaction execution site

pdinit: Database initialization utility

pdstart dbdestroy: HiRDB forcible startup

pdvrup: HiRDB version upgrade

S: Continues processing.

Action

Refer to the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide, and perform preparation for log application.

KFPS05270-I L

Pd_system_expand_unit specified in system configuration

The pd_system_expand_unit operand is specified in the HiRDB system definition.
This is the system that has the expansion unit.

S: Continues processing.

KFPS05273-I L

HiRDB expand unit aaaa initialization process complete

Start processing for expansion unit aaaa is finished.

aaaa: Unit identifier

S: Continues processing.

KFPS05274-I L

HiRDB expand unit aaaa termination process complete

Termination processing for expansion unit aaaa is finished.

aaaa: Unit identifier

S: Continues processing.

KFPS05275-W L

Error occurred in status file while bb....bb expand unit status, unit_id=aaaa

An error was detected while the status of expansion unit aaaa was being read from the status file or written to the status file.

aaaa: Unit identifier

bb....bb: Processing classification (content of processing to the status file)

reading: Reading of the status file

writing: Writing of the status file

S: Continues processing.

Action

Follow the error message that was output before this error message to eliminate the cause of the error.

KFPS05276-E L

Error occurred in status file while aa....aa expand unit status

An error was detected while the status of the expansion unit was being read from the status file or written to the status file.

aa....aa: Processing classification (content of processing to the status file)

reading: Reading of the status file

writing: Writing of the status file

S: Terminates abnormally.

Action

Follow the error message that was output before this error message to eliminate the cause of the error.

KFPS05288-I L

HiRDB unit aaaa status change to ACTIVE

Because the running status of STOP(A) unit aaaa has been confirmed, the status of the unit is changed to ACTIVE.

aaaa: Unit name

S: Resumes processing.

KFPS05289-E L

HiRDB unit aaaa status change to STOP(A)

Communication with unit aaaa or data reception from unit aaaa failed. Or, a status in which the client cannot connect to unit aaaa was detected. The status of unit aaaa is changed to STOP(A).

aaaa: Unit name

S: Resumes processing.

Action

Execute the ps command on unit aaaa to determine whether the process is active.

If the HiRDB process is active, a communication error or a service slowdown in unit aaaa may have occurred. Check the cause of the error based on the message output before this message, stop the unit by entering pdstop -z, then restart the unit.

While the HiRDB process is inactive, either a system switchover or abnormal termination could have occurred. If abnormal termination occurred, take action according to the message that was output. To restart the HiRDB process, execute either the pdstart -x or pdstart -u command.

KFPS05290-E L

Communication error occurred, from host aa....aa to host bb....bb, processing code=ccc

An error occurred during communication from host aa....aa to host bb....bb.

aa....aa: Host name

bb....bb: Host name

ccc: Code being processed (HiRDB internal code)

S: Resumes processing or terminates abnormally, depending on the status.

Action

If this message is issued during HiRDB startup, a HiRDB unit other than the system manager (MGR) may not be active. Start the applicable HiRDB unit.

If action 1 does not apply, take corrective action according to the description in Table 4-1 Frequently occurring causes and required action for RPC-related errors.

Otherwise, contact the customer support center.

KFPS05291-E L

Communication error occurred,to host=aa....aa processing code=bbb reason code=ccc

An error occurred during communication to host aa....aa.

aa....aa: Host name

bbb: Code being processed (HiRDB internal code)

cccc: Reason code (HiRDB internal code)

S: Resumes processing or terminates abnormally, depending on the status.

Action

Check whether a unit of host aa....aa is inactive. If so, start the corresponding unit. If the corresponding unit is not running in reduced mode, ignore this message.

If this message is output even though the corresponding unit is running, a communication error has occurred. Take corrective action according to 4.1 Detail codes for RPC-related errors.

In cases other than the above, contact the customer support center.

KFPS05292-I L

Unit aaaa inactive

Unit aaaa is not on normal active status.

aaaa: Unit identifier

S: Terminates processing.

Action

Take action appropriate to the unit status.

KFPS05293-E E

Unable to access shared memory

Shared memory cannot be accessed during execution of the pdls command.

S: Terminates processing.

Action

Start the corresponding host and enter the pdls command.

KFPS05294-E L

Unable to stop normally HiRDB system due to auto audit trail loading service is operating

The facility for automatically loading audit trail table data was enabled when the pdaudatld -b command was executed during termination processing. As a result, the HiRDB system cannot terminate normally.

S: Terminates processing.

O: Re-execute the pdstop command.

Action

Do not execute the pdaudatld command during termination processing.

KFPS05300-I E+L

Now preparing for statistics log service. run ID=aaaaaaaa

Preparation is underway for the statistics log service function.

aaaaaaaa: Run ID

S: Resumes processing.

KFPS05303-E E+L

Unable to start statistics log service. reason code=aaaa

The statistics log service function cannot be started for the displayed reason (aaaa).

aaaa: Reason code:

101: Memory shortage

103: Communication error

401: Undefined error

405: Definition error

514: til start failure

S: Terminates processing.

O: Contact the HiRDB administrator, take action appropriate to the reason code, then restart the HiRDB system.

Action

Take action appropriate to the reason code.

KFPS05304-I L

Specified pd_stj_file_size is too small; sets pd_stj_file_size at 1024 and continues processing

The value of the pd_stj_file_size operand was too small, so it was rounded up to 1024 KB and processing continues.
The value of the pd_stj_file_size operand must satisfy the following condition:
pd_stj_file_size pd_stj_buff_size 2

S: Continues processing.

Action

Once HiRDB has terminated, change the pd_stj_file_size operand value.

KFPS05308-W E+L

Error occurred while terminating statistics log service; continues processing. reason code=aaaa

An error occurred while terminating the statistics log service function, but processing continues.

aaaa: Reason code:

103: Communication error

S: Resumes processing.

KFPS05321-E E+L

Insufficient memory. required memory size=aa....aa, area type=bb....bb

A memory shortage occurred. The message displays the size and type of the memory that was to be allocated.

aa....aa: Size of memory that was to be allocated

bb....bb: Type of memory:

STATIC_SHMPOOL: Static shared memory

S: Terminates processing.

O: Contact the HiRDB administrator, take appropriate action, then restart the HiRDB system.

Action

Increase the shared memory available to the system.

KFPS05350-E E+L

Failure to open statistics log file. file name=aa....aa, reason code=bbbb-cc

Statistics log file open processing failed.

aa....aa: Name of the statistics log file

bbbb: Reason code:

303: Open system call error

cc: HiRDB internal code

S: Terminates processing.

O: Contact the HiRDB administrator, eliminate the cause of the error, then re-execute.

Action

Determine the cause of the error from the preceding KFPO00107-E message and take appropriate action.

KFPS05351-W E+L

Failure to close statistics log file. file name=aa....aa, reason code=bbbb-cc

Statistics log file close processing failed.
aa....aa: Name of the statistics log file

bbbb: Reason code:

304: Close system call error

cc: HiRDB internal code

S: Resumes processing.

O: Contact the HiRDB administrator and eliminate the cause of the error.

Action

Eliminate the cause of the error indicated by the reason code.

KFPS05352-W E+L

Failure to write statistics log file. fime name=aa....aa, reason code=bbbb-cc

Output to a statistics log file failed.

aa....aa: Name of the statistics log file

bbbb: Reason code:

305: Write system call error

cc: HiRDB internal code

S: Resumes processing.

O: Contact the HiRDB administrator and eliminate the cause of the error.

Action

Determine the cause of the error from the preceding KFPO00107-E message and take appropriate action.

KFPS05353-E E+L

Error occurred while handling statistics log file. file name=aa....aa, reason code=bbbb-cc

An error occurred while handling a statistics log file.

aa....aa: Name of the statistics log file

bbbb: Reason code:

103: Communication error

cc: HiRDB internal code

S: Terminates processing.

Action

Eliminate the cause of the error indicated by the reason code.

KFPS05354-E E+L

Error occurred while handling statistics log file. reason code= aa....aa - bb....bb

An error occurred while handling a statistics log file.

aa....aa: Reason code:

101: Memory shortage

103: Communication error

105: Timeout (communication)

If the reason code is 101 or 103, information in the statistics log buffer is not output to the statistics log file. If the reason code is 105, the information might be output.

bb....bb: HiRDB internal code

S: Continues processing.

If this message is output during execution of the pdstjsync command, the pdstjsync command outputs message KFPS05840-I and terminates normally.

O: Contact the HiRDB administrator to eliminate the cause of the error.

Note that when this message is output, statistics from around the time the message was output will not be included in the statistics to be edited by the statistics analysis utility (pdstedit).

Action

Eliminate the cause of the error indicated by the reason code.

KFPS05355-I E+L

Statistics log file swapped. from=aa....aa, to=bb....bb, unit ID=cccc

Statistics log files were swapped.

aa....aa: Name of the old file (before swapping)

bb....bb: Name of the new file (after swapping)

cccc: Unit identifier

S: Resumes processing.

KFPS05360-W L

Cancels statistics output. unit ID=aaaa

Unit aa....aa has stopped collecting statistical information.
An error message concerning the statistics log file has been output immediately before this message; see that message for the cause of the error.

aaaa: Unit identifier

S: Terminates processing.

Statistical information that was in the buffer when this message was output and that was to be written into the statistics log file has been discarded.

Action

If the statistical information is not needed for the unit displayed in the message, operation can be continued. If the statistical information is needed, terminate the applicable unit, eliminate the immediate cause of the error indicated by the message output immediately before this message. Then, execute the pdstjswap command for the unit or restart the unit and resume collection of statistical information.

KFPS05361-W L

Already canceled statistics output. unit ID=aaaa

Output of statistical information for unit aaaa has already been terminated due to a previous error.

aaaa: Unit identifier

S: Resumes processing.

Statistical information that was in the buffer when this message was output and that was to be written into the statistics log file has been discarded.

Action

If the statistical information is not needed for the displayed unit, operation can be continued. If the statistical information is needed, terminate the corresponding unit, eliminate the cause of the error indicated by the message output immediately before this message, restart the unit, then restart collection of statistical information.

KFPS05362-W L

Unable to cancel statistics output. unit ID=aaaa

Statistical information collection cannot be stopped for unit aaaa.
An error message concerning the statistics log file has been output immediately before this message; see that message for the cause of the error.

aaaa: Unit identifier

S: Resumes processing.

Statistical information that was in the buffer when this message was output and that was to be written into the statistics log file has been discarded.

Action

Enter the pdstend command to terminate collection of statistical information. If the statistical information is not needed for the displayed unit, operation can be continued. If the statistical information is needed, terminate the corresponding unit, eliminate the cause of the error indicated by the message that was output immediately before this message, restart the unit, then restart collection of statistical information.

KFPS05370-I E

Usage:pdstjswap [-x host_name| -u unit_id]

Displays the format of the pdstjswap command.

S: Continues processing.

KFPS05372-E E

One of aa....aa option must be specified.

One of the indicated options must be specified.

aa....aa: Options

S: Terminates processing.

O: Specify an option and re-execute the command.

KFPS05373-E E

Unable to execute command due to failure of aa....aa system call (command), code= bb....bb

Command cannot be executed because of an error in system call (or command) aa....aa.

aa....aa: System call or command in which the error occurred

{exec|fork|rsh|tempnam|open}

bb....bb: Internal code for the return value of the system call or rsh

If tempnam or open is output in aa....aa, the errno value is output.

S: Terminates processing.

O: Contact the administrator, take corrective action, and then re-execute the command.

Action

In UNIX:

If tempnam or open is output in aa....aa, refer to errno.h or the applicable OS manual to eliminate the cause of the error based on the errno value, and then re-execute the command once recovery from the error is complete. The cause of the error is in the directory specified in the environment variable TMPDIR (if the environment variable TMPDIR is not specified, the cause of the error is in the directory $PDDIR/tmp), or in a file that begins with the prefix psjcm in that directory. For typical errno examples, see 4.3 System call return codes.

If exec, fork, or rsh is output in aa....aa, determine the cause of the error and take corrective action based on message KFPO00107-E, which was output immediately before this one.

In Windows:

If tempnam or open is output in aa....aa, check the mnemonic in the OS's errno definition file or refer to the applicable OS manual to eliminate the cause of the error based on the errno value, and then re-execute the command once recovery from the error is complete. The cause of the error is in the directory specified in the environment variable TMP or TEMP (if environment variables TMP and TEMP are not specified, the cause of the error is in the directory %PDDIR%\tmp), or in a file that begins with the prefix psjcm in that directory. For typical errno examples, see 4.3 System call return codes.

If exec, fork, or rsh is output in aa....aa, determine the cause of the error and take corrective action based on message KFPO00107-E, which was output immediately before this one.

KFPS05374-E E

Specified hostname invalid in "pdstart" operand

The host name specified in the pdstart operand in the system definition is invalid.

S: Terminates processing.

O: Correct the host name specified in the pdstart operand in the system definition.

KFPS05375-E E

Hostname must be equal to SDS hostname for single server.

For a HiRDB/Single Server, the host name that is specified must be the host name of the single server. Because there is only one single server host for a HiRDB/Single Server, the specification may be omitted. This message is output when a host name is specified but that name is invalid.

S: Terminates processing.

O: Omit the host name or specify the correct host name, and then re-execute the command.

KFPS05381-E E

Insufficient memory

A memory shortage occurred.

S: Terminates processing.

O: Re-examine the number of processes, take appropriate action, and re-execute.

KFPS05393-E E

Communication error occurred. info=aa....aa

A communication error occurred during command execution.

aa....aa: Maintenance information

S: Terminates processing.

O: Eliminate the cause of the communication error, then re-execute the command.

Action

If a message that shows the cause of the communication error was output immediately before this message, take the action indicated in the message to eliminate the cause of the communication error. If no message that displays the cause of the communication error was output, save the maintenance information and contact the customer support center.

KFPS05394-E E

Unit state not online. info=aa....aa

The unit is not online.

aa....aa: Maintenance information

S: Terminates processing.

O: If the unit is not running, start the unit and re-execute the command.

Action

If this message is output, even though the unit is running, save the maintenance information and contact the customer support center.

KFPS05395-E E

Statistics log service is inactive. info=aa....aa

The statistics log is not being acquired for this unit.

aa....aa: Maintenance information

S: Terminates processing.

O: Start acquisition of the statistics log and re-execute the command.

Action

If this message is output, even though the statistics log is being acquired for this unit, save the maintenance information and contact the customer support center.

KFPS05396-W E

Statistics log file not deleted.

Swap processing of the statistics log file has terminated, but the statistics log file could not be deleted. Consider the following causes:

There was an attempt to delete the statistics log file that is currently being output

The statistics log file to be deleted is being used by another program or command

S: Continues processing.

O:

If the statistics log file was deleted, subsequent swapping of the statistics log file may not perform normally. If statistical information is being acquired, stop the acquisition of statistical information before swapping the statistics log file. If statistical information is not to be acquired, suppress the acquisition of statistical information. To acquire statistical information, stop and then restart HiRDB.

If the statistics log file is in use by another program or command, inherited statistical information can be acquired. However, because the statistics log file to be deleted is not deleted, be careful when unloading or editing it.

Action

If the reason indicated in the message explanation is not appropriate, contact the customer support center when this message is output.

KFPS05397-E E

Unexpected error occurred. info:(aa....aa:bbbb)cc....cc

An unexpected error occurred.

aa....aa: Maintenance information

bbbb: Maintenance information

cc....cc: Maintenance information

S: Abnormally terminates.

Action

Save the maintenance information and contact the customer support center.

KFPS05398-E E

Statistics log file can not open

The statistics log file could not be opened during command execution. Consider the following causes:

There is a shortage in the file system area.

The swap target statistics log file cannot be overwritten (there is no write privilege for the statistics log file or the directory that stores the statistics log file).

S: Terminates processing.

O:

If this message is output, statistical information cannot be acquired. If statistical information is being acquired, immediately stop the acquisition of statistical information. If statistical information is not being acquired, suppress statistical information acquisition.

If the cause is a file system area shortage, delete any unnecessary files in the file system. If the swap target statistics log file cannot be overwritten, enable the overwriting attribute of the statistics log file.

After taking appropriate measures, execute the pdstjswap command to restart acquisition of statistical information.

Action

If the reason indicated in the message explanation is not appropriate, contact the customer support center when this message is output.

KFPS05600-I L

HiRDB unit aaaa prepare for starting. status=bb....bb

Preparations are underway to start unit aaaa.
aaaa: Unit identifier

bb....bb: Unit status:

ACCEPT pdstart

The pdstart command has been accepted.

FIX SHARED MEMORY

Fixing of shared memory page has started.

CREATE PIPE FILE

Creation of a pipe file has started.

S: Continues processing.

KFPS05601-I L

This program is HiRDB/Workgroup Server

This program is HiRDB/Workgroup Server.
S: Continues processing.

KFPS05602-I L

HiRDB Option = aa....aa, unit_id = bbbb, version = cc....cc

Displays the embedded option program product names. This message is output during normal starting or restarting of a unit. During restart, this message shows the previous environment.

aa....aa: Option program product names

Staticizer Option: HiRDB Staticizer Option

Advanced High Availability: HiRDB Advanced High Availability

Non Recover FES: HiRDB Non Recover FES

Disaster Recovery Light Edition: HiRDB Disaster Recovery Light Edition

Accelerator: HiRDB Accelerator

bbbb: Unit identifier

cc....cc: Option program product names (vv-rr)

Displays the version (vv) and revision (rr) of the option program product.

S: Continues processing.

Action

Check the execution environment.

KFPS05603-I L

Server aa....aa starting on unit bbbb

On unit bbbb, server aa....aa was started as the running system.

aa....aa: Name of the server started as the running system

bbbb: Identifier of the server start target unit

S: Continues processing.

KFPS05604-I L

Allocated shared memory for aa....aa.owner=bb....bb,size=cc....cc

Allocated shared memory.

aa....aa: Type of shared memory that was allocated

UNIT_CONTROLLER: Unit controller

bb....bb: Attribute of the process using the shared memory (same as the value of SHM-OWNER displayed by the pdls -d mem command)

MANAGER: Manager

cc....cc: Size of the shared memory that was allocated (bytes)

S: Continues processing.

KFPS05605-W L

No more guest servers activatable on unit aaaa, number of active guest servers reached pd_ha_max_act_guest_servers

Because there is no free guest area, unit aaaa cannot receive any more guest BES's.

aaaa: Identifier of the unit for which there is no free guest area

S: Continues processing.

KFPS05606-W L

Unable to activate server aa....aa on unit bbbb,number of act guest servers over pd_ha_max_act_guest_servers

Because there is no free guest area on unit bbbb, server aa....aa could not become the running system on unit bbbb.

aa....aa: Name of the server that cannot become the running system

bbbb: Identifier of the unit with no free guest area

S: Continues processing.

Action

Use one of the following methods to check whether the corresponding server is operating as the running system on another unit in the HA group:

Check whether this message is followed by a KFPS01813-I message output to another unit in the HA group.

Execute the pdls -d ha command.

Execute the pdls -d svr command.

If the corresponding server is not operating as the running system, see the message output to the system manager unit or to each unit. Take the indicated action as necessary, and then start the server.

KFPS05607-I L

HiRDB server aa....aa stop request issued from HA monitor;stops HiRDB server aa....aa, reason=bb....bb

Server aa....aa was stopped because a stop request was issued from the HA monitor or the Hitachi HA Toolkit Extension.

aa....aa: Name of the server to be stopped

bb....bb: HiRDB internal stop reason code

S: Abnormally terminates.

O: See the HA monitor or Hitachi HA Toolkit Extension message.

KFPS05608-I L

HiRDB server aa....aa restart request issued from HA monitor;stop HiRDB server aa....aa temporarily, reason=bb....bb

Server aa....aa stopped because a restart request was issued from the HA monitor or Hitachi HA Toolkit Extension.

aa....aa: Name of the stopped server

bb....bb: HiRDB internal stop reason code

S: Stops and restarts the server.

O: After this message is output, check the server running status using the pdls -d ha (or pdls -d ha -a) command from the system manager unit. If the server has not restarted, depending on the error cause it may not be able to start. See any messages output after this message, and take any indicated action.

KFPS05609-I L

HiRDB server aa....aa start mode determined, start mode:bb....bb

The server start mode has been determined.

aa....aa: Server name

bb....bb: Start mode

R: Restart

R(P): Restart after planned termination

S: Normal start

S: Continues processing.

KFPS05610-I E+L

Server aa....aa is placed in the starting wait state

Server aa....aa is in running system server starting wait state.

aa....aa: Server name

S: Continues processing.

O: The running system server is not activated. Either start the running system server, or use the HA monitor or Hitachi HA Toolkit Extension command to activate it as the running system server.

KFPS05611-I E+L

Server aa....aa is placed in the standby state

Server aa....aa is placed in standby state.

aa....aa: Server name

S: Continues processing.

KFPS05612-I E+L

Unable to recognize HiRDB server aa....aa initialization completion

Completion of server aa....aa initialization processing cannot be recognized using the pdstart command.
Or, for whatever reason, the server cannot be activated.

S: Continues processing.

O:

Server activation took too much time or failed. Enter the pdls command to check the server running state.

If the server is activating
Wait a period of time, and then re-enter the pdls command to check the system status. If server initialization processing has not completed, check the messages to determine if there may be another cause.

If the server is stopping
An error may occur during server activation, preventing the server from activating. Check the messages in the message log file and the event log (in UNIX, syslogfile), and investigate the cause of the server activation failure. If there are no messages, the reason that the server could not be activated may be that there are no unused guest areas in the unit. Use the pdls -d ha command to check the number of unused guest areas in the unit from the number of guest back-end servers running in the unit and the value of the pd_ha_max_act_guest_servers operand. If the number of guest back-end servers running in the unit reaches the value of the pd_ha_max_act_guest_servers operand, start the back-end server on another unit.

If the reason cannot be determined, contact the customer support center.

If server activation processing always takes a lot of time, specify the time required for system activation in the pd_system_complete_wait_time operand, and terminate it normally with the pdstart command.

KFPS05613-W E+L

Too big "pd_ha_max_act_guest_servers". Max value assumed, reason code = aa....aa, unit = bbbb, original value = cc....cc, assumed value = dd....dd

A value greater than the maximum was specified in the pd_ha_max_act_guest_servers operand. The maximum value is assumed.

aa....aa: Reason code

SERVER LIMIT:

The total of the value specified in the unit control information definition pd_ha_max_act_guest_servers operand and the number of host BES's exceeds the maximum number of servers in a unit. Specify a value in the pd_ha_max_act_guest_servers operand that does not exceed the maximum number of servers in a unit.

GUEST BES COUNT:

The value set in the unit control information definition pd_ha_max_act_guest_servers operand exceeds the maximum number of guest BES's. Set the number of BES's in the pd_ha_max_act_guest_servers operand.

bbbb: Unit identifier

cc....cc: Value specified in the unit control information definition pd_ha_max_act_guest_servers operand

dd....dd: The value set in the pd_ha_max_act_guest_servers operand based on internal calculation

S: Continues processing.

Action

Consider the following explanations on the basis of the reason code, and consider whether the specification of the unit control information definition pd_ha_max_act_guest_servers operand is correct.

SERVER LIMIT: The total of the value specified in the pd_ha_max_act_guest_servers operand and the number of host BES's inside the unit exceeds the maximum. Specify a value in the pd_ha_max_act_guest_servers operand that does not exceed the maximum number of servers in the unit. The number of guest servers that can run concurrently becomes less than the value specified in the pd_ha_max_act_guest_servers operand.

GUEST BES COUNT: The pd_ha_max_act_guest_servers operand specifies a value greater than the number of guest BES's running in the unit. To allocate the appropriate resources, set the number of guest BES's running in the unit in the pd_ha_max_act_guest_servers operand.

KFPS05614-W E+L

Too small "pd_ha_max_server_process". Total of host BES "pd_max_bes_process" assumed, unit = aaaa, original value = bb....bb, assumed value = cc....cc

The value specified in the unit control information definition pd_ha_max_server_process operand is less than the total of the pd_max_bes_process operands for the host BES in the corresponding unit. Set the total of the pd_max_bes_process operands for the host BES in the corresponding unit.

aaaa: Unit identifier

bb....bb: Value specified in the unit control information definition pd_ha_max_server_process operand

cc....cc: Value set in the pd_ha_max_server_process operand based on internal calculation

S: Continues processing.

Action

Reconsider the specification of the unit control information definition pd_ha_max_server_process operand.

KFPS05615-W E+L

Too small "pd_ha_process_count". Total of host BES "pd_process_count" assumed, unit = aaaa, orginal value = bb....bb, assumed value = cc....cc

The value specified in the unit control information definition pd_ha_process_count operand is less than the total specified in the pd_process_count operands of the host BES in the corresponding unit. Set the total specified in the pd_process_count operands of the host BES in the corresponding unit.

aaaa: Unit identifier

bb....bb: Value specified in the unit control information definition pd_ha_process_count operand

cc....cc: Value set in the pd_ha_process_count operand based on internal calculation

S: Continues processing.

Action

Reconsider the specification of the unit control information definition pd_ha_process_count operand.

KFPS05616-I L

Guest servers became activatable on unit aaaa

Because there is a free guest area, unit aaaa can receive the guest BES.

aaaa: Unit identifier

S: Continues processing.

KFPS05617-I L

Server aa....aa stop request accept from HA monitor; stops server reason=bb....bb

Because a server stop request was issued from the HA monitor or Hitachi HA Toolkit Extension, server aa....aa is stopped.

aa....aa: Server name

bb....bb: HiRDB internal stop reason code (maintenance information)

S: Terminates processing.

O: See the HA monitor message that was output immediately before.

KFPS05618-E E+L

Unable to specify definition in HAgroup unit, unit ID=aaaa, definition file=bb....bb, record number=cc....cc

In the unit control information definition of units for which standby-less system switchover (effects distributed) is applied, an operand was specified that cannot be specified for units for which standby-less system switchover (effects distributed) is applied.

aaaa: Unit identifier

bb....bb: Name of the definition file being analyzed

cc....cc: Number of the record with the error

S: Abnormally terminates.

Action

Revise the unit control information definition. On units where the standby-less system switchover (effects distributed) facility is being used, the operands that can be specified in the unit control information definition are restricted. Remove the operands that cannot be specified in the unit control information definition. Because the operands that were specified in error can be specified in the system common definition, specify them there as necessary, and then restart HiRDB.

KFPS05619-E E+L

Unable to execute aa....aa command,server bb....bb state not cc....cc

The status of server bb....bb is not cc....cc. Therefore, the command cannot be executed.

aa....aa: Name of the command that was input {pdstart | pdstop | pdxdsstart | pdxdsstop }

bb....bb: Name of the server that could not execute the command

cc....cc: Status that can enter the command

OFFLINE: Offline

ONLINE: Online

S: Terminates processing.

Action

Wait for the status of server bb....bb to become cc....cc, then re-execute the command. However, the pdstart command cannot be executed in start status (including during start processing), and the pdstop command cannot be executed in stop status (including during stop processing). In this case, check that the system has stopped or started and then execute the command.

If the pdxdsstart command is executed and this message is output, even though the XDS specified in the argument is offline, a previously-executed pdxdsstart command might have terminated abnormally or been terminated with the kill command. In that case, take corrective action by following these steps:

Determine the status of the XDS from the XDS log or syslogfile. If message KFPQ80001-I was output, the XDS began starting without a problem.

If you can verify that XDS is offline, execute pdxdsstop -s XDS-server-name -f.

After execution of the pdxdsstop command, execute the pdxdsstart command.

If the pdxdsstop command is executed and this message is output, even though the XDS specified in the argument is online, a previously-executed pdxdsstop command might have terminated abnormally or been terminated with the kill command. In that case, take corrective action by following these steps:

Determine the status of the XDS from the XDS log or syslogfile. If message KFPQ80021-I was output, the XDS began stopping without a problem.

If you can verify that XDS is online, execute pdxdsstop -s XDS-server-name -f.

After execution of the pdxdsstop command, recover the database. For details about how to recover the database, see Using the memory database recovery facility to recover the database in the HiRDB Version 9 Memory Database Installation and Operation Guide.

KFPS05620-I L

Invalid version of HiRDB option, option=aaa, invalid version=bb....bb, required version=cc....cc

The version of the additional PP aaa that has been set up is invalid. The version of the additional PP aaa that has been set up is bb....bb, and valid versions are cc....cc or later.

aaa: Additional PP

aha: Advanced High Availability

bb....bb: Version of the additional PP that has been set up

cc....cc: Correct version of additional PP

S: Interrupts HiRDB start processing.

O: This message provides additional information to the KFPS01801-E message that was output before this message. Check the additional PP name and the correct version of the additional PP, and follow the directions of the KFPS01801-E message.

KFPS05621-I L+S

Server aa....aa standby state released, status=bb....bb

The standby state of server aa....aa has been released.

aa....aa: Server name

bb....bb: Server status code (maintenance information)

S: Continues processing.

KFPS05622-E E

pdtrnqing command failed, reason=aa....aa, inf=bb....bb

An error occurred during execution of the pdtrnqing command.

aa....aa: Reason code

bb....bb: Internal code

S: Terminates processing.

Action

Take action on the basis of the reason code. If an error occurred during transaction queuing release, the transaction queuing status might remain unchanged. In that case, use the pdtrnqing -f command to release the transactions forcibly.

aa....aa (Reason code)
Action

NOT_HAGROUP
A server that is specified is not a target of the standby-less system switchover (effects distributed) facility. In the -s option, specify a back-end server that is a target of the standby-less system switchover (effects distributed) facility.

NOT_ACTIVE
The server is not running on the command execution unit. Execute the command on the unit where the back-end server specified in the -s option is running. If performing a transaction queuing release specification, specify the -f option.

TIMEOUT_S
When transaction queuing started, the system waited for transactions running on the back-end server or unit specified in the -s option to finish, but the transactions did not finish before the expiration of the wait time specified in the pd_ha_trn_queuing_wait_time operand in the system definition or the -t option of the pdtrnqing command.
Terminate the transactions running on the back-end server or unit specified in the -s option, or use the pdcancel command to cancel them.
In addition, revise the wait time specified in the pd_ha_trn_queuing_wait_time operand in the system definition or the -t option of the pdtrnqing command.

TIMEOUT_E
During transaction queuing release, the system waited for server startup processing to finish, but the server startup processing did not finish before the time specified in the system definition pd_ha_trn_queuing_wait_time operand. Ensure that the server startup did not fail. If it failed, eliminate the cause of the error, and then start the server. Also, review the value of the system definition pd_ha_trn_queuing_wait_time operand.

PROCESS_MEMORY
There is insufficient process native memory. Terminate unnecessary processes, reduce the memory in use in the server machine, and then re-execute the command.

INVALID_UNIT
The pdtrnqing command cannot be executed in this system configuration.

CANCEL
During transaction queuing start processing, the wait for the end of the transactions was canceled by one of the following commands:

pdstop

pdprgrenew

pdchgconf

pdtrnqing -d

If the cancellation was done with the pdstop, pdprgrenew, or pdchgconf commands, check and, if necessary, revise the operating procedures, including those for the pdtrnqing command. If cancellation was done with the pdtrnqing -d command, re-execute the pdtrnqing command if necessary.

STOPPING
HiRDB is stopping. The pdtrnqing command cannot be executed while HiRDB is stopping.

EXECUTING_UTILITY
A utility is executing. Terminate or cancel the utility, and then re-execute the pdtrnqing command.

EXECUTING_ORG
Updatable online reorganization is executing. Re-execute the pdtrnqing command after updatable online reorganization has completed.

EXECUTING_PDTRNQING
The pdtrnqing command cannot be executed because transaction queuing is starting.

KFPS05623-I L

Online server not exist, unit=aa....aa

There is no running system server in the unit. Unit start processing continued.
This message might be output when the standby-less system switchover (effects distributed) facility is used.

aa....aa: Unit name

S: Continues processing.

Action

Use the cluster software commands to check the status of the servers in unit aa....aa. If the cluster software is HA monitor, use the monshow command; if it is Hitachi HA Toolkit Extension, use the hateshow command. Based on the result, take one of the following actions:

If all servers on the unit are started as standby systems
No action is required.

If a server is waiting to be activated as the running system server
Activate the running system server from any unit in the HA group. If using HA monitor, use the monact command; if using Hitachi HA Toolkit Extension, execute the command to activate the package from the upper level cluster software.

If a server is activated as the running system server
The processing of commands specified in the usrcommand operand in the sysdef file of HA Monitor might take a long time. Consider increasing the value of the pd_ha_resource_act_wait_time operand.

KFPS05700-I L

HiRDB unit aaaa Security Audit bb....bb

Indicates the status of the security audit facility when HiRDB (or unit, for a HiRDB/Parallel Server) starts.

aaaa: Unit identifier

bb....bb: Status of the security audit facility

inactive: Does not start audit tracing from when the HiRDB system starts.

S: Continues processing.

Action

Because HiRDB was forcibly started, the security audit facility is stopped. To enable the security audit facility, execute the pdaudbegin command. If it is acceptable that it is stopped, no action is necessary.

KFPS05701-E L

Unable to start Security Audit, unit=aaaa, reason code=bb....bb

Audit tracing could not be started because an error occurred in unit aaaa.

aaaa: Unit identifier

bb....bb: Reason code

S: Abnormally terminates the HiRDB system.

Action

Take appropriate action according to the reason code, and then restart the HiRDB system.

Reason code | Action
PROCESS_MEMORY | There is a shortage of process private memory. Re-estimate the process private memory.
COMMUNICATION | A network error occurred. Recover from the network error.
CONFIGURATION | An error occurred during analysis processing in the HiRDB system definition. See the definition analysis error message output before or after this message and re-evaluate the operand in the system definition.
NO_FILE_NAME | The pd_aud_file_name operand is not specified. Specify the pd_aud_file_name operand.
FILE_ACCESS | An error occurred when accessing the audit trace file. See the KFPS05704-E message output before or after this message, and then take appropriate action.

KFPS05702-I L+S

aa....aa assigned as current audit trail generation file, unit=bbbb

Audit trail file aa....aa is assigned to unit bbbb as the current file.

aa....aa: Audit trail file name

bbbb: Unit identifier

S: Continues processing.

KFPS05703-I L+S

Audit trail generation file aa....aa released, unit=bbbb

Audit trail file aa....aa for unit bbbb is no longer the current file.

aa....aa: Audit trail file name

bbbb: Unit identifier

S: Continues processing.

KFPS05704-E E+L

aa....aa error occurred in audit trail generation file bb....bb, unit=cccc, reason code=dd....dd

An error occurred when accessing audit trail file bb....bb for unit cccc.

aa....aa: Processing when an error occurs:

Open: Open the file.

Close: Close the file.

Read: Read the file.

Write: Write the file.

Create: Create the file.

Delete: Delete the file.

bb....bb: Audit trail file name

Displays **************** when an access error of the HiRDB file system area for audit trace files occurs.

cccc: Unit identifier

dd....dd: Reason code

S: Terminates processing.

Action

Take appropriate action according to the reason code, and then restart the HiRDB system.

Reason code
Action

PROCESS_MEMORY
There is a process private memory shortage. Re-estimate the process private memory.

OPEN_MAX
The number of files opened by an open process for audit trace files exceeded the maximum number of files that can be opened. Re-evaluate the maximum number of files that can be opened by a single process. If necessary, re-create the kernel.

FILE_PERMISSION
The user does not have access privileges for the HiRDB file system area for audit trace files. Check your access privileges using the operating system ls command or other command. If you do not have access privileges, ask the HiRDB administrator to grant you access privileges.

IO_ERROR
An I/O error occurred.
Action:

Check for the cause of the I/O error, and then take appropriate action.

Execute the pdaudrm command to delete the audit trace files that the I/O error generated. If some files cannot be deleted, continue working on the remaining files.

If this procedure does not solve the problem, replace the disk and re-create the HiRDB file system area for audit trail files.

VERSION
The version of the HiRDB file system area for audit trail files does not match. To re-create the HiRDB file system area for audit trail files, execute the pdfmkfs command.
To restore the previous version after upgrading HiRDB and restarting, return the HiRDB file system area for audit trail files to the previous version. To restore the pre-upgrade version, use the pdfrstr command on the HiRDB file system area for audit trail files that was backed up using the pdfbkup backup command before the upgrade.

GEN_FILE_PERMISSION
You do not have access privileges to the audit trail file. To check your access privileges to audit trail files, execute the pdfls command. If you do not have access privileges, request that the HiRDB administrator grants you access privileges.

FILE_NOT_FOUND
The audit trail file does not exist.
When the error process is not Delete:

Check if the HiRDB file system area for audit trail files was created. If the area was not created, execute the pdfmkfs command to create the HiRDB file system area for audit trail files.

Check if the created HiRDB file system area for audit trail files and the HiRDB file system area name specified in the pd_aud_file_name operand match.

Check if the audit trail file name specified in the control statement file when the pdload command was executed is correct.

When the error process is Delete:

Check if the HiRDB file system area for audit trail files was created.

Check if the created HiRDB file system area for audit trail files and the HiRDB file system area name specified in the pd_aud_file_name operand match.

GEN_FILE_NOT_FOUND

The audit trail file does not exist. To check if the audit trail file exists, execute the pdls -d aud command.

To check if the audit trail file name specified in the control statement file during command execution is correct, execute the pdload command.

LOCKSEGMENT
There is a lock segment shortage. Re-evaluate the number of record lock segments specified when performing a system build of the OS.

NO_SPACE
The free space required to create audit trail files could not be secured. Re-estimate the size of the HiRDB file system area for audit trail files.

FILE_TYPE
The HiRDB file system area for audit trail files was not created in character special files. To create HiRDB file system areas in character special files, execute the pdfmkfs file.

FILE_OBJECT
The usage objective (-k option of the pdfmkfs command) of the HiRDB file system area for audit trail files is not SYS or SVR. Specify SYS or SVR in the -k option of the pdfmkfs command, and then re-create the HiRDB file system area.

FILE_AREA
The area for audit trail files was not created as a HiRDB file system area. Create a HiRDB file system area for audit trail files by executing the pdfmkfs command.

LARGE_FILE
The possible causes are as follows:

The HiRDB file system area for audit trail files was created as a large file (if the HiRDB server is the Windows edition, a HiRDB file system area of 2,048 MB or greater), but N is specified in the pd_large_file_use operand.

The HiRDB file system area for audit trail files was created by the pdfmkfs -a command, but N is specified in the pd_large_file_use operand.

Specify Y for the pd_large_file_use operand, or omit the specification.

FILE_NUM
The maximum number of audit trail files that can be created was exceeded.
Action:

Re-evaluate the value of the pd_aud_max_generation_num operand.

Re-create the HiRDB file system area for audit trail files by executing the pdfmkfs command. Re-estimate the maximum file count in the HiRDB file system and the area size. To change the maximum file count or the area size, re-evaluate the value of the pd_aud_max_generation_num and pd_aud_max_generation_size operands.

INTERNAL_ERROR
An internal error occurred. Save all files under C:\PDDIR\spool, save the event log (in UNIX, syslogfile), and contact the customer support center.

INVALID_SYSTEM_ID
The HiRDB identifier of the audit trail file is invalid.
Specify an audit trail file whose HiRDB identifier is valid.

KFPS05705-E L

Available audit trail generation file number=a. HiRDB unit bbbb force terminate

The number of audit trail files available for use as the swap destination is 0 or 1. unit bbbb was forcibly terminated because down is specified in the pd_aud_no_standby_file_opr operand.

a: Number of audit trail files that are available for use as the swap destination

bbbb: Unit identifier

S: Abnormally terminates HiRDB.

Action

For details about how to work with audit trail files, see the HiRDB Version 9 System Operation Guide.

KFPS05706-W L

No standby audit trail generation file available, unit=aaaa. Force overwrite audit trail generation file

There are no audit trail files in unit aaaa that are available for use as the swap destination. The data load standby file (excluding files in shutdown status) with the earliest update date/time is made available as the swap destination because forcewrite (default value) is specified in the pd_aud_no_standby_file_opr operand.

aaaa: Unit identifier

S: Continues processing.

Action

Request that the auditor load the data of data load standby audit trail files. For details about how to work with audit trail files, see the HiRDB Version 9 System Operation Guide.

KFPS05707-E L

Error occurred in all audit trail generation files, unit=aaaa. Security Audit stopped

forcewrite (default value) is specified in the pd_aud_no_standby_file_opr operand, but output of the audit trail was stopped because all audit trail files in the HiRDB file system area were shut down.

aaaa: Unit identifier

S: Continues processing.

Action

For details about how to handle errors that occur in audit trail files, see the HiRDB Version 9 System Operation Guide.

KFPS05708-W E+L

Unable to use Security Audit, unit=aaaa, reason code=bb....bb

The security audit facility could not be used because the system configuration does not meet the preconditions of the security audit facility.

If there is a unit (including units with just a system manager) on the HiRDB/Parallel Server with no server, the security audit facility cannot be used.

Cannot use the security audit facility in the utility special unit.

aaaa: Unit identifier

bb....bb: Reason code

ONLY_SYSTEM_MANAGER: Cannot use the security audit facility because only the system manager is defined in the unit.

NO_SERVER: Cannot use the security audit facility because no server is defined in the unit.

UTILITY: Cannot use the security audit facility because the current unit is not a utility special unit.

S: Continues processing.

Action

When using the security audit facility, change the system configuration.

KFPS05709-E E+L

Internal function error occurred, unit=aaaa, function=bb....bb, return code=cc....cc

An internal processing error occurred in unit aaaa.

aaaa: Unit identifier

bb....bb: Name of function where the error occurred

cc....cc: Detail code of a system-related error.

S: Terminates processing.

Action

Take action according to the detail code of an output system-related error. For detail codes of system-related errors, see 4.2 Detail codes for system-related errors. Contact the customer support center for errors that cannot be solved.

KFPS05710-I L

Auto audit trail loading service status=aa....aa

The execution status of the facility for automatically loading the audit trail table data is aa....aa.

aa....aa: The execution status of the facility for automatically loading the audit trail table data

ENABLE: Operating

DISABLE: Stopped

Note that if it was started using pdstart -r, DISABLE is normally displayed.

S: Continues processing.

KFPS05711-I L+S

Auto audit trail loading service restart

The facility for automatically loading audit trail table data is restarting.

S: Continues processing.

KFPS05712-I L+S

Auto audit trail loading service stopped

The facility for automatically loading audit trail table data stopped.

S: Continues processing.

KFPS05713-E L

Auto audit trail loading service stopped, because of loading error occurred

An error occurred during loading, so the facility for automatically loading audit trail table data stopped.

S: Continues processing.

Action

Refer to the message that was output directly prior to this message, investigate the reason why an error occurred while data was being loaded to the audit trail table, and take corrective action. After taking action, if you want to restart the automatic data load facility, execute the pdaudatld -b command.

KFPS05714-I L

Audit trail generation file loading started, unit=aaaa

Loads the audit trail file of unit aaaa to the audit trail table.

aa....aa: Unit identifier of the unit with the audit trail file

S: Continues processing.

KFPS05715-I L

Audit trail generation file loading ended, unit=aaaa

The audit trail file of unit aaaa was loadedto the audit trail table.

aa....aa: Unit identifier of the unit with the audit trail file

S: Continues processing.

KFPS05716-W L

Audit trail generation file loading failed, unit=aaaa; continue processing

Loading of the audit trail file of unit aaaa to the audit trail table failed. Re-execute load processing.

aa....aa: Unit identifier of the unit with the audit trail file

S: Continues processing.

KFPS05717-W L

Error occurred while starting pdload command, reason code=aa....aa

The pdload command failed to start.

aa....aa: Reason code

FORK FAILED: A process fork failed.

MEMORY: A memory shortage occurred.

PARAMETER ERROR: Parameter generation failed.

S: Use a set time interval (pd_aud_auto_loading_retry_intvl specification) at which to retry starting pdload.

Action

Take appropriate action according to the reason code.

aa....aa (reason code) | Action
FORK FAILED | Re-examine the quantity of memory used and the number of processes.
MEMORY | Re-examine the quantity of memory used.
PARAMETER ERROR | An internal conflict was detected, so contact the customer support center.

KFPS05718-W L

Audit trail generation file loading skipped, unit=aaaa, status=bb....bb

Skips the loading of the audit trail file of unit aaaa into the audit trail table.

aaaa: Unit identifier of the unit with the audit trail file

bb....bb: Operational status of the unit with the audit trail file

STARTING: In the process of starting

STOPPING: In the process of stopping

STOP: Stopped (for all cases of normal termination, forced termination, and abnormal termination)

NO_SERVER: No operating server (Servers in the unit have all stopped, or running system servers do not exist in units to undergo standby-less system switchover (effects distributed).)

S: Continues processing.

Action

If bb....bb is STARTING, STOPPING, or STOP:

Use the pdls -d svr command to check the status of the corresponding unit, and if it has stopped, restart the unit. If it is operating, there is a chance that a network error occurred between the MGR unit and the corresponding unit. Therefore, resolve the network error.

If the corresponding unit was changed during operation (ACTIVE shown in pdls -d svr command), loading of the audit trail file that was skipped is re-scheduled.

If bb....bb is NO_SERVER:

Restart the server by executing the pdstart -s command for one or more servers from among the servers that have stopped on unit aaaa. If unit aaaa is the object of standby-less system switchover (effects distributed), execute the system switchover or the pdstart -s command to start up one or more running systems in unit aaaa. Once the server starts up, loading of the audit trail file that was skipped is re-scheduled.

KFPS05719-W L+S

Now waiting for termination of audit trail generation file loading process

Waiting for audit trail table load processing to finish.

S: Continues processing.

Once the process of loading to the audit trail table is finished, the KFPS05720-I message is displayed and command processing continues.

KFPS05720-I L+S

Audit trail generation file loading process complete

Audit trail table load processing is finished.

S: Continues processing.

KFPS05721-W L+S

Audit trail generation file loading process error occurred

An error occurred during audit trail table load processing.

S: Continues processing.

Action

Refer to the message that was output directly prior to this message to determine which error occurred during audit trail table load processing. Take corrective action if necessary.

KFPS05722-E L

Audit trail buffer full occurred. HiRDB unit aaaa force terminate

Output processing of the audit trail is centralized, and all segments of the asynchronous output buffer of the audit trail are in a flush waiting state. Because down is specified in the pd_aud_no_standby_file_opr operand in the system common definition, forcibly terminate HiRDB (for HiRDB/Parallel Servers: the unit).

aaaa: Forced termination unit identifier

S: Terminates abnormally.

Action

Re-examine the size and segment count of the asynchronous output buffer of the audit trail.
If the size and segment count of the asynchronous output buffer is smaller than the output count of the audit trail per unit of time, increase the specification value of the pd_aud_async_buff_size and pd_aud_async_buff_count operands in the HiRDB system definition.

If there is a heavy load on the machine or network, decrease the load.

If a network error occurred, resolve the network error.

For details, see When all sectors of the asynchronous output buffer are placed in flush-wait status in the HiRDB Version 9 System Operation Guide.

KFPS05723-W L

Audit trail buffer full occurred, unit=aaaa. Force overwrite audit trail buffer

Output processing of the audit trail is centralized, and all segments of the asynchronous output buffer of the audit trail are in a flush waiting state. Because forcewrite is specified in the pd_aud_no_standby_file_opr operand in the system common definition, the audit trail of the asynchronous output buffer that was initially waiting for flush is discarded.

aaaa: Forced termination unit identifier

S: Continues processing.

Action

HiRDB processing continues, but because the audit trail was discarded and lost, take the following corrective actions.

Re-examine the size and segment count of the asynchronous output buffer of the audit trail.
If the size and segment count of the asynchronous output buffer is smaller than the output count of the audit trail per unit of time, increase the specification value of the pd_aud_async_buff_size and pd_aud_async_buff_count operands in the HiRDB system definition.

If there is a heavy load on the machine or network, decrease the load.

If a network error occurred, resolve the network error.

For details, see When all sectors of the asynchronous output buffer are placed in flush-wait status in the HiRDB Version 9 System Operation Guide.

KFPS05724-E L

No standby audit trail generation file available, unit=aaaa

No audit trail generation files available in unit aaaa.

aaaa: Unit identifier

S: Continues processing.

Action

Take corrective action based on the KFPS05725-W message that was output after this message.

KFPS05725-W L

Security Audit stopped, unit=aaaa. Continues HiRDB unit start processing

The security audit facility stopped, but start processing of the HiRDB unit continues.

aaaa: Unit identifier

S: Continues processing.

Action

Unit start processing is completing, but the audit trail cannot be acquired because the security audit facility has stopped. Contact the auditor to load the data from the pending audit trail file into the audit trail table. After the data has been loaded, use the pdaudbegin command to restart the security audit facility.

Because an audit trail cannot be acquired, until the security audit facility resumes, do not execute any transactions or commands other than loading data into the audit trail table.

For details, see When an error occurs in an audit trail file in the HiRDB Version 9 System Operation Guide.

KFPS05750-I S

Security Audit aaaaaaa, unit=bbbb

Acquisition of audit trails of unit bbbb started or stopped.

aaaaaaa: Status of audit trails

started: Acquisition of audit trails has started.

stopped: Acquisition of audit trails has stopped.

bbbb: Unit identifier

S: Continues processing.

KFPS05751-I E+S

Usage: aa....aa

Indicates the usage of the aa....aa command at the HiRDB/Single Server. This message is output when an error is found in the command format.

aa....aa: Usage of the command

pdaudbegin

pdaudend

pdaudrm -g audit_generation_file_name [-f]

pdaudswap [-U user_id]

pdaudatld [-b|-t|-i] [-U user_id]

S: Terminates processing.

Action

Re-execute the command.

KFPS05751-I E+L

Usage: aa....aa

Indicates the usage of the aa....aa command at the HiRDB/Parallel Server. This message is output when an error is found in the command format.

aa....aa: Usage of the command

pdaudbegin [-u unit_id]

pdaudend [-u unit_id]

pdaudrm -u unit_id -g audit_generation_file_name [-f]

pdaudswap -u unit_id [-U user_id]

pdaudatld [-b|-t|-i] [-U user_id]

S: Terminates processing.

Action

Re-execute the command.

KFPS05752-E E+L

Error occurred during aa....aa command execution, unit=bbbb, reason code=cc....cc

An error occurred when executing the aa....aa command.

aa....aa: Command name

pdaudbegin

pdaudend

pdaudrm

pdaudswap

pdls -d aud

pdaudatld

bbbb: Unit identifier when an error occurred

cc....cc: Reason code indicating the type of failure

S: Terminates processing.

Action

Take action according to the reason code.

Reason code
Action

ALREADY_STARTED
Acquisition of audit trails has already started.

COMMUNICATION
A network error occurred. Recover from the network error.

CONFIGURATION
An error occurred during analysis processing in the HiRDB system definition. See the definition analysis error message output before or after this message and re-evaluate the operand in the system definition.

PROCESS_MEMORY
There is a process private memory shortage. Re-estimate the process private memory.

ALREADY_STOPPED
Already stopped acquiring audit trails.

DELETE_ERROR
The audit trail file could not be deleted because it is in one of the following statuses:

It is not locked

It is waiting for data loading

It has not been generated yet

To check the status of the audit trail files, execute the pdls -d aud command. Files that are not locked or generated cannot be deleted. To delete files waiting for data loading, execute the pdaudrm command with the -f option specified.

NOT_AUDITOR
Check the auditor's authorization identifier and password. If the command pdls -d aud was executed, check the status of HiRDB. If HiRDB is running, only the auditor can execute the command pdls -d aud, unless HiRDB was started by the pdstart -r command, in which case the command pdls -d aud cannot be executed at all. If HiRDB is not running, only the HiRDB administrator can execute the command pdls -d aud.

UNABLE_SWAP
One remaining file cannot be made the swap destination because pd_aud_no_standby_file_opr=down is specified.
Action:

Request that the auditor load data for the audit trail files that are waiting for data loading.

For details about how to handle errors that occur in audit trail files, see the HiRDB Version 9 System Operation Guide.

NO_STANDBY_FILE
An attempt to swap failed because no files can be made into the swap destination.
Action:

Request that the auditor load data for the audit trail files that are waiting for data loading.

For details about how to handle errors that occur in audit trail files, see the HiRDB Version 9 System Operation Guide.

NO_GEN_FILE
Swap processing could not be performed on the audit trail files because no audit trail files were created.

OTHER_COMMAND
The command could not be executed because another command (pdaudbegin, pdaudend, pdaudrm, pdaudswap, or pdaudatld) is executing. Re-execute the command after the other command terminates.

SECURITY_AUDIT_NOT_UP
An audit trail was not acquired. Execute the command when acquiring audit trails.

FILE_ACCESS
An error occurred when accessing an audit trail file. See the KFPS05704-E message output before or after this message, and then take appropriate action.
An attempt was made to delete an audit trail file, but it was a file that failed to be created due to a shortage of space. If an attempt was made to use the pdaudrm command to delete an audit trail file that failed to be created due to a shortage of space, this message is output but no action is required. When HiRDB starts normally, this file will not be displayed by the command pdls -d aud. If necessary, revise the space for audit trail files and the system definition values related to the space for audit trail files to prevent a shortage of space from occurring.

UNIT_NOT_ONLINE
The target unit for the command is inactive. Execute the command after starting the unit.

NO_FILE_NAME
The pd_aud_file_name operand is not specified. Specify the pd_aud_file_name operand.

UTILITY
The security audit facility could not be used because the unit is a utility special unit.

ONLY_SYSTEM_MANAGER
The security audit facility could not be used because only the system manager is defined in the unit. When using the security audit facility, change the system configuration.

NO_SERVER
The security audit facility could not be used because the server is not defined in the unit. When using the security audit function, change the system configuration.

LOCK
A lock error occurred when executing the command. Wait for a short time, and then re-execute the command.

NO_AVAILABLE_GEN_FILE
An audit trail file available for use as the swap destination could not be found. Take the following action to secure an audit trail file that can be available for use as the swap destination. Then, restart HiRDB.

Request that the auditor load the data for files waiting for data loading into the audit trail table.

For details about how to handle errors that occur in audit trail files, see the HiRDB Version 9 System Operation Guide.

RESTORE_MODE
The following commands cannot be executed because HiRDB was started with the pdstart -r command:

pdaudswap

pdls -d aud

pdaudatld

AUTO_LOADING_NOT_SETUP
The facility for automatically loading audit trail table data cannot be used. To use the facility for automatically loading audit trail table data, the pd_aud_auto_loading operand must be set to Y. Set the pd_aud_auto_loading operand to Y, and then restart HiRDB.

AUTO_LOADING_ALREADY_RUNNING
The facility for automatically loading audit trail table data is already running. If you want to terminate the facility for automatically loading audit trail table data, execute the pdaudatld -t command.

AUTO_LOADING_STOPPING
The facility for automatically loading audit trail table data is in the process of stopping. If you want to start the facility for automatically loading audit trail table data, wait until stop processing has completed, and then execute the pdaudatld -b command.

AUTO_LOADING_ALREADY_STOPPED
The facility for automatically loading audit trail table data is already stopped. If you want to start the facility for automatically loading audit trail table data, execute the pdaudatld -b command.

TIME_OUT
There was a timeout while the facility for automatically loading audit trail table data was restarting.
Because the facility for automatically loading audit trail table data cannot be restarted, execute the pdaudatld -i command and make sure that there are no units performing automatic data loading. After that, use the pdaudatld -b command to restart the facility for automatically loading audit trail table data.
If there is a unit performing automatic data loading, wait for the automatic data loading to finish, and then restart the facility for automatically loading audit trail table data.

KFPS05753-W L

Unable to read audit trail generation file=aa....aa, unit=bbbb

The version of the audit trail file does not match the version of HiRDB being used. Therefore, part or all of the information in the audit trail file is not reflected in the audit trail table.

aa....aa: Audit trail file name

bbbb: Unit identifier

S: Continues processing.

Action

If, after a HiRDB version upgrade, there is a return to the previous version, part or all of the information collected to the audit trail file after the upgrade is not reflected in the audit trail table. To make sure all of the information is reflected, contact the customer support center.

KFPS05801-I S

Usage: pdvrchk -x host_name -d directory_name

The specification format of the pdvrchk command option is invalid.

S: Terminates processing.

Action

Correct the option specification, and then re-execute the command.

KFPS05802-E S

Error occurred in execute pdvrchk command, reason_code = aa(bb....bb,cc....cc,dd....dd)

An error occurred during execution of the pdvrchk command.

aa: Error code

bb....bb: Internal information of the HiRDB system

cc....cc: Internal information of the HiRDB system

dd....dd: Internal information of the HiRDB system

S: Terminates processing.

Action

Take action according to the error cause.

Error code
Error cause
Action

01
The environment variable PDDIR was not found.
Set environment variable PDDIR in the environment of the person executing this command, and then re-execute the command.

02
An error occurred in the remote shell regarding the host name specified in the -x option.
Possible causes:

The HiRDB directory specified in the -d option was not found.

The network of the host specified in the -x option was not found.

The host name specified in the -x option is invalid.

Use the execution results of ping or other similar utility to determine if the network for the specified host is active. Alternatively, check if the HiRDB directory specified in the -d option or the host name specified in the -x option is correct.

03
Internal processing error
Take action according to the message output before this message, and then re-execute the command.

KFPS05803-I S

pdvrchk ended, return code = aa....aa

The pdvrchk command terminated with return code aa....aa.

aa....aa: Return code of the command

S: Terminates processing.

Action

Take appropriate action according to the return code.

Return code
Description
Action

0
Version information and additional options between the command execution source server machine and the target server machine match.
Not necessary.

8
Version information and additional options between the command execution source server machine and target server machine do not match.
Unify the versions of the HiRDB and installed option program product.
With HiRDB Advanced High Availability, some version information, additional option comparison source, and configurations of the target unit are displayed as a mismatch (comparing units of the system manager and units of the back-end server).

12
An error occurred during execution of the command (including command argument errors).
Take action according to the KFPS05801-I, KFPS05802-E or other message output before this message.

KFPS05809-I S

Usage: pdriseset [{-P|-S|-D} [-f]]

The option specification format of the pdriseset command is invalid.

S: Terminates processing.

Action

Specify valid options, and then re-execute the command.

KFPS05810-I E+L+S

Usage: pdrisechk [-d {all|db|sys}] [{-u unit_id|-s server_name}] [-l [-n]] [-r]

The specification format of the pdrisechk command options is incorrect.

S: Terminates processing.

Action

Specify valid options and re-execute the command.

KFPS05813-E E

Unable to execute aa....aa command, reason bb....bb

Execution of aa....aa command failed.

aa....aa: Name of the command that could not be executed

bb....bb: Reason that it could not be executed

pd_rise_use is not 'Y': Y is not specified in the pd_rise_use operand.

NEED TO SPECIFY pd_rise_pairvolume_combination: The pd_rise_pairvolume_combination operand was not specified, or the specified value is invalid.

NEED TO SPECIFY pd_rise_fence_level: The pd_rise_fence_level operand was not specified, or the specified value is invalid.

UNABLE TO SPECIFY pd_inner_replica_control: The pd_inner_replica_control operand cannot be specified.

secondary system: Operands that cannot be specified for a secondary system were specified.

ONE_UNIT: HiRDB/Parallel Server cannot execute in a single-unit system configuration.

S: Terminates processing.

Action

If bb....bb is not secondary system or ONE_UNIT:

Check the system common definition, revise the system common definition, and then re-execute the command.

If bb....bb is a secondary system:

If a system switchover facility is being used, check the system where the command was executed, and execute the command on the primary system. If this message was output when the command was executed on the primary system, revise the specification of the pd_hostname operand. If the pd_hostname operand specifies other than the standard host name of the primary system, specify the standard host name of the primary system.

If bb....bb is ONE_UNIT:

To forcibly terminate the single-unit configuration HiRDB system on the HiRDB/Parallel Server, execute the pdstop -f command.

KFPS05814-I S

Usage: pdrisedbto [-f]

The option specification format of the pdrisedbto command is invalid.

S: Terminates processing.

Action

Specify valid options, and then re-execute the command.

KFPS05815-I S

"pdrisechk" ended, end code=aa....aa

The pdrisechk command terminated with termination code aa....aa.

aa....aa: Command termination code

S: Terminates processing.

O: Follow the action appropriate to the termination code.

Action

Follow the action appropriate to the termination code.

Command termination code | Explanation | Operator action | HiRDB administrator action
OK | The pdrisechk command terminated normally. The pair volume setting is invalid. | -- | --
INVALID_PAIR_SETUP | The pair volume setting used by HiRDB is invalid. | Contact the HiRDB administrator. | See the KFPS05816-E message, and correct the invalid pair volume setting.
ERROR_SOME_UNIT | During execution of the pdrisechk command, an error occurred during a unit's configuration check. | See the message output before this message and take action, then re-execute the command. If necessary, contact the HiRDB administrator. | See the message output before this message and take action, then re-execute the command.

Legend:

--: Not applicable.

KFPS05816-E E

Invalid volume setup. aa....aa, file type=bb....bb, group=cc....cc, code=dd....dd

The pair setting of pair logical volume group cc....cc is invalid.

aa....aa: Depending on the HiRDB file type allocated to the pair logical volume group where there is a problem with the pair setting, the output is in the following format:

bb....bb is DB, LOG, SPD, or SSTS:

server=ee....ee

ee....ee: HiRDB server name

bb....bb is USTS:

unit=ffff

ffff: Unit identifier

bb....bb is ALL:

system=gggg

gggg: HiRDB identifier

bb....bb: File type created in pair logical volume group cc....cc

DB: Database file (file that comprises the RDAREA)

LOG: System log file

SPD: Synchronization point dump file

SSTS: User status file

USTS: Unit status file

ALL: Database file and system files

cc....cc: Name of the pair logical volume group

dd....dd: Reason code

S: Terminates processing.

O: Take action appropriate to the reason code.

Action

Take action appropriate to the reason code.

Reason code
Explanation
HiRDB administrator action

INVALID_VOLUME_ATTRIBUTE
The pair attribute of the corresponding pair logical volume group is invalid.
Confirm that the site where the command was executed is correct. Confirm that the pair attribute of the corresponding pair logical volume is valid. Also, if no pair logical volume group has been created, create a pair logical volume group.

INVALID_FENCE_LEVEL
The fence level setting of the corresponding pair logical volume group is invalid.
Take one of the following actions:

If the value of the pd_rise_pairvolume_combination operand is sync, set the value of the pair volume group fence level to data or never, to match the value of the pd_rise_fence_level operand.

If the value of the pd_rise_pairvolume_combination operand is hybrid and DB is displayed in bb....bb, set the value of the pair volume group fence level to async.
If other than DB is displayed in bb....bb, set the value of the pair volume group fence level to data or never, to match the value of the pd_rise_fence_level operand.

If the value of the pd_rise_pairvolume_combination operand is async, set the value of the pair volume group fence level to async.

If the value of the pd_rise_pairvolume_combination operand is syssync, set the fence level of the pair logical volume to data or never to match the specification of the pd_rise_fence_level operand.

INVALID_STATUS
A pair with a pair status of other than PAIR or PFUL exists in the corresponding pair logical volume group.
Check the pair status of the corresponding pair logical volume group, check the reason that it became that pair status, and take appropriate action. For details on the how to check the reason and take action, see the RAID Manager documentation.

KFPS05821-E E+L

Unable to specify hostname or server name outside HAGROUP

The error is one of the following:

The specified host name (unit identifier) or server name is not a host (unit) or server that is applicable to the standby-less system switchover (effects distributed) facility.

The specified host (unit) and the server belong to different HA groups.

S: Terminates processing.

Action

Make sure that the specified host name (unit identifier) and server name belong the same HA group, and then re-execute the command.

KFPS05822-E E

aa....aa invalid; stops server restart.server ID=bb....bb, old value=cc....cc,new value=dd....dd

Because the value specified for the aa....aa operand has changed, the server cannot be restarted. The value of the aa....aa operand cannot be changed after abnormal termination, forced termination, or planned termination.

aa....aa: Definition items that do not match

"pd_utl_exec_mode": Utility execution mode

"pd_max_list_users": Number of users that can own the list concurrently

"pd_max_list_count": Number of lists created per user

"pd_max_reflect_process_count": Number of processes to be allocated for reflection processing

"pd_max_users": Maximum number of concurrent connections (SDS, FES)

"pd_max_bes_process" or "pd_max_users": Maximum number of startup processes (BES)

"pd_max_dic_process" or "pd_max_users": Maximum number of startup processes (DS)

bb....bb: Server name (if the aa....aa operand is the system common definition or the unit control information definition, ******** is displayed)

cc....cc: Value before the aa....aa operand was changed

dd....dd: Value after the aa....aa operand was changed

S: Terminates processing.

Action

Return the value of the aa....aa operand to the value before the change (cc....cc) and restart the server. However, if any of the following operands was output in the aa....aa operand, make it as follows:

If "pd_max_bes_process", "pd_max_dic_process", or "pd_max_users" was output, and the pd_max_bes_process or pd_max_dic_process operand is not specified, change the value of pd_max_users.

If "pd_max_bes_process", "pd_max_dic_process", or "pd_max_users" was output, and the pd_max_bes_process or pd_max_dic_process operand is specified, make it as follows:

cc....cc > value specified for pd_max_users:

Change the value of the pd_max_bes_process or pd_max_dic_process operand.

cc....cc value specified for pd_max_users:

If cc....cc > value of pd_max_bes_process or pd_max_dic_process, change the value of pd_max_users.

If cc....cc value of pd_max_bes_process or pd_max_dic_process, change the value of the pd_max_users, pd_max_bes_process, or pd_max_dic_process operand.

KFPS05827-E E+L

Unable to stop server outside HAGROUP with "aa....aa" option

The "aa....aa" option cannot be specified in the pdstop -s server_name command for servers that are not used with the standby-less system switchover (effects distributed) facility.

aa....aa: Specified option {-x host_name | -u unit_id} -z

S: Terminates processing.

Action

If the specified option is -x host_name or -u unit_id:

Reconsider the specification of the command options. If stopping a server that is not used with the standby-less system switchover (effects distributed) facility, execute the command without specifying the -x host_name or -u unit_id option.

If the specified option is -z:

Reconsider the specification of the command options. Servers other than those that use the standby-less system switchover (effects distributed) facility cannot be forcibly terminated. To terminate them, use normal termination (execute the pdstop -s server_name command from the unit that contains the system manager).

KFPS05828-E S

Unable to stop normally because server terminated abnormally

HiRDB cannot be normally terminated because there are servers that were abnormally terminated or that were forcibly terminated with the pdstop -f or pdstop -z command.

S: Terminates processing.

Action

Use one of the following methods to terminate HiRDB:

Use the pdls command to check servers that were abnormally terminated or that were forcibly terminated using the pdstop -f or pdstop -z command, start the servers, and then normally terminate them using the pdstop command.

Use the pdstop -f command to forcibly terminate HiRDB.

KFPS05829-E E

Unable to stop, reason code=aa....aa

Normal termination or planned termination of HiRDB cannot be performed.

aa....aa: Reason termination cannot be executed

resident RDAREA exists: There is an in-memory RDAREA.

XDS exists: XDS is operating.

S: Terminates processing.

Action

When aa....aa is resident RDAREA exists:

Release in-memory allocation and then re-execute the pdstop command. If you want to terminate HiRDB before releasing in-memory allocation, use the pdstop -f command to forcibly terminate HiRDB.

If aa....aa is XDS exists:

Stop XDS and then re-execute the pdstop command. If you want to terminate HiRDB before stopping XDS, use the pdstop -f command to forcibly terminate HiRDB. In this case, data in the XDS memory cannot be recovered.

KFPS05837-I E

Usage: pdtrnqing {[-d|-t wait_time]|[-d [-f]][-t wait_time]-s server_name}

Displays how to use the pdtrnqing command. This message is displayed in the following circumstances:

The pdtrnqing command was specified with the -h option.

An option or argument to the command was specified incorrectly.

S: Terminates the pdtrnqing command.

O: If there is an error in the usage of the command, re-enter the command correctly.

KFPS05839-I E

Usage: pdstjsync [-m]

The specification format of the pdstjsync command options is invalid.

S: Terminates processing.

O: Re-execute on the basis of the command usage method.

KFPS05840-I S

Statistics log written, from statistics log buffer to statistics log file

Information in the statistics log buffer was output to the log file.

S: Continues processing.

KFPS05841-E S

pdstjsync command failed, readson=a....a

Information in the statistics log buffer could not be output to the log file.

aa....aa: Reason code that indicates the contents of the error

ALREADY_STOPPED: Statistical information is already stopped.

S: Terminates processing.

Action

ALREADY_STOPPED:

Execute this command during statistical information acquisition.

KFPS05842-I E

Usage: pdsvhostname -s server_name [-b]

The specification format of the pdsvhostname command options is invalid.

S: Terminates the pdsvhostname command.

Action

If there is an error in the command usage method, re-execute using a correct usage method.

KFPS05843-E E

Invalid environment variable aa....aa, reason code=bb....bb

The value of an environment variable is incorrect.

aa....aa: Environment variable name {PDDIR|PDCONFPATH}

bb....bb: Reason code

NOTHING: No environment variable is set.

INVALID_LENGTH: The value set for the environment variable exceeds the limit.

S: Terminates processing.

Action

Refer to the reason code, and confirm that the environment variable is set appropriately.

KFPS05844-E L

Unable to recognize stop HiRDB units by force

Completion of forced termination processing of the HiRDB unit cannot be confirmed.

S: Terminates processing.

Action

Re-execute the pdstart -R command or the pdstart -R -t command.

If the situation does not change, use the following procedure to terminate all non-MGR units.

Execute the pdls -d ust command.

If the status of the unit (UNIT_STAT) is STARTING, ONLINE, or STOPPING, run the pdstop -z command, and forcibly terminate non-MGR units.
If the status of the unit is other than any of those mentioned above, terminate the non-MGR units.

KFPS05901-W L

pdprfd service failed. pid=aa....aa

The troubleshooting information collection process (pdprfd) terminated abnormally. As a result, collection of performance trace information was terminated.

aa....aa: Process ID

S: Terminates processing.

Action

Check whether any error messages were output before this message. In addition, make sure no disk I/O errors have occurred. To restart collection of performance trace information, terminate HiRDB and then restart it.

KFPS05902-W L

Unable to start pdprfd service. detail code=aa....aa

The troubleshooting information collection process (pdprfd) could not be started. As a result, collection of performance trace information was terminated.

aa....aa: Maintenance information

S: Terminates processing.

Action

Check whether any error messages were output before this message. In addition, make sure that no disk I/O errors have occurred. To restart collection of performance trace information, terminate HiRDB, and then restart it.

KFPS05903-I L

PRF trace started. level=aaaaaaaa

Collection of performance trace information started.

aaaaaaaa: Performance trace collection level

S: Continues processing.

KFPS05904-I S+L

PRF level changed. before=aaaaaaaa, after=bbbbbbbb

The performance trace collection level changed from aaaaaaaa to bbbbbbbb.

aaaaaaaa: Performance trace collection level before the change

bbbbbbbb: Performance trace collection level after the change

S: Continues processing.

KFPS05905-I E+S

Usage: aa....aa

Indicates how to use the aa....aa command.

aa....aa: How to use the command (displays one of the following)

pdprflevel [-l prf_level]

pdprfed [-T begin_time,end_time] [-p pid[,pid]...] [-e event_id[,event_id]...] [-H] prf_file_name

S: Continues processing.

O: Specify the correct options and re-execute the command.

KFPS05906-E E

pdprfd service has been stopped. command=aa....aa, detail code=bb....bb

The troubleshooting information collection process (pdprfd) has stopped.

aa....aa: Command name

pdprflevel

bb....bb: Maintenance information

S: Terminates processing.

Action

Take the corrective action indicated in the following, and then execute the command:

If message KFPS05901-W is output and the pdprfd process has stopped, terminate and restart HiRDB to restart collection of performance trace information.

If the performance trace facility was disabled by specifying N in the pd_prf_trace operand in the system definition, enable the performance trace facility by specifying Y in the pd_prf_trace operand, or by omitting the pd_prf_trace operand.

KFPS05907-E E

Unable to read file. command=aa....aa, rc=bb....bb, errno=cc....cc

The performance trace information file was specified incorrectly, or there is a problem with access privileges.

aa....aa: Command name

pdprfed

bb....bb: Maintenance information

cc....cc: Maintenance information

S: Terminates processing.

O: Change the specification of the performance trace information file, and then re-execute the command.

KFPS05908-E E

Insufficient memory. command=aa....aa, rc=bb....bb, errno=cc....cc

A memory shortage occurred in the execution of the aa....aa command.

aa....aa: Command name

pdprfed

bb....bb: Maintenance information

cc....cc: Maintenance information

S: Terminates processing.

O: Resolve the memory shortage, and then re-execute the command.

KFPS06001-E L

Error occurred in system call aa....aa. errno= bbb

An error occurred in a system call issued during initialization at processing activation.
The KFPS04621-E message may be output following this message; however, it may be ignored.

aa....aa: Name of the system call that was issued

bbb: System call return code (errno)

S: Terminates this processing by issuing abort code Popt001.

O: To determine the cause, refer to the OS documentation based on the system call name and return code.

Action

Determine the cause of the error from the system call name and the system call return code. If the error was caused by a memory shortage, increase the available memory by stopping unneeded processes or increasing the system swap area. If the error was not caused by a memory shortage, contact the customer support center.

2.14 KFPT messages

KFPT00001-E E+L

aa....aa:system call error, func=bb....bb,errno=cc....cc

An error occurred in a system call (function).

aa....aa: Command name

pdorcheck: Application condition check for online reorganization

pdorcreate: Create a discrepancies application environment for online reorganization

pdrdrefls: Display information of related RDAREAs

pdorend: Discrepancies application for online reorganization

bb....bb: System call when the error occurred

cc....cc: Error number set in errno

S: Terminates processing.

O:

Based on the error number (errno: foreign variable indicating the error status), see errno.h and reference documentation on the applicable functions to eliminate the cause of the error, and then re-execute the command. For representative errno examples, see 4.3 System call return codes.

KFPT00002-E E+L

aa....aa:insufficient memory, size=bb....bb

A memory shortage occurred.

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

bb....bb: Memory size to be secured (unit: bytes)

S: Terminates processing.

O:

Check if a process uses a lot of memory. If such a process is found, wait for the process to terminate, and then re-execute the command. If such a process is not found, contact the HiRDB administrator.

Action

Re-evaluate the size of the system's virtual memory. If there is a space shortage, add real memory. If real memory cannot be added, free up more virtual memory by stopping other resident programs or processes, for example.

KFPT00003-E E+L

aa....aa:interface error, func=bb....bb,code=cc....cc

An interface error occurred between functions in the program.

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

bb....bb: Name of function causing the error

cc....cc: Detail code

S: Terminates processing.

O: Contact the customer support center.

KFPT00004-E E+L

aa....aa:system management function error, func=bb....bb,code=cc....cc

A system-related error occurred.

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

bb....bb: Name of function causing the error

cc....cc: Error detail code

S: Terminates processing.

O:

See 4.2 Detail codes for system-related errors or 4.1 Detail codes for RPC-related errors to eliminate the cause of the error, and then re-execute the command. If the error is not resolved, contact the customer support center.

KFPT00005-E E+L

aa....aa:SQL error occurred

An SQL error occurred.

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

S: Terminates processing.

O:

See the message related to the SQL statement issued immediately before this message to eliminate the cause of the error. If no message related to the SQL statement is output, contact the customer support center.

KFPT00006-E E

aa....aa:bb....bb not setup

Cannot execute the command because bb....bb is not embedded.

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

bb....bb: Option name

Staticizer Option: HiRDB Staticizer Option

S: Terminates processing.

Action

Embed bb....bb, and then re-execute the command.

KFPT00007-E E+L

aa....aa:unable to access to dictionary table, kind=bb....bb,table=cc....cc

An error occurred when accessing the dictionary table.

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

bb....bb: SQL type

OPEN: OPEN error

CLOSE: CLOSE error

SELECT: SELECT error

PREPARE: PREPARE error

FETCH: FETCH error

cc....cc: Name of the dictionary table

S: Terminates processing.

O:

See the KFPAxxxxx message output immediately before this message to eliminate the cause of the error indicated by the message, and then re-execute the command. If no KFPAxxxxx message is output, contact the customer support center.

KFPT00008-E L

aa....aa:unable to access to reflection management table

An error occurred when accessing the reflection management table.

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

S: Terminates processing.

O:

See the KFPAxxxxx message output immediately before this message to eliminate the cause of the error the message indicates, and then re-execute the command. If no KFPAxxxxx message is output, contact the customer support center.

KFPT00009-E E+L

aa....aa:SQL error occurred during reflection execution, TBLID=bb....bb, kind=cccc,code=dd....dd

An SQL error occurred during discrepancies application processing of the table ID (bb....bb).

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

bb....bb: Table ID

cccc: SQL type

PREP: PREPARE error

EXEC: EXECUTE error

dd....dd: Internal code

S: Terminates processing.

O:

See the KFPAxxxxx message output immediately before this message to eliminate the cause of the error the message indicates, and then re-execute the command. If no KFPAxxxxx message is output, contact the customer support center.

KFPT00010-E L

aa....aa:failed to load library, library name=bb....bb, reason=cc....cc

Failed to load the library.

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

bb....bb: Name of the library failing to load

cc....cc: Reason loading failed

S: Terminates processing.

O: Contact the HiRDB administrator.

Action

If the library name is lib_phsgml_rpl, lib_phsgml_rpl64, or lib_phsgml_rpl_r, check if the HiRDB Text Search Plug-in is set up correctly.

KFPT00011-E L

aa....aa:failed to get procedure address, procedure name=bb....bb, library name=cc....cc, reason=dd....dd

Acquisition of the function address failed.

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

bb....bb: Function name

cc....cc: Library name

dd....dd: Reason for failure

S: Terminates processing.

O: Contact the HiRDB administrator.

Action

If the function name is get_sgml_indata_ex, check if the HiRDB Text Search Plug-in is set up correctly.

KFPT00012-E L

aa....aa:file access error, func=bb....bb,file=cc....cc,errno=dd....dd

A file access error occurred.

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

bb....bb: Element (name of the system call causing the error)

cc....cc: File name

If the file name is more than 150 bytes long, 150 bytes is displayed from the end.

dd....dd: Error number set to errno

S: Terminates processing.

O: Contact the HiRDB administrator.

Action

Based on the error number (errno: foreign variable indicating the error status), see errno.h and reference documentation on the applicable functions to eliminate the cause of the error, and then re-execute the command. For representative errno examples, see 4.3 System call return codes.

KFPT00013-E L

aa....aa:LOCK TABLE failed, table name=bb....bb, lock kind=cc....cc

Locking on table bb....bb failed.

aa....aa: Command name (see the command name in the embedded character in message KFPT00001-E).

bb....bb: "authorization-identifier"."table-identifier"

cc....cc: Lock mode

EXCLUSIVE: Lock mode

S: Terminates processing.

O: See the KFPAxxxxx message that was output before this message, resolve the error, and then re-execute the command.

KFPT00019-E L

aa....aa:Unable to load compression library, name="bbbbbb", return code=cc....cc, errno=dd....dd

Compression library bbbbbb cannot be loaded for the reason indicated in return code cc....cc and error code dd....dd.

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

bbbbbb: Name of compression library

PDZLIB

cc....cc: Return code

4: Library bbbbbb, which was specified as the name of the compression library during table definition, is not installed in HiRDB.

8: An error occurred when loading the compression library bbbbbb.

12: The compression library loaded successfully, but an error occurred during symbol resolution.

dd....dd: Error code (errno)

When cc....cc is 4: ****

When cc....cc is 8: errno when loading the compression library

When cc....cc is 12: errno during symbol resolution in the compression library

S: Terminates processing.

O: Contact the HiRDB administrator.

Action

Refer to the return code and error code to eliminate the cause of the error, and then re-execute the command. For typical errno examples, see 4.3 System call return codes. If you cannot eliminate the cause of the error, contact the customer support center.

KFPT00020-E L

aa....aa:Expand processing error occurred, library="bbbbbb", errinf=cc....cc

The error indicated in cc....cc occurred during expansion processing with compression library bbbbbb.

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

bbbbbb: Name of compression library

PDZLIB

cc....cc: Error information

Error information for the error that occurred during expansion processing with compression library bbbbbb

S: Terminates processing.

O: Contact the HiRDB administrator.

Action

Based on the error information below, eliminate the cause of the error, and then re-execute the command. If you cannot eliminate the cause of the error, contact the customer support center.

When the error information has a value of less than -1000 (-1nnn)
Taking errno to be the value nnn (equal to error information + 1,000), look up errno (value 1 to 151) in errno.h and in the documentation of the applicable OS, eliminate the cause of the error, and then re-execute the command. For typical errno examples, see 4.3 System call return codes.

When the error information is -4
Add the memory required to execute the compression library, about 260KB, and then re-execute the command.

Other than above
Contact the customer support center.

KFPT00021-E L

aa....aa:"bbbbbb" return with invalid code cc....cc

Invalid return code cc....cc was returned from compression library bbbbbb.

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

bbbbbb: Name of compression library

PDZLIB

cc....cc: Return code

Return code of compression library bbbbbb

S: Terminates processing.

O: Contact the customer support center.

KFPT00022-E L

aa....aa:Length of Expand data bb....bb cc....cc, compression library name="dddddd"

One of the following error occurred in compression library dddddd.

When cc....cc is invalid
The post-expansion data length bb....bb is invalid.

When bb....bb is larger than
The post-expansion data is larger than the post-expansion area cc....cc.

When bb....bb is a message that contains less than compressed data length
The post-expansion data length (the length displayed before less than compressed data length) is smaller than the pre-expansion data length cc....cc.

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

bb....bb: post-expansion-data-length, larger than, or post-expansion-data-length less than compressed data length

cc....cc: invalid, the size of the post-expansion data storage area, or the pre-expansion data length

dddddd: Name of compression library

PDZLIB

S: Terminates processing.

O: Contact the customer support center.

KFPT01000-E E+L

aa....aa:insufficient memory in message buffer pool

A temporary memory shortage occurred in the message storage buffer pool during process allocation.

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

S: Terminates processing.

O:

Too many utilities were executed concurrently. Revise the number of utilities that can be executed at the same time. To find out the maximum number of utilities that can be executed concurrently, see the manual HiRDB Version 9 Command Reference.

KFPT01001-E E+L

aa....aa:unable to send message from bb....bb to cc....cc

An attempt to transmit data from host bb....bb to host cc....cc failed because a transmission error occurred.

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

bb....bb: Transmission source host name

cc....cc: Transmission host name

S: Terminates processing.

O:

Take action according to the KFPT00004-E message output before this message. However, if a physical communication error did not occur, it is possible for a contradiction to result in the system definition between hosts. Re-evaluate the host-to-host definition that causes the error, and then re-execute.

KFPT01002-E E+L

aa....aa:invalid log record format exists in system log file, server=bb....bb, file_group=cc....cc, block_number=0xdd....dd, record_number=0xee....ee

A system log record in an invalid format was detected.

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

bb....bb: Server name

cc....cc: File group name of the system log file

dd....dd: Block number (hexadecimal)

ee....ee: Record number (hexadecimal)

S: Abnormally terminates.

O: Contact the customer support center.

KFPT01003-E L

aa....aa:unable to reflect,because reflect management table initialized

Discrepancies application processing could not be re-executed because the reflection management table was initialized.

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

S: Abnormally terminates.

O: Recover the state immediately before starting discrepancies application processing for the target RDAREA from the stored backup data. Then, re-execute discrepancies application processing.

KFPT01004-I L

Pdorend:interrupt request accepted

An interrupt request was accepted.

S: Continues processing.

KFPT01005-E L

Pdorend:request for reflect service failed, request=aa....aa,code=bb....bb

A request to the pdorend reflection process failed.

aa....aa: Request content (maintenance information)

CONNECT: Activation request

CNTLINF: Control information transmission request

TABLEFRST: Table definition information transmission start request

TABLENEXT: Table definition information transmission continue request

TABLELAST: Table definition information transmission terminate request

DBUPDINF: DB update request

COMMIT: COMMIT request

DISCONNECT: Stop request

bb....bb: Response code (maintenance information)

S: Terminates processing.

O: Take action according to the KFPTxxxxx-E message output immediately before this message.

KFPT01006-E L

aa....aa:procedure for obtain ADT input data returned error status, procedure name=bb....bb, information=cc....cc

An abstraction data type input data retrieval function returned error label status.

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

bb....bb: Name of function where the error occurred

cc....cc: Additional information

S: Terminates processing.

O: Contact the customer support center.

KFPT01007-E L

aa....aa:server down detected

An abnormal server termination was detected, or processing could not be executed because a system switchover occurred.

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

S: Terminates processing.

P:

Based on error messages already output, eliminate the cause of the error resulting in abnormal server termination, and then re-execute the command. If a system switchover occurred during processing, make the files required for command processing available from the host executing the command for referencing or updating, and then re-execute.

KFPT01008-E L

Pdorend:error occurred during reflection execution, server=aa....aa,pdorend command process id=bb....bb

An error occurred during discrepancies application processing of server aa....aa.

aa....aa: Name of server where the discrepancies application processing error occurred

bb....bb: Process ID of the pdorend command executing the discrepancies application processing on server aa....aa

S: Terminates processing.

O:

Refer to the message log file and the event log (in UNIX, syslogfile). Take action based on the error message (error message for the same process as process ID bb....bb) output after this message.

KFPT01009-I L

Pdorend:reflection execution finished, server=aa....aa,pdorend command process id=bb....bb,ins=cc....cc,upd=dd....dd,del=ee....ee,cmt=ff....ff

The catch-up processing by server aa....aa terminated.

aa....aa: The name of the server subject to catch-up processing

bb....bb: Process ID for the updatable online reorganization database reflection command (pdorend) that executed the catch-up processing for server aa....aa.

cc....cc: INSERT number of rows#

dd....dd: UPDATE number of rows#

ee....ee: DELETE number of rows#

ff....ff: target transaction commit count

#: If a rollback occurs on the subsystem RDAREA during an updatable online reorganization operation, this also includes the number of DB updates performed for the recovery of the transaction.

S: Continues processing.

KFPT01010-W L

aa....aa:SQL error skip occurred during reflection execution, server=bb....bb, pid=cc....cc

An SQL error occurred on the item to be skipped during reflection processing by server bb....bb.

aa....aa: Command name (see the command name in the embedded character in message KFPT00001-E)

bb....bb: Name of the server on which the reflection processing error occurred.

cc....cc: Process ID

S: Continues processing.

Action

See the contents of the skip information output file _bb....bb_cc....cc that was specified in the skip_info operand of the report statement of the reflection control file. Acquire the contents (key value) of the update information that was skipped. From the acquired key value, retrieve the original RDAREA and the replica RDAREA, and update the data in the original RDAREA with the contents of the replica RDAREA as necessary.

KFPT01011-E E+L

aa....aa:only one "bb....bb" can be specified in reflection control file

Only one "bb....bb" statement can be specified in the reflection control file.

aa....aa: Command name (see the command name in the embedded character in message KFPT00001-E).

bb....bb: Name of the statement

S: Terminates processing.

Action

Reduce the number of "bb....bb" statements specified in the reflection control file, and then re-execute the command.

KFPT01012-E E+L

aa....aa:invalid absolute pathname, operand="bb....bb", max length=cccc, line=dd....dd

The absolute path name of the "bb....bb" operand specified in the dd....dd th row of the reflection control file is greater than the maximum value cccc for absolute path names.

aa....aa: Command name (see the command name in the embedded character in message KFPT00001-E).

bb....bb: Operand name

skip_info:The skip_info operand of the report statement.

sqltrc_dir: The sqltrc_dir operand of the report statement.

cccc: Maximum value for absolute path names

dd....dd: Row number

S: Terminates processing.

Action

For the skip_info operand of the report statement
Create a file with a name that is _server-name (9 characters maximum) appended to _process-ID (11 characters maximum) in the absolute path name specified in the skip_info operand. Change the absolute path name to a length less than or equal to the length that is obtained by subtracting the maximum length (20 characters) of the _server-name_process_ID from the maximum absolute path name that is indicated in the message, and then re-execute the command.

For the sqltrc_dir operand of the report statement
Specify a directory path for the sqltrc_dir operand whose absolute path name length is no greater than the maximum value of the absolute path name indicated in cccc.

KFPT01013-E E+L

aa....aa:invalid format exists in reflection control file, line=bb....bb, info="cc....cc"

The "cc....cc" format specified in the bb....bb th row of the reflection file is in error.

aa....aa: Command name (see the command name in the embedded character in message KFPT00001-E).

bb....bb: Row number

cc....cc: Character string containing the error (if the character string is more than 30 characters in length, only the first 30 characters are output)

S: Terminates processing.

Action

Revise the contents of "cc....cc", and then re-execute the command.

KFPT01014-E E+L

aa....aa:invalid attribute exists in reflection control file, line=bb....bb, operand="cc....cc"

The value of the "cc....cc" operand specified in the bb....bb th row of the reflection file contains an error.

aa....aa: Command name (see the command name in the embedded character in message KFPT00001-E).

bb....bb: Row number

cc....cc: Operand name

S: Terminates processing.

Action

Revise the value of the "cc....cc" operand, and then re-execute the command.

KFPT01015-E E+L

aa....aa:"bb....bb" statement not specified in reflection control file

The "bb....bb" statement required in the reflection file is missing.

aa....aa: Command name (see the command name in the embedded character in message KFPT00001-E).

bb....bb: Name of the statement

S: Terminates processing.

Action

Specify the "bb....bb" statement in the reflection file, and then re-execute the command.

KFPT01016-E L

aa....aa:SQLWARN occurred. Unable to reflection execution, server=bb....bb, pid=cc....cc, SQLCODE=dd....dd, SQLWARN=ee....ee

In server bb....bb, an SQLWARN error that prematurely terminated reflection processing occurred.

aa....aa: Command name (see the command name in the embedded character in message KFPT00001-E).

bb....bb: Name of the server on which the reflection processing error occurred.

cc....cc: Process ID

dd....dd: SQLCODE

ee....ee: SQLWARN

The value of n for the SQLWARNn error that occurred is output. If multiple SQLWARNn errors occurred, they are output delimited with commas.

S: Terminates processing.

Action

Refer to the SQL statement message that is output immediately after this message, and resolve the cause of the error. If an SQL statement-related message is not output, contact the customer support center.

KFPT01017-E L

aa....aa:invalid attribute exists in reflection control file, operand="bb....bb", value="cc....cc", reason=dd....dd

The value "cc....cc" specified in the "bb....bb" operand in the reflection file is in error.

aa....aa: Command name (see the command name in the embedded characters of message KFPT00001-E).

bb....bb: Operand name

cc....cc: Operand specification value#

For the skip_info operand:
Name of the directory part in the skip information output file name that was specified in the operand

#: If the value specified in the operand is more than 100 bytes, the first 100 bytes from the end of the operand are output.

dd....dd: Reason code

Invalid-device: Invalid file format

Invalid-permission: Invalid file permission

No-directory: A directory is missing

S: Terminates processing.

Action

Invalid-device:

Specify the directory correctly and re-execute the command.

Invalid-permission:

Grant the user the necessary privileges to the directory and re-execute the command.

No-directory:

Create the directory and re-execute the command.

KFPT01018-W L

aa....aa:unable to bb....bb, table name=cc....cc

bb....bb processing cannot be performed on table cc....cc.

aa....aa: Command name (see the command name in the embedded characters of message KFPT00001-E)

bb....bb: Processing type

set check pending status: Set in check pending status

cc....cc: "authorization-identifier"."table-identifier "

S: Continues processing.

Action

If the processing type is set check pending status, use the following procedure:

Complete the reflection processing that was interrupted by the pdorend command request to perform updatable online reorganization, then refer to the error message output immediately before this message, and eliminate the cause of the error indicated in the message.

Identify tables set in check pending status.
(a) Table cc....cc is a referenced table
Set all referencing tables that make table cc....cc a referenced table in check pending status.
(b) Table cc....cc is a referencing table and a check constraint table
Set table cc....cc in check pending status.
(c) Table cc....cc is a referencing table and a referenced table, and table cc....cc is a check constraint table and a referenced table
Set table cc....cc and all referencing tables that make table cc....cc a referenced table in check pending status.

Use an integrity check utility to forcibly set in check pending status the original generation of (-q 0 specified) tables identified in 2.

Use an integrity check utility to check the integrity of tables set in check pending status in 3.

For details about integrity check utilities, see the manual HiRDB Version 9 Command Reference. For the procedure for table integrity checking, see the manual HiRDB Version 9 Installation and Design Guide.

KFPT01019-E E+L

Pdorend:invalid combination of operand exists in reflection control file, operand name=aa....aa and bb....bb

There is an invalid combination of operands in the attached reflection control file.

aa....aa: Invalid combination of operands

bb....bb: Invalid combination of operands

S: Terminates processing.

O: Check the control statement specifications described in the attached reflection control file, correct the specifications, and then re-execute the pdorend command.

KFPT01020-I L

Pdorend:SQL trace information file swapped, from=aa....aa, to=bb....bb

An SQL trace information file was switched.

aa....aa: File name before switch

bb....bb: File name after switch

If the file name exceeds 84 bytes, the last 84 bytes are displayed.

S: Continues processing.

KFPT02000-E E

aa....aa:invalid option specified with this command, option=bb

An invalid option was specified.

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

bb: Invalid option

S: Terminates processing.

O: Correct the command line specification, and then re-execute.

KFPT02001-E E

aa....aa:invalid combination of option flags (bb and cc) exists in command line

An invalid combination of option flags was found in the command line.

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

bb: Invalid combination of option flags

cc: Invalid combination of option flags

S: Terminates processing.

O: Correct the command line specification, and then re-execute.

KFPT02002-E E

aa....aa:invalid bb option

An error was found in the specification of the bb option.
This message is output in one of the following cases:

There is no specified value.

The specified value exceeds the maximum value.

The type of the specified value is invalid.

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

bb: Invalid option flag

S: Terminates processing.

O: Correct the option specification, and then retry the operation. If you need to correct the pattern character string of the RDAREA batch specification, see the manual HiRDB Version 9 Command Reference to determine how to correctly specify a pattern character string, and then re-execute the command.

KFPT02003-E E

aa....aa:option flag bb....bb not specified in command line

No specification for a required option flag was found in the command line.

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

bb....bb: Required option flag

S: Terminates processing.

O: Correct the option specification, and then re-execute.

KFPT02004-W E

aa....aa:no data, RDAREA="bb....bb",server=cc....cc

There is no table, index, or LOB data in the specified RDAREA.

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

bb....bb: RDAREA name

cc....cc: Server name

S: Continues processing.

O: Check the specified RDAREA name.

KFPT02005-E E+L

aa....aa:not original RDAREA, RDAREA="bb....bb",server=cc....cc

The specified RDAREA is not the original RDAREA.

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

bb....bb: RDAREA name

cc....cc: Server name

S: Terminates processing. However, if this message is output by an application condition check (pdorcheck command) for online reorganization, processing terminates after all RDAREAs specified in the option have been checked.

O: Specify the original RDAREA, and then re-execute.

KFPT02006-E E

aa....aa:number of bb....bb exceeds cc....cc

The specified number of bb....bb exceeds maximum value cc....cc.

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

bb....bb: Type of specified value

server names: Server name

RDAREA names: RDAREA name

table names: Table name

cc....cc: Maximum specifiable value

S: Terminates processing.

O: Check the number of specified bb....bb, correct this number, and then re-execute the command.

KFPT02007-E E

aa....aa:error exists in command line

An invalid specification value with no option flag was found in the specified command line.

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

S: Terminates processing.

O: See the usage of the command output after this message, correct the error, and then re-execute the command.

KFPT02008-E E

Pdrdrefls:invalid AUTHID in PDUSER

The authorization identifier set in environment variable PDUSER is invalid.
This message is output in the following cases:

The specified value exceeds the maximum length.

The content of the specified value is invalid.

The character code of the specified value is invalid.

S: Terminates processing.

O: Correct the environment variable PDUSER, and then re-execute the command. For details about PDUSER, see the HiRDB Version 9 UAP Development Guide.

KFPT02009-I E

Usage: pdrdrefls [-k dsp] -e org {-r RDAREA_name[,RDAREA_name, ...] |-r ALL |-t [auth_id.]table_name} [-s server_name[,server_name, ...]] [-l [-d separator]] [-a] [-c constraint_type]

Indicates the specification format of the pdrdrefls command (-k dsp). This message is output when the specification format of the command is invalid.

S: Terminates processing.

O: Correct the specification format of the pdrdrefls command, and then re-execute.

KFPT02010-I E

Usage: pdrdrefls -k chk -e org {-r RDAREA_name[,RDAREA_name, ...] |-r ALL} [-s server_name[,server_name, ...]] [-c constraint_type]

Indicates the specification format of the pdrdrefls command (-k chk). This message is output when the specification format of the command is invalid.

S: Terminates processing.

O: Correct the specification format of the pdrdrefls command, and then re-execute.

KFPT02012-I E

Usage: pdorcheck {-r RDAREA_name[,RDAREA_name, ...] |-r ALL}

Indicates the specification format of the pdorcheck command. This message is output when the specification format of the command is invalid.

S: Terminates processing.

O: Correct the specification format of the pdorcheck command, and then re-execute.

KFPT02014-I E+L

Pdorcreate terminated, return code=a

Creation of the discrepancies application environment for online reorganization terminated.

a: Return code

0: Normal termination

8: Abnormal termination

S: Terminates processing.

O: If the return code is 8, eliminate the cause of the error based on the E-level message output during processing, and then re-execute.

KFPT02015-I E

Usage: pdorcreate {[-r RDAREA_name[,RDAREA_name, ...]] -o RDAREA_name | -d}

Indicates the specification format of the pdorcreate command. This message is output when the specification format of the command is invalid.

S: Terminates processing.

O: Correct the specification format of the pdorcreate command, and then re-execute.

KFPT02016-E E+L

aa....aa:unable to execute Online DB Reorganization, reason=bb....bb,resource kind=cc....cc,name=dd....dd

Updatable online reorganization could not be executed.

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

bb....bb: Reason

"invalid datatype": A data type not subject to processing is defined.

"unique index": The UNIQUE specification index required to execute updatable online reorganization is not defined.

"invalid RECOVERY type": The update log acquisition mode of the RDAREA for storing LOB columns is defined by a mode other than the log acquisition mode (ALL).

cc....cc: Resource type

table: Table

dd....dd: Name of resource not meeting the application condition:

Resource type is table: "authorization-identifier"."table-identifier"

S: Continues processing.

O: Contact the HiRDB administrator.

Action

If bb....bb is "invalid datatype":

Check the data type of the configuration column in the table output by the applicable resource name, and then take one of the following actions:

Define the table output by the applicable resource name in another RDAREA not subject to updatable online reorganization.

Change the table output by the applicable resource name to a data type that can perform updatable online reorganization. For details about the data types on which updatable online reorganization can be performed, see the description of the pdorcheck command in the manual HiRDB Version 9 Command Reference.

If bb....bb is "unique index":

Take one of the following actions on a table output by the applicable resource name:

Define one of the following indexes:

A primary key index not including in the configuration columns VARCHAR or MVARCHAR with a definition length of 256 bytes or more, nor an NVARCHAR column with a definition length of 128 characters or more

A cluster key index specifying PRIMARY not including in the configuration columns VARCHAR or MVARCHAR with a definition length of 256 bytes or more, nor an NVARCHAR column with a definition length of 128 characters or more

A cluster key index specifying UNIQUE not including in the configuration columns VARCHAR or MVARCHAR with a definition length of 256 bytes or more, nor an NVARCHAR column with a definition length of 128 characters or more

An index specifying UNIQUE not including in the configuration columns (all configuration columns having the NOT NULL constraint) VARCHAR or MVARCHAR with a definition length of 256 bytes or more, nor an NVARCHAR column with a definition length of 128 characters or more

Define the table output by the applicable resource name in another RDAREA not subject to updatable online reorganization.

If bb....bb is "invalid RECOVERY type":

Check the data type of the configuration columns for the table output by the applicable resource name, and then take one of the following actions:

Define the table output by the applicable resource name in another RDAREA not subject to updatable online reorganization.

Execute DROP TABLE on a table output by the applicable resource name, set the column recovery restriction for all columns defined in the user LOB RDAREA to ALL, and then redefine the table.

KFPT02017-E E+L

aa....aa:invalid execution node

Server machine attempting to execute command aa....aa is invalid.

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

S: Terminates processing.

O: For HiRDB/Single Servers, execute the command from a server machine with Single servers. For HiRDB/Parallel Servers, execute the command from a server machine with the system manager.

KFPT02018-W E+L

Pdorcreate:reflection management table already aaaaaaa

If aaaaaaa is created:
The reflection management table was already created.

If aaaaaaa is dropped:
The reflection management table was already deleted or cannot be created.

aaaaaaa: Status type

created: Created

dropped: Deleted or was not created

S: Terminates processing.

KFPT02019-E E+L

aa....aa:specified value not found in system, bb....bb=cc....cc

The specified name cc....cc was not found in the HiRDB system.
When bb....bb is table, cc....cc might be one of the following tables:

A viewed table

A dictionary table

A temporary table

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

bb....bb: cc....cc type

server: Server

RDAREA: RDAREA

table: Table

cc....cc: The specified identifier name (names other than the server name are enclosed in double quotation marks ("))

S: Performs one of the following:

pdorcheck command:

If what is output in cc....cc is a batch-specified RDAREA name, processing terminates.

Otherwise, processing continues until all RDAREAs specified in the option have been checked.

pdorcreate command or pdrdrefls command:

Terminates processing.

O: Check whether the specified name is defined in HiRDB, and whether it is a permissible identifier. Specify the correct name, and then re-execute the command.

If ALL is output as the RDAREA name, take one of the following actions:

If the option allows ALL to be specified
If ALL is specified at the beginning, re-execute the command in a state in which the RDAREAs that are the target of the command exist.
If multiple RDAREA names are specified and ALL is specified as the second or subsequent RDAREA name, specify ALL by itself and re-execute the command.

If the option does not allow ALL to be specified
Delete ALL, or change it to the correct name, and then re-execute the command.

KFPT02020-I E+L

Pdorcreate:reflection management table aaaaaaa

Creation process or deletion process of the reflection management table is complete.

aaaaaaa: Status type

created: Created

dropped: Dropped

S: Continues processing.

KFPT02021-E E+L

aa....aa:invalid RDAREA type, name="bb....bb"

RDAREA "bb....bb" is not a user RDAREA or user LOB RDAREA.

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

bb....bb: RDAREA name

S: Terminates processing. If this message is output by an application condition check (pdorcheck command) for online reorganization, processing terminates after all RDAREAs specified in the option have been checked.

O: Check the specified RDAREA name, specify the correct name, and then re-execute the command.

KFPT02022-I E+L

Pdorcheck:all resources conformed to Online DB Reorganization

All resources in the specified RDAREA are subject to updatable online reorganization.

S: Continues processing.

KFPT02023-W E+L

Pdorcreate:unable to delete environment of Online DB Reorganization, reason=aa....aa,server=bb....bb

A discrepancies application environment for online reorganization could not be deleted.

aa....aa: Reason

EXECUTING ORG: No servers are executing updatable online reorganization

bb....bb: Server name

S: Continues processing.

O: Execute the pddbls command, and then check the status of all RDAREAs defined at the server output by bb....bb. Reply as follows to the dialog message (KFPT02024-Q) prompt output immediately after this message:

If there is an RDAREA in online reorganization hold status:
Enter n at the dialog input prompt, wait for updatable online reorganization to terminate, and then re-execute the command.

If there is no RDAREA in online reorganization hold status:
Enter y at the dialog input prompt, and then continue the deletion process.

KFPT02024-Q E+L

Pdorcreate:command will delete environment of Online DB Reorganization by force. If RDAREA in Online DB Reorganization hold status exists, delete operation may destroy DB. Do you really want to proceed?(y/n)

This is a prompt message asking whether or not to forcibly delete the execution environment for updatable online reorganization.
If there is an RDAREA that is in online reorganization hold status, be careful, because specifying y may damage the database.

S: Continues processing if the user entered y. Terminates processing if the user entered n or any other value beside y or n.

O:

Check if the status of all RDAREAs belonging to the server for the KFPT02023-W message output immediately before this message is in online reorganization hold status.

If no RDAREAs are in online reorganization hold status, enter y. If some RDAREAs are in online reorganization hold status, enter n.

The status of the RDAREA can be checked using the pddbls command.

KFPT02025-E E+L

Pdorcreate:plural RDAREAs defined for same server specified, server=aa....aa, RDAREA="bb....bb" and "cc....cc"

Multiple RDAREAs on the same server were specified.

aa....aa: Server name

bb....bb: RDAREA name on server aa....aa

cc....cc: RDAREA name on server aa....aa

S: Terminates processing.

O: Remove specified RDAREA aa....aa or "bb....bb" from the specification in the -r option, and then re-execute the command.

KFPT02026-I E+L

Pdorcreate:dropping reflection management table canceled

Dropping of the reflection management table was cancelled.

S: Continues processing.

KFPT02027-E E+L

aa....aa:replicated RDAREA not defined, name="bb....bb"

No replica RDAREA is defined in RDAREA "bb....bb".

aa....aa: Command name (see the command name in the embedded characters of KFPT00001-E)

bb....bb: RDAREA name

S: Terminates processing. If this message is output by an application condition check (pdorcheck command) for online reorganization, processing terminates after all RDAREAs specified in the option have been checked.

O: Define a replica RDAREA in RDAREA "bb....bb", and then re-execute the command.

KFPT02028-W E

Pdrdrefls:insufficient specification of RDAREA about relation, relation kind=aaa, required RDAREA name="bb....bb"

Specification of RDAREA is insufficient for the relation indicated by aaa.

aaa: Relation type

org: Relation to updatable online reorganization

bb....bb: Specified RDAREA name

S: Terminates processing.

O: Add the RDAREA name output by this message, and then re-execute the command. Alternatively, execute the pdrdrefls -k dsp command to check the related resources.

KFPT02029-W E

Pdrdrefls:all specified RDAREAs unsatisfied condition of aa option

No specified RDAREAs meet the conditions for the aa option.

aa: Option name of condition

-s: Server name

S: Continues processing.

O: Check the aa option specification and the RDAREA specified by the option, correct the option, and then re-execute the command.

KFPT02030-W E

Pdrdrefls:all table RDAREAs of specified table unsatisfied condition of aa option

No RDAREAs for table storage in the specified table meet the conditions of the aa option.

aa: Option name of condition

-s: Server name

S: Continues processing.

O: Check the specification content of the aa option and the content of the RDAREA storing the table specified by the option, correct the content, and then re-execute the command.

KFPT02031-E E+L

Pdrdrefls:RDAREA unsatisfied condition of option aa specified, RDAREA=bb....bb

The RDAREA specified by option aa does not meet the conditions.

aa: Option name of condition

-s: Server name

bb....bb: RDAREA name that does not meet the conditions

S: Checks if the command is executable by the aa option on all RDAREAs specified by the option, and then terminates processing.

O: Check the specification content of the aa option and the content of the RDAREA specified by the option, correct the content, and then re-execute the command.

KFPT02032-E E

aa....aa:not available without specification of bb....bb operand

Command aa....aa could not be executed because the bb....bb operand is not defined in the system definition.

aa....aa: Command name

pdorcreate: Creates the discrepancies application environment of online reorganization

pdorcheck: Application condition check of online reorganization

bb....bb: Operand of the system definition

pd_inner_replica_control: Maximum number of inner replica groups

pd_max_reflect_process_count: Number of processes secured during discrepancies application processing

S: Terminates processing.

O: Terminate HiRDB, add the system definition operand, and then start HiRDB. Then, re-execute the command.

KFPT02034-E E+L

aa....aa:invalid RDAREA, name="bb....bb", reason="cc....cc"

The specified RDAREA is not a valid execution target for the command.

aa....aa: Command name

pdorcheck: Application condition check for online reorganization

pdorcreate: Create a reflection processing environment for online reorganization

pdrdrefls: Display information of related RDAREAs

pdorend: Reflection processing for online reorganization

bb....bb: Name of RDAREA

cc....cc: Reason

RDAREA for temporary table: The temporary table RDAREA is displayed.

S: Terminates processing. However, if this message is output by an application condition check (pdorcheck command) for online reorganization, processing terminates after all RDAREAs specified in the option have been checked.

O: Change the RDAREA indicated in bb....bb to an RDAREA that can be executed by aa....aa, and then re-execute the command.

2.15 KFPU messages

KFPU00200-E E+L

Invalid option is specified with this command

An invalid option was specified in the command. Or, an option argument was not specified.

S: Cancels command processing.

O: Specify the correct option or option argument, and then re-execute the command.

KFPU00201-E E

Number of command arguments or options exceeds the limit

Reduce the number of options to no more than 32 or the number of command arguments to no more than 64.

S: Cancels command processing.

O: Reduce the number of command arguments or options to no more than the maximum number and re-execute.

KFPU00202-E E

Length of cc....cc arguments bb....bb exceeds the limit aa....aa

Reduce the total length of command arguments or option arguments to no more than 4,096 characters.

aa....aa: The total length of command arguments or flag arguments that can be specified (bytes)

bb....bb: The total length of the command arguments or flag arguments that caused the error (bytes)

cc....cc: Type of argument

command: command argument

flag: flag argument

S: Cancels command processing.

O: Specify command arguments or flag arguments whose total length does not exceed aa....aa, and then retry the operation.

KFPU00210-W E+L

Argument bb....bb of aa....aa function incorrect

Argument bb....bb is invalid in function aa....aa.

aa....aa:

pdi_umt_malloc: Module trace buffer allocation request

pdi_urt_open: RPC trace buffer open request

pdi_uat_malloc: UAP trace buffer allocation request

bb....bb:

trnum: Maximum number of module or UAP trace information items that can be stored

file: RPC trace file name

size: RPC trace file switching size

flags: RPC trace file attribute in effect when the file is opened

S: Resumes processing without collecting trace information.

P: Check the HiRDB installation for an error.

KFPU00211-W E+L

Function aa....aa already issued

Function aa....aa has already been issued.

aa....aa:

pdi_umt_malloc: Module trace buffer allocation request

pdi_urt_open: RPC trace buffer open request

S: Resumes processing.

KFPU00212-W E+L

Unable to perform tracing due to buffer allocation for aa....aa failed. process ID=bb, buffer size=cc....cc

Trace information is not being collected, because a buffer for aa....aa could not be allocated in the process private area.

aa....aa: Type of processing:

MODULE TRACE: Module trace

UAP TRACE: UAP trace

bb....bb: Process ID for which buffer could not be allocated

cc....cc: Size of buffer that was to be allocated

S: Resumes processing without collecting trace information.

P: If trace collection is not necessary, resume processing. If trace collection is necessary, terminate the corresponding process and check the size of the trace buffer.

KFPU00215-E E+L

Unable to open analysis file. analysis file=aa....aa, errno=bbb

An analysis file required for definition information analysis cannot be opened.

aa....aa: Analysis file name

bbb: Error number (errno)

(if the error number is 0, the specified path name is invalid).

S: Cancels definition file analysis processing.

O: Contact the HiRDB administrator.

Action

Eliminate the cause of the error, and then restart HiRDB.

KFPU00216-E E+L

Incorrect variable. file=aa....aa, line=bb....bb, variable=cc....cc

A specified variable value in a definition file is invalid.

aa....aa: Definition file name

bb....bb: Erroneous line

cc....cc: Variable name

S: Cancels analysis of the definition information resulting in the error.

O: Contact the HiRDB administrator.

Action

Check the specification format of the corresponding variable and correct the error.

KFPU00217-E E+L

Command name invalid. file=aa....aa, line=bb....bb, command=cc....cc

A command specified in a definition file cannot be analyzed.

aa....aa: Definition file name

bb....bb: Erroneous line

cc....cc: Command name

S: Cancels analysis of the definition information resulting in the error.

O: Contact the HiRDB administrator.

Action

Check the specification format of the corresponding command and correct the error.

KFPU00218-E E+L

Option name in definition file invalid. file=aa....aa, line=bb....bb, option=cc....cc

A specified option name in a definition file is invalid.

aa....aa: Definition file name

bb....bb: Erroneous line

cc....cc: Option name

S: Cancels analysis of the definition information resulting in the error.

O: Contact the HiRDB administrator.

Action

Check the specification format of the corresponding option and correct the error.

KFPU00219-E E+L

Command argument invalid. file=aa....aa, line=bb....bb, command=cc....cc

A command argument is invalid.

aa....aa: Definition file name

bb....bb: Erroneous line

cc....cc: Command name

S: Cancels analysis of the definition information resulting in the error.

O: Contact the HiRDB administrator.

Action

Check the specification format of the corresponding command and correct the argument.

KFPU00220-E E+L

Option argument invalid. file=aa....aa, line=bb....bb, option=cc....cc

An option argument is invalid.

aa....aa: Definition file name

bb....bb: Erroneous line

cc....cc: Option name

S: Cancels analysis of the definition information resulting in the error.

O: Contact the HiRDB administrator.

Action

Check the specification format of the corresponding option and correct the argument.

KFPU00221-E E+L

Unable to analyze definition file due to insufficient memory. memory requirement=aa....aa

A memory shortage occurred during definition file analysis processing.

aa....aa: Size of memory to be allocated when the error occurred

S: Cancels definition file analysis processing.

O: Contact the HiRDB administrator.

Action

Change the process size so that the maximum process size allowed by the system is not exceeded, and then restart HiRDB.

KFPU00222-E E+L

Number of nests in definition file exceeds the limit. file=aa....aa, line=bb....bb

The maximum number of nesting levels in a definition file was exceeded.

aa....aa: Definition file name

bb....bb: Erroneous line

S: Cancels analysis of the definition information resulting in the error.

O: Contact the HiRDB administrator.

Action

Check the include command utilization status and correct the information in the definition file so that the number of nesting levels does not exceed 5.

KFPU00223-E E+L

Option aa....aa specified twice. file=bb....bb, line=cc....cc

An option is duplicated.

aa....aa: Definition file name

bb....bb: Erroneous line

cc....cc: Option name

S: Cancels analysis of the definition information resulting in the error.

O: Contact the HiRDB administrator.

Action

Check the option specifications. If the same option is specified more than once, delete one of them.

KFPU00224-E E

Error occurred in system call (function) aa....aa. errno=bb....bb, function (command) name=cc....cc

A system call issued from within the program or a HiRDB function resulted in an error.

aa....aa: Name of the issued system call or HiRDB function

bb....bb: Return code of the system call or function

cc....cc: Name of the HiRDB function or command resulting in the error

S: Cancels processing and returns control to the calling source.

O: Refer to the return code to check the cause of the error. Also, output the module trace or core file.

Action

Refer to the return information to check the cause of the error, and correct the program; alternatively modify the system definition.

KFPU00240-E E+L

Unable to set environmental variable. file=aa....aa, line=bb....bb

A variable environment variable is invalid.

aa....aa: File name

bb....bb: Erroneous line

S: Cancels analysis of the definition information resulting in the error.

O: Contact the HiRDB administrator.

Action

Check the format of the putenv operand in the system common definition and correct the environment variable.

KFPU00241-E E+L

I/O error occurred. file=aa....aa

An error occurred while reading a definition file and analysis file in order to analyze the definition information.

aa....aa: File name

S: Cancels definition file analysis processing.

O: Contact the HiRDB administrator.

Action

Eliminate the cause of the error, and then restart HiRDB.

KFPU00242-E E+L

Unable to open definition file. definition file=aa....aa, errno=bbb

A definition file cannot be opened.

aa....aa: Name of definition information file

bbb: Error number (errno)

(if the error number is 0, the specified absolute pathname is invalid)

S: Cancels analysis of the definition file resulting in the error.

O: Contact the HiRDB administrator.

Action

Check the specification format of the corresponding file and correct the file name and absolute pathname.

KFPU00243-E E+L

Record length exceeds the limit. file=aa....aa, line=bb....bb

The length of a definition information record exceeds the maximum (80 bytes).

aa....aa: File name

bb....bb: Erroneous line

S: Cancels analysis of the definition information resulting in the error.

O: Contact the HiRDB administrator.

Action

Check the specification format of the corresponding definition information and correct its length to no more than 80 bytes. Or, use a continuation line to specify the information.

KFPU00244-E E+L

Variable name specified wrong. file=aa....aa, line=bb....bb

A variable cannot be analyzed due to one of the following errors:

No variable name is specified.

The specified variable name is invalid.

aa....aa: File name

bb....bb: Erroneous line

S: Cancels analysis of the definition information resulting in the error.

O: Contact the HiRDB administrator.

Action

Specify the correct variable name. Or, check the relationship between the definition file and the defined information for an error.

KFPU00245-E E+L

Unable to open definition file specified with include. file=aa....aa, line=bb....bb, definition file=cc....cc, errno=ddd

The definition file specified in include cannot be opened.

aa....aa: File name

bb....bb: Erroneous line

cc....cc: Definition file name

ddd: Error number (errno)

(if the error number is 0, the specified absolute pathname is invalid)

S: Cancels analysis of the definition information resulting in the error.

O: Contact the HiRDB administrator.

Action

Check the specification format of the corresponding file and correct the file name and absolute pathname.

KFPU00246-E E+L

Definition aa....aa described wrong. file=bb....bb, line=cc....cc

Specification format of aa....aa is invalid.

aa....aa: Name of the erroneous definition (set, putenv, etc.)

bb....bb: File name

cc....cc: Erroneous line

S: Cancels analysis of the definition information resulting in the error.

O: Contact the HiRDB administrator.

Action

Check the specification format of the corresponding definition and correct the error.

KFPU00247-E E+L

Command name aa....aa invalid

A command name is invalid.

aa....aa: Command name

S: Cancels processing of the erroneous command.

O: Check the corresponding command name, correct the error, and then re-execute.

KFPU00248-E E+L

Option name in aa....aa command invalid

An option name is invalid.

aa....aa: Command name

S: Cancels processing of the erroneous command.

O: Check the option name in the command resulting in the error, correct the option name, and then re-execute.

KFPU00249-E E+L

Command argument invalid. command=aa....aa

A command argument is invalid.

aa....aa: Command name

S: Cancels processing of the erroneous command.

O: Check the argument in the command resulting in the error, correct the argument, and then re-execute.

KFPU00250-E E+L

Option argument invalid. option=aa....aa

An option argument is invalid.

aa....aa: Option name

S: Cancels processing of the erroneous command.

O: Check the option argument of the command resulting in the error, correct the argument, and then re-execute.

KFPU00251-E E+L

Option specified twice. command=aa....aa

An option is duplicated.

aa....aa: Command name

S: Cancels the processing of erroneous command.

O: Check the option specifications.

If the same option is specified more than once, delete one of them and re-execute the command.

KFPU00252-E E

Unable to analyze definition file due to PDDIR not specified, user=aa....aa

The definition file could not be analyzed because the environment variable PDDIR was not set.

aa....aa: Login user name executing the process

S: Terminates processing.

O: Re-evaluate if the environment variable PDDIR is set in the login shell environment of the user executing the process. If execution of the command fails, set the environment variable PDDIR, and then re-execute.

2.16 KFPX messages

KFPX14004-E L

Line aaaa:bb....bb operand value cc....cc invalid

Operand bb....bb is invalid.

aaaa: Line number

bb....bb: Operand name

cc....cc: Invalid operand value

S: Terminates processing after analyzing all the specified control statements.

Action

Correct the operand in the control statement and re-execute.

KFPX14017-E L

No control statements

The specified control statements file contains no control statements.

S: Terminates processing.

Action

Specify control statements in the control statements file and re-execute.

KFPX14018-E L

Specified control statement incomplete

A semicolon (;) was specified before the end of a control statement.

S: Terminates processing after analyzing all the specified control statements.

Action

Correct the control statement and re-execute.

KFPX14019-E L

Unable to omit aa....aa RDAREA

An RDAREA required for the database initialization utility is missing.

aa....aa: Type of RDAREA:

datadictionary: Data dictionary RDAREA

datadictionary(LOB): Data dictionary LOB RDAREA

datadirectory: Data directory RDAREA

masterdirectory: Master directory RDAREA

S: Terminates processing after analyzing all the specified control statements.

Action

Specify the displayed RDAREA (aa....aa) with the create rdarea statement and re-execute. Specify two data dictionary LOB RDAREAs.

KFPX14020-E L

Line aaaa:bb....bb operand value cc....cc duplicate

Value cc....cc specified in operand bb....bb has already been specified.

aaaa: Line number

bb....bb: Operand keyword

cc....cc: Duplicated operand value

S: Terminates processing after analyzing all the specified control statements.

Action

Delete the unnecessary operand value (cc....cc) and re-execute.

KFPX14023-E L

Line aaaa:number of bb....bb rdarea exceeds cccc

The number of bb....bb RDAREAs exceeded the maximum of cccc.

aaaa: Line number

bb....bb: Type of RDAREA:

datadictionary: Data dictionary RDAREA

datadictionary (LOB): Data dictionary LOB RDAREA

datadictionary of routines: Data dictionary RDAREA specifying routines

datadirectory: Data directory RDAREA

masterdirectory: Master directory RDAREA

cccc: Maximum number of RDAREAs

S: Terminates processing after analyzing all the specified control statements.

Action

Correct the number of RDAREAs so that the maximum is not exceeded and re-execute.

KFPX14024-E L

Line aaaa:required bb....bb operand not specified

Required operand bb....bb is missing.

aaaa: Line number

bb....bb: Required operand

S: Terminates processing after analyzing all the specified control statements.

Action

Specify the required operand and re-execute.

KFPX14025-E L

Line aaaa:number of parameters in bb....bb operand exceeds cccc

The number of parameters in operand bb....bb exceeds the maximum value cccc.

aaaa: Line number

bb....bb: Operand name

cccc: Maximum number of parameters

S: Terminates processing after analyzing all the specified control statements.

Action

Correct the number of parameters so that the maximum is not exceeded and re-execute.

KFPX14026-E L

Line aaaa:invalid string "bb....bb" in statement cc....cc

Invalid character string "bb....bb" was found in control statement cc....cc.

aaaa: Line number

bb....bb: Invalid character string

cc....cc: Name of the control statement containing the invalid character string

S: Terminates processing after analyzing all the specified control statements.

Action

Delete the invalid character string ("bb....bb") and re-execute.

KFPX14027-E L

Line aaaa:duplicate bb....bb operand

Operand bb....bb is duplicated.

aaaa: Line number

bb....bb: Operand name

S: Terminates processing after analyzing all the specified control statements.

Action

Delete the duplicated operand and re-execute.

KFPX14029-E L

Line aaaa:number of bb....bb operands exceeds cccc

The number of operands bb....bb exceeded the maximum of cccc.

aaaa: Line number

bb....bb: Operand name

cccc: Maximum number of operands

S: Terminates processing after analyzing all the specified control statements.

Action

Correct the number of operands so that the maximum is not exceeded and re-execute.

KFPX14030-E L

Line aaaa:invalid bb....bb statement

An invalid control statement was detected.

aaaa: Line number

bb....bb: Detected invalid control statement

S: Terminates processing after analyzing all the specified control statements.

Action

Correct the control statement and re-execute.

KFPX14031-E E

Line aaaa:control statements out of sequence

The input sequence of control statements is invalid.

aaaa: Line number

S: Terminates processing after analyzing all the specified control statements.

Action

Rearrange the control statements in the correct sequence and re-execute the statements.

RDAREAs must be specified in the following sequence:

Master directory

Data directory

Data dictionary

Data dictionary (LOB)

User

LOB

LIST

Note

Nos. 5, 6, and 7 may be specified in any order.

KFPX14035-E L

Line aaaa:mismatched double quotations in bb....bb

Quotation marks (") are not correctly paired for operand value bb....bb in a control statement.

aaaa: Line number

bb....bb: Specified operand value

S: Terminates processing after analyzing all the specified control statements.

Action

Correct the quotation marks and re-execute.

KFPX14045-W L

Line aaaa:page size raised to bb....bb

A page length was rounded up to bb....bb, because it was not a multiple of 2048.

aaaa: Line number

bb....bb: Assumed value

S: Resumes processing, assuming the indicated page length.

Action

Specify a multiple of 2048 as the page length in the page bb....bb characters operand of the create rdarea statement.

KFPX14046-W L

Line aaaa: bb pages assumed for segment size

The system constant 50 was assumed for the segment length of the master directory RDAREA or the data directory RDAREA. Or, the system constant 1 was assumed for the segment length of the LOB RDAREA.

aaaa: Line number

bb: Assumed value for segment length { 1|50 }

S:

Master directory RDAREA or data directory RDAREA:

Resumes processing with 50 as the segment length.

LOB RDAREA:

Resumes processing with 1 as the segment length.

Action

Correct to bb the segment length in the storage control segment operand of the create rdarea statement.

Master directory RDAREA or data directory RDAREA:

Set the segment length value to 50.

LOB RDAREA:

Set the segment length value to 1.

KFPX14047-W L

Line aaaa:missing semicolon assumed

A semicolon (;) was assumed, because it was missing at the end of a control statement.

aaaa: Line number

S: Resumes processing.

Action

Specify a semicolon (;).

KFPX14051-E L

Too small RDAREA size, RDAREA name aa....aa, size=bbbb

There are not enough units for the number of segments in RDAREA aa....aa.

aa....aa: RDAREA name

bbbb: Required number of segments

S: Terminates processing.

Action

Specify a value of at least bbbb in the initial operand of the control statement and re-execute.

KFPX14078-W L

Line aaaa: extension nouse assumed

The automatic extension facility can be specified only for the types of RDAREAs listed below. Because another type of RDAREA was specified, nouse was assumed for the extension operand specification value.

Data dictionary RDAREA

Data dictionary LOB RDAREA

User RDAREA

User LOB RDAREA

Registry RDAREA

Registry LOB RDAREA

aaaa: Line number

S: Continues processing.

Action

Correct to nouse the specification value of the extension operand in the create rdarea statement.

KFPX14204-E L

Line aaaa:bb....bb operand value cc....cc invalid

Specified operand bb....bb is invalid.

aaaa: Line number

bb....bb: Operand name

cc....cc: Invalid operand value

S: Terminates processing after analyzing all the specified control statements.

Action

Correct the operand value in the control statement and re-execute.

KFPX14217-E L

No control statements

Specified control statements file contains no control statements.

S: Terminates processing.

Action

Specify control statements in the control statements file and re-execute.

KFPX14218-E L

Specified control statement incomplete

A semicolon (;) was specified before the end of a control statement.

S: Terminates processing after analyzing all the specified control statements.

Action

Correct the control statement and re-execute.

KFPX14220-E L

Line aaaa:bb....bb operand value cc....cc duplicate

Value cc....cc specified in operand bb....bb has already been specified or already exists in the system.

aaaa: Line number

bb....bb: Operand keyword

cc....cc: Duplicate operand value

S: Terminates processing after analyzing all the specified control statements.

Action

Delete the unnecessary operand value (cc....cc) and re-execute.

KFPX14223-E L

Line aaaa:number of bb....bb rdarea exceeds cccc

The number of RDAREAs of type bb....bb exceeded the maximum value of cccc.

aaaa: Line number

bb....bb: Type of RDAREA:

datadictionary (LOB): Data dictionary LOB RDAREAs

datadictionary of routines: Data dictionary RDAREAs specifying routines

registry: Registry RDAREA

registry (LOB): Registry LOB RDAREA

datadictionary of dbmanagement: Data dictionary RDAREA with a dbmanagement specification

cccc: Maximum number of RDAREAs of the indicated type

S: Terminates processing.

Action

Correct the number of RDAREAs so that the maximum is not exceeded and re-execute.

KFPX14224-E L

Line aaaa:required bb....bb operand not specified

Required operand bb....bb is missing.

aaaa: Line number

bb....bb: Required operand

S: Terminates processing after analyzing all the specified control statements.

Action

Specify the required operand and re-execute.

KFPX14225-E L

Line aaaa:number of parameters in bb....bb operand exceeds cccc

The number of parameters in operand bb....bb exceeds the maximum of cccc.

aaaa: Line number

bb....bb: Operand name

cccc: Maximum number of parameters

S: Terminates processing after analyzing all the specified control statements.

Action

Correct the number of parameters so that the maximum is not exceeded and re-execute.

KFPX14226-E L

Line aaaa:invalid string "bb....bb" in statement cc....cc

Control statement cc....cc contains invalid character string "bb....bb".

aaaa: Line number

bb....bb: Invalid character string

cc....cc: Name of the control statement containing the invalid character string

S: Terminates processing after analyzing all the specified control statements.

Action

Delete the invalid character string ("bb....bb") and re-execute.

KFPX14227-E L

Line aaaa:duplicate bb....bb operand

Operand bb....bb is duplicated.

aaaa: Line number

bb....bb: Operand name

S: Terminates processing after analyzing all the specified control statements.

Action

Delete the duplicated operand and re-execute.

KFPX14229-E L

Line aaaa:number of bb....bb operands exceeds cccc

The number of operands bb....bb exceeded the maximum of cccc.

aaaa: Line number

bb....bb: Operand name

cccc: Maximum number of operands

S: Terminates processing after analyzing all the specified control statements.

Action

Correct the number of operands so that the maximum is not exceeded and re-execute.

KFPX14230-E L

Line aaaa:invalid bb....bb statement

An invalid control statement was detected.

aaaa: Line number

bb....bb: Detected invalid control statement

S: Terminates processing after analyzing all the specified control statements.

Action

Correct the control statement and re-execute.

KFPX14235-E L

Line aaaa:mismatched double quotations in bb....bb

Quotation marks (") are not correctly paired for operand value bb....bb in a control statement.

aaaa: Line number

bb....bb: Specified operand value

S: Terminates processing after analyzing all the specified control statements.

Action

Correct the quotation marks and re-execute.

KFPX14236-E L

Unable to aa....aa rdarea due to invalid RDAREA status[, server name= bb....bb]

Structure modification processing aa....aa cannot be executed due to invalid RDAREA status.

aa....aa: Structure modification processing:

alter: Modification

expand: Expansion

initialize: Re-initialization

remove: Deletion

define copy: Copy configuration information

recast: Integrate

replicate: Replica definition

move: Move

bb....bb: Server name (this is output only for a shared RDAREA)

S: Cancels structure modification processing for the corresponding RDAREA and processes the next control statement.

Action

When the RDAREA that is the target of structure modification is in-memory:

Release in-memory allocation of the RDAREA, and then retry the operation.

When the RDAREA that is the target of structure modification is not in-memory:

Place the RDAREA on the following status and re-execute:

alter: Closed status or command shutdown status

expand: Open status or command shutdown status (non-shutdown or hold)

initialize: Closed and command shutdown status or error shutdown status

remove: Closed and command shutdown status or error shutdown status

define copy: Closed and command shutdown status

recast: Closed and command shutdown status

move: Closed and command shutdown status

KFPX14238-E L

Unable to aa....aa "bb....bb" due to invalid RDAREA type

Because the RDAREA type is invalid for RDAREA "bb....bb", structure modification processing aa....aa cannot be executed.

aa....aa: Structure modification processing:

initialize: Reinitialize the RDAREA

remove: Delete the RDAREA

replicate: RDAREA replica definition

define copy: Copy RDAREA configuration information

move: Move the RDAREA

create audit table: Create an audit trail table for the RDAREA

alter: Modify the RDAREA

bb....bb: RDAREA name

S: Cancels structure modification processing for the corresponding RDAREA and resumes processing.

Action

See Functions of the database structure modification utility in the manual HiRDB Version 9 Command Reference, to determine how to specify an RDAREA on which structure modification can be executed, and then retry the operation.

KFPX14245-W L

Line aaaa: page size raised to bb....bb

A page length was rounded up to bb....bb, because it was not a multiple of 2048.

aaaa: Line number

bb....bb: Assumed value

S: Assumes the indicated page length and resumes processing.

Action

Specify a multiple of 2048 as the page length in the page bb....bb characters operand of the create rdarea statement.

KFPX14246-W L

Line aaaa: bb pages assumed for segment size

The system constant 1 was assumed as the segment length of the LOB RDAREA.

aaaa: Line number

bb: Assumed segment length value

S: Resumes processing with 1 as the segment length.

P: Correct to 1 the segment length value in the storage control segment operand of the create rdarea statement.

KFPX14247-W L

Line aaaa:missing semicolon assumed

A semicolon (;) was assumed, because it was missing at the end of a control statement.

aaaa: Line number

S: Resumes processing.

Action

Specify a semicolon (;).

KFPX14250-I L

Processing of [aa....aa] statement ended return code=bb[, RDAREA name ="cc....cc"[to dd....dd]]

Structure modification utility function bb....bb terminated with return code bb.

aa....aa: Database structure modification utility function (this information may not be displayed in the event of a control statement analysis error):

alter rdarea: RDAREA modification

alter HiRDB mode: Conversion from single to parallel

alter system: Modification of system definitions

create rdarea: RDAREA addition

expand rdarea: RDAREA expansion

initialize rdarea: RDAREA re-initialization

remove rdarea: RDAREA deletion

create generation: HiRDB file system area generation registration

remove generation: HiRDB file system area generation removal

replicate rdarea: RDAREA replica definition

define copy rdarea: RDAREA configuration information copying

recast rdarea: RDAREA integration

move rdarea: RDAREA moving

create auditor: Auditor registration

create audit table: Audit trail table creation

bb: Return code:

0: Normal termination

4: Warning error occurred, but processing terminated

8: Terminated abnormally (refer to the output error message to eliminate the cause of the error, and then re-execute)

cc....cc: RDAREA name

In some cases, this message is not output when a control statement analysis error occurs. This message also is not output when using the alter HiRDB mode or create auditor functions.

dd....dd: Server name for the migration destination (is only output during RDAREA migration)

S: Resumes processing.

KFPX14251-E L

Too small RDAREA size, RDAREA name aa....aa, size=bbbb

There are too few segments in RDAREA aa....aa.

aa....aa: RDAREA name

bbbb: Required number of segments

S: Terminates processing.

P: Set the specification of the initial operand in the control statement to bbbb or greater and re-execute.

KFPX14253-E L

aa....aa bb....bb not defined

aa....aa named bb....bb was not found in the system.

aa....aa: Type of name:

RDAREA: RDAREA

File: HiRDB file

Rfile: Replica HiRDB file system area name

bb....bb: Displays one of the following:

RDAREA name

HiRDB file name

Replica HiRDB file system area name (generation number)

S: Cancels structure modification processing for the corresponding RDAREA and processes the next control statement.

Action

Correct the RDAREA name and the HiRDB file name, and then re-execute. For the replica HiRDB file system area name, register the generation of the HiRDB file system area, and then re-execute.

KFPX14255-W L

Unable to initialize index aa....aa.bb....bb due to cc....cc, RDAREA name="dd....dd"

Index aa....aa.bb....bb cannot be initialized because cc....cc.

aa....aa: Authorization identifier

bb....bb: Index identifier

cc....cc: Error cause:

RDAREA status is invalid: Status of RDAREA is invalid.

HiRDB system error occurred: An SQL error occurred.

dd....dd: RDAREA name

S: Interrupts index initialization of the affected RDAREA and executes the next process.

Action

If RDAREA status is invalid:

RELEASE and OPEN the RDAREA status and re-execute initialization. Or, re-create the index when inserting data into the RDAREA index that was initialized with the database reorganization utility.

If SQL error occurred:

Refer to the SQL message, eliminate the cause of the error, and then re-execute initialization. Or, re-create the index when inserting data into the RDAREA index that was initialized with the database reorganization utility.

If this action is not performed and retrieval or insertion is executed on the aa....aa.bb....bb index, the results are not guaranteed because the index data was not deleted.

KFPX14259-E L

Unable to remove due to exist table or index

There is a table, index, LOB column, sequence generator, or replica RDAREA in the RDAREA to be deleted. As a result, the RDAREA cannot be deleted.

S: Terminates processing.

Action

Delete any table, index, LOB column, sequence generator, or replica RDAREA in the RDAREA to be deleted, and then retry the operation.

KFPX14262-E L

Unable to aa....aa due to insufficient master directory rdarea

aa....aa cannot be processed, because a space shortage occurred in the master directory RDAREA.

aa....aa: Processing resulting in the error:

create rdarea: RDAREA addition

replicate rdarea: RDAREA replica definition

S: Terminates processing.

Action

Re-execute after expanding the master directory RDAREA (expand rdarea).

KFPX14268-W L

Too small RDAREA size, RDAREA = aa....aa, area size=bbbb-cccc

Because the RDAREA size (number of segments) is less than the number of table and index definitions in the area, some of the tables and indexes cannot be used.

aa....aa: RDAREA name

bb....bb: Minimum number of segments required to use the tables and indexes in the target RDAREA (total number of tables and indexes stored in the target RDAREA)

cc....cc: Number of allocated RDAREA segments

S: Resumes processing.

Action

Specify a larger number of segments, and then re-execute initialization. Or, delete unneeded table or index definitions.

KFPX14280-E L

Failed to allocate RDAREA "aa....aa" to global buffer bb....bb, return code=cc[, server name= dd....dd]

An error occurred while allocating RDAREA "aa....aa" in global buffer bb....bb.

aa....aa: RDAREA name

bb....bb: Global buffer name

cc: Reason code:

4: Specified buffer length is less than the RDAREA page length.

8: The specified buffer pool was not found (if a global buffer is not allocated to the original RDAREA or replica RDAREA, the item bb....bb may not be displayed).

12: Specified buffer pool is for indexes or LOB.

16: Output to status log file failed.

dd....dd: Server name (this name is output only for a shared RDAREA)

S: Cancels structure modification processing for the corresponding RDAREA and resumes processing.

Action

Eliminate the cause of the error and re-execute.

KFPX14302-W L

Line aaaa: extension nouse assumed

The automatic extension facility can be specified only for the types of RDAREAs listed below. Because another type of RDAREA was specified, nouse was assumed for the extension operand specification value.

Data dictionary RDAREA

Data dictionary LOB RDAREA

User RDAREA

User LOB RDAREA

Registry RDAREA

Registry LOB RDAREA

aaaa: Line number

S: Continues processing.

Action

Correct to nouse the specification value of the extension operand in the create rdarea, expand rdarea, initialize rdarea, or alter rdarea statement.

KFPX18400-I S

Pdexp terminated, return code=aa....aa

Processing of the dictionary export/import utility (pdexp) terminated with the indicated return code.

aa....aa: Return code:

0: Normal termination

4: Warning error occurred, but processing terminated

8: Normal termination for some items but abnormal termination for others

12: Processing terminated without normal completion of any item, or the utility server process was cancelled or terminated abnormally

S: Terminates processing.

O:

If the return code is other than 0, check the message output by the utility and take action appropriate to that message.

In the following cases, the return code is 12 even if some processing was completed normally:

Processing was cancelled with the pdcancel command.

An error occurred in the utility server process.

If exit processing terminates with return code 12, retrieve the TABLE_SCHEMA and TABLE_NAME columns of the SQL_TABLES dictionary table to determine which processes terminated normally.

KFPX18410-E L+S

Insufficient memory on aa....aa, size=bb....bb

Work area could not be allocated because a memory shortage occurred.

aa....aa: Area type:

DYNAMIC_SHMPOOL: Dynamic shared memory

PROCESS: Process private area

STATIC_SHMPOOL: Static shared memory

bb....bb: Size of area to be allocated (in bytes)

S: Terminates processing.

O: Increase the amount of memory that can be used and re-execute.

KFPX18430-E E+L+S

Error occurred:aa....aa

An error was detected in export/import processing or in HiRDB.

aa....aa: Error detected by the utility or error message detected by HiRDB

S: Terminates processing.

O: Take one the following actions:

Take action appropriate to the message output before this message.

Take action appropriate to the message output by HiRDB.

KFPX18431-E E+L+S

cc....cc import error occurred, error_sql_no=aa....aa,error_sql=bb....bb

An error was detected in the create cc....cc issued during import.

aa....aa: Number of procedure statement in the create cc....cc statement

bb....bb: SQL statement or SQL procedure statement causing the error in the procedure of the create cc....cc statement

cc....cc: {Procedure|Trigger}

S: Terminates processing.

O: Eliminate the cause of the error on the basis of the displayed error_sql_no, error_sql, and the SQL error message output after this message, and then re-execute.

KFPX18467-E E

Line aa....aa:incorrect control statement

One of the following errors was found in the -t, -p, or -g specification:

Quotation marks (") are not specified correctly.

Length of specification value is incorrect.

Line is not in the schema-name.identifier format.

No value is specified for -t, -p, or -g.

aa....aa: Line number

S: Analyzes the control statements and terminates processing.

O: Correct the control statement.

KFPX18468-E E

Line aa....aa:invalid operation

An error was found in the specification of the control statement. Or, an option other than -t, -p or -g was specified.

aa....aa: Line number

S: Analyzes the control statements and terminates processing.

O: Correct the control statement.

KFPX18476-E E

Line aa....aa:invalid value in bb....bb name

The bb....bb specification is incorrect.

aa....aa: Line number

bb....bb: Specification containing the error

{ procedure | schema | table | trigger }

S: Analyzes the control statements and terminates processing.

O: Correct the control statement.

KFPX18477-E E

Line aa....aa:unable to specify -t and -p and -g at the same time

A table import/export (-t option), stored procedure import/export (-p option), and trigger import/export (-g option) cannot be specified concurrently.

aa....aa: Line number

S: Terminates processing at the point where the error is detected.

O: Import/export tables, stored procedures, or triggers separately.

KFPX18480-E E

Number of -t/-p/-g statement exceeds 64

The number of tables (-t option), stored procedures (-p option), or triggers (-g option) to be imported/exported with the dictionary import/export utility exceeded the maximum (10,000).

S: Terminates processing.

O: Modify the specification of the -t, -p, or -g option so that it does not exceed 10,000.

To process 10,001 or more tables, stored procedures, or triggers, start by splitting the number to be processed at one time into groups of 10,000 or fewer.

KFPX18481-E E

No -t/-p statement

There are no table (-t option), stored procedure (-p option), or trigger (-g option) specifications for import/export processing.

S: Analyzes the control statements and terminates processing.

O: Specify at least one -t, -p, or -g option.

KFPX18490-E E

Line aa....aa:duplicate name

The same table (-t option), stored procedure (-p option), or trigger (-g option) is specified more than once for import or export.

aa....aa: Line number

S: Analyzes the control statements and terminates processing.

O: Correct the control statements.

KFPX18502-E L+S

No privileges to export/import

The user does not have the necessary privilege for exporting or importing objects; the DBA privilege is required.

S: Terminates processing.

O: Have the administrator grant the DBA privilege, and then re-execute.

KFPX18504-E L+S

Unable to export aa....aa, name="bb....bb"."cc....cc"

aa....aa cannot be exported for the reason indicated in the message output before this message.

aa....aa: Item to be exported { procedure|table|trigger }

bb....bb: Schema name (PUBLIC for a public view or public procedure)

cc....cc: Table identifier, routine identifier, or trigger identifier

S: Terminates processing.

O: Take action appropriate to the message output before this message.

KFPX18506-E L+S

Specified aa....aa not found in dictionary, name="bb....bb"."cc....cc"

aa....aa, which was specified for export, was not found in the dictionary.

aa....aa: Item to be exported { procedure|table|trigger }

bb....bb: Schema name (PUBLIC for a public view or public procedure)

cc....cc: Table identifier, routine identifier, or trigger identifier

S: Aborts the process for this table and executes the next process.

O: Specify the correct table name, procedure name, or trigger name.

KFPX18507-W L+S

cc....cc invalid, name="aa....aa."bb....bb"

cc....cc is invalid.
Export processing was performed normally, but the invalid cc....cc and whether or not all the specified tables were processed were not checked during import processing. If any of the specified tables is not found at the import destination, import processing will be cancelled at that point. cc....cc can be imported successfully if all the specified tables are found at the import destination.

aa....aa: Schema name (PUBLIC for a public procedure)

bb....bb: Procedure identifier or trigger identifier

cc....cc: {Procedure|Trigger}

S: Processing of cc....cc terminated normally. However, the return code of the utility is 4.

O: When this cc....cc is imported, check that all the specified tables are at the import destination.

KFPX18508-E L+S

Not support facility in definition of aa....aa"bb....bb"."cc....cc"

The definition specified as object aa....aa for export contains a function that is not supported by the Dictionary Import/Export Utility (pdexp); the object cannot be exported.

The following functions are not supported by the Dictionary Import/Export Utility:

If aa....aa is a table:

Tables and viewed tables containing an abstract data type

If aa....aa is a procedure:

Procedures using an abstract data type

Procedures that are declared within an abstract data type

Procedures using a procedure

Procedures using a function definition (CREATE FUNCTION and system definition scalar functions)

aa....aa: {table|procedure}

bb....bb: Schema name (PUBLIC for a public view or public procedure)

cc....cc: Table identifier or routine identifier

S: Resumes processing by skipping the export processing of the table, viewed table, or procedure. However, if an attempt was made to export a procedure that uses abstract data types, procedures, or function definitions, the system terminates processing.

O: If an error occurred in a procedure that uses abstract data types, procedures, or function definitions, remove the procedure specification from the control statement file, and then re-execute the utility.

If an error occurred in other unsupported tables, viewed tables, or procedures, use the pddef command, or related commands, to execute the indicated definition SQL statement for the system to which items were to be exported.

KFPX18550-E L+S

Unable to import aa....aa, name="bb....bb"."cc....cc"

aa....aa cannot be imported for the reason indicated in the message that was output before this message.

aa....aa: Item to be exported { index|procedure|table|trigger }

bb....bb: Schema name (PUBLIC for a public view or public procedure)

cc....cc: Index identifier, routine identifier, table identifier, or trigger identifier

S: Terminates processing.

O: Take action appropriate to the message that was output before this message.

KFPX18551-E L+S

Table not defined, name="aa....aa"."bb....bb"

Table "aa....aa"."bb....bb" is not defined in the import destination system. Therefore, importing of the stored procedure or trigger indicated in message KFPX18550-E cannot be performed.

aa....aa: Schema name (PUBLIC for a public view or public procedure)

bb....bb: Table identifier

S: Aborts import processing of the stored procedure or trigger indicated in the KFPX18550-E message, which is output after this message, and then executes the next import process.

O: Define table "aa....aa"."bb....bb" and import the table again.

KFPX18555-E L+S

Same cc....cc already exist, name="aa....aa"."bb....bb"

A cc....cc to be imported already exists at the import destination system.

aa....aa: Schema name (PUBLIC for a public procedure)

bb....bb: Routine identifier or trigger identifier

cc....cc: {procedure|trigger}

S: Aborts import processing of this cc....cc, and then executes the next import processing.

O: To reimport, delete cc....cc using the DROP cc....cc statement, and then execute.

KFPX18560-E L+S

Invalid export file

The specified file is not an export file, or the specification of the table, stored procedure, or trigger did not match the content of the export file for the following reasons:

An option other than table importing (option -t) was specified for the table export file.

An option other than stored procedure importing (option -p) was specified for the stored procedure export file.

An option other than trigger importing (option -g) was specified for the trigger export file.

S: Terminates processing.

O: Specify the correct export file in the-i option.

KFPX18562-E L+S

Export file incompleted

An export file error or an inappropriate EOF was detected.

S: Terminates processing.

O: Check that the export file was exported normally. If it was not, import an export file that was exported normally.

KFPX18563-E L+S

Same table already exist, name="aa....aa"."bb....bb"

A table to be imported already exists at the import destination system.

aa....aa: Schema name (PUBLIC for a public view)

bb....bb: Table identifier

S: Aborts processing for the table and resumes processing.

O: To reimport the table, delete the table with the DROP TABLE statement and re-execute.

KFPX18566-E L+S

Specified aa....aa not found in export file, name="bb....bb"."cc....cc"

Import item aa....aa was not found in the export file.

aa....aa: Item to be imported { procedure|table|trigger }

bb....bb: Schema name (PUBLIC for a public view or public procedure)

cc....cc: Table identifier, routine identifier, or trigger identifier

S: Aborts processing of the applicable table and resumes processing.

O: Specify the correct table name, stored procedure name, or trigger name.

KFPX18579-E L+S

aaaaa error occurred on bb....bb

An error occurred when the dictionary table indicated by bb....bb was accessed.

aaaaa: Processing {Input}

bb....bb: Dictionary table identifier

S: Terminates processing.

O: Take action appropriate to the message that was output before this message.

KFPX21000-I S

Usage: pdobjconv

The option format of the pdobjconv command is invalid.

S: Terminates processing.

O: Check the command format of the pdobjconv command, and then re-execute.

KFPX21001-I E+L

SQL OBJECT converter start at aa....aa on bb....bb

The pdobjconv command was started.

aa....aa: Start time (in the format hh:mm:ss)

bb....bb: Start date (in the format yyyy:mm:dd)

S: Continues processing.

KFPX21002-I E+L

SQL OBJECT converter ended, return code= aa

The pdobjconv command terminated with return code aa.

aa: Return code:

0: Normal termination

4: Although a warning error occurred, processing terminated normally.

8: Although processing terminated, conversion of some SQL objects failed.

12: Abnormal termination

S: Terminates processing.

Action

Take appropriate action based on the return code:

0 or 4:

No action is needed.

8:

SQL object conversion failed for some viewed tables, procedures, or functions.

If HiRDB automatically activated the pdobjconv command, refer to the $PDDIR/spool/pdobjconv.log file, eliminate the cause of the error, and then re-execute the pdobjconv command. If the operator executed the pdobjconv command, refer to the pdobjcon.log file in the current directory, eliminate the cause of the error, and then re-execute the pdobjconv command.

12:

Processing was cancelled in midstream. Refer to the message, eliminate the error, and then re-execute the pdobjconv command.

KFPX21003-E S

Invalid option for pdobjconv

The specification of the pdobjconv command is invalid.

S: Terminates processing.

O: Correct the specification of the pdobjconv command and re-execute.

KFPX21004-E E

Insufficient memory on PROCESS for SQL OBJECT conversion, size=aa....aa

During execution of the pdobjconv command, there was an attempt to allocate the process native memory area, but the allocation failed due to insufficient memory.

aa....aa: Area size that was to be allocated (in bytes)

S: Terminates processing.

Action

Increase the size of the available memory using one of the following methods:

Reduce the number of concurrently executing processes.

Increase the swap area size.

Add real memory.

KFPX21005-E E+L

System call error in SQL OBJECT conversion, func=aa....aa, errno=bb....bb

During execution of the pdobjconv command, an error occurred in a system function.

aa....aa: System function name

bb....bb: Error code

S: Terminates processing.

Action

Check the errno of the system function, eliminate the cause, and then re-execute.

KFPX21006-E E+L

Open error in report file "aa....aa" for SQL OBJECT conversion, errno=bb....bb

An error occurred during opening of the pdobjconv command's execution report file, due to reason bb....bb.

aa....aa: File name

bb....bb: Error code

S: Terminates processing.

Action

Check the errno of the system function, eliminate the cause, and then re-execute.

KFPX21007-E E+L

RPC(aa....aa) error occurred in SQL OBJECT conversion, code=bb....bb

An RPC error occurred during execution of the pdobjconv command.

aa....aa: RPC processing type

bb....bb: Error detail code

S: Terminates processing.

Action

Eliminate the cause of the error by referring to 4.2 Detail codes for system-related errors and the preceding KFPS05032-E message, and then re-execute the command. If the error code is -999, error information indicating the error cause is output before this message (KFPX21007-E). If the error code is 310, the communication destination server may not be active.

KFPX21008-E E

Pdobjconv must be executed at HiRDB unit including system manager

Execute the pdobjconv command on the unit where the system manager is defined.

S: Terminates processing.

Action

Re-execute the command at the unit in which the system manager is defined.

KFPX21100-E E+L

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

Specified viewed table, procedure, or function "bb....bb"."cc....cc" was not found in the HiRDB system.

aa....aa: One of the following:

View: Viewed table

Procedure: Procedure

Function: Function

bb....bb: Authorization identifier

cc....cc: Table name, procedure name, or function name

S: Terminates processing.

Action

Specify the correct viewed table, procedure, or function, and then re-execute.

KFPX21101-W E+L

aa....aa "bb....bb"."cc....cc" dropped from system during SQL OBJECT conversion

During execution of the pdobjconv command, a viewed table, procedure, or function "bb....bb"."cc....cc" was dropped from the HiRDB system.

aa....aa: One of the following:

View: Viewed table

Procedure: Procedure

Function: Function

bb....bb: Authorization identifier

cc....cc: Table name, procedure name, or function name

S: Continues processing.

KFPX21102-I E+L

SQL OBJECT of aa....aa "bb....bb"."cc....cc" already converted

Because the SQL object (viewed table, procedure, or function "bb....bb"."cc....cc") had already been converted, conversion processing was not performed.

aa....aa: One of the following:

View: Viewed table

Procedure: Procedure

Function: Function

bb....bb: Authorization identifier

cc....cc: Table name, procedure name, or function name

S: Continues processing.

KFPX21103-I E+L

SQL OBJECT of aa....aa "bb....bb"."cc....cc" converted successfully

Conversion of the SQL object (viewed table, procedure, or function "bb....bb"."cc....cc") was successful.

aa....aa: One of the following:

View: Viewed table

Procedure: Procedure

Function: Function

bb....bb: Authorization identifier

cc....cc: Table name, procedure name, or function name

S: Continues processing.

KFPX21104-E E+L

SQL OBJECT conversion for aa....aa "bb....bb"."cc....cc" failed

Conversion of the SQL object (viewed table, procedure, or function "bb....bb"."cc....cc") failed.

aa....aa: One of the following:

View: Viewed table

Procedure: Procedure

Function: Function

bb....bb: Authorization identifier

cc....cc: Table name, procedure name, or function name

S: Continues processing.

Action

Determine the cause of the error from the message that follows this message, correct the error, and then re-execute.

KFPX21105-W S+E+L

Register again REGISTRY MANIPULATION PROCEDURE; enter pdreginit command

The registry manipulation procedure must be re-registered.

S: Continues processing.

Action

Use the pdreginit command to re-register the registry manipulation procedure.

KFPX21200-I S

Usage: pdjarsync [-S |-l |-R |-D |-L][-x host_name [,host_name]][-u owner_name [,owner_name]][-f jar_file_name]

The specification of the pdjarsync command was invalid.

S: Terminates processing.

O: Enter the command correctly and re-execute.

KFPX21201-E S

Specification host aa....aa not found in system definition file

Specified host aa....aa was not found in the system common definition.

aa....aa: Host name

S: Terminates processing.

O: Specify the correct host name and re-execute.

KFPX21202-E E

aa....aa file "bb....bb" already exist

Specified JAR file "aa....aa" is already registered.

aa....aa: File type

JAR: JAR file

CLIB: C library file

bb....bb:file name

S: Terminates processing.

O: Re-register the JAR file or C library file as required (re-execute the command with the -R option specified).

KFPX21203-E S

Internal function error, func=aa....aa, return code=bb....bb

An error occurred in the internal processing of the command.

aa....aa: Name of the function in which the error occurred

bb....bb: System-related error detail code

See 4.2 Detail codes for system-related errors.

S: Terminates processing.

O: Correct the error and re-execute.

KFPX21204-E S

Insufficient memory on PROCESS for aa....aa file synchronizer, size=bb....bb

Because of a memory shortage, a process private area could not be allocated during execution of the pdjarsync or pdclibsync command.

aa....aa: Type of file to be synchronized

JAR: JAR file

CLIB: C library file

bb....bb: Size of the process private area that was to be allocated (bytes)

S: Terminates processing.

O: Take one of the following actions:

Reduce the number of concurrently executing processes.

Increase the swap area size.

Add real memory.

KFPX21205-E S

Pdstart command parameter missing in system common definition

An error was detected in the pdstart command in the system common definition.

S: Terminates processing.

O: Correct the pdstart command in the system common definition and re-execute.

KFPX21206-E S

Incorrect hostname or unitid specified in system definition

The specified host name or unit identifier is not defined in the system definition as a HiRDB host or unit.

S: Terminates processing.

O: Correct the host name or unit identifier specified in pdunit or pdstart in the system common definition or the unit identifier specified in the pd_unit_id operand in the unit control information definition, and then re-execute.

KFPX21207-E S

System call error in aa....aa file synchronizer, func=bb....bb, errno=cc....cc

An error occurred in system function bb....bb.

aa....aa: File type

JAR: JAR file

CLIB: C library file

bb....bb: Function that was executed

cc....cc: Error code (errno)

S: Terminates processing.

O: Determine the cause of the error from the error code (errno), correct the error, and then re-execute. For the error codes, see the applicable OS manual.

KFPX21208-E S

Invalid option

Command line specification is invalid.

S: Terminates processing.

O: Specify the command correctly and re-execute.

KFPX21209-E E

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

File bb....bb was not found.

aa....aa: File type

JAR: JAR file

CLIB: C library file

bb....bb:File name

S: Terminates processing.

O: Check that the specified file name and authorization identifier are correct. If there is an error, correct the file name or authorization identifier and re-execute the command.

KFPX21210-I S

Usage: pdclibsync [-S|-I|-R|-D|-L] [-x host_name[,host_name]] [-u auth_id[,auth_id]] [-f c_library_file_name]

An error was found in the specification format of the pdclibsync command option.

S: Terminates processing.

O: Check the specification format of the option, and re-execute the pdclibsync command.

KFPX21300-I E

Usage: pdextfunc {-c|-e[ force]}

There is an error in the specification format of an option of the pdextfunc command.

S: Terminates processing.

O: Check the specification format of the option, and then re-execute the pdextfunc command.

KFPX21301-W E

Function "aa....aa(bb....bb)" already defined

The function that was to be defined, aa....aa(bb....bb), is already defined.

aa....aa: Name of the function that was to be defined

bb....bb: List of data types of parameters of the function that was to be defined

S: Continues processing.

O: If an extended system-defined scalar function was previously defined with the pdextfunc command, ignore this message. If this message is output in other circumstances, contact the customer support center.

KFPX21302-W E

Function"aa....aa(bb....bb)" not found

The function that was to be deleted aa....aa(bb....bb) was not found.

aa....aa: Name of the function that was to be deleted

bb....bb: List of data types of the arguments of the function that was to be deleted

S: Continues processing.

O: If the extended system-defined scalar function was previously deleted with the pdextfunc command, or has not been defined, ignore this message. If this message is output in other circumstances, contact the customer support center.

KFPX21303-E E

Error occurred during execution of pdextfunc, aa....aa

An error occurred during execution of the pdextfunc command.

aa....aa: Error detail message

S: Terminates processing.

O: Take appropriate action as indicated in the error detail message, and then re-execute the pdextfunc command.

KFPX21304-I E

Process completed

The definition or deletion of the extended system-defined scalar function has completed.

S: Terminates processing.

KFPX21305-E E

Timeout occurred during execution of pdextfunc

A timeout occurred during execution of the pdextfunc command. A timeout occurs when a request from the command to the server does not yield a response from the server within 1 minute.

S: Terminates processing.

O: Server-side processing might have been delayed due to an increase in the load on the machine (CPU or file I/O, for example). If there is a high load on the machine, remove the high load, and then re-execute the command. If the error still cannot be resolved, contact the customer support center.

KFPX21306-E E

PDUSER has no DBA privilege

The user specified as PDUSER does not have DBA privileges.

S: Terminates processing.

O: Specify a user with DBA privileges as PDUSER, and then re-execute the command.

KFPX24000-I S

DB initialize ended, return code=aa

The database initialization utility terminated with the indicated return code.

aa: Return code:

0: Normal termination.

4: Warning error occurred, but processing terminated.

8: An error occurred during the execution of the database initialization utility. The initialization terminated. Terminate HiRDB, and then restart it.

12: Error occurred while executing the database initialization utility (refer to the output message to eliminate the cause of the error, and then re-execute).

S: Terminates processing.

KFPX24001-E L

Insufficient memory on PROCESS, size=aa....aa

Attempt to allocate the process private area during execution of the database initialization utility failed due to a memory shortage.

aa....aa: Size (in bytes) of the area that was to be allocated

S: Terminates processing.

Action

Check the number of processes and re-execute. If the same error recurs, contact the customer support center.

KFPX24002-E L

System call error, func=aa....aa, errno=bbbb

System function aa....aa was executed, but an error occurred.

aa....aa: Executed function

bbbb: Error code (errno)

S: Terminates processing.

Action

Eliminate the cause of the error according to the error code and re-execute.

KFPX24003-E S

Message output failed, return code=aa, msgno=bbbb

Attempt to output messages to a log file resulted in return code aa....aa.

aa....aa: Detail code for system-related error

bbbbb: Message number that was subject to output

S: Terminates processing.

Action

See 4.2 Detail codes for system-related errors to eliminate the cause of the error, and then re-execute.

KFPX24004-E L

Control statement file open failed : aa....aa

Control information file open processing failed for reason aa....aa.

aa....aa: Reason for open failure:

errno=bbbb: Processing terminated with error code bbbb.

no such file: Specified file was not found.

permission denied: Specified file was found, but the required privilege is not defined.

S: Terminates processing.

Action

Eliminate the cause of the error and re-execute. For the control information file, specify the absolute pathname of the file in the dictionary server (DS).

KFPX24005-E L

Line aaaa:HiRDB file name unable to start with "pl"

A name beginning with pl cannot be specified as a HiRDB file name

aaaa: Line number

S: Terminates processing.

Action

Change the HiRDB file name to a name that does not begin with the string pl, and then re-execute the command.

KFPX24006-E L

Line aaaa:double quotations missing

Quotation marks (") are missing from a file name.

aaaa: Line number

S: Terminates processing after analyzing all the specified control statements.

Action

Specify quotation marks (") around the file name and re-execute.

KFPX24007-E L

Line aaaa:number of bb....bb operands exceed the server limit cccc

The number of bb....bb operands exceeded the maximum of cccc permitted per server.

aaaa: Line number

bb....bb: Operand name

cccc: Maximum number of operands

S: Terminates processing after analyzing all the specified control statements.

O: Correct the number of bb....bb operands so that the maximum is not exceeded and re-execute.

KFPX24008-E L

Interprocess communication failed, return code=aaaa

A communication error occurred while reporting termination of the database initialization utility.

aaaa: Detail code for system-related error

S: Terminates processing.

Action

See 4.2 Detail codes for system-related errors to eliminate the cause of the error, and then re-execute. Or, because the initialization has terminated, terminate HiRDB, and then restart it.

KFPX24009-W L

Line aaaa:bb....bb assumed for page size

Only page length bb....bb can be specified for the RDAREA, but a different value was specified; the system assumed bb....bb.

aaaa: Line number

bb....bb: Assumed page length

S: Resumes processing.

Action

Correct the page length to bb....bb in the page operand of the create rdarea statement.

Master directory RDAREA or data directory RDAREA:

Set the page length to 4096.

LOB RDAREA:

Set the page length to 8192.

KFPX24010-E L

RPC "aa....aa" failed, return code=bb....bb, svname=cc....cc

RPC function "aa....aa" terminated with error code bb....bb.

aa....aa: RPC function:

callv: Send

reply: Receive

bb....bb: Error code

cc....cc: Server identifier

S: Terminates processing.

Action

When expansion units are in use (the pd_system_expand_unit operand is specified):

If the server indicated in cc....cc is on an expansion unit, delete the create rdarea statement that specifies the server identifier from the control statement file, and then re-execute the database initialization utility (pdinit). If you want to create an RDAREA on the expansion unit, create the RDAREA using the database structure modification utility (pdmod). For details about expansion units, see the HiRDB Version 9 System Operation Guide.

Other than above:

See 4.1 Detail codes for RPC-related errors to resolve the cause of the error, and then re-execute the command.

KFPX24011-W L

Line aaaa:dictionary server name assumed

The specified dictionary server was not found; the system assumed the defined dictionary server name.

aaaa: Line number

S: Resumes processing.

KFPX24012-I L

DB initialize start at aa....aa on bb....bb

Execution of the database initialization utility has started.

aa....aa: Start time hh:mm:ss (hour:minute:second)

bb....bb: Start date yyyy/mm/dd (year/month/date)

S: Resumes processing.

KFPX24013-I L

DB initialize ended return code=aa at bb....bb on cc....cc

The database initialization utility terminated with return code aa.

aa: Return code:

0: Normal termination

4: Warning error occurred, but processing terminated.

8: Initialization terminated normally, but a communication error occurred during termination of initialization. Terminate HiRDB, and then restart it.

12: Terminated abnormally (refer to the output message to eliminate the cause of the error, and then re-execute).

bb....bb: Start time hh:mm:ss (hour:minute:second)

cc....cc: Start date yyyy/mm/dd (year/month/date)

S: Terminates processing.

KFPX24014-E L

HiRDB system "aa....aa" failed, return code=bb....bb

Function "aa....aa" terminated with return code bb....bb.

aa....aa: Function name:

besinf: Collection of back-end server information

branchdel: Deletion of registered transaction branch

branchreg: Registration of transaction branch

dicinf: Collection of dictionary server information

getpath: Collection of DBPATH

mainloop: Execution of RPC service

open: Initialization of RPC server

bb....bb: Detail code for system-related error

S: Terminates processing.

Action

See 4.2 Detail codes for system-related errors to eliminate the cause of the error, and then re-execute.

KFPX24015-E L

Putenv failed, due to insufficient memory on PROCESS

Attempt to set an environment variable resulted in an error due to a space shortage.

S: Terminates processing.

P: Check the number of processes and re-execute. If the same error recurs, contact the customer support center.

KFPX24016-E L

RPC service failed, no such communication id, return code=aa....aa

RPC communication terminated with error code aa....aa, but the server resulting in the communication error cannot be identified.

aa....aa: Error code

S: Terminates processing.

Action

See 4.1 Detail codes for RPC-related errors to eliminate the cause of the error, and then re-execute. If a message has been output before this message, eliminate the cause of the error according to that message and re-execute.

KFPX24017-E L

HiRDB file "aa....aa" failed, return code=bb....bb, HiRDB file name=cc....cc

Function "aa....aa" for HiRDB file cc....cc terminated with return code bb....bb.

aa....aa: HiRDB file system function:

close: Close HiRDB file

create: Create HiRDB file

write: Write data to HiRDB file

statfs: Acquire HiRDB file system area information

bb....bb: Error code

cc....cc: HiRDB file name

S: Terminates processing.

Action

See 5.1 Error codes returned from HiRDB file system access requests to eliminate the cause of the error, and then re-execute.

KFPX24018-E L

Masterdirectory 1st file name invalid, name = "aa....aa"

The first file name "aa....aa" in the master directory RDAREA does not match the file name specified in the system common definition.

aa....aa: Name of the first file specified in the master directory RDAREA

S: Terminates processing.

Action

Specify in the control statement and in pd_master_file_name of the system common definition the same name for the first file in the master directory RDAREA, and then re-execute.

KFPX24019-E L

View definition file open failed : aa....aa

pdview.pddef open processing failed for reason aa....aa.

aa....aa: Reason for open failure:

errno=bbbb: Processing terminated with error code bbbb.

no such file: Specified file was not found in %PDDIR%\lib\sysdef.

permission denied: Specified file was found, but the required privilege is not defined.

S: Terminates processing.

Action

Contact the customer support center.

KFPX24020-E L

Number of aa....aa exceeds bb....bb

The number of RDAREAs or HiRDB files exceeded value bb....bb specified in system common definition aa....aa.

aa....aa: System common definition:

pd_max_rdarea_no: Maximum number of RDAREAs

pd_max_file_no: Maximum number of HiRDB files comprising an RDAREA

pd_max_tmp_table_rdarea_no: Maximum number of RDAREAs for temporary tables

bb....bb: Defined value

S: Terminates processing.

Action

Reduce to no more than aa....aa the number of RDAREAs or HiRDB files specified in the control statements and re-execute. Or, terminate HiRDB, correct the value of aa....aa, and then re-execute.

KFPX24021-E L

Control statement file invalid device(a)

The specified control statements file is invalid.

a: File entry type

Same as mode entry that was output by the OS's ls -l command

S: Terminates processing.

Action

Specify a regular file and re-execute.

KFPX24022-E L

Line aaaa:unable to specify "bb....bb" and "cc....cc" statement at the same time in "define system" statement

"bb....bb" and "cc....cc"cannot be specified together in the define system statement.

aaaa: Line number

bb....bb: Operand specification value

cc....cc: Operand specification value

S: Terminates processing.

Action

Correct the values specified in the define system statement and re-execute the statement.

KFPX24024-E L

Unable to send message from aa....aa to bb....bb

A communication error occurred between host aa....aa and host bb....bb.

aa....aa: Send source host name#

bb....bb: Send destination host name#

#: If the system switchover facility is being used, the host name of the primary system is indicated.

S: Terminates processing.

Action

Take action appropriate to the KFPX24010-E message, which was output before this message. If the error is not a physical communication error, there may be an inconsistency in the system definitions concerning the relationship between the hosts; check the interhost definitions for the hosts affected by the error and re-execute.

KFPX24025-W L

Line aaaa:"bb....bb" operand ignored because cannot be specified

Operand "bb....bb" was ignored because it cannot be specified.

aaaa: Line number

bb....bb: Operand name

open attribute:

This operand cannot be specified for a master directory, data directory, data dictionary, or data dictionary LOB RDAREA

S: Resumes processing.

Action

Delete operand "bb....bb".

KFPX24026-E L

Line aaaa:dd....dd operand value bb....bb invalid, because HiRDB file size exceeds ccc byte

The specified value bb....bb is invalid for the initial operand, because the HiRDB file in the database will exceed maximum value ccc (bytes) if created based on the specified value.
The specified value bb....bb is invalid for the extension operand, because the HiRDB file in the database will exceed maximum value ccc (bytes) after automatic extension if created based on the specified value.

aaaa: Line number

bb....bb: Specified value

ccc: Maximum permissible value:

In UNIX:

64G: 64 gigabytes

In Windows:

2G: 2 gigabytes

dd....dd: Specified operand:

initial: initial operand

extension: extension operand

S: Terminates processing after analyzing all control statements.

Action

Specify a smaller value in this control statement operand and re-execute.

KFPX24028-W L

Line aaaa:max entries raised to bb....bb

Because the value specified for the max entries operand in the create rdarea statement was not a multiple of 500, it was rounded up to bb....bb. This operand specifies the maximum number of lists that can be created in a list RDAREA.

aaaa: Line number

bb....bb: Rounded-up number

S: Continues processing.

KFPX24029-W L

Extension use specification for RDAREA aa....aa ignored, due to no expand option for HiRDB file system area of last HiRDB file

Specification of extension use is invalid because extension (-e option of the pdfmkfs command) is not specified for the HiRDB file system area in which the last HiRDB file comprising RDAREA aa....aa was created.

aa....aa: RDAREA name

S: Continues processing.

Action

To use the automatic extension facility, extension must be specified for the applicable HiRDB file system area. Use the -e option of the pdfmkfs command to specify a maximum number of extensions.

KFPX24030-E L

Unable to create shared RDARED aa....aa due to not specified pd_shared_rdarea_use=Y

Unable to create the shared RDAREA aa....aa because Y is not specified in the pd_shared_rdarea_use operand.

aa....aa: RDAREA name

S: Terminates processing.

Action

Terminate HiRDB, specify Y in the pd_shared_rdarea_use operand, and then re-execute the command.

KFPX24031-E L

Unable to aa....aa "bb....bb" due to invalid operand combination

Initialization aa....aa of RDAREA bb....bb cannot be performed due to an error in the specified combination of operands.
This message is output only if there is an error in the check for the prerequisite conditions when temporary table use is specified. This message is not output if nouse is specified.
When the shared operand (shared RDAREA) is also specified, an error results due to the combination of operands, and this message is output.

aa....aa: Initialization processing

create rdarea: Creation of RDAREA

bb....bb: Name of RDAREA

S: Terminates processing.

Action

A user RDAREA that is to be used as a temporary table RDAREA must be a public RDAREA. To specify a temporary table operand, specify user used by PUBLIC. Do not specify the shared operand (shared RDAREA) for a temporary table RDAREA.

KFPX24200-I S

DB modification ended, return code=aa

The database structure modification utility terminated with return code aa.

aa: Return code:

0: Normal termination

4: Warning error occurred, but processing terminated.

8: Part of the processing terminated (eliminate the cause of the error and execute the part that resulted in the error).

12: Terminated abnormally (refer to the output message to eliminate the cause of the error, and then re-execute).

16: Database has been damaged (it must be recovered).

S: Terminates processing.

KFPX24201-E L

Insufficient memory on PROCESS, size=aa....aa

Attempt to allocate the process private area during execution of the database structure modification utility failed due to a memory shortage.

aa....aa: Size (in bytes) of the area that was to be allocated

S: Terminates processing.

Action

Check the number of processes and re-execute. If the same error recurs, contact the customer support center.

KFPX24202-E L

System call error, func=aa....aa, errno=bbbb

System function aa....aa executed, but an error occurred.

aa....aa: Executed function

bbbb: Error code (errno)

S: Terminates processing.

Action

Eliminate the cause of the error according to the error code and re-execute.

KFPX24203-E S

Message output failed, return code=aa....aa, msgno=bbbbb

Attempt to output messages to a log file resulted in return code aa....aa.

aa....aa: Detail code for system-related error

bbbbb: Message number that was subject to output

S: Terminates processing.

Action

See 4.2 Detail codes for system-related errors to eliminate the cause of the error, and then re-execute.

KFPX24204-E L

Control statement file open failed : aa....aa

Control information file open processing failed for reason aa....aa.

aa....aa: Reason for open failure:

errno=bbbb: Processing terminated with error code bbbb.

no such file: Specified file was not found.

permission denied: Specified file was found, but the required privilege is not defined.

S: Terminates processing.

Action

Eliminate the cause of the error and re-execute.

KFPX24205-E L

Line aaaa:HiRDB file name unable to start with "pl"

A name beginning with pl cannot be specified as a HiRDB file name.

aaaa: Line number

S: Cancels structure modification for the corresponding RDAREA and processes the next control statement.

Action

Specify a HiRDB file name beginning with any character string other than pl, and then re-execute.

KFPX24206-E L

Line aaaa:double quotations missing

Quotation marks (") are missing from a file name.

aaaa: Line number

S: Terminates processing after analyzing all the specified control statements.

Action

Specify quotation marks (") around the file name and re-execute.

KFPX24207-E L

Line aaaa:number of bb....bb operands exceed the server limit cccc

The number of bb....bb operands exceeded the maximum of cccc permitted per server.

aaaa: Line number

bb....bb: Operand name

cccc: Maximum number of operands

S: Terminates processing after analyzing all the specified control statements.

Action

Correct the number of bb....bb operands so that the maximum is not exceeded, and then re-execute.

KFPX24208-E L

Work file open failed, aa....aa

A work file open error occurred.

aa....aa: Cause of the error:

errno=bbbb: Processing terminated with error code bbbb.

no such file: Specified file was not found.

permission denied: Specified file was found, but the required privilege is not defined.

S: Terminates processing.

Action

Eliminate the cause of the error by referring to the file created under %PDDIR%\tmp and re-execute the command.

KFPX24209-W A

Line aaaa:bb....bb assumed for page size

A page length value other than bb....bb was specified for an RDAREA for which the page length specification must be bb....bb; bb....bb was assumed.

aaaa: Line number

bb....bb: Assumed page length

S: Terminates processing.

P: Correct the page length in the page operand of the create rdarea statement to bb....bb. The page length for a LOB RDAREA is 8192.

KFPX24210-E L

RPC "aaaaa" failed, return code=bb....bb, svname=cc....cc

RPC function "aaaaa" for server cc....cc terminated with error code bb....bb.

aaaaa: RPC function:

callv: Send

reply: Receive

bb....bb: Detail error code for RPC-related error

cc....cc: Server identifier

S: Terminates processing.

Action

When expansion units are in use (the pd_system_expand_unit operand is specified):

If the server indicated in cc....cc is on an expansion unit, start up the expansion unit, and then re-execute the database structure modification utility (pdmod). For details about expansion units, see the HiRDB Version 9 System Operation Guide.

Other than above:

See 4.1 Detail codes for RPC-related errors to eliminate the cause of the error, and then re-execute.

KFPX24211-W L

Line aaaa:dictionary server name assumed

Because the specified dictionary server name could not be found, the defined dictionary server name was assumed.

aaaa: Line number

S: Terminates processing.

KFPX24212-I L

DB modification start at aa....aa on bb....bb

Execution of the database structure modification utility has started.

aa....aa: Start time hh:mm:ss (hour:minute:second)

bb....bb: Start date yyyy/mm/dd (year/month/date)

S: Resumes processing.

KFPX24213-I L

DB modification for ended return code=aa at bb....bb on cc....cc

The database structure modification utility terminated with return code aa.

aa: Return code:

0: Normal termination

4: Warning error occurred, but processing terminated.

8: Part of the processing terminated (eliminate the cause of the error and execute the part that resulted in the error).

12: Terminated abnormally (refer to the output message to eliminate the cause of the error, and then re-execute).

16: Database has become inconsistent (it must be recovered).

bb....bb: Start time hh:mm:ss (hour:minute:second)

cc....cc: Start date yyyy/mm/dd (year/month/date)

S: Terminates processing.

KFPX24214-E L

HiRDB system "aa....aa" failed, return code=bb....bb

Function "aa....aa" terminated with return code bb....bb.

aa....aa: Function name:

begin: Transaction startup

besinf: Collection of back-end server information

branchdel: Deletion of registered transaction branch

branchreg: Registration of transaction branch

commit: Termination of transaction

dicinf: Collection of dictionary server information

rollback: Rollback of transaction

getpath: Collection of DBPATH

bb....bb: Detail code for system-related error

S: Terminates processing.

Action

See 4.2 Detail codes for system-related errors to eliminate the cause of the error, and then re-execute.

If aa....aa is commit and bb....bb is -902, it is possible that an error caused the unit to terminate abnormally or perform a system switchover. Refer to any messages output before this message, eliminate the cause of the error, and then re-execute.

KFPX24215-E L

Putenv failed, due to insufficient memory on PROCESS

Attempt to set an environment variable resulted in an error due to a space shortage.

S: Terminates processing.

Action

Check the number of processes and re-execute. If the same error recurs, contact the customer support center.

KFPX24216-E L

RPC service failed, no such communication id, return code=aa....aa

RPC communication terminated with return code aa....aa, but the server resulting in the communication error cannot be identified because the communication ID is unknown.

aa....aa: Detail code for RPC-related error

S: Terminates processing.

Action

See 4.1 Detail codes for RPC-related errors. If a message has been output before this message, eliminate the cause of the error according to that message and re-execute.

KFPX24217-E L

HiRDB file "aa....aa" failed, return code=bb....bb, HiRDB file name=cc....cc

Function "aa....aa" for HiRDB file cc....cc terminated with return code bb....bb.

aa....aa: HiRDB file system function:

close: Close HiRDB file

create: Create HiRDB file

delete: Delete HiRDB file

write: Write data to HiRDB file

fstat: Acquire HiRDB file information

statfs: Acquire HiRDB file system area information

bb....bb: Error code for HiRDB file system

cc....cc: HiRDB file name

S: If delete, continues processing. If other than delete, terminates processing.

Action

delete:

See 5.1 Error codes returned from HiRDB file system access requests to eliminate the cause of the error. If the HiRDB file is not needed, delete it with the pdfrm command.

Function other than delete:

See 5.1 Error codes returned from HiRDB file system access requests to eliminate the cause of the error and re-execute.

KFPX24218-E L

Line aaaa:unknown file name "bb....bb" in used cc....cc

File "bb....bb" in an RDAREA specified for addition is already in use by server cc....cc. Or, file "bb....bb" cannot be checked for duplication, because server cc....cc is not defined in the system common definition.

aaaa: Line number

bb....bb: File name

cc....cc: Server name

S: Terminates processing.

Action

The initialized status has been changed in the server definition of the system common definition. Restore the initial definition or change the name of the file to be added in the RDAREA.

KFPX24219-E L

Unable to execute "pdmod" at the same time

A mutually exclusive utility is executing. The database structure modification utility cannot be executed in the following cases:

When another database structure modification utility is executing

When a dictionary is being reorganized

S: Terminates processing.

Action

Re-execute the database structure modification utility after the mutually exclusive utility has terminated.

KFPX24220-E L

Number of aa....aa exceeds bb....bb[, server name=cc....cc]

The number of RDAREAs, HiRDB files, or the maximum number of inner replica groups exceeded the value bb....bb of the aa....aa operand of the system common definition.

aa....aa: Operand in the system common definition

pd_max_file_no: Maximum number of HiRDB files comprising the RDAREA

pd_max_rdarea_no: Maximum number of RDAREAs

pd_inner_replica_control: Maximum number of inner replica groups

pd_max_tmp_table_rdarea_no: Maximum number of RDAREAs for temporary tables

bb....bb: Defined value

cc....cc: Server name (this is output only for a shared RDAREA)

S: Cancels structure modification for the corresponding RDAREA and processes the next control information file.

Action

Terminate HiRDB, correct the value of aa....aa, and then re-execute.

KFPX24221-E L

Control statement file invalid device(a)

The specified control statements file is invalid.

a: File entry type

Same as mode entry that was output by OS's ls -l command

S: Terminates processing.

Action

Specify a regular file and re-execute.

KFPX24222-E L

Too small page size aa....aa for bb....bb cc....cc, dd....dd name=ee....ee.ff....ff

FIX table or index ee....ee.ff....ff cannot be stored with modified page length aa....aa.

aa....aa: Modified page length

bb....bb: Type of length

row length: Row length

key length: Key length

cc....cc: Row length (unit: bytes)

dd....dd: Type of name

TABLE: FIX table

INDEX: Index

ee....ee: Authorization identifier

ff....ff: Table identifier or index identifier

S: Terminates processing.

Action

Specify a page length meeting the following conditions, and then re-execute the command:

Calculation equation: row-lengthRDAREA-page-length 1000 1000

key-length MIN((RDAREA-page-length 2) - 1,240, 4,036)

KFPX24223-E L

RDAREA aa....aa not specified

RDAREA aa....aa was not specified in the control statement.

aa....aa: RDAREA name

S: Terminates processing

Action

Specify RDAREA aa....aa or others in the server operand, and then re-execute.

KFPX24224-E L

Unable to send message from aa....aa to bb....bb

A communication error occurred between host aa....aa and host bb....bb.

aa....aa: Send source host name#

bb....bb: Send destination host name#

#: If the system switchover facility is being used, the host name of the primary system is indicated.

S: Terminates processing.

Action

Take action appropriate to the KFPX24210-E message, which was output before this message. If the error is not a physical communication error, there may be an inconsistency in the system definitions concerning the relationship between the hosts; check the interhost definitions for the hosts affected by the error and re-execute.

KFPX24225-I L

Processing of aa....aa statement ended, RDAREA name="bb....bb"

The aa....aa process of the database structure modification utility ended for RDAREA "bb....bb".
However, because the transaction is not concluded until the KFPX24226-I message is output, processing is rolled back if the return code in KFPX24226-I is 8.

aa....aa: Database structure modification utility function:

create rdarea: Add RDAREA

bb....bb: RDAREA name

S: Resumes processing.

KFPX24226-I L

Processing of create rdarea statement ended return code=a

The addition of a dictionary RDAREA or registry RDAREA terminated with a return code indicated in a.

a: Return code:

0: Normal completion

4: Warning error occurred, but processing terminated.

8: Terminated abnormally. By referring to the preceding error messages, correct the cause of the error, and then re-execute.

S: Resumes processing.

KFPX24227-E L

Line aaaa:unable to specify bb....bb and cc....cc statement at the same time

Functions bb....bb and cc....cc of the database structure modification utility cannot be specified in the same control statements file.

aaaa: Line number

bb....bb: Database structure modification utility function:

alter HiRDB mode: Change RDAREA from HiRDB/Single Server configuration to HiRDB/Parallel Server configuration.

alter rdarea: Modify RDAREA.

alter system: Modify system definitions.

create rdarea: Add RDAREA.

expand rdarea: Expand RDAREA.

initialize rdarea: Reinitialize RDAREA.

remove rdarea: Delete RDAREA.

cc....cc: Database structure modification utility function:

create rdarea for system:

Add data dictionary RDAREA or data dictionary LOB RDAREA.

S: Terminates processing.

Action

Specify functions that cannot be specified in the same control statements file in separate files and re-execute the functions independently.

KFPX24228-E L

Unable to omit DATADICTIONARY LOB RDAREA

No control statement for adding a data dictionary LOB RDAREA was specified.
In the cases shown below, two data dictionary LOB RDAREAs with the LOB used by HiRDB (SQL_ROUTINES) specification must be specified in the same control statements file:

To add an RDAREA with the datadictionary of routines specification

To add a data dictionary LOB RDAREA with the LOB used by HiRDB (SQL_ROUTINES) specification

S: Terminates processing.

Action

Define two RDAREAs with the LOB use by HiRDB (SQL_ROUTINES) specification in the same control statement and re-execute.

KFPX24229-E L

Control statement for create rdarea in system must first statement of control statement file

Control statements for adding data dictionary RDAREAs and data dictionary LOB RDAREAs must be specified at the beginning of the control statements file.

S: Terminates processing.

Action

Specify the control statements for adding data dictionary RDAREAs and data dictionary LOB RDAREAs at the beginning of the control statements file and re-execute.

KFPX24230-E L

Line aaaa:unable to create rdarea due to already exist RDAREA type

An RDAREA of the type of RDAREA to be added already exists in the system.

aaaa: Line number

S: Terminates processing.

Action

Delete unneeded control statements and re-execute.

KFPX24231-W L

Unable to initialize LOB column aa....aa. bb....bb due to cc....cc, RDAREA name="dd....dd"

RDAREA "dd....dd", which stores a LOB column of LOB column structure base table aa....aa.bb....bb, cannot be initialized because cc....cc.

aa....aa: Authorization identifier

bb....bb: Table identifier

cc....cc: Reason for error:

RDAREA status is invalid: The RDAREA status is invalid.

HiRDB system error occurred: An SQL error occurred.

dd....dd: Name of user LOB RDAREA

S: Aborts initialization of the affected user LOB RDAREA and executes the next process.

Action

Do one of the following:

Set user LOB RDAREA "dd....dd" to HOLD or CLOSE status, and then reinitialize "dd....dd".

Eliminate cause cc....cc, and then re-execute this control statement.

Execute the PURGE TABLE statement for the LOB column structure base table.

If no action is taken and retrieval or insertion is executed on table aa....aa.bb....bb, the results are not guaranteed because the LOB column data has not been deleted.

KFPX24232-E L

Unable to initialize rdarea "aa....aa" allocated for SQL_ROUTINES.DEF_SOURCE

RDAREA aa....aa cannot be reinitialized because it is a data dictionary LOB RDAREA allocated to the DEF_SOURCE column of the SQL_ROUTINES data dictionary table.

aa....aa: Name of data dictionary LOB RDAREA

S: Terminates processing.

Action

Execute re-initialization of the database dictionary LOB RDAREA only for RDAREAs in which objects are stored.

KFPX24233-E L

Definition file aa....aa open failed: bb....bb

Open error occurred in definition file aa....aa under %PDDIR%\lib\sysdef for reason bb....bb.

aa....aa: File name

bb....bb: Reason for the open error:

no such file: The specified file was not found in %PDDIR%\lib\sysdef.

permission denied: The specified file was found, but there was no applicable privilege.

errno=cccc: Processing terminated with error code cccc.

S: Terminates processing.

Action

Contact the customer support center.

KFPX24234-E L

Unable to execute "cc....cc" in "alter system" statement due to exist view table derived from DATADICTIONARY, view table name "aa....aa".bb....bb

The "cc....cc" operand of the alter system statement cannot be executed because no viewed table refers to the dictionary table.
All viewed tables that refer to the dictionary table must be deleted.

aa....aa: Authorization identifier

bb....bb: Name of the viewed table

cc....cc: Operand name

S: Terminates processing.

Action

Delete the viewed tables that refer to the dictionary table, and then re-execute. To determine the names of the viewed tables that refer to the dictionary tables, execute the following SQL statement:

SELECT VIEW_SCHEMA, VIEW_NAME
FROM MASTER.SQL_VIEW_TABLE_USAGE
WHERE BASE_OWNER='MASTER'

KFPX24235-E L

Line aaaa:unable to specify "dicinf limited" due to "HiRDB security" is "no"

dicinf limited cannot be specified in the alter system statement because the HiRDB security function is not being used.

aaaa: Line number

S: Terminates processing.

Action

To specify dicinf limited, specify HiRDB security yes, and restart processing with the database initialization utility.

KFPX24236-E L

Unable to execute "aa....aa" in "alter system" due to UAP and/or utility is executing

The "aa....aa" operand in the alter system statement cannot be executed because a UAP or utility is executing.

aa....aa: Operand name

S: Terminates processing.

Action

Re-execute the operand after all UAPs and utilities that are accessing the dictionary table have terminated.

KFPX24237-I L

Dicinf mode change to aa....aa

dicinf was changed to aa....aa.

aa....aa: Type of change:

limited: Referencing of the dictionary table is restricted.

unlimited: Referencing of the dictionary table is not restricted.

S: Terminates processing.

Action

Re-execute after all UAPs and utilities that are accessing the dictionary table have terminated.

KFPX24238-W L

SQL OBJECT of procedure "aa....aa".bb....bb invalidated

The SQL object of procedure "aa....aa".bb....bb was invalidated.

aa....aa: Authorization identifier

bb....bb: Routine identifier

S: Resumes processing.

Action

Re-create the SQL object for procedure "aa....aa".bb....bb using the ALTER ROUTINE statement. For a procedure with an authorization identifier MASTER and a routine identifier that begins with SQL_REGISTRY, re-create the SQL object by specifying -k renew in the Registry Function Initialization Utility (pdreginit).

When the database structure modification utility (pdmod) is used to change the RDAREA name, an error will occur during the execution of ALTER ROUTINE if you have specified the previous RDAREA name in the SQL procedure statements in procedure "aa....aa".bb....bb. In this case, re-create the routine or trigger as follows:

Execute GET DIAGNOSTICS, and identify the routine or trigger that produced the error using the diagnostic information for ALTER ROUTINE.

Use DROP PROCEDURE or DROP TRIGGER to delete the routine or trigger that produced the error.

Change the RDAREA name in the SQL procedure statements to the new RDAREA name.

Re-create the routine or trigger using CREATE PROCEDURE or CREATE TRIGGER.

KFPX24239-I L

Dictionary datatype mchar changed to "use"

The dictionary datatype mchar option was changed to "use".

S: Resumes processing.

KFPX24240-W L

Line aaaa:"bb....bb" operand ignored because cannot specified

Operand "bb....bb" was ignored because it cannot be specified.

aa....aa: Line number

bb....bb: Operand name

open attribute:

This operand cannot be specified for a master directory, data directory, data dictionary, or data dictionary LOB RDAREA.

S: Resumes processing.

Action

Delete operand "bb....bb".

KFPX24241-E L

Line aaaa:dd....dd operand value bb....bb invalid, because HiRDB file size exceeds ccc byte

The specified value bb....bb is invalid for the initial operand, because the HiRDB file in the database will exceed maximum value ccc (bytes) if created based on the specified value.
The specified value bb....bb is invalid for the extension operand, because the HiRDB file in the database will exceed maximum value ccc (bytes) after automatic extension if created based on the specified value.

aaaa: Line number

bb....bb: Specified value

ccc: Maximum value:

When using large files:

64G: 64 gigabytes

When not using large files:

2G: 2 gigabytes

dd....dd: Specified operand:

initial: initial operand

extension: extension operand

S: Terminates processing after analyzing all control statements.

Action

Specify a smaller value in this control statement operand and re-execute.

KFPX24242-W L

Unable to aa....aa bb....bb.cc....cc due to dd....dd, RDAREA name="ee....ee"[(generation number ff)]

Processing aa....aa on storage RDAREA "ee....ee" at bb....bb.cc....cc cannot be performed due to the reason dd....dd.

aa....aa: Processing type

purge BLOB attribute: Deletion of BLOB-attribute data

purge PLUGIN INDEX: Deletion of plug-in index data

set check pending status: Set in check pending status

bb....bb: Authorization identifier

cc....cc: Table identifier or index identifier

dd....dd: Reasons for the error

RDAREA status is invalid: RDAREA status error

HiRDB system error occurred: SQL error

not found replica RDAREA: Replica RDAREA does not exist

ee....ee: RDAREA name

Outputs the bb....bb.cc....cc storage RDAREA name. However, if the reason for the error is not found replica RDAREA, the name of the original RDAREA where the replica RDAREA was not found is output.

ff: Generation number (1 to 10)

The generation number of the replica RDAREA that did not exist is output only when the error reason is not found replica RDAREA.

S: Skips processing aa....aa on the indicated RDAREA; continues with the next processing operation.

Action

Processing type is purge BLOB attribute or purge PLUGIN INDEX
If the problem is an RDAREA status error, either RELEASE or OPEN the RDAREA at "ee....ee". If the problem is an SQL error, see the preceding SQL message, correct the cause of the problem, and then re-execute.

Processing type is set check pending status
Forcibly set bb....bb.cc....cc in check pending status. Also, if the "ee....ee" RDAREA is using the inner replica facility, specify the generation number of "ee....ee", and forcibly set it in check pending status. However, if the reason for the error is not found replica RDAREA, the corresponding RDAREA does not exist; create a replica RDAREA with generation number ff, or combine RDAREAs, and then use an integrity check utility to check the integrity. For details about the procedure for integrity checking, see the manual HiRDB Version 9 Installation and Design Guide.

KFPX24244-I L

Unable to delete LIST data, rdarea id = aa....aa

Deletion of list data created from a table stored in the RDAREA that was to be initialized failed.

aa....aa: ID of list RDAREA in which the error occurred

Format: A 10-digit RDAREA ID is displayed (9 is used as the padding character for IDs that consist of fewer characters than 10 digits); the comma (,) is used as a delimiter.

S: Continues processing.

P: If an error occurred in the list RDAREA identified in this message, an error may occur during list re-creation or list deletion following re-initialization completion. Determine the error details based on the message that is output before this message and identify the RDAREA from the RDAREA ID that is output in this message, and investigate the cause of the error.

KFPX24245-W L

Line aaaa:max entries raised to bb....bb

Because the value specified for the max entries operand in the create rdarea statement or initialize rdarea statement was not a multiple of 500, it was rounded up to bb....bb. This operand specifies the maximum number of lists that can be created in a list RDAREA.

aaaa: Line number

bb....bb: Rounded-up number

S: Continues processing.

KFPX24246-W L

Extension use specification for RDAREA aa....aa ignored, due to no expand option for HiRDB file system area of last HiRDB file

Specification of extension use is invalid because extension (-e option or -a option of the pdfmkfs command) is not specified for the HiRDB file system area in which the last HiRDB file comprising RDAREA aa....aa was created.

aa....aa: RDAREA name

S: Continues processing.

Action

To use the automatic extension facility, extension must be specified for the applicable HiRDB file system area. Use the -e option of the pdfmkfs command to specify the maximum number of extensions, or the -a option to specify automatic extension.

KFPX24247-E L

Unable to remove generation "aa....aa" due to bb....bb

HiRDB file system area generation "aa....aa" could not be deleted because of reason bb....bb.

aa....aa: HiRDB file system area name whose generation is to be deleted

bb....bb: Reason

original HiRDB file system area: Specified the original HiRDB file system area.

exist replica rdarea: The replica RDAREA is using the target HiRDB file system area.

not defined: The generation of the specified HiRDB file system area is not registered.

S: Terminates processing.

Action

Deleting all generation information for the HiRDB file system area makes it possible to delete the original HiRDB file system area. When the replica RDAREA uses the HiRDB file system area, use the following SQL statements to check the replica RDAREA. Delete the replica RDAREA if it is unnecessary, and then re-execute the command.

SELECT RDAREA_NAME
 FROM MASTER.SQL_RDAREAS X,MASTER.SQL_PHYSICAL_FILES Y
   WHERE X.ORIGINAL_RDAREA_ID IS NOT NULL
     AND X.RDAREA_NAME = Y.RDAREA_NAME AND X.SERVER_NAME='server-name'
     AND Y.PHYSICAL_FILE_NAME LIKE 'HiRDB-file-system-area-name%'

KFPX24248-E L

Unable to initialize rdarea "aa....aa" due to not found replica RDAREA(generation number bb) for original RDAREA "cc....cc"

Another RDAREA cannot be processed while RDAREA "aa....aa" is being initialized, because the replica RDAREA for generation number bb in original RDAREA "cc....cc" was not found.

aa....aa: Name of the RDAREA to be reinitialized

bb: Generation number

cc....cc: Name of original RDAREA used to process another RDAREA

S: Terminates processing.

Action

Create the corresponding replica RDAREA, and then re-execute the command.

KFPX24249-E L

Unable to "aa....aa" due to generation already registerd in HiRDB file system area

Process "aa....aa" could not be performed because the generation of the HiRDB file system area was already registered.

aa....aa: Process

alter HiRDB mode: Reconfigure to a HiRDB/Parallel Server

S: Terminates processing.

Action

Delete all generation information in the HiRDB file system area, and then re-execute the command.

KFPX24250-E L

Unable to aa....aa rdarea due to invalid replica status

Process aa....aa could not be performed because the replica status of the replica RDAREA is invalid.

aa....aa: Process

remove: Deletes the RDAREA

S: Terminates processing.

Action

Change the replica status of the replica RDAREA from current to sub, and then re-execute the command.

KFPX24251-W L

Not found HiRDB file system area "aa....aa"

The replica HiRDB file system area or original HiRDB file system area could not be found.

aa....aa: HiRDB file system area name

S: Continues processing.

Action

Because the generation information of the HiRDB file system area is already registered, you have to create an applicable HiRDB file system area before using the replica RDAREA.

KFPX24252-E L

Unable to recast rdarea due to aa....aa rdarea "bb....bb" in progress

The RDAREA could not be integrated because RDAREA "bb....bb" is performing the aa....aa process.

aa....aa: Process

initialize: Initializes the RDAREA.

remove: Deletes the RDAREA

bb....bb: RDAREA name

S: Terminates processing.

Action

Re-execute the command after the aa....aa process terminates.

KFPX24253-E L

Staticizer Option required

The HiRDB Staticizer Option is required to register the generation of the HiRDB file system area or define the replica RDAREA.

S: Terminates processing.

Action

Install the HiRDB Staticizer Option, and then re-execute the command.

KFPX24254-E L

Unable to replicate rdarea due to not exist table or index

The replica RDAREA could not be defined because no table, index, or LOB column was defined in the original RDAREA.

S: Terminates processing.

Action

Check if the target original RDAREA is correct, and then re-execute the command.

KFPX24255-E L

Unable to aa....aa due to not specified original RDAREA

Process aa....aa could not be performed because the original RDAREA was not specified.

aa....aa: Reconfiguration process

replicate rdarea: Defines RDAREA replica.

recast rdarea: Integrates the RDAREA.

S: Terminates processing.

Action

Specify the original RDAREA, and then re-execute the command.

KFPX24256-E L

Number of replica count exceed 10,replica count limit over RDAREA aa....aa

The replica counter exceeded the maximum value of 10 at RDAREA aa....aa.

aa....aa: Name of the RDAREA where the replica counter exceeded the maximum value (original RDAREA)

S: Terminates processing.

Action

Check the number of replica definitions in the original RDAREA, and then re-execute the command.

KFPX24257-E L

Unable to define copy rdarea due to specified RDAREA aa....aa invalid original RDAREA/replica RDAREA

The configuration information of the RDAREA could not be copied because specified RDAREA aa....aa was neither the original RDAREA nor the replica RDAREA.

aa....aa: RDAREA name

S: Terminates processing.

Action

Check if the specified RDAREA is correct. Specify either the original RDAREA or the replica RDAREA, and then re-execute the command.

KFPX24258-E L

Unable to define copy rdarea due to invalid sameness original RDAREA

The configuration information of the RDAREA could not be copied because the original RDAREA of the RDAREA specified in the copy destination and copy source were not the same.

S: Terminates processing.

Action

Check the original RDAREA name of the RDAREA specified in the copy destination and copy source, and then re-execute the command.

KFPX24259-E L

Unable to aa....aa due to create generation invalid HiRDB file system area

Process aa....aa could not be performed because the generation of the HiRDB file system area was not registered.

aa....aa: Reconfiguration process

replicate rdarea: RDAREA replica definition

define copy rdarea: Copies configuration information of the RDAREA

S: Terminates processing.

Action

Register the generation of the HiRDB file system area, and then re-execute the command.

KFPX24260-E L

Unable to recast rdarea due to invalid original RDAREA replica count 1

RDAREA could not be integrated because the replica counter of the original RDAREA was not 1.

S: Terminates processing.

Action

Check the replica counter count of the original RDAREA, and then re-execute the command.

KFPX24261-I L

HiRDB system must restarted

Always restart the HiRDB system after you have migrated an RDAREA.

S: Continues processing.

Action

Restart the HiRDB system.

KFPX24262-E L

Line:aaaa:unable to move rdarea "bb....bb" due to lack of specification for related RDAREA "cc....cc"

RDAREA "bb....bb" could not be migrated because related RDAREA "cc....cc" was not specified.

aaaa: Row number

bb....bb: RDAREA to be migrated

cc....cc: Related RDAREA

S: After analysis of the applicable control statement ends, processing terminates, and then processing of the next control statement starts.

Action

Specify all related RDAREAs, and then re-execute the command.

KFPX24263-E L

Line aaaa:unable to move rdarea "bb....bb" due to rdarea in different server

RDAREA "bb....bb" could not be migrated because a different back-end server was specified.

aaaa: Row number

bb....bb: RDAREA name

S: After analysis of the applicable control statement ends, processing terminates, and then processing of the next control statement starts.

Action

Specify only RDAREAs on the same server, and then re-execute the command.

KFPX24264-E L

Line aaaa:unable to move rdarea. Source BES and destination BES identical

The RDAREA could not be migrated because the current server name of the migration target RDAREA was specified.

aaaa: Row number

S: After analysis of the applicable control statement ends, processing terminates, and then processing of the next control statement starts.

Action

Respecify the server name of the migration destination, and then re-execute the command.

KFPX24265-E L

Line aaaa:unable to move rdarea "bb....bb" due to NONDIV_IDX defined, index_name=cc....cc. "dd....dd"

The RDAREA could not be migrated because a non-partitioning key index was defined in specified RDAREA "bb....bb".

aaaa: Row number

bb....bb: RDAREA name

cc....cc: Authorization identifier

dd....dd: Index identifier

S: After analysis of the applicable control statement ends, processing terminates, and then processing of the next control statement starts.

Action

Drop the non-partitioning index, and then re-execute the command.

KFPX24266-E L

Line aaaa:unable to move rdarea "bb....bb" due to create generation invalid HiRDB file system area

The RDAREA could not be migrated because the generation of the HiRDB file system area in the HiRDB file comprising specified RDAREA "bb....bb" was not registered on the migration target server.

aaaa: Row number

bb....bb: RDAREA name

S: After analysis of the applicable control statement ends, processing terminates, and then processing of the next control statement starts.

Action

Register the generation of the HiRDB file system area on the migration target server, and then re-execute the command.

KFPX24268-E L

Unable to aa....aa rdarea "bb....bb" due to exist INSERT ONLY table cc....cc.dd....dd

aa....aa could not be performed because falsification prevented table cc....cc.dd....dd was found in RDAREA "bb....bb".

aa....aa: Database structure modification utility (pdmod) facility

initialize: Reinitializes the RDAREA.

replicate: RDAREA replica definition

bb....bb: RDAREA name

cc....cc: Authorization identifier

dd....dd: Table identifier

S: Processing of the applicable control statement terminates, and then processing of the next control statement starts.

Action

When reinitializing the RDAREA, take one of the following actions:

When recovery is necessary, recover from a backup file.

To increase the RDAREA size, either expand the RDAREA (expand rdarea) or perform automatic extension of the RDAREA.

KFPX24269-E L

Unable to aa....aa because bb....bb already exists in HiRDB system

aa....aa could not be performed because bb....bb was already registered or created.

aa....aa: Database structure modification utility facility

create auditor: Registers an auditor.

create audit table: Creates an audit trail table.

bb....bb: Auditor or audit trail table

auditor: Auditor

audit table: Audit trail table

S: After analysis of the applicable control statement ends, processing terminates, and then processing of the next control statement starts.

Action

When recreating an audit trail table, execute the command after the auditor drops the audit trail table using DROP TABLE.

KFPX24270-E L

Unable to create audit table unless privilege for RDAREA "aa....aa" granted only auditor

An audit trail table could not be created because a user other than the auditor had usage privileges to RDAREA "aa....aa".

aa....aa: RDAREA name

S: After analysis of the applicable control statement ends, processing terminates, and then processing of the next control statement starts.

Action

Specify an RDAREA for users so that only the auditor has usage privileges, and then re-execute the command.

KFPX24271-E L

Unable to create auditor because user "aa....aa" bb....bb

Because user "aa....aa" is bb....bb, he or she cannot be registered as an auditor.

aa....aa: Authorization identifier

bb....bb: Reason

has DBA privilege: User "aa....aa" already has the DBA privilege.

password account locked: User "aa....aa" is in a password invalid account lock state.

S: After analysis of the applicable control statement ends, processing terminates, and then processing of the next control statement starts.

Action

Take one of the following actions:

If the reason is has DBA privilege:
Take one of the following actions:
Use the REVOKE statement to delete the user's DBA privilege, and then re-execute the command.
Specify a user who does not have DBA privilege or a new user, and then re-execute the command.

If the reason is password account locked:
Either clear the password invalid account lock state or specify a user (including new users) who is not in password invalid account lock state, and then re-execute the command.

KFPX24272-E L

Unable to create audit table due to no auditor

An audit trail table could not be created because there was no auditor.

S: After analysis of the applicable control statement ends, processing terminates, and then processing of the next control statement starts.

Action

Register an auditor using the create auditor statement in the database structure modification utility, and then re-execute.

KFPX24273-E L

Unable to create audit table due to duplicate table name aa....aa.bb....bb

This name could not be used in the audit trail table because table aa....aa.bb....bb already exists.

aa....aa: Authorization identifier

bb....bb: Table identifier

S: After analysis of the applicable control statement ends, processing terminates, and then processing of the next control statement starts.

Action

Give the audit trail table a different name, and then re-execute the command.

KFPX24274-E L

Unable to create shared RDAREA aa....aa due to not specified pd_shared_rdarea_use=Y

Y is not specified in the pd_shared_rdarea_use operand; unable to add the shared RDAREA aa....aa.

aa....aa: RDAREA name

S: Cancels the structural change on the specified RDAREA and continues processing another control statement.

Action

Terminate HiRDB, assign Y to the pd_shared_rdarea_use operand, and then re-execute the command.

KFPX24275-E L

No schema for aa....aa

A schema is missing; unable to create an audit trail table.

aa....aa: Authorization identifier for the auditor for which a schema is missing (8-character maximum)

S: Cancels the structural change on the specified RDAREA and continues processing another control statement.

Action

Use create schema to create a new schema, and then re-execute the command.

KFPX24276-E L

Unable to replicate rdarea "aa....aa" due to exist SEQUENCE,number=bbb

The RDAREA replica definition cannot be executed because a sequence generator does not exist in RDAREA aa....aa.

aa....aa: RDAREA name

bbb: Sequence generator stored in RDAREA aa....aa

S: Stops structure change processing of the RDAREA, and continues processing the following control statement.

Action

Delete all of the sequence generators stored in RDAREA aa....aa, and then re-execute.

KFPX24277-E L

Unable to aa....aa due to exist memory table or memory index

The structure change processing indicated in aa....aa cannot be performed because a memory database allocation table or index defined in that table does not exist in the RDAREA that was targeted for the structure change.

aa....aa: Structure change processing

move rdarea: RDAREA migration

replicate rdarea: RDAREA replica definition

alter HiRDB mode to parallel: Altering RDAREA attribute from a single server to a parallel server

S: Stops structure change processing of the RDAREA, and continues processing the following control statement.

Action

Deallocate the in-memory database, and then re-execute the configuration change. However, if you execute the RDAREA replica definition after deallocating the memory database, you cannot allocate the table that exists in that RDAREA to the memory database.

KFPX24278-E L

Unable to aa....aa "bb....bb" due to invalid operand combination

Structure modification processing aa....aa cannot be performed on RDAREA bb....bb due to an error in the specified combination of operands.
This message is output only if there is an error in the check for the prerequisite conditions when temporary table use is specified. This message is not output if nouse is specified.
When the shared operand (shared RDAREA) is also specified, an error results due to the combination of operands, and this message is output.

aa....aa: Structure modification processing

create rdarea: Addition of RDAREA

bb....bb: Name of RDAREA

S: Cancels structure modification processing for the corresponding RDAREA and processes the next control statement.

Action

A user RDAREA that is to be used as a temporary table RDAREA must be a public RDAREA. To specify a temporary table operand, specify user used by PUBLIC. Do not specify the shared operand (shared RDAREA) for a temporary table RDAREA.

KFPX24400-E L

HiRDB system "aa....aa" failed return code=bb....bb

The "aa....aa" function terminated with return code bb....bb.

aa....aa: Function name:

pd_com_call: Communication calling

pdi_adm_get_my_orghostname: Collection of host name

pdi_adm_pdmgrinf: Collection of manager server information

pdi_adm_pddicinf: Collection of dictionary server information

pdi_ndm_branchreg: Branch registration

pdi_ndm_branchdel: Deletion of branch registration

pdi_utl_sh_prolog: Start of RPC environment

pdi_utl_sh_epilog: Termination of pdvrup control process

bb....bb: Detail code of system-related error

S: Terminates processing

Action

See 4.2 Detail codes for system-related errors to eliminate the cause of the error and re-execute.

KFPX24401-I E

Usage:pdvrup

Displays the specification format for the pdvrup command. There are no options in this command.

S: Terminates processing.

Action

Correct the command's format and re-execute.

KFPX24402-E L

System call error, func=aa....aa, errno=bbbb

An error occurred while system function aa....aa was executing.

aa....aa: Function that was executing

bbbb: Error code

S: Terminates processing.

Action

Eliminate the cause of the error based on the error code and re-execute.

KFPX24403-E L

Pdvrup must be executed at unit where manager is defined

The pdvrup command must be executed at the server machine where the system manager is defined.

S: Terminates processing.

Action

Log onto the remote server machine where the system manager is defined and execute the pdvrup command.

KFPX24404-I L

Pdvrup ended, return code=aa

The pdvrup command terminated with return code aa.

aa: Return code:

0: Normal termination

4:An error occurred during execution of the pdvrup command; the version upgrading terminated normally. Terminate HiRDB, and then restart it.

12: Abnormal termination

S: Terminates processing.

Action

If the return code is 12, correct the error by referring to the error message that is output and then re-execute.

KFPX24405-E L

Insufficient memory on PROCESS, size=aa....aa

Because of a memory shortage, a process private area could not be allocated during execution of the pdvrup command.

aa....aa: Area size that was to be allocated (in bytes)

S: Terminates processing.

Action

Check the total number of processes, including processes external to HiRDB, delete unneeded processes, and then re-execute. If this message is output repeatedly, contact the customer support center.

KFPX24406-E L

Message output failed, return code=aa....aa, msgno=bbbbb

An attempt to output a message to a log file terminated with return code aa....aa.

aa....aa: System-related error detail code

bbbbb: Message number that was to be output

S: Terminates processing.

Action

Correct the error by referring to 4.2 Detail codes for system-related errors.

KFPX24407-E L

Unable to execute "pdvrup" at the same time

Because the pdvrup command is already being executed, the pdvrup command that was specified subsequently cannot be executed.

S: Terminates processing.

Action

Wait for the pdvrup command being executed to terminate.

KFPX24408-E L

Pdvrup command failed, due to DATABASE Version already coincide with HiRDB version, version=aaaaa

Version upgrading was not executed because the HiRDB version already matches the dictionary version.

aaaaa: Version number

S: Terminates processing.

KFPX24409-E L

Pdvrup command terminated, due to server process abnormal end

Remote server process terminated abnormally during execution of the pdvrup command.

S: Terminates processing.

Action

Unless the server process was terminated with the pdstop or pdcancel command, contact the customer support center.

KFPX24410-E L

Definition file aa....aa open failed: bb....bb

Open error occurred in definition file aa....aa under %PDDIR%\lib\sysdef for reason bb....bb.

aa....aa: File name

bb....bb: Reason for the open error:

no such file:

The specified file was not found in %PDDIR%\lib\sysdef.

permission denied:

The specified file was found, but there was no applicable privilege.

errno=cccc:

Processing terminated with error code cccc.

S: Terminates processing.

Action

Contact the customer support center.

KFPX24600-I S

Pdreginit command start at aa....aa on bb....bb

The Registry Function Initialization Utility was started.

aa....aa: Starting time (hh:mm:ss)

hh: hour

mm: minute

ss: second

bb....bb: Starting date (yyyy/mm/dd)

yyyy: year

mm: month

dd: day

S: Resumes processing.

KFPX24601-I S

Pdreginit command for ended return code=a at bb....bb on cc....cc

The Registry Function Initialization Utility terminated on return code a.

a: Return code

0: Normal termination

4: A warning-level error was detected, but processing terminated.

8: The utility terminated abnormally. See the preceding message, correct the cause of the error, and then re-execute.

bb....bb: Starting time (hh:mm:ss)

hh: hour

mm: minute

ss: second

cc....cc: Starting date (yyyy/mm/dd)

yyyy: year

mm: month

dd: day

S: Terminates processing.

KFPX24602-E S

Invalid option is specified with pdreginit command

An option not specifiable in the pdreginit command has been specified. Or, an option has been specified without an argument.

S: Terminates processing.

Action

Either specify the correct option or the argument for the option and re-execute.

KFPX24603-I S

Usage: pdreginit [-k {all|proc|renew} ] [-a statement_control_file_name]

An option for the Registry Function Initialization Utility (pdreginit) contains a specification format error.

S: Terminates processing.

Action

Specify the pdreginit utility correctly and re-execute.

KFPX24604-E S

No RDAREA for routine definition

A data dictionary LOB RDAREA is not defined. Therefore, a registry RDAREA and a registry LOB RDAREA cannot be added.

S: Terminates processing.

Action

Define a data dictionary LOB RDAREA using the Database Structure Modification Utility (pdmod) and re-execute.

KFPX24605-E S

EXEC SQL aa....aa Error

The SQL statement indicated by aa....aa is in error.

aa....aa: SQL statement on which execution was attempted

S: Terminates processing.

Action

Correct the cause of the error based on the error message following this message and re-execute.

KFPX24606-E L

Unable to omit registry RDAREA or registry LOB RDAREA

A control statement for adding a registry RDAREA or a registry LOB RDAREA is not specified.
For adding an RDAREA with a for registry specification or an RDAREA with a for LOB used by HiRDB (SQL_REGISTRY) specification, specify both control statements.

S: Terminates processing.

Action

Define an RDAREA with a for registry specification and an RDAREA with a for LOB used by HiRDB (SQL_REGISTRY) specification in the same control statement file, and then re-execute.

KFPX27000 level

Messages output by HiRDB SQL Executer

Messages (KFPX27001 to KFPX27999) output by HiRDB SQL Executer. For details, see online Help for HiRDB SQL Executer.

KFPX28400-I L+S

aa....aa process started

aa....aa processing has started.

aa....aa: Processing { Export|Import|Create DDL }

S: Resumes processing.

KFPX28401-I L+S

aa....aa process terminated

aa....aa processing has terminated.

aa....aa: Processing { Export|Import|Create DDL }

S: Resumes processing.

KFPX28402-I L+S

aa....aa, name="bb....bb"."cc....cc"

Table "bb....bb"."cc....cc", stored procedure "bb....bb"."cc....cc", or trigger "bb....bb"."cc....cc" was exported or imported, or definition SQL statements were generated.

aa....aa: Processing that was executed

{Procedure exported|Procedure imported|Table exported|Table imported|Trigger exported|Trigger imported|DDL Created}

bb....bb: Schema name (PUBLIC for a public view or public procedure)

cc....cc: Table identifier, routine identifier, or trigger identifier

S: Resumes processing.

KFPX28403-E E+S+L

HiRDB call error, func=aa....aa, errno=bb....bb

An error occurred during control processing between a utility and HiRDB.

aa....aa: Processing in which error occurred

{connect|disconnect|commit|rollback}

For all other cases, the code indicates the HiRDB processing type.

bb....bb: Error code

S: Terminates processing.

O: Take one of the following actions. If the operator cannot resolve the error, notify the HiRDB manager.

If another message was output before this message:

Take action appropriate to the previous message.

If no message was output before this message:

See 4. Error Detail Codes, correct the error, and then re-execute the command.

KFPX28404-E E+L+S

System call error, func=aa....aa, errno=bb....bb

An error occurred in a system function.

aa....aa: System function

bb....bb: Error code

S: Terminates or resumes processing.

O:

Message was output before this message:

Take action appropriate to that message.

Error occurred in system function indicated by func:

Check the errno of the system function and take action appropriate to the errno contents.

Error occurred in tcgetattr function during password input:

In UNIX, consider the following causes:

A utility was started by rsh (remote shell).

The terminal environment is invalid.

These messages are output before and after password input.

In Windows, the terminal environment is invalid. These messages are output before and after password input.

KFPX28405-E L+S

Dictionary error(aa....aa, bb....bb)

A dictionary error was detected.

aa....aa: Name of dictionary table

bb....bb: Cause of error

S: Terminates processing.

O: Check whether the dictionary was recovered correctly and recover it using the correct procedure.

KFPX28406-E E

RPC error occurred

In UNIX:
An error occurred during communication between a utility's pdexp control process and a server process.

In Windows:

An error occurred during communication between a utility server and a server process.

S: Terminates processing.

O: Check to see whether HiRDB started normally at the utility startup host or a host containing an export file.

KFPX28407-E E+L+S

File error occurred, func=aa....aa, file=bb

aa....aa error occurred in file bb.

aa....aa: Type of error

{ OPEN|CLOSE|READ|WRITE|CREATE }

bb: File name:

-e: Export file at the time of exporting

-f: Control statements file

-i: Import file

-p: Processing result output file

-o: Definition SQL output file

S: Terminates processing.

O:

OPEN error:

Check that the specified file name is correct.

Other error:

Check the specified file to see if required information has been set, such as privileges.

-o file:

Host name not specified in -i
Check the file specified in -o to see if required information (such as privileges) has been set.

Host name specified in -i
Check the file name specified in o or the temporary work file (file with name beginning with pdexp_sql) that is created under %PDDIR%\tmp at the corresponding host to see if required information (such as privileges) has been set.

-p file:

Check the contents of the message log file because the processing results are output to that file.

KFPX28408-E E

Invalid execution node

The server machine that started the pdexp utility is invalid.

S: Terminates processing.

O:

HiRDB/Single Server:
Start pdexp at the Single Server (SDS) server machine.

HiRDB/Parallel Server:
Start pdexp at the server machine of the system manager (MGR).

KFPX28409-E E

Invalid device, file=-f

The control statements file specified by -f is invalid, or the specified file cannot be accessed.

S: Terminates processing.

O: Specify the correct file, or check that the status of the directory in the path specification is correct.

KFPX28410-E E

Insufficient memory in message buffer pool due to concurrent execution of "pdexp"

When the pdexp command was executed concurrently, a temporary memory shortage occurred in the message storage buffer pool during process allocation.

S: Terminates processing.

O: Re-execute pdexp after the current pdexp execution is completed. If the number of XDSs to be started at the same time is greater than 32, set pd_utl_exec_mode to 1 in the system common definition.

KFPX28411-E E

Unable to send message from aa....aa to bb....bb

A communication error occurred between host aa....aa and host bb....bb.

aa....aa: Send source host name#

bb....bb: Send destination host name#

#: If the system switchover facility is being used, the host name of the primary system is indicated.

S: Terminates processing.

Action

Take action appropriate to the KFPX28403-E message, which was output before this message. If the error is not a physical communication error, there may be an inconsistency in the system definitions concerning the relationship between the hosts; check the interhost definitions for the hosts affected by the error and re-execute.

KFPX28412-E E

Invalid environment, reason=aaaaaa

An error was detected in the execution environment of the dictionary export/import utility.
The following is a possible cause:

In UNIX:

The utility is being executed in the remote shell environment.

An & was attached to the shell and the utility was executed in the background.

The utility was executed in an environment in which password response is disabled.

In Windows:

The utility was executed in an environment in which password response is disabled.

aaaaaa: Reason code:

no_tty: The execution environment does not have a terminal.

S: Terminates processing.

O: Reason code is no_tty:

To execute the utility in an environment in which password response is disabled, specify the authorization identifier and password in the PDUSER environment variable and re-execute without specifying the -u option on the command line.

KFPX28413-E E+S+L

File I/O error occurred, reason=aa....aa, func=bb....bb, errno=cc....cc, (dd....dd)

An error occurred during a file I/O operation.

aa....aa: Error reason

In UNIX, if the entry type of the file specified by Invalid-device cannot be identified, a single character enclosed in parentheses is displayed. This entry type is the same as the entry mode that was printed by specifying the OS's ls -l command.

Invalid-parameter:

The combination of specified parameter is invalid.

Invalid-device:

The entry type for the specified file is invalid.

File-format:

The specified format does not match the actual format.

File-lock:

A write was attempted on a file that the utility is reading or writing.

No-file:

The file to be opened for read does not exist. Or, the file being written to was erased.

Invalid-permission:

The specified file contains an invalid permission.

No-space:

The file to be written to does not have enough space.

Invalid-file:

An invalid file was specified.

bb....bb: Name of the system function in which the error occurred

If the error is not with a system function, the symbol *** is output.

cc....cc: Error number

The number 0 is output if no errors have occurred in a system function.

dd....dd: Name of the source file and the line number at which an error was detected

S: Terminates processing.

Action

Correct the cause of the error by referring to the error reason and the error number, and then re-execute.

KFPX28440-E E

Invalid option

An error was detected in the command line specification (an invalid option was specified).

S: Terminates processing.

O: Correct the option.

KFPX28441-I E

Usage: pdexp {-e [host_name:] export_file_name |-i [host_name:]export_file_name [-o output_file_name [-a]]} [-f statement_control_file_name] [-u user_name]

An error was detected in an option specification of the dictionary export/import utility.

S: Terminates processing.

O: Re-execute the utility with the correct specifications.

KFPX28442-E E

Unable to specify -e and -i at the same time

An error was detected on the command line (-e and -i were specified at the same time).

S: Terminates processing.

O: Specify either -e or -i, not both.

KFPX28443-E E

Missing aa....aa option

An error was detected on the command line (neither -e nor -i is specified, or -e is specified but -f is not).

aa....aa: Option name { -e/-i|-f }

S: Terminates processing.

O: Specify the option correctly.

KFPX28445-E E

Invalid value in aa option

One of the following errors was detected in the command line specification:

The value specified for the aa option is invalid.

The value specified for the aa option is too long (if the -u option is specified, there were more than 8 characters; if other than the -u option is specified, there were more than 1,023 bytes).

No value is specified for the aa option.

The value specified for the aa option is not an absolute path name.

aa: Name of invalid option

S: Terminates processing.

O: Specify the option correctly.

KFPX28446-E E

Invalid value in host name

One of the following errors was detected in the command line specification:

The host name specification is invalid.

The specified host name is not a host that supports export/import processing.

The specified host name indicates the host for a secondary system in the system switchover facility.

S: Terminates processing.

O: Specify the correct host name.

When executing this command on the local host in a HiRDB/Single Server, the host name should be omitted.

If the system switchover facility is used, specify the host name for the primary system.

KFPX28447-E E

Invalid aa....aa

During execution of the dictionary export/import utility, the authorization identifier or password that was specified in the environment variable was invalid.

aa....aa: Invalid item:

auth_id: Authorization identifier

password: Password

S: Terminates processing.

O:

auth_id is output:

Correct the contents of the PDUSER environment variable and re-execute the command.

password is output:

Correct the contents of the PDUSER environment variable and re-execute the command. If a password was entered as the response to an input response message, re-execute the command, making sure that the response is correct.

In the Windows edition of HiRDB, if the -u option is omitted, check if the character string specifying the authorization identifier or the password is not enclosed in single quotation marks (') at the command prompt.

Example of correct specification: PDUSER="root"/"root"

If specifying in a client environment definition (hirdb.ini), this is further enclosed in single quotation marks.

Example of correct specification: PDUSER='"root"/"root"'

KFPX28501-E E

Invalid environment for aa....aa

This HiRDB system cannot import or export aa....aa because there is no dictionary table for aa....aa.

aa....aa: {procedure|trigger}

S: Terminates processing.

O:

Export:

aa....aa cannot be exported because the system has no aa....aa.

Import:

Add RDAREAs for the stored procedures with the database structure modification utility, and then import the stored procedures.

KFPX28502-E L+S

Incompatible aa....aa between export and import system

Objects cannot be imported because the aa....aa of the export system is different from that of the import system.

aa....aa: Item:

byte order: Byte order

S: Terminates processing.

O: Export/import objects between systems that support the same byte order.

KFPX28503-E L+S

Incompatible character code set, HiRDB= aa....aa, export file=bb....bb

The character codes of the export file are inconsistent with the character codes of the import destination HiRDB.

aa....aa: HiRDB Character codes:

CHINESE: EUC Chinese kanji codes

LANG-C: One-byte character codes

SJIS: Shift JIS kanji codes

UJIS: EUC Japanese kanji codes

UTF-8: Unicode (UTF-8)

bb....bb: Export file character codes:

CHINESE: EUC Chinese kanji codes

LANG-C: One-byte character codes

SJIS: Shift JIS kanji codes

UJIS: EUC Japanese kanji codes

UTF-8: Unicode (UTF-8)

S: Terminates processing.

O: Export/import objects between systems that support the same type of character codes.

KFPX28504-W L+S

Unable to specify aa....aa name, reason~bb....bb, name="cc....cc"."dd....dd"

Triggers internally created by HiRDB during the table definition of a referencing table cannot be exported. Such triggers, which are created when a referencing table is imported/exported, need not be imported/exported.

aa....aa: Name

trigger

table

bb....bb: Reason

system trigger

AUDIT TRAIL TABLE

cc....cc: Schema name

dd....dd: Trigger name or table identifier

S: Ignores the processing of the specified name, and continues processing.

O: Take one of the following actions:

If bb....bb is system trigger, the name of the trigger internally created by HiRDB during the definition of the referencing table should not be specified as the name of the control statement.

If bb....bb is AUDIT TRAIL TABLE, the name of the audit trail table should not be specified as the name of the control statement.

KFPX28505-E E+L

Audit trail file write error, reason=aaaaa

An error occurred during output of the audit trail file. The audit trail for the utility is not output to the audit trail file.

aaaaa: Error detail code

S: Continues processing.

O: Resolve the cause of the error by referencing the error detail code. For details about error codes, see 4.2 Detail codes for system-related errors.

FPX29001-E S

Specified value aa....aa invalid

The specified value was outside the permitted range of values.

aa....aa: Specified invalid value

S: Ignores the specified value, in which case the set value is not changed.

Action

Select the menu again and correct the value.

KFPX29003-E S

Enter file or directory name with complete path name=aa....aa

The directory and file names must be absolute path names beginning with /.

aa....aa: Specified file name and directory name

S: Ignores the specified value, in which case the set value is not changed.

Action

Specify the complete path name.

KFPX29005-E S

Invalid file or director specified aa....aa bb....bb

The specified directory or file name was invalid.

aa....aa: Specified directory or file name

bb....bb: Type of error:

not character special file:

A raw file was selected, but the specified file was not a character special file; or, the specified file was not found.

invalid directory name:

A regular file was selected, but a file name was specified without the high-order directory name.

not UNIX file:

A regular file was selected, but the specified file was not a regular file.

S: Ignores the specified value, in which case the set value is not changed.

Action

Select the item again and enter the correct directory or file name.

KFPX29006-E S

Rdarea-add-menu can select after system generation

The Add RDAREA menu cannot be selected until system generation is completed.

S: Resumes processing.

Action

Add RDAREAs after system generation is completed.

KFPX29009-E S

System-generation can select after unit initialized

When a HiRDB/Parallel Server environment is being created, system generation cannot be selected until unit initialization has been completed. A unit has not been initialized, or initialization of the unit containing the system manager or dictionary server has not been completed.

S: Resumes processing by ignoring the specified value.

Action

Select the unit initialization menu to initialize units and generate the system after unit initialization has been completed.

KFPX29010-E S

Invalid status

Menu selection order is invalid. Or, HiRDB has already been started in the HiRDB directory where the HiRDB environment is to be created.

S: Ignores the specified value.

Action

Select the menus in the correct order.

To re-create the HiRDB environment in this HiRDB directory, terminate HiRDB, execute the pdsetup command, and then re-execute.

KFPX29011-E S

HiRDB directory or /tmp is full in aa....aa

Specified menu processing cannot be executed because there is not enough space in the HiRDB directory or /tmp at host aa....aa.

aa....aa: Name of the host where the space shortage occurred

S: Cancels the specified menu processing.

Action

Create at least 1 MB of space in the HiRDB directory and /tmp at host aa....aa and re-execute the menu.

KFPX29012-E S

Plugin-setup-menu can select after system generation

The plug-in setup screen can be selected only after system generation is complete.

S: Resumes processing by ignoring the specified value.

Action

After the system build is complete, select the plug-in setup screen from the main menu.

KFPX29013-E S

Invalid file or directory specified aa....aa

The specified directory or file name contains an error. The following are possible causes of the problem:

A plug-in PP is not installed.

A name specified in an item contains an error.

aa....aa: Specified directory or file name (for a remote host, hostname: is indicated at the beginning of the name)

S: Resumes processing.

Action

Check whether a plug-in PP is installed. If it is installed, check the name of the plug-in PP installation directory, the name of the plug-in, the name of the plug-in definition file, and the name of the plug-in PIC file.

After correcting the cause of the error, re-execute the plug-in setup option(s) in the plug-in setup menu.

KFPX29015-E S

Unable to setup PLUGIN for necessary parameter omitted

A required parameter is omitted on the plug-in setup screen; the plug-in was not installed.
The name of the plug-in PP installation directory, the name of the plug-in, the name of the plug-in definition file, and the name of the plug-in PIC file cannot be omitted on the plug-in setup screen.

S: Resumes processing.

Action

On the plug-in setup screen, specify the name of the plug-in PP installation directory, the name of the plug-in, the name of the plug-in definition file, and the name of the plug-in PIC file and then re-execute the plug-in setup option(s).

KFPX29017-E S

PLUGIN already exists

The specified plug-in is already registered.

S: Resumes processing.

Action

Confirm the values specified on the plug-in installation screen. After revising any values that need to be modified, re-execute.

KFPX29500-I L

HiRDB system generation start at aa....aa on bb....bb

HiRDB system environment generation will be started.

aa: Start time (hh:mm:ss)

bb....bb: Start date (yyyy/mm/dd)

S: Continues processing.

KFPX29501-I L

HiRDB system generation ended return code=aa....aa at bb....bb on cc....cc

HiRDB system environment generation has terminated.

aa....aa: Return code:

0: Normal termination

8: Abnormal termination

bb....bb: Termination time (hh:mm:ss)

cc....cc: Termination date (yyyy/mm/dd)

S: Terminates processing.

Action

If the return code is 8, HiRDB system environment generation failed and the process was cancelled. Correct the error by referring to the %PDDIR%\spool\result_generate.log file, and then re-execute environment generation from setup.

KFPX29502-I L

HiRDB definition files creation start, PDCONFPATH=aa....aa

Creation of a HiRDB system definition file group is starting.

aa....aa: Name of the directory in which the HiRDB system definition file group will be created

S: Continues processing.

KFPX29503-I L

HiRDB definition files creation ended

Creation of a HiRDB system definition file group has terminated.

S: Continues processing.

KFPX29504-I L

HiRDB file system area initialization for aa....aa start, file=bb....bb:cc....cc, size=dd....dd

Initialization of a HiRDB file system area is starting.

aa....aa: Purpose of the HiRDB file system area:

DB: For RDAREAs

SYS: For system files

WORK: For work tables

UTL: For utilities

SVR: For any purpose other than utilities

bb....bb: Host name

cc....cc: Name of the HiRDB file system area

dd....dd: Size of the HiRDB file system area (in MB)

S: Continues processing.

KFPX29505-I L

HiRDB file system area initialization ended, file=aa....aa:bb....bb

Initialization of a HiRDB file system area terminated.

aa....aa: Host name

bb....bb: Name of the HiRDB file system area

S: Continues processing.

KFPX29506-I L

HiRDB system file initialization for aa....aa start

Initialization of a system file is starting.

aa....aa: System file type:

system_log: System log file

synchronization_point_dump: Synchronization point dump file

server_status: Server status file

unit_status: Unit status file

S: Continues processing.

KFPX29507-I L

HiRDB system file initialization ended

Initialization of a system file has terminated.

S: Continues processing.

KFPX29508-I L

HiRDB system starting at aa....aa on bb....bb

Activation of the HiRDB system is starting.

aa....aa: Activation start time (hh:mm:ss)

bb....bb: Activation start date (yyyy/mm/dd)

S: Continues processing.

KFPX29509-I L

HiRDB system started at aa....aa on bb....bb

Activation of a HiRDB system has been completed.

aa....aa: Activation completion time (hh:mm:ss)

bb....bb: Activation completion date (yyyy/mm/dd)

S: Continues processing.

KFPX29510-I L

HiRDB management file creation start, HiRDB file system area=aa....aa

Creation of the HiRDB management information file is starting.

aa....aa: Name of the HiRDB file system area

S: Continues processing.

KFPX29511-I L

HiRDB management file creation ended

Creation of HiRDB management information has terminated.

S: Continues processing.

KFPX29512-E L

Specified directory aa....aa is not HiRDB directory

The directory specified in the PDDIR environment variable is not a HiRDB directory, or its setup has not been completed.

aa....aa: Name of the directory specified in the PDDIR environment variable

S: Terminates processing.

Action

If the name of the HiRDB directory is incorrect, correct it. If setup has not been completed, rebuild the environment after setup is completed.

KFPX29513-E L

Invalid HiRDB status, PDDIR=aa....aa

HiRDB is already active in the HiRDB directory in which an attempt to build a HiRDB environment is being made.

aa....aa: Name of the directory specified in the PDDIR environment variable

S: Terminates processing.

Action

Check the value specified in the PDDIR environment variable. If the specified value is correct, stop the active HiRDB, perform setup again, and then build an environment.

KFPX29514-E L

System call error, func=aa....aa, errno=bb....bb

An error occurred in a system function.

aa....aa: System function name

bb....bb: Error code

S: Terminates processing.

Action

Check the errno of the system function, correct the error, and then re-execute.

KFPX29515-E L

aa....aa file "bb....bb" open failed, reason code=cc....cc

Opening of file aa....aa failed.

aa....aa: File type:

Management: Management information

bb....bb: File name

cc....cc: Error detail code

S: Terminates processing.

Action

Check the error detail codes related to the management information access library, correct the error, and then re-execute.

KFPX29516-E L

HiRDB definition file creation failed, file="aa....aa"

Creation of a HiRDB system definition file failed.

aa....aa: File name

S: Terminates processing.

Action

Determine the cause of the error from the error message output to the execution results log file for environment building that was performed before this message was output, correct the error, and then re-execute.

KFPX29517-E L

HiRDB file system area initialization failed, path name="aa....aa"

Initialization of a HiRDB file system area failed.

aa....aa: Name of the HiRDB file system area

S: Terminates processing.

Action

Determine the cause of the error from the error message output to the execution results log file for environment building that was performed before this message was output, correct the error, and then re-execute.

KFPX29518-E L

HiRDB system file initialization failed, file="aa....aa"

Initialization of a system file failed.

aa....aa: File name

S: Terminates processing.

Action

Determine the cause of the error from the error message output to the execution results log file for environment building that was performed before this message was output, correct the error, and then re-execute.

KFPX29519-E L

HiRDB start failed

HiRDB system startup failed.

S: Terminates processing.

Action

Determine the cause of the error from the error message output to the execution results log file for environment building that was performed before this message was output, correct the error, and then re-execute.

KFPX29520-E L

HiRDB management file creation failed, reason code=aa....aa

Creation of the HiRDB management information file in the HiRDB file system area failed.

aa....aa: Error detail code

S: Terminates processing.

Action

Check the error detail codes related to the management information access library, correct the error, and then re-execute.

KFPX29521-I L

PLUGIN setup start

Plug-in setup is starting.

S: Continues processing.

KFPX29522-I L

PLUGIN setup ended

Plug-in setup has terminated.

S: Continues processing.

KFPX29523-I L

Registry initialization start

Registry initialization is starting.

S: Continues processing.

KFPX29524-I L

Registry initialization ended

Registry initialization has terminated.

S: Continues processing.

KFPX29525-I L

Processing of PLUGIN registration start

Plug-in registration is starting.

S: Continues processing.

KFPX29526-I L

Processing of PLUGIN registration ended

Plug-in registration has terminated.

S: Continues processing.

KFPX29527-E L

PLUGIN setup failed, PLUGIN name=aa....aa, install directory=bb....bb

Setup of plug-in aa....aa failed.

aa....aa: Plug-in name

bb....bb: Name of the installation directory in which the plug-in was to be set up

S: Terminates processing.

Action

Determine the cause of the error from the error message output to the execution results log file for environment building that was performed before this message was output, correct the error, and then re-execute.

KFPX29528-E L

Registry initialization failed

Registry initialization failed.

S: Terminates processing.

Action

Determine the cause of the error from the error message output to the execution results log file for environment building that was performed before this message was output, correct the error, and then re-execute.

KFPX29529-E L

Processing of PLUGIN registration failed, PLUGIN name=aa....aa

Registration of plug-in aa....aa failed.

aa....aa: Plug-in name

S: Terminates processing.

Action

Determine the cause of the error from the error message output to the execution results log file for environment building that was performed before this message was output, correct the error, and then re-execute.

KFPX29631-E D

The value of [aa....aa] is not numeric.

In the definition of the detail definition screen, a non-numeric value was specified in a numeric specification input item.

aa....aa: Name of the input item with an invalid specification value

S: Displays an error message; waits until the correct value is entered.

Action

Specify a numeric value, and then re-execute the command.

KFPX29632-E D

The value of [aa....aa] contains an out-of-range error.

In the definition of the detail definition screen, an out-of-range value was specified in an input item.

aa....aa: Name of the input item with an invalid specification value

S: Displays an error message; waits until the correct value is entered.

Action

Specify a value within the range, and then re-execute the command.

KFPX29633-E D

An error occurred when the operand information file was being read.
Detail: <aa....aa>
Error row: <bb....bb>

An error occurred during the reading of the operand information file (an internal information file for managing the simple setup tool).

aa....aa: Detailed information on the error (one of the following character strings is embedded):

Operand information is coded before the version.

Invalid operand information type.

Invalid operand format.

Invalid operand abbreviation criteria.

Invalid operand disclosure criteria.

Invalid target server type.

Invalid specifiable definition type.

Invalid value type.

Invalid minimum value.

Invalid maximum value.

Invalid OS type.

Invalid multiple operand specification criteria.

Invalid option flag abbreviation criteria.

Invalid option flag disclosure criteria.

Invalid flag argument criteria.

Operand information in COM0 format not found.

Operand information does not exist.

bb....bb: Error row

S:

In cases other than Operand information does not exist:
The operand that produced the error will not be editable in the detail definition screen.

In the case of Operand information does not exist:
Terminates processing.

Action

Re-install HiRDB, and then re-run the simple setup tool.

KFPX29634-E D

Operand information file (aa....aa) not found.

Operand information file aa....aa not found.

aa....aa: Name of the operand information file

S: Processing continues, but the operand in error cannot be edited on the detail definition screen.

Action

Set the operand information file indicated in aa....aa, and then re-execute the command.

KFPX29635-E D

Operand information file (aa....aa) is empty.

Invalid contents of operand information file aa....aa.

aa....aa: Name of the operand information file

S: Processing continues, but the operand in error cannot be edited on the detail definition screen.

Action

Review the operand information file aa....aa, and then re-execute the command.

KFPX29636-E D

Unable to open the operand information file (aa....aa)

Operand information file aa....aa cannot be opened.

aa....aa: Name of the operand information file

S: Processing continues, but the operand in error cannot be edited on the detail definition screen.

Action

Check the status of the operand information file aa....aa, make sure that it is in the open-enabled status, and then re-execute the command.

KFPX29637-E D

The value of [aa....aa] has a character count limit error.

The number of characters specified in an input item in the detail definition screen exceeded the limit.

aa....aa: Name of the input item with the invalid specification value

S: Displays an error message; waits until the correct value is entered.

Action

Reduce the number of characters to within the limit, and then re-execute the command.

KFPX29638-E D

Attempt to read the check results on the system definition failed.
Detail: <aa....aa>

The file storing the results of system definition checks could not be read.

aa....aa: Error details and the name of the affected file

S: Processing continues; the results of system definition checks are not displayed.

Action

Based on the error detail information indicated in aa....aa, resolve the error, and then re-execute the command.

KFPX29639-E D

No value was input.

A value is not specified in the required input item in the definition of the detail definition screen.

S: Displays an error message; waits until the correct value is entered.

Action

Specify a value, and then re-execute the command.

KFPX29640-E D

Less than the minimum required number of characters.

The value specified on the detail definition screen is less than the minimum required number of characters.

S: Displays an error message; waits until the correct value is entered.

Action

Change the specified value to greater than or equal to the minimum required number of characters, and then re-execute the command.

KFPX29641-E D

More than the maximum allowable number of characters.

The value specified on the detail definition screen is more than the maximum allowable number of characters.

S: Displays an error message; waits until the correct value is entered.

Action

Change the value to less than or equal to the maximum allowable number of characters, and then re-execute the command.

KFPX29642-E D

Non-numeric value.

A non-numeric value was specified in the input item in the definition of the detail definition screen.

S: Displays an error message; waits until the correct value is entered.

Action

Specify a numeric value, and then re-execute the command.

KFPX29643-E D

Less than the minimum required value.

The value specified in the definition of the detail definition screen is less than the minimum required value.

S: Displays an error message; waits until the correct value is entered.

Action

Specify a value greater than or equal to the minimum required value, and then re-execute the command.

KFPX29644-E D

Greater than the maximum allowable value.

The value specified in the definition of the detail definition screen is greater than the maximum allowable value.

S: Displays an error message; waits until the correct value is entered.

Action

Specify a value less than or equal to the maximum allowable value, and then re-execute the command.

KFPX29645-E D

The operand [aa....aa] cannot be deleted.

An attempt was made to delete an operand that cannot be omitted.

aa....aa: Operand name

S: Continues processing.

KFPX29646-E D

The operand to be added is not selected.

The operand to be added in the Select an add operand dialog box is not selected.

S: Displays an error message; waits until the correct operand is selected.

Action

Select the operand to be added.

KFPX29647-E D

The option flag to be added is not selected.

The option flag to be added in the Select an add option flag dialog box is not selected.

S: Displays an error message; waits until the correct option flag is selected.

Action

Select the option flag to be added.

KFPX29648-E D

The specified item [aa....aa] already exists.

An attempt was made to add item aa....aa, which already exists.

aa....aa: The parameter or name that was to be added

S: Displays an error message; waits until the correct value is entered.

KFPX29649-E D

The HiRDB file to which an RDAREA is to be allocated does not exist.

A HiRDB file name was not specified in the Specifying a HiRDB file to which an RDAREA is to be allocated dialog box.

S: Displays an error message; waits until the correct value is entered.

Action

Specify a HiRDB file, and then re-execute the command.

KFPX29650-E D

The name of the System A status file is the same as the name of the System B status file.

The same name was specified for the System A status file and the System B status file.

S: Displays an error message; waits until the correct value is entered.

Action

Eliminate any name duplication between the System A and System B system status files, and then re-execute the command.

KFPX29651-E D

The name of the System A system log file is the same as the name of the System B system log file.

The same name was specified for both the System A and System B system log files.

S: Displays an error message; waits until the correct value is entered.

Action

Eliminate nay name duplication between the System A and System B system log files, and then re-execute the command.

KFPX29652-E D

The -o option can be specified only for one buffer.

In the Edit global buffer dialog box, an attempt was made to allocate the -o option to more than one global buffer.

S: Displays an error message, and cancels the allocation operation.

Action

Review the -o option to be specified for global buffers, and then re-execute the command.

KFPX29653-E D

No value specified in [aa....aa]

No value is specified in the aa....aa input item in the detail definition screen for the simple setup tool.

aa....aa: Name of the input area with an invalid specification value

S: Displays an error message; waits until the correct value is entered.

Action

Specify a value, and then re-execute the command.

KFPX29654-E D

A hosts file read error occurred.
Detail: <aa....aa>

The error indicated by aa....aa occurred during the reading of the hosts file.

aa....aa: Detailed information on the hosts file read error

S: Continues processing.

Action

Based on the detailed error information indicated in aa....aa, resolve the error, and then re-execute the command.

KFPX29655-E D

Select a host name.

A host name is not selected in the Select a host name from the hosts file dialog box.

S: Displays an error message; waits until the correct host name is selected.

Action

Select a host name, and then re-execute the command.

KFPX29656-E D

Incomplete specification of [aa....aa].

The specification of aa....aa is incomplete in the definition of the detail definition screen for the simple setup tool.

aa....aa: Name of the input item with an incomplete specification value

S: Displays an error message; waits until the correct value is entered.

Action

Specify the correct value, and then re-execute the command.

KFPX29657-E D

No RDAREA allocated to global buffer [aa....aa].

No RDAREA is allocated to the global buffer in the Edit global buffer dialog box.

aa....aa: Name of the error-generating global buffer.

S: Displays an error message; waits until the command is executed with the correct specification.

Action

Allocate an RDAREA to the global buffer, and then re-execute the command.

KFPX29658-E D

No HiRDB file allocated to RDAREA [aa....aa].

In the Edit RDAREA dialog box, no HiRDB is allocated to RDAREA aa....aa.

aa....aa: RDAREA name

S: Displays an error message; waits until the correct value is entered.

Action

Allocate a HiRDB file to the RDAREA indicated by aa....aa, and then re-execute the command.

KFPX29659-E D

Only one HiRDB setup tool can be started.

An attempt was made to start more than one HiRDB simple setup tool.

S: Continues processing.

Action

The previously started simple setup tool should be closed. Or, the previously started simple setup tool should be used.

KFPX29660-E D

The pdconfchk command in the current version of HiRDB does not support this setup tool; so definition checks cannot be performed. After the setup process is complete or the definition is updated, run the pdconfchk command from the command prompt to check the contents of the definition.

Because the HiRDB version being used is old, the pdconfchk command does not support HiRDB's simple setup tool. For this reason, operands cannot be checked. Use the pdconfchk command to check the operands after the setup process or the definition updating process is complete.

S: Continues processing.

Action

Use the pdconfchk command to check the operands after the setup process or the definition updating process is complete. The pdconfchk command compatible with the simple setup tool is available in HiRDB 06-02-/B or later.

KFPX29661-E D

The pd_system_id operand cannot be changed when the definition.

For updating a definition, the pd_system_id operand cannot be changed.

S: Continues processing.

KFPX29662-E D

In [aa....aa], the value of [bb....bb] is not specified.

In a system switchover specification, bb....bb for unit aa....aa is not specified.

aa....aa: Unit name

bb....bb: Missing item

S: Displays an error message; waits until the correct value is entered.

Action

Specify the input item where the error is indicated, and then re-execute the command.

KFPX29663-E D

The value of [bb....bb] in [aa....aa] is not numeric.

In a system switchover specification, bb....bb required for unit aa....aa is not specified as a numeric value.

aa....aa: Unit name

bb....bb: Input item where the error is indicated

S: Displays an error message; waits until the correct value is entered

Action

Specify a numeric value, and then re-execute the command.

KFPX29664-E D

The value of [bb....bb] in [aa....aa] has an out-of-range error.

In a system switchover specification, the value specified in bb....bb for unit aa....aa is out of range.

aa....aa: Unit name

bb....bb: Input item where the error is indicated

S: Displays an error message; waits until the correct value is entered.

Action

Specify a value within the range, and then re-execute the command.

KFPX29665-E D

The value of [bb....bb] in [aa....aa] has a character count limit error.

The value of bb....bb in unit aa....aa has a character count limit error.

aa....aa: Unit name

bb....bb: Error-indicated input item

S: Displays the error message, and waits for input of the correct value.

Action

Specify a value within the range, and then re-execute the command.

KFPX29666-E D

The -i option (initializing an area) is not specified. When using the system switchover facility, the -i option (initializing an area) must be specified.

The system switchover facility is specified, but the -i option (initializing an area) is not specified in the Edit the HiRDB file system area dialog box.

S: Displays an error message; waits until the correct value is entered.

Action

When using the system switchover facility, specify the -i option (initializing an area), and then re-execute the command.

KFPX29667-E D

The -i option (initializing an area) in [aa....aa] is not specified. When using the system switchover facility, the -i option (initializing an area) must be specified.

The system switchover facility is specified, but the -i option (initializing an area) for the HiRDB file system area aa....aa is not specified in the Edit the HiRDB file system area dialog box.

aa....aa: Name of the HiRDB file system area

S: Displays an error message; waits until the correct value is entered.

Action

When using the system switchover facility, specify the -i option (initializing an area), and then re-execute the command.

KFPX29668-E D

SVR is specified in the -k option (purpose of use) of [aa....aa]. When the system switchover facility is used, SVR cannot be specified in the -k option (purpose of use).

The system switchover facility is specified, but SVR is specified as the purpose of use for the HiRDB file system area aa....aa.

aa....aa: Name of the HiRDB file system area

S: Displays an error message; waits until the correct value is entered.

Action

When using the system switchover facility, specify an appropriate purpose of use other than SVR, and then re-execute the command.

KFPX29669-E D

No secondary system host name is specified for a unit. When the system switchover facility is used, a secondary system host name must be specified in the setup dialog for the system switchover facility.

The system switchover facility is specified, but no secondary system host name is specified for the unit.

S: Displays an error message; waits until a secondary system host name is entered and the command is re-executed.

Action

For the unit for which no secondary system host name is specified, use the setup dialog for the system switchover facility to specify a secondary system host name, and then re-execute the command.

KFPX29670-E D

Acquisition of a folder name failed. Processing has been terminated.

The acquisition of the folder name specified in the Reference a folder dialog box failed.

S: Displays an error message; waits until the correct folder name is specified and the command is re-executed.

Action

Either check the status of the specified folder and put it in a reference-enabled status or specify another folder, and then re-execute the command.

KFPX29671-E D

The execution directory is invalid. Processing has been terminated.
The setup tool should be executed in the HiRDB install directory\pdzistup\bin directory.

The execution directory for the simple setup tool is invalid.

S: Terminates processing.

Action

Review the execution directory. Re-execute the command from an appropriate directory. Notice that this error is generated when the system searches for the HiRDB installation directory \bin\pdntcmd.bat from the execution directory for the simple setup tool and if the installation directory is not found.

KFPX29672-E D

The installation environment file (Setup.ini) for HiRDB is invalid. Processing has been terminated.
HiRDB may not have been installed correctly. Check the HiRDB installation environment.

The contents of the installation environment file (Setup.ini) for HiRDB are invalid.

S: Terminates processing.

Action

Review the HiRDB installation environment. If the environment is invalid, re-install HiRDB, and then re-execute the command.

KFPX29673-E D

The port number is incorrect. Port numbers must be between 5001 and 65535.

A value other than 5001 through 65535 was specified as a port number.

S: Generates an error message; waits until the correct value is specified as a port number and the command is re-executed.

Action

Change the port number specification to within the 5001 through 65535 range, and then re-execute the command.

KFPX29674-E D

The specified drive does not have enough space; setup cannot be continued.
aa....aa

The destination drive for the setup process does not have enough free space; the setup processing cannot be continued.

aa....aa:

Standard or custom setup:

setup-destination-folder-name (this is output if the system files and the RDAREA are stored in different folders)

Wizard setup:

hostname:setup-destination-folder-name

S: Generates an error message; waits until the command is executed by specifying the name of an appropriate folder for the setup process.

Action

Specify a folder in a drive that has enough free space as a setup destination, and then re-execute the command.

KFPX29675-E D

There are too many backup files for aa....aa. Delete some backup files, and then select OK. If the cancel option is entered, the files will be overwritten.

There are too many backup files; a backup file cannot be created.

aa....aa: Name of the file to be backed up.

S: Waits for an action in response to the message.

Action

When deleting a backup file, delete the file, and then click OK. To overwrite a backup file, click Cancel.

KFPX29676-E D

The port number is already used by another program. <Default: 22200>
Check the following files, and specify an available number:
Host is UNIX
"/etc/services"
Host is Windows
"Windows system directory \drivers\etc\services"

The port number specified in the HiRDB system definition is already being used by another program listed in the services file.

S: Generates an error message; waits until an available port number is specified and the command is executed.

Action

Check the contents of the services file of the setup target host, and ensure that there are no duplicate port numbers specified in the HiRDB system definition. Also, because other programs do not check for duplication of port numbers that are being used but are not listed in the services file, execute the netstat command from the setup target host to verify whether the specified port number is in use.

KFPX29677-E D

A system error occurred.
Error code: aa....aa
Error contents: bb....bb
[ API name: cc....cc]

A system error has occurred. This error message is output when an error occurs during setup in Windows system process processing or with the Windows API.

aa....aa: System error code

bb....bb: System error contents

cc....cc: Name of the API where the error occurred

S: Terminates processing.

Action

There may be insufficient memory. Increase the memory or delete unnecessary applications, and then re-execute. If this error occurs even when there is no memory shortage, contact the customer support center. The term process processing used in the message refers to the processing of the Win32 API Create Process function. The API name is not always displayed.

KFPX29678-E D

File creation failed.
File name: aa....aa
Terminates processing.

Creation of the file indicated by aa....aa failed.

aa....aa: File name

S: Terminates processing.

Action

Check to see if the system is in a condition that permits the creation of the aa....aa; resolve the cause of the error, and then re-execute the command.

KFPX29679-E D

Setup tool ini file open failure.
File name: aa....aa
Terminates processing.

Opening of the ini file indicated by aa....aa failed.

aa....aa: Name of the ini file that failed to open

S: Terminates processing.

Action

Check to see if the ini file indicated by aa....aa exists or it is in a condition in which it can be opened; resolve the cause of the error, and then re-execute the command.

KFPX29680-E D

An error occurred in aa....aa processing. The contents of the error have been output to the log file pdi_log.txt.

Error occurred during aa....aa processing.

aa....aa: The processing in which the error occurred

S: Terminates processing.

Action

Investigate the contents of the error that are output to the log file pdi_log.txt; resolve the cause of the error, and then re-execute the command.

KFPX29681-E D

An error occurred during socket initialization. Processing has been terminated.

An error occurred during the initialization of a Windows socket. It is possible that the system is not ready to establish a network connection or the maximum number of processes that can simultaneously use WinSock has been reached.

S: Terminates processing.

Action

Either the system is not ready to establish a network connection or the maximum number of processes that can simultaneously use WinSock has been reached. Re-execute the command after a while.

KFPX29682-E D

Creation of a temporary file directory failed.
Directory name: aa....aa
Terminates processing.

Creation of temporary file directory aa....aa failed.

aa....aa: Directory name

S: Terminates processing.

Action

Investigate whether directory aa....aa is in a condition in which it can be created; resolve the cause of the error, and then re-execute the command.

KFPX29683-E D

The variable aa....aa is specified incorrectly. The variable aa....aa must be specified as four alphanumeric characters.

The input item aa....aa is specified incorrectly.

aa....aa: Input item

S: Displays an error message; waits until the correct value is entered.

Action

Specify the input item with four alphanumeric characters, and then re-execute the command.

KFPX29684-E D

An attempt to read the system definition file failed.
Terminates processing.
Subject file: aa....aa
Error contents: bb....bb

The reading of the system definition file aa....aa failed due to the cause indicated by bb....bb.

aa....aa: System definition file

bb....bb: Error contents

S: Continues processing.

Action

Based on the error description indicated in bb....bb, resolve the cause of the error, and then re-execute the command.

KFPX29685-E D

An error occurred during creation of database information.
Error contents: aa....aa
Details of the error are output to the log file pdi_log.txt.

An error occurred during database information creation processing.

aa....aa: Error contents

File open failure

File read failure

Memory shortage

Invalid format for definition contents

S: Terminates processing.

Action

If the error contents indicated by aa....aa and the log file (pdi_log.txt) are output, reference the contents of the log file, resolve the cause of the error, and then re-execute the command.

KFPX29686-E D

An error occurred during access to the remote host. Processing has been terminated.
[Details of the error are output to the log file pdi_log.txt.]

An error occurred during access to the remote host for the following possible reasons:

Unable to open the target file.

Target file inaccessible.

Either the remote host has not started or does not exist.

The port number for the Rsh Port Name (the name set by the pdntenv command) code in the service file for the remote host does not match that of the local host.

The user starting up the HiRDB service for the remote host does not match that of the local host.

The HiRDB service for the remote host does not start.

The logon user/password (HiRDB administrator) for the remote host does not match that of the local host.

S: Terminates processing.

Action

Based on the contents that are output to the log file (pdi_log.txt) and conceivable reasons, resolve the cause of the error, and then re-execute the command.

KFPX29687-E D

An error occurred during the generation of an internal object. Processing has been terminated.
It is possible that there is a memory shortage.

An error occurred during the generation of an internal object for the simple setup tool. A possible cause is a memory shortage.

S: Terminates processing.

Action

Either provide additional memory or close any applications that are not needed, and then re-execute the command.

KFPX29688-E D

An error occurred during file generation (directory).
Cause: aa....aa
Name of the host on which the file was being created: bb....bb
File name: cc....cc

An error occurred during creation of a file (directory) for the following possible reasons:

Target file cc....cc cannot be opened in the overwrite mode.

Target file cc....cc is inaccessible.

Either remote host bb....bb has not started or does not exist.

The port number for Rsh Port Name (the name set by the pdntenv command) code in the service file for the remote host bb....bb does not match that of the local host.

The user starting up the HiRDB service for remote host bb....bb does not match that of the local host.

The HiRDB service for the remote host bb....bb has not been started.

The logon user/password (HiRDB administrator) for the remote host bb....bb does not match that of the local host.

aa....aa: Cause of error

Copying failed

Backup failed

File open failed

Access to remote host file failed

Directory creation failed

bb....bb: Name of the host in which a file (directory) was to be created

cc....cc: File (directory) name

S: Terminates processing.

Action

Investigate the cause of the error indicated by aa....aa, resolve the cause of the error, and then re-execute the command.

KFPX29689-E D

File open failure
File name: aa....aa

Opening the file aa....aa failed.

aa....aa: File name

S: Terminates processing.

Action

Investigate whether file aa....aa is in a condition in which it can be opened, resolve the cause of the error, and then re-execute the command.

KFPX29690-E D

A memory shortage occurred. KFPX29687-

A memory shortage occurred.

S: Terminates processing.

Action

Either provide additional memory or close any applications that are not needed, and then re-execute the command.

KFPX29691-E R

An error occurred during HiRDB startup processing. Refer to the messages output to syslogfile (in Windows, the event log), and take action as indicated in the messages.

An error occurred during HiRDB starting processing. Refer to the messages output to the event log (in UNIX, syslogfile), and take appropriate action.

S: Terminates processing.

Action

Refer to the messages output to the event log (in UNIX, syslogfile), eliminate the cause of the error, and re-execute.

KFPX29692-Q D

Operand [aa....aa] will be deleted. OK to proceed?

This is a deletion confirmation message on operand aa....aa.

aa....aa: Operand name

S: Take action in response to the message.

KFPX29693-Q D

Option flag [bb....bb] for operand [aa....aa] will be deleted. OK to proceed?

This is an option flag bb....bb deletion confirmation message on operand aa....aa.

aa....aa: Operand name

bb....bb: Option flag

S: Take action in response to the message.

KFPX29694-Q D

In operand [aa....aa] only the option flag [bb....bb] exists. The operand itself will be deleted. OK to proceed?

This is an option flag bb....bb deletion confirmation message on operand aa....aa. Because the operand aa....aa only contains the option flag bb....bb, deleting the option flag also deletes the operand.

aa....aa: Operand name

bb....bb: Option flag

S: Take action in response to the message.

KFPX29695-Q D

In operand [aa....aa], option flag [bb....bb] cannot be omitted. Deleting the option flag will result in the deletion of the operand itself. OK to proceed?

This is an option flag bb....bb deletion confirmation message on operand aa....aa. Because the option flag bb....bb cannot be omitted, deleting the option flag also deletes the operand.

aa....aa: Operand name

bb....bb: Option flag

S: Take action in response to the message.

KFPX29696-Q D

Item aa....aa will be deleted. OK to proceed?

This is an aa....aa deletion confirmation message.

aa....aa: Item to be deleted

S: Take action in response to the message.

KFPX29697-Q D

Checks on the system definition are not yet complete; the setup process cannot be started. OK to terminate the detailed definition?

This is a confirmation message asking whether the detail definition screen can be closed when checks on the system definition are not yet complete. The setup process cannot be executed unless checks on the system definition are complete.

S: Take action in response to the message.

KFPX29698-Q D

The contents of the system definition have been modified, but definition update processing has not yet been executed. Close the detailed definition?

This is a confirmation message asking whether the detail definition screen can be closed when definition updating processing has not yet been executed.

S: Take action in response to the message.

KFPX29699-Q D

HiRDB is starting. Stop HiRDB and continue with setup?
Note: If the HiRDB environment has already been set up, executing the setup process will overwrite the current environment.

This is a confirmation message asking whether the processing of the simple setup tool is to be continued by closing HiRDB, in view of the fact that the simple setup tool was started when HiRDB was still running.

S: Take action in response to the message.

KFPX29700-Q D

The specified setup directory is not found. [<aa....aa>]
Create a directory?

This is a confirmation message asking whether a directory is to be created when the directory created at the setup destination is not found.

aa....aa: Setup destination directory name (indicated for a custom screen)

S: Take action in response to the message.

KFPX29701-Q D

All currently set information will be reset if control is returned to the startup screen. OK to proceed?

This is a confirmation message asking whether it is OK to proceed in view of the fact that if control is returned from the custom screen to the startup screen, all information defined on the custom screen is reset to the default status.

This is a confirmation message asking whether it is OK to proceed in view of the fact that if control is returned from the wizard setup screen to the startup screen, all information defined in the wizard setup is reset to the default status.

S: Take action in response to the message.

KFPX29702-Q D

The system definition file already exists in the setup destination HiRDB environment. Create a backup for the existing file?

This is a confirmation message asking whether a backup for the existing system definition file is to be created during the setup process.

S: Take action in response to the message.

KFPX29703-Q D

A HiRDB environment already exists. Continue with the setup process?
Note: If the HiRDB environment has already been set up, executing the setup process will overwrite the current environment.

This is a confirmation message asking whether the setup process is to be continued on the existing HiRDB environment.

S: Take action in response to the message.

KFPX29704-I D

Starting HiRDB setup processing.

This is a setup startup message.

S: Continues processing.

KFPX29705-I D

The setup process has been cancelled.

This is a setup cancellation message.

S: Continues processing.

KFPX29706-I D

In the current version of HiRDB, system definition files cannot be distributed to standby systems. Such files must be distributed manually.

Because the current version of HiRDB is old, system definition files cannot be distributed to the standby systems. Version 06-02/E or later should be used. If a version upgrade is not available, such files must be distributed manually.

S: Continues processing.

Action

Manually distribute the system definition files to the secondary system host.

KFPX29707-E D

Specify a setup directory.

An attempt was made to execute setup without specifying a setup directory.

S: Displays an error message; waits until the command is executed by specifying a setup directory.

Action

Execute the command by specifying a setup directory.

KFPX29708-E D

A non-alphanumeric character is specified in a logical file name.

Alphanumeric characters are not specified as a logical file name in the detail definition screen of the simple setup tool.

S: Displays an error message; waits until the command is executed with the correct value.

Action

Execute the command by specifying the correct value.

KFPX29709-I D

Item [aa....aa] has reached the maximum number that can be set in HiRDB.

In the detail definition screen of the simple setup tool, the value of the input item aa....aa reached the maximum number that can be set in HiRDB.

aa....aa: Input item name

S: Continues processing (by preventing the applicable value from being increased).

KFPX29710-I D

Item [aa....aa] has reached the minimum number that can be set in HiRDB.

In the detail definition screen of the simple setup tool, the value of the input item aa....aa reached the minimum number that can be set in HiRDB.

aa....aa: Input item name

S: Continues processing (by preventing the applicable value from being reduced).

KFPX29711-E D

A value other than SYS or SVR is specified as the type of the HiRDB file system area.

In the detail definition screen of the simple setup tool, a value other than SYS or SVR is specified as the purpose of the HiRDB file system area.

S: Displays an error message; waits until the command is executed with the correct value.

Action

Specify either SYS or SVR depending on the purpose of use, and then execute the command.

KFPX29712-E D

In [aa....aa], a non-alphanumeric character is specified.

In the detail definition screen of the simple setup tool, a non-alphanumeric character is specified in the input item aa....aa.

aa....aa: Input item name

S: Displays an error message; waits until the command is executed with the correct value.

Action

Execute the command by specifying the correct value.

KFPX29713-E D

The server [aa....aa] contains a mix of non-redundant and redundant file groups.

In the detail definition screen of the simple setup tool, the server aa....aa contains a non-redundant file group and redundant file groups on a mixed basis.

aa....aa: Server name

S: Displays an error message; waits until the command is executed with the correct value.

Action

Specify in a manner that eliminates the mixing of non-redundant and redundant file groups, and then execute the command.

KFPX29714-W D

HiRDB file system area for System A may be on the same disk as HiRDB file system area for System B.

It is possible that in the detail definition screen of the simple setup tool, the system A HiRDB file system area and the system B HiRDB file system area are set up on the same disk. If a disk failure occurs, setting up these areas on the same disk defeats the purpose of file redundancy. (Determine whether the file system areas are set up on the same disk as follows: In Windows, refer to the drive name of the specified HiRDB file system area path name; in UNIX, refer to the initial directory name of the specified HiRDB file system area path name).

S: Continues processing.

Action

Check to see whether the system A HiRDB file system area and the system B HiRDB file system area are set up on the same disk; if necessary, set them up so that they occupy separate disks.

KFPX29715-E D

Login to the setup target host failed.
Error code: aa....aa

Login to the setup target host failed.
aa....aa: Reason code indicating the nature of the error

S: Displays an error message; waits until the command is re-executed.

Action

Check the items corresponding to the indicated reason code, and then log in again. If you still cannot log in after performing these checks, the HiRDB server needs to be upgraded.

Reason code
What to check

10

Is the setup target host running?

Does the setup target host exist?

Does the ping command successfully reach the specified host name or IP address?

20

Does the login user's password on the setup target host match the HiRDB administrator password?

Does the login user exist on the setup target host?

If the setup target host is running Windows, has the HiRDB service (HiRDB/Single Server or HiRDB/Parallel Server) been started?
For details about how to check whether a service has been started, see the documentation for Windows.

Does the HiRDB server version on the setup target host match the HiRDB server version on the host that is executing the simple setup tool?

30

If the setup target host is running Windows, are the paths to the Windows directories correctly set?

If the setup target host is running UNIX, is there sufficient space available in /tmp/login-user-name?

If the setup target host is running UNIX, has rsh.exe been set to execute with HiRDB administrator privileges?

40

If the setup target host is running Windows, is there sufficient space available in %windir%\Temp\login-user-name?

KFPX29716-E D

Select the host to be set up.

The setup process was started when the input item in which a host name is specified is still empty.

S: Displays an error message; waits until the command is executed with the correct value.

Action

Specify a host name, and then re-execute the command.

Specify a UNIX host as a remote host, and then re-execute the command.

KFPX29718-E D

For host name [aa....aa], capacity of disk [bb....bb] is short by [cc....cc]MB.

For host name aa....aa, the disk capacity of bb....bb is insufficient by the disk volume indicated in cc....cc.

aa....aa: Host name

bb....bb: In Windows, the drive name; in UNIX, the file system name

cc....cc: Amount of disk capacity shortage

S: Displays an error message; waits until the command is re-executed.

Action

Take one of the following actions:

Delete any unneeded files from the disk to increase the amount of available space.

Reduce the size of the file to be created. Alternatively, create the file on a separate disk.

KFPX29720-E D

The name of the system A sync-point dump file is identical to that of the system B sync-point dump file.

The same name was specified for the system A sync-point dump file and the system B sync-point dump file.

S: Displays an error message; waits until the command is executed with the correct value.

Action

Specify files so that the system A sync-point dump file name and the system B sync-point dump file are not duplicated, and then re-execute the command.

KFPX29721-E D

Setup could not continue because the HiRDB environment does not exist in the setup target host.

There is no HiRDB environment in the specified target host.

S: Displays an error message; waits until the command is executed with the correct value.

Action

Specify the correct host name and operation directory, and then re-execute the command.

KFPX29722-E D

Specify the working directory.

The HiRDB directory was not specified.

S: Displays an error message, and waits for re-execution.

Action

Specify the HiRDB directory, and re-execute.

KFPX29724-Q D

The specified detailed definition information file (directory) does not exist. Create the file (directory)?

This confirmation message is output so that the user can confirm whether to create a file or directory when the named file or directory does not exist at the location specified for saving the detailed definitions.

S: Performs message response processing.

Action

Respond to the confirmation message.

KFPX29725-Q D

The specified detail definition information file (directory) already exists. Overwrite?

This message is for checking whether to overwrite the contents of a file or directory when there is already file or directory specified in the location for saving detailed definitions.

S: Performs message response processing.

Action

Respond to the confirmation message.

KFPX29727-E D

An error occurred while saving or reading a file (directory).
- Cause: aa....aa
- File name: bb....bb
- Detail code: cc....cc

An error occurred while the file (directory) was being saved or read. The following are possible causes:

The file cannot open in overwrite mode.

The file cannot be accessed.

There is a shortage of disk capacity for storing the file.

The file was not found.

aa....aa: Cause of the error:

The file could not be opened.

The file could not be written.

The file could not be read.

File deletion failed.

Directory creation failed.

Directory deletion failed.

bb....bb: Name of the file in which the error occurred

cc....cc: Code that displays the error detail information

S: Terminates processing.

Action

Investigate the cause of the error shown in aa....aa, eliminate the cause of the error, and then re-execute.

KFPX29731-E D

The specified value is invalid.
Detail: aa....aa

The specified value is invalid, so processing cannot continue.

aa....aa:

If aa....aa is Failed to connect to the local machine, the following are possible causes:

A name was not been input for the local machine.

The name that was input for the local machine is invalid.

The name that was input for the local machine exceeds the maximum length (HiRDB limit) of the host name.

If aa....aa is Environment contains an unspecified value or an out-of-range value, the following are possible causes:

No port number was input.

No unit number was input.

The value specified for the number of units is outside of the valid range.

The HiRDB size per unit is smaller than the minimum size (RDAREA capacity or system file capacity check error).

The maximum number of concurrently connected users was not input.

The value specified for the maximum number of concurrently connected users is outside of range.

No HiRDB size has been input.

The value specified for the HiRDB size is outside of the valid range.

The number set for front-end servers is out of the valid range.

The number set for back-end servers is out of valid range.

No automatic unload directory was input.

S: Terminates processing.

Action

If aa....aa is Failed to connect to the local machine:

Re-execute the simple setup tool to input the correct local machine name.

If aa....aa is Environment contains an unspecified value or an out-of-range value:

Input the correct value in the field where the cursor was set.

KFPX29732-E D

The HiRDB versions do not match.

The HiRDB versions do not match, so processing cannot continue. The following are possible causes:

The version of HiRDB in which the simple setup tool was started does not match the version of the setup destination HiRDB that is remotely connected.

S: Terminates processing.

Action

Check the version of HiRDB in which the simple setup tool was started and the version of the setup destination HiRDB that is remotely connected. If the versions are different, re-execute using the same version of HiRDB.

KFPX29733-E D

The size of the HiRDB file system area is insufficient.
aa....aa requires [bb....bb] or greater

A calculation for estimating the HiRDB file system area requirements indicates that there is a capacity shortage. The following are possible causes:

The specified HiRDB size, RDAREA capacity, or system file capacity is too small.

The settings (database configuration) for fields such as the specified number of users is too large

S: Terminates processing.

Action

Take one of the following corrective actions, and then re-execute.

Enlarge the size of HiRDB.

Change the RDAREA capacity ratio.

Reduce the settings (database configuration).

KFPX29734-I D

The user RDAREA set in the wizard was more than 64 GB.
Set to 64 GB.

Because a user RDAREA exceeding 64 GB cannot be created in the wizard, the value was set to 64 GB.

S: Continues processing.

2.17 KFPY messages

KFPY01001-E L

Defined PLUGIN name aa....aa not matched between units, unit=bb....bb

The plug-in name aa....aa specified in the pdplugin system common definition operand for unit bb....bb does not match the name specified in the pdplugin system common definition operand for the unit that contains the dictionary server.

aa....aa: Plug-in name

bb....bb: Identifier of the unit whose pdplugin operand did not match that of the unit containing the dictionary server

S: Terminates abnormally.

Action

Correct the system common definition for the unit containing the dictionary server and the unit whose unit ID is bb....bb so that the names specified in the pdplugin operands match.

If the KFPY01002-W message has been issued, take an appropriate action according to that message.

KFPY01002-W L

PLUGIN aa....aa not registered

Plug-in aa....aa has not been registered.

aa....aa: Plug-in name

S: Resumes processing.

Action

Take one of the following actions:

If an invalid plug-in name was specified in the pdplugin system common definition operand, specify the correct plug-in name in this operand. To make plug-in aa....aa available, restart HiRDB.

If plug-in aa....aa has not been registered using the pdplgrgst command, start HiRDB with the pdplugin operand in aa....aa omitted from the system common definition, and then register aa....aa using the pdplgrgst command. To use aa....aa, terminate HiRDB, code the aa....aa pdplugin operand in the system common definition, and then start HiRDB.

KFPY01003-E L

System command error occurred, cmd=aa....aa, code=bb....bb, inf="cc....cc"

An internal command error occurred in the system.

aa....aa: Command name

bb....bb: Shell termination code

cc....cc: Command error output information

S: Terminates abnormally.

Action

Take one of the following actions:

If aa....aa is rcp, the remote shell execution environment is set incorrectly or has not been set up.
Referring to the description of the remote shell execution environment in the HiRDB Version 9 Installation and Design Guide, set up the remote shell execution environment, and then start HiRDB.

If aa....aa is not rcp, see the applicable OS manual to resolve the cause of the error based on the error output information "cc....cc" and shell termination code bb....bb, and then start HiRDB.

KFPY01004-E L

Copy error, code=aa....aa, unit=bb....bb

An error occurred while copying the plug-in internal information from the dictionary server to the unit with unit identifier bb....bb.

aa....aa: Return code of the function resulting in the error

bb....bb: Unit ID of the copy destination

S: Terminates abnormally.

Action

If an OS message or OS command message has been issued before this message, see the applicable OS manual and take an appropriate action.

If you are unable to determine the cause of the problem, contact the customer support center.

KFPY01005-E L

System error, func=aa....aa, code=bb....bb, call func=cc....cc, line=dd....dd

An internal processing error occurred.

aa....aa: Name of the function where the error occurred

bb....bb: Error number

cc....cc: Name of the function that called the erroneous function

dd....dd: Line number

S: Terminates abnormally.

Action

Save the following files and contact the customer support center; if HiRDB is down, it should be restarted:

Files under %PDDIR%\spool and %PDDIR%\tmp

Event log (in UNIX, syslogfile)

KFPY01006-I L

PLUGIN available, unit=aa....aa, PLUGIN name=bb....bb

Plug-in bb....bb is available on unit aa....aa.

aa....aa: Unit ID

bb....bb: Plug-in name

S: Resumes processing.

KFPY01007-E L

Insufficient memory, memory kind="aa....aa", size=bb....bb

A memory shortage occurred.

aa....aa: Type of memory:

SHARE: Shared memory

PROCESS: Process memory

bb....bb: Size of memory to be allocated

S: Terminates abnormally.

Action

Take an appropriate action according to what is displayed in "aa....aa":

If SHARE is displayed in "aa....aa":

Save the following files, contact the customer support center, and then start HiRDB:

Files under %PDDIR%\spool and %PDDIR%\tmp

Event log (in UNIX, syslogfile)

If PROCESS is displayed in "aa....aa":

Wait for the termination of the concurrently executing process, and then re-execute the command. If the error recurs, save the following files and contact the customer support center:

Files under %PDDIR%\spool and %PDDIR%\tmp

Event log (in UNIX, syslogfile)

KFPY01008-E L

PLUGIN error, PLUGIN name=aa....aa, inf1=bb....bb, inf2=cc....cc

Plug-in aa....aa detected an error.

aa....aa: Plug-in name

bb....bb: Maintenance information 1

cc....cc: Maintenance information 2

S: If it is possible to resume processing, cancels the processing and rolls back. If it is impossible to resume processing, terminates abnormally.

Action

Check the message that was issued before this message. If there is an error, take an appropriate action according to the corresponding message. If no message was output, save the following files and contact the customer support center:

Files under %PDDIR%\spool, %PDDIR%\tmp, and %PDDIR%\plugin

pdsys under %PDDIR%\conf

Event log (in UNIX, syslogfile)

KFPY01010-E L

Failed to load PLUGIN, PLUGIN name=aa....aa, reason="bb....bb", unit=cc....cc

A plug-in load operation failed.

aa....aa: Plug-in name

bb....bb: Reason code:

NO LIBRARY

NO PERMISSION

NO SPACE

BROKEN

cc....cc: Unit identifier

S: Terminates abnormally.

Action

Take one of the following actions:

If reason code = NO LIBRARY:

In UNIX:
Plug-in aa....aa was not found. Check $PDDIR/plugin/lib for the library file for plug-in aa....aa. If there is no such library file, use the pdplgset command to set up the plug-in, and restart HiRDB.

In Windows:
Plug-in aa....aa was not found. Check %PDDIR%\plugin\lib for the library file for plug-in aa....aa. If there is no such library file, install the plug-in, and restart HiRDB.

If reason code = NO PERMISSION:

The user is not authorized to access the library for plug-in aa....aa.

In UNIX, use the pdplgset -d command to uninstall plug-in aa....aa while HiRDB is inactive, and then re-install it. In the case of Windows, uninstall the plug-in while HiRDB is inactive, and then reinstall it.

If this action does not solve the problem, save the following files and contact the customer support center:

Files under %PDDIR%\spool, %PDDIR%\tmp, and %PDDIR%\plugin

Event log (in UNIX, syslogfile)

If reason code = NO SPACE:

There is not enough process address space to load plug-in aa....aa. Reduce the number of plug-ins that are executed concurrently.

If reason code = BROKEN:

Plug-in aa....aa is damaged.

In UNIX, use the pdplgset -d command to uninstall plug-in aa....aa while HiRDB is inactive, and then re-install it. In the case of Windows, uninstall the plug-in while HiRDB is inactive, and then reinstall it.

If this action does not solve the problem, reinstall plug-in aa....aa and then implement this action again.

KFPY01011-E L

Not found function in PLUGIN, PLUGIN name=aa....aa, function=bb....bb, unit=cc....cc

Function bb....bb was not found in plug-in aa....aa on unit cc....cc.

aa....aa: Plug-in name

bb....bb: Plug-in function

cc....cc: Unit identifier

S: Terminates abnormally.

Action

Save the following files and contact the customer support center:

Files under %PDDIR%\spool, %PDDIR%\tmp, and %PDDIR%\plugin

pdsys under %PDDIR%\conf

Event log (in UNIX, syslogfile)

KFPY01012-E L

PLUGIN not available, unit=aa....aa, PLUGIN name=bb....bb

Plug-in bb....bb cannot be used on unit aa....aa.

aa....aa: Unit ID

bb....bb: Plug-in name

S: Processing continues without a plug-in usage declaration, or terminates abnormally.

Action

If the KFPY01002-W message was output:

The specified plug-in name bb....bb is invalid. Specify the correct plug-in name in the pdplugin operand of the system common definition, and then restart HiRDB.

Plug-in bb....bb is not registered using the pdplgrgst command. Delete the pdplugin operand associated with system common definition bb....bb, and start HiRDB. Register bb....bb using the pdplgrgst command. Terminate HiRDB, and then restart it.

If the KFPY01002-W message was not output:

The pdplugin system common definition operands of these units do not match. Correct the pdplugin operands so that they match.

KFPY01013-E L

Failed to execute rollback for PLUGIN, PLUGIN name=aa....aa, PLUGIN ID=bb....bb, unit=cc....cc, inf=dd....dd

Rollback failed in the RDAREA that was updated by plug-in aa....aa.

aa....aa: Plug-in name

If an attempt was made to roll back a plug-in whose utilization has not been declared, *** is displayed.

bb....bb: Plug-in ID

cc....cc: Unit ID

dd....dd: Maintenance information (RDAREA ID)

S: Shuts down the RDAREA whose rollback was attempted by the plug-in, and resumes processing.

P: Shut down the RDAREA whose rollback was attempted by the plug-in, and resume processing.

Action

See the KFPH00306-E message issued after this message, and restore the RDAREA from shutdown status. If another KFPYxxxxx-E message is displayed, take an appropriate action according to the message (xxxxx: 5-digit message number).

KFPY01015-W L

PLUGIN not available due to held dictionary RDAREA

A plug-in is not available because the dictionary RDAREA is shut down.

S: Continues with HiRDB startup processing while the plug-in is not available.

Action

See the error handling procedures in the HiRDB Version 9 System Operation Guide to restore the dictionary RDAREA.

KFPY01016-E L

Unable to call PLUGIN, PLUGIN ID=aa....aa, unit=bb....bb, reason code="cc....cc"

The system was unable to call a plug-in with plug-in ID aa....aa due to reason "cc....cc".

aa....aa: Plug-in ID

bb....bb: Unit ID

cc....cc: Reason code:

UNAVAILABLE: The plug-in with plug-in ID aa....aa is not available.

UNDEFINED: The pdplugin operand is undefined for the plug-in with ID aa....aa. Or, an error occurred during plug-in initialization processing.

S: If the database recovery utility is being executed, cancels the execution. During a rerun, shuts down the RDAREA to be restored and resumes processing.

Action

If reason code = UNAVAILABLE:

Take an appropriate action according to the KFPYnnnnn message (nnnnn: 5-digit message number) that was issued before this message.

If reason code = UNDEFINED:

Terminate HiRDB, code a plug-in utilization declaration (pdplugin operand) with a plug-in ID of aa....aa in the system common definition, and then start HiRDB.

In UNIX, if the plug-in with the plug-in ID aa....aa is not set up, use pdplgset to set up the plug-in. In Windows, if the plug-in with plug-in ID aa....aa is not installed, install it.

Otherwise, take an appropriate action according to the KFPYnnnnn message (nnnnn: 5-digit message number) that was issued before this message.

KFPY01017-E L

PLUGIN aa....aa not setup, unit=bb....bb

Plug-in aa....aa has not been set up. Or, the invalid plug-in name aa....aa was specified in the pdplugin system common definition operand.

aa....aa: Plug-in name

bb....bb: Unit ID

S: Resumes processing while plug-in aa....aa is not available.

Action

Take one of the following actions:

In UNIX, if plug-in aa....aa is not set up, stop HiRDB, use pdplgset to set up plug-in aa....aa, and then restart HiRDB.

In Windows, if plug-in aa....aa is not installed, terminate HiRDB, install the plug-in, and then restart HiRDB.

If an incorrect plug-in name aa....aa is specified in the pdplugin operand of the system common definition, terminate HiRDB, specify the correct plug-in name in the pdplugin operand of the system common definition, and then restart HiRDB.

KFPY01018-E L

PIC file broken, PLUGIN name=aa....aa, unit=bb....bb, inf=cc....cc

The PIC file for plug-in aa....aa is damaged.

aa....aa: Plug-in name

bb....bb: Unit ID

cc....cc: Maintenance information (reason code):

Architecture does not match.

Data is invalid.

Data is missing.

S: Resumes processing while plug-in aa....aa is not available.

Action

In UNIX:

Terminate HiRDB, uninstall plug-in aa....aa with pdplgset -d, set it up, and then start HiRDB.

If the setup is deleted from the plug-in, all files are deleted from $PDDIR/plugin/aa....aa. Therefore, save any files that are needed from this directory before deleting the setup from the plug-in.

In Windows:

Stop HiRDB, install the plug-in, and restart HiRDB.

In this case, all files in %PDDIR%\plugin\aa....aa will be deleted. Therefore, if there are any required files, they must be saved prior to this procedure.

KFPY01019-E L

Failed to read PIC file, PLUGIN name=aa....aa, unit=bb....bb, func=cc....cc, code=dd....dd

A read error occurred on the PIC file for plug-in aa....aa.

aa....aa: Plug-in name

bb....bb: Unit ID

cc....cc: Name of function where the error occurred

dd....dd: Function's error code

S: Resumes processing while plug-in aa....aa is not available.

Action

See errno.h and the applicable OS manual based on the displayed error code dd....dd and take an appropriate action.

After taking corrective action, to use the plug-in, terminate HiRDB, and then restart HiRDB.

KFPY01020-E L

No PLUGIN available, unit=aa....aa

None of the plug-ins are available on unit aa....aa.

aa....aa: Unit ID

S: Resumes processing while no plug-in is available on unit aa....aa.

Action

Take an appropriate action according to the KFPYnnnnn message (nnnnn: 5-digit message number) that was issued before this message.

KFPY01021-E L

Too long path name, unit=aa....aa, file name=bb....bb

The path is too long for file bb....bb.

aa....aa: Unit ID

bb....bb: File name

S: Resumes processing.

Action

Create the HiRDB directory so that the length of file bb....bb's absolute path does not exceed the maximum system value.

KFPY01022-E I

aa....aa

This message displays information about a system call error. If the OS system log feature does not support the Japanese character code, messages may not be output to the system log correctly. If this happens, see HiRDB's message log.

aa....aa: Error information

S: Resumes processing.

KFPY01023-E L

System call error, func=aa....aa, PLUGIN=bb....bb

A system call error occurred.

aa....aa: Name of the function where the error occurred

bb....bb: Plug-in name

S: Resumes processing.

Action

Resolve the cause of the error based on the contents of the KFPY01022-I message that was output before this message, terminate HiRDB, and then restart it.

KFPY01024-E L

PLUGIN aa....aa not defined in system definition file, operand=bb....bb, server=cc....cc

Plug-in aa....aa specified in operand bb....bb in the server definition for server cc....cc is not defined in the system common definition.

aa....aa: Plug-in name

bb....bb: Operand name

cc....cc: Server name

S: Terminates processing.

Action

Ensure that plug-in aa....aa specified by operand bb....bb in the server definition of server cc....cc is specified in the pdplugin operand in the system common definition.

KFPY01025-E L

Duplicate aa....aa operand for PLUGIN bb....bb in cc....cc server definition file

Operand aa....aa, which specifies plug-in bb....bb in the server definition of server cc....cc, is duplicated.

aa....aa: Operand name

bb....bb: Plug-in name

cc....cc: Server name

S: Terminates processing.

Action

Check the server definition of server cc....cc and correct the specification of plug-in bb....bb specified in operand aa....aa.

KFPY01026-E L

Error found in system definition, file=aa....aa, line=bb....bb

An error was detected in the system definition.

aa....aa: Name of the system definition file

bb....bb: Line number

S: Terminates abnormally.

Action

Correct system definition file aa....aa and re-execute.

KFPY01027-E L

PLUGIN library aa....aa incompatible load model type with HiRDB

The load type of plug-in library aa....aa (in UNIX, POSIX library or non-POSIX library) does not match the load type of HiRDB.

aa....aa: Plug-in name

S: Continues processing without a plug-in usage declaration.

Action

Reregister a plug-in that matches the HiRDB load type.

KFPY01028-E L

Incompatible PLUGIN library format with HiRDB, PLUGIN data model=aa, HiRDB data model=bb

The format of the plug-in library does not match the HiRDB format.

aa: Data model of the plug-in

bb: Data model of the HiRDB system

S: Continues processing without a plug-in usage declaration.

Action

When aa is 32 and bb is 64, set the plug-in to the 64-bit mode. When aa is 64 and bb is 32, either set HiRDB to the 64-bit mode or the plug-in to the 32-bit mode. When migrating to a 64-bit mode HiRDB system, you cannot return the system to a 32-bit mode HiRDB.

KFPY01200-I L+ S

PLUGIN setup start, func="aa....aa", PLUGIN name=bb....bb

Plug-in setup processing has started.

aa....aa: Function name:

add: Plug-in setup

delete: Plug-in deletion

bb....bb: Plug-in name

S: Resumes processing.

KFPY01201-I L+ S

PLUGIN setup ended, return code=aa....aa

Plug-in setup processing is terminated.

aa....aa: Termination code:

0: Processing terminated normally.

8: Error occurred during processing.

S: Terminates processing.

Action

If the termination code is not 0, see the KFPY012nn-E message (nn: 2-digit number) issued before this message, along with the OS command message, and take an appropriate action.

KFPY01202-I S

Usage: pdplgset plugin_name installed_plugin_directory pdplgset -d plugin_name

This message indicates the usage of the pdplgset command. It is displayed when the command format is invalid.

S: Terminates processing.

Action

Check the command format and re-execute the command.

KFPY01203-E E+L

Invalid "PDDIR", path name="aa....aa"

The contents of environment variable PDDIR are invalid.

aa....aa: Information that is set in environment variable PDDIR

If this information is not displayed, no value is set in PDDIR.

S: Terminates processing.

Action

Take one of the following actions:

If "aa....aa" is displayed:

Check if the correct HiRDB directory is set in PDDIR. If the path is invalid, set the correct path and then re-execute the command.

Check if the HiRDB directory's absolute path is set in PDDIR. If a relative path is set in PDDIR, replace it with the absolute path and then re-execute the command.

If "aa....aa" is not displayed:

Specify the HiRDB directory's absolute path name in PDDIR and then re-execute the command.

KFPY01204-E E+L

PLUGIN aa....aa already setup

The specified plug-in aa....aa has already been set up.

aa....aa: Plug-in name

S: Terminates processing.

Action

If the setup command for the previous plug-in aa....aa terminated normally, there is no need to re-execute it. If setup of aa....aa was not terminated normally, execute pdplgset -d and then re-execute the pdplgset command.

KFPY01206-E E+L

Permission error occurred, path name=aa....aa

An access permission error occurred in aa....aa. The following are possible causes:

The specified command argument is invalid.

No access privilege is granted for the installation directory.

An error occurred on an internal OS command.

Other (cause other than the previous ones)

aa....aa: File or directory in which the read or write error occurred

S: Terminates processing.

Action

If the specified command argument is invalid:

Specify the correct command argument and re-execute the command.

If no access privilege is granted for the installation directory:

Delete the installation directory and reinstall it. Or, grant an access privilege so that the HiRDB administrator can access the installation directory.

If an error occurred in an internal OS command:

Check the cause of the error based on the OS command's error message, and take an appropriate action.

If the cause is other than those listed previously:

Save the files under %PDDIR%\plugin and the files under the installation directory specified in the argument, and then contact the customer support center.

KFPY01207-E E+L

Failed to create file or directory, path name="aa....aa"

Creation of file or directory "aa....aa" failed. The following are possible causes:

The user did not execute the command as the HiRDB administrator.

The HiRDB administrator does not have the HiRDB directory write privilege.

An error occurred on an internal OS command.

Other (cause other than the previous ones)

aa....aa: File or directory whose creation failed

S: Terminates processing.

Action

If the user did not execute the command as the HiRDB administrator:

Execute the command as the HiRDB administrator.

If the HiRDB administrator does not have the HiRDB directory write privilege:

Grant the HiRDB directory write privilege.

If an error occurred in an internal OS command:

If an OS command error message is displayed, check the cause of the error based on the message, and take an appropriate action.

If the cause is other than those listed previously:

Save the files under %PDDIR%\plugin, and then contact the customer support center.

KFPY01208-E E+L

File or directory not exists, path name=aa....aa

The file or directory aa....aa was not found. The following are possible causes:

The specified command argument is invalid.

The installation directory is damaged.

An error occurred in an internal OS command.

Other (cause other than the previous ones)

aa....aa: Name of the file or directory referenced

S: Terminates processing.

Action

If the specified command argument is invalid:

Specify the correct command argument and re-execute the command.

If the installation directory is damaged:

Reinstall the plug-in to be set up.

If an error occurred on an internal OS command:

If an OS command error message is displayed, check the cause of the error based on the message and take an appropriate action.

If the cause is other than those listed previously:

Save the files under %PDDIR%\plugin and the files under the installation directory specified in the argument, and then contact the customer support center.

KFPY01209-E E+L

Not a directory, path name=aa....aa

aa....aa is not a directory.

aa....aa: Name of the directory referenced

S: Terminates processing.

Action

Check the path specified in the argument for any error. If the path is invalid, specify the correct installation directory and re-execute the command.

If a file called plugin was created in the HiRDB directory, rename the file.

KFPY01210-E E+L

PLUGIN aa....aa not installed

Plug-in aa....aa has not been installed.

aa....aa: Plug-in name

S: Terminates processing.

Action

Check if the path specified in the argument is correct. If it is wrong, specify the correct path and re-execute the command.

If plug-in aa....aa has not been installed, install it.

KFPY01211-E E+L

Internal error occurred, func=aa....aa, location=bb....bb, info="cc....cc"

An internal error occurred.

aa....aa: Name of function where the internal error occurred

bb....bb: Location within aa....aa

cc....cc: Error information

S: Terminates abnormally.

Action

If messages have been output to files in %PDDIR%\plugin or to the event log (in UNIX, syslogfile), or (for OS commands) messages have been displayed in the command execution window, save the messages and contact the customer support center.

Before starting HiRDB, delete the plug-in pdplugin operand that was to be set up from the system common definition for all units, and then start HiRDB.

KFPY01213-E E+L

Specified directory not full path name

The specified directory is not an absolute path name.

S: Terminates processing.

Action

Specify the absolute path of the installation directory in the command argument and execute the command.

KFPY01214-E E+L

PLUGIN aa....aa not setup

Plug-in aa....aa has not been set up. The following are:

The plug-in name specified in the argument is invalid.

The path set in the PDDIR environment variable is invalid.

The plug-in with its name specified in the argument has not been set up.

aa....aa: Plug-in name

S: Terminates processing.

Action

If the plug-in name specified in the argument is invalid:

Specify the correct plug-in name in the argument and re-execute the command.

If the path set in the PDDIR environment variable is invalid:

Specify the correct path in the PDDIR environment variable and re-execute the command.

If the plug-in with its name specified in the argument has not been set up:

There is no need to execute the command.

KFPY01215-E E+L

Unable to execute aa....aa command while HiRDB running

It is impossible to execute the indicated command because HiRDB is running.

aa....aa: Name of executed command

S: Terminates processing.

Action

Execute the command while HiRDB is not running.

KFPY01216-E E+L

Pdplgset already used by another user

The pdplgset command is already being executed.

S: Terminates processing.

Action

Wait until the current pdplgset command is terminated, and then re-execute the pdplgset command.

KFPY01227-E L

PLUGIN library aa....aa incompatible load model type with HiRDB

The load type (POSIX or non-POSIX) of plug-in library aa....aa and the load type of HiRDB do not match.

aa....aa: Plug-in name

S: Terminates processing.

Action

Install a plug-in that matches the HiRDB version, specify a plug-in matching the HiRDB load type, and then re-execute the command.

KFPY02001-E E

Fatal error, inf=aa....aa

A fatal error occurred during command execution.

aa....aa: Maintenance information

S: Terminates processing.

Action

Contact the customer support center.

KFPY02006-E E

Invalid arguments
usage: pdplgrgst [{-a| -d}] [-u] definition_file PIC file

The specified plug-in definition file or PIC file is invalid. This message displays the command usage.

S: Terminates processing.

Action

Specify a plug-in definition file name and PIC file name as the arguments in the command line. Make sure that the specified file name is correct, and then re-execute the command.

KFPY02007-E E

Read error occurred, file="aa....aa", errno=bbb

A read error occurred in file "aa....aa".

aa....aa: Name of the file where the read error occurred

bbb: Value set in errno

S: Terminates processing.

Action

Eliminate the cause of the error by checking errno.h and the applicable OS manual based on the value of the errno (external integer variable indicating the error status), and then re-execute the command.

KFPY02010-E E

Insufficient process local memory, size=aa....aa

An attempt was made to allocate a process private area during command execution, but it failed due to insufficient memory.

aa....aa: Size of area to be allocated (in bytes)

S: Terminates processing.

Action

Check if another process is using a large amount of memory and take one of the following actions:

If there is a process using a large amount of memory:

Wait until the process is terminated and then re-execute the command.

If there is no process using a large amount of memory:

Terminate any unneeded processes and then re-execute the command. If this message is displayed again, contact the customer support center.

KFPY02011-E E

Invalid PLUGIN definition file, file=aa....aa

The contents of the plug-in definition file are invalid.

aa....aa: File name specified in the command line

S: Terminates processing.

Action

Make sure that the file specified in the command argument is a plug-in definition file.

KFPY02012-E E

Invalid PIC file, file=aa....aa

The contents of the PIC file are invalid.

aa....aa: File name specified in the command line

S: Terminates processing.

Action

Make sure that the file specified in the command argument is a PIC file.

KFPY02013-E E

aaaaa type "bb....bb" already defined

Abstract data type or index type "bb....bb" is already defined.

aaaaa: Type:

Data: Abstract data type

Index: Index type

bb....bb: Name of the type already defined

S: Terminates processing.

Action

If type "bb....bb" is a user-defined abstract data type, delete the abstract data type ("bb....bb") to use the plug-in. If type "bb....bb" is not a user-defined abstract data type, the plug-in has not been registered correctly. Execute the pdplgrgst command, specifying the -d option to delete the plug-in from HiRDB, and then register the plug-in again.

KFPY02014-E E

PLUGIN definition file aa....aa does not correspond to PIC file bb....bb

The specified plug-in definition file does not correspond to the specified PIC file.

aa....aa: Name of the plug-in definition file specified in the command line

bb....bb: Name of the PIC file specified in the command line

S: Terminates processing.

Action

Make sure that both the plug-in definition file and the PIC file specified in the command line belong to the plug-in subject to registration processing, and then re-execute the command.

KFPY02015-E E

PLUGIN aa....aa already registered in schema "bb....bb"

Plug-in aa....aa is already registered in HiRDB.

aa....aa: Name of the plug-in subject to registration processing

bb....bb: Schema in which the plug-in is registered

S: Terminates processing.

Action

Plug-in aa....aa is already registered in HiRDB. To use the plug-in, code the pdplugin operand in the system common definition, and then restart HiRDB. To delete the plug-in, execute the pdplgrgst command, specifying the -d option. To upgrade the plug-in, execute the pdplgrgst command, specifying the -a option.

KFPY02016-I E

Processing of PLUGIN aa....aa ended, PLUGIN=bb....bb, return code=c

Registration or deletion of the indicated plug-in has terminated.

aa....aa: Nature of processing:

registration: Registration

unregistration: Deletion

updating: Version upgrading

bb....bb: Plug-in name

c: Termination code (0 or 8)

S: Terminates processing.

Action

If the termination code is not 0, take an appropriate action according to the message that was displayed before this message. Note that ******** is displayed as the plug-in name in the following cases:

The argument specified in the command line is invalid.

An invalid combination of the plug-in definition file and PIC file was specified in the command file.

The establishment of a connection with HiRDB failed.

The PDUSER environment variable setting is invalid for the user with the DBA privilege.

Memory allocation failed.

KFPY02017-E E

PLUGIN aa....aa not registered

Plug-in aa....aa is not registered.

aa....aa: Name of the plug-in subject to deletion

S: Terminates processing.

Action

Plug-in aa....aa either has not been registered or has already been deleted. To register the plug-in, omit both -a and -d options. If the -u option was specified to register the plug-in in the pdplgrgst command executor's schema, be sure to specify the -u option when deleting or upgrading the plug-in.

KFPY02018-E E

PLUGIN aa....aa registered in schema "bb....bb", not in schema "cc....cc"

Plug-in aa....aa has been registered in schema "bb....bb", but not in schema "cc....cc".

aa....aa: Plug-in name

bb....bb: Schema in which the plug-in is registered

cc....cc: Schema subject to deletion of plug-in

S: Terminates processing.

Action

The specified plug-in is not registered in the schema subject to deletion of plug-in. Set the pdplgrgst command option and PDUSER environment variable values according to the following table, and then re-execute the command:

bb....bb | Option to be specified | PDUSER setting
MASTER | -d | User with DBA privilege
Other | -d -u | Authorization identifier and password of user "bb....bb"

KFPY02019-E E

Error occurred while unregistering PLUGIN, inf=aa....aa

An error occurred in the SQL that was executed to delete a plug-in.

aa....aa: Information about the SQL execution error

S: Terminates processing.

Action

Eliminate the cause of the error based on the displayed message text, and then re-execute the command.

KFPY02021-E E

Error occurred while updating PLUGIN, inf=aa....aa

An error occurred while upgrading a plug-in.

aa....aa: Information about the SQL execution error

S: Terminates processing.

Action

Eliminate the cause of the error based on the displayed message text, and then re-execute the command.

KFPY02022-E E

Newer version of PLUGIN aa....aa registered, registered PLUGIN version=bb....bb, specified PLUGIN version=cc....cc

A newer version of the plug-in is registered.

aa....aa: Plug-in name

bb....bb: Version of the currently registered plug-in

cc....cc: Version of the plug-in whose registration was attempted

S: Terminates processing.

Action

A plug-in cannot be upgraded to an older version. Install and set up the plug-in version bb....bb.

KFPY02023-E E

PLUGIN definition file incompatible with PIC file

The plug-in definition file is not compatible with the PIC file.

S: Terminates processing.

Action

The plug-in is not set up correctly. Set it up again.

KFPY02024-E E

Newer version of HiRDB required to aa....aa version bb....bb of PLUGIN cc....cc

A newer version of HiRDB is required to register or upgrade plug-in cc....cc version bb....bb.

aa....aa: Type of processing:

register: Registration

update: Version upgrading

bb....bb: Plug-in version

cc....cc: Plug-in whose registration or upgrading was attempted

S: Terminates processing.

Action

Upgrade the HiRDB system.

KFPY02025-E E

Incompatible PLUGIN library format with HiRDB, PLUGIN data model=aa, HiRDB data model=bb

The format of the plug-in library does not match the HiRDB format.

aa: Data model of the plug-in

bb: HiRDB data model

S: Terminates processing.

Action

When aa is 32 and bb is 64, set the plug-in to the 64-bit mode. When aa is 64 and bb is 32, either set HiRDB to the 64-bit mode or the plug-in to the 32-bit mode. When migrating to a 64-bit mode HiRDB system, you cannot return the system to a 32-bit mode HiRDB.

KFPY02027-E E

PLUGIN library aa....aa incompatible load model type with HiRDB

The load type for the plug-in library (POSIX or non-POSIX library version) and the load type for HiRDB do not match.

aa....aa: Plug-in name

S: Terminates processing.

Action

Register a plug-in that matches the load type (POSIX or non-POSIX library version) for HiRDB, and then re-execute the command.

KFPY02039-E E

Open error occurred, file="aa....aa", errno=bbb

An open error occurred on file "aa....aa", which is used to register a plug-in.

aa....aa: Name of the file where the open error occurred

bbb: Error number (errno)

S: Terminates processing.

Action

Eliminate the cause of the error by checking errno.h and the applicable OS manual based on the value of the errno (external integer variable indicating the error status), and then re-execute the command.

KFPY02101-E E

Failed to get time

The system was unable to obtain the current time.

S: Terminates processing.

Action

Contact the customer support center.

KFPY02110-E E

Data type "aa....aa" not defined

Abstract data type "aa....aa" is required for the plug-in, but it is not defined.

aa....aa: Name of the undefined abstract data type

S: Terminates processing.

P: Define the abstract data type named "aa....aa", and then re-execute the command. If this message is issued again, contact the customer support center.

Action

Contact the customer support center.

KFPY02111-E E

Index type "aa....aa" not defined

Index type "aa....aa" is required for the plug-in, but it is not defined.

aa....aa: Name of the undefined index type

S: Terminates processing.

P: Define the index type named "aa....aa", and then re-execute the command. If this message is issued again, contact the customer support center.

Action

Contact the customer support center.

KFPY02112-E E

Duplicate data type PLUGIN for "aa....aa"

The data type plug-in for "aa....aa" is already registered.

aa....aa: Name of the abstract data type

S: Terminates processing.

Action

If the plug-in is already registered, there is no need to use this command. If the plug-in has not been registered, but this message was issued, contact the customer support center.

KFPY02113-E E

Duplicate index type PLUGIN for "aa....aa"

The index type plug-in for "aa....aa" is already registered.

aa....aa: Name of the index type

S: Terminates processing.

Action

If the applicable plug-in is already registered, there is no need to use this command.

KFPY02114-E E

Duplicate PLUGIN name "aa....aa"

Plug-in "aa....aa" is already registered.

aa....aa: Name of the plug-in that is already registered

S: Terminates processing.

Action

If the applicable plug-in is already registered, there is no need to use this command.

KFPY02120-E E

PIC file error, inf=aa....aa

The PIC file is invalid.

aa....aa: Maintenance information

S: Terminates processing.

Action

The contents of the PIC file may be damaged. Re-execute plug-in installation and setup. If this message is issued again, contact the customer support center.

KFPY02121-E E

PIC file version error

The plug-in subject to registration is not compatible with the HiRDB version.

S: Terminates processing.

Action

Make sure that the HiRDB version supports the operating conditions for the plug-in to be registered.

KFPY02122-E E

PIC file header error

The PIC file header is invalid.

S: Terminates processing.

Action

Make sure that the PIC file name is specified in the command argument, and then re-execute the command. If the PIC file name was specified, but this message was issued, contact the customer support center.

KFPY02140-E E

PLUGIN ID(aa....aa) already used

aa....aa is already in use as a plug-in ID.

aa....aa: Plug-in ID

S: Terminates processing.

Action

Contact the customer support center.

KFPY02200-E E

Error occurred on server, inf=aaa

An error occurred when accessing the server to register a plug-in.

aaa: Maintenance information

S: Terminates processing.

Action

If another message was issued before this message:

Eliminate the cause of the error according to the message issued before this message, and then re-execute the command.

If no message was issued before this message:

Contact the customer support center.

KFPY02201-E E

Error occurred while defining PLUGIN, inf=aa....aa

An error occurred when executing SQL to define a plug-in.

aa....aa: Nature of SQL execution error

S: Terminates processing.

Action

Eliminate the cause of the error based on the output message text, and then re-execute the command.

KFPY02202-E E

Error occurred while processing PIC file, inf=aaaa

An error occurred while processing a PIC file.

aaaa: Maintenance information

S: Terminates processing.

Action

Contact the customer support center.

KFPY02210-E E

Connect error occurred

An error occurred while connecting to the server.

S: Terminates processing.

Action

If an SQL-statement-related message was issued before this message:

Eliminate the cause of the error indicated in the message, and then re-execute the command.

If no SQL-statement-related message was issued before this message:

Make sure that the user has the DBA privilege on the HiRDB system, and then re-execute the command.

KFPY02213-E E

User aa....aa has no DBA privilege

The user does not have the DBA privilege that is required to execute the pdplgrgst command.

aa....aa: User name

S: Terminates processing.

Action

The DBA privilege is required to execute the pdplgrgst command. Specify a user with the DBA privilege in the PDUSER environment variable and re-execute the command.

KFPY02220-E E

Failed in definition

Plug-in definition failed.

S: Terminates processing.

Action

Eliminate the cause of the error according to the message issued before this message, and then re-execute the command.

For example, check the name of the plug-in definition file.

KFPY02230-E E

Invalid setting of environment variable PDUSER

The setting of the PDUSER environment variable is invalid.

S: Terminates processing.

Action

Check the setting of the PDUSER environment variable and then re-execute the command. The PDUSER environment variable must be set to execute this command.

KFPY02300-E E

Error occurred, inf1=aa....aa, inf2=bbbb

An error occurred during command execution.

aa....aa: Maintenance information 1

bbbb: Maintenance information 2

S: Terminates processing.

Action

Contact the customer support center.

KFPY03001-E L

PLUGIN module requested abortion. PLUGIN ID=aa....aa, Abort code=bb....bb, Information=cc....cc

The indicated plug-in requested abnormal termination.

aa....aa: Plug-in ID

bb....bb: Abort code

cc....cc: Abort information

S: Terminates abnormally.

Action

Save the files under %PDDIR%\spool, %PDDIR%\tmp, and %PDDIR%\plugin, as well as the event log (in UNIX, syslogfile).

Additionally, check the manual for the indicated plug-in, and take an appropriate action according to the abort code. Use the saved information, if necessary, to correct the error.

KFPY99999-I L

(dddddddd)xxxxx-y :zz....zz

This is a message from a plug-in named dddddddd.

dddddddd: Plug-in name

xxxxx: Message ID

y: Significance of the error message

zz....zz: Message text

S: Depends on the handling of message xxxxx-y that was issued by plug-in dddddddd.

Action

Take an appropriate action according to plug-in dddddddd's message xxxxx-y.

2.18 KFPZ messages

KFPZ02401-E R

Environment definition error, valiable=aa....aa, reason=bb....bb

A specified environment variable is invalid.

aa....aa: Name of the invalid environment variable

bb....bb: Cause of the error:

NET ENVIRONMENT:

The specified information does not match the network environment.

S: Terminates processing.

P: Check the environment variable displayed in the message, correct the error, and then re-execute. If reason=NET ENVIRONMENT is displayed, check that the host name specified in PDHOST is a hosts file.

KFPZ02402-E R

Memory shortage, size=aa....aa, inf=bb....bb

Indicated size (aa....aa) of memory cannot be allocated.

aa....aa: Size (in bytes) that was to be allocated

bb....bb: Maintenance information

S: Terminates processing.

P: Contact the system administrator.

Action

Recheck the amount of memory that is required. If this message is output to the XDS log file, revise the value specified in the operand pdq_memory_xdb_limit_size in the XDS server definition.

KFPZ02404-E R

Parameter error, func=aa....aa, item=bb....bb

An internal contradiction was detected.

aa....aa: Name of the function resulting in the error

bb....bb: Name of the erroneous function

S: Terminates processing.

P: Contact the system administrator.

Action

Contact the customer support center.

KFPZ02405-E R

System call error, func=aa....aa, errno=bb....bb

The system call indicated by func resulted in an error.

aa....aa: Name of the system call resulting in the error

bb....bb: Error indicator

S: Terminates processing.

P: Check the value of the error indicator, see the errno.h (for Windows, including Winsock error codes) and the applicable OS manual, resolve the cause of the error, and then re-execute the command.

KFPZ02406-E R

Error occurred in HiRDB/client, reason=aa....aa, inf=bb....bb

An error occurred during HiRDB/client internal processing.

aa....aa: One of the following is displayed as the cause of the error:

MEMORY: Memory shortage occurred.

NETWORK: Network error occurred.

RESIDENT MEM: There was no available resident memory.

RESOURCE: There were not enough resources.

TIME OUT: Timeout occurred.

TSR MODULE: Resident module was inactive.

UNEXPECT: Other error occurred.

bb....bb: Maintenance information

S: If unavailable resident memory is the cause of the error, ignores the error and resumes processing; otherwise, cancels the current processing.

P: Save the client error log where this message was output and contact the HiRDB administrator.

Action

Look for the cause of the error in the client error log where the message was output, and then eliminate the cause of the error.

KFPZ02410-E R

HiRDB replied error, code=aa....aa, IPaddr=bb....bb, port=cc....cc, inf=dd....dd

An error was reported from HiRDB.

aa....aa: Error code returned from HiRDB

bb....bb: IP address at the send side (if a client UAP and the HiRDB server a rerun on the same server machine, 0 is displayed)

cc....cc: Port number at the send side

dd....dd: Name of the erroneous file

S: Resumes processing.

P: If no message with the client error log lead identifier >> is output immediately after this message, retry processing was successful. If a message with the client error log lead identifier >> is output, refer to the corrective action in that message. In addition, if the error code returned by HiRDB is in 4.1 Detail codes for RPC-related errors or 4.2 Detail codes for system-related errors, refer to the causes and corrective actions associated with the code.

KFPZ02411-E R

Invalid message received, IPaddr=aaaaaaaa, port=bb....bb, inf=cc....cc

A received message cannot be analyzed.

aaaaaaaa: IP address at the send side (if a client UAP and the HiRDB server a rerun on the same server machine, 0 is displayed)

bb....bb: Port number at the send side

cc....cc: Name of the erroneous file

S: Resumes processing; ignores the received message and waits for the next message.

P: Contact the HiRDB administrator.

Action

Refer to the displayed IP address and port number to determine the process at the send side, and check the network environment.

KFPZ02420-E R

Protocol error, IPaddr=aaaaaaaa, port=bb....bb, reason=cc....cc

Invalid information was detected in the HiRDB inter-process communication protocol header.

aaaaaaaa: IP address at the send side (if a client UAP and the HiRDB server a rerun on the same server machine, 0 is displayed)

bb....bb: Port number at the send side

cc....cc: One of the following is displayed as the reason:

INF2 ERROR:

Contents of additional information 2 are invalid.

SIZE OVER:

Message longer than 12 bytes was received as the HiRDB IPC header.

SIZE SHORT:

Message shorter than 12 bytes was received as the HiRDB IPC header.

SIZE ZERO:

Message with a length of 0 bytes was received as the HiRDB IPC header.

S: Terminates processing.

P: Contact the HiRDB administrator.

Action

SIZE ZERO displayed:

Check the cause of the server termination (HiRDB/Single Server (SDS) or HiRDB/Parallel Server (FES)), eliminate the cause, and then re-execute the UAP.

Other reason displayed:

Contact the customer support center.

KFPZ02421-E R

Invalid size, received size=aa....aa, size in head=bb....bb, IPaddr=cccccccc, port=dd....dd

Processing was cancelled because the data length of the receive completion report was less than the data length of the protocol header used for HiRDB inter-process communication.

aa....aa: Received data length

bb....bb: Data length in header

cccccccc: IP address at the send side (if a client UAP and the HiRDB server a rerun on the same server machine, 0 is displayed)

dd....dd: Port number at the send side

S: Terminates processing.

P: Check whether or not the server terminated abnormally.

KFPZ02444-E R

Communication error, func=aa....aa [(bb....bb)], errno=cc....cc[, count=dddd, interval=eeee]

A communication error occurred.

aa....aa: Name of the socket interface function resulting in the error (up to 21 characters)

bb....bb: Displayed character strings:

IP address:

Displayed when the connect function name is invoked during INET communication.

Port number:

Displayed when the connect function name is invoked during communication other than INET.

File name:

Displayed when the function name is bind during UNIX domain communication.

cc....cc: Error indicator

dddd: Number of retries

The value of the client environment definition PDBINDRETRYCOUNT.

eeee: Retry interval (milliseconds)

The value of the client environment definition PDBINDRETRYINTERVAL.

S: Terminates processing.

P:

Check the value of the error indicator, see the errno.h (for Windows, including Winsock error codes) and the applicable OS manual, resolve the cause of the error, and then re-execute the command.

If func=write, read, or errno indicates the value EPIPE or (WSA)# ECONNRESET, it suggests an abnormal termination of the HiRDB server.

If the value indicated by func=connect or errno is either ENOENT or (WSA)# ECONNREFUSED, it is possible that the specification of the client environment definition that identifies the connection destination is incorrect. For details about the client environment definitions used to specify connection destinations, see XDS environment definition in the HiRDB Version 9 Memory Database Installation and Operation Guide if you are using an XDS client, or see Environment definition information in the HiRDB Version 9 UAP Development Guide if you are using the client for the server providing the primary facilities.

If the value of the client environment definition is correct, and the value indicated by func=connect or errno is either (WSA)# ETIMEDOUT or (WSA)# ECONNREFUSED, it is possible that there are too many connection requests to the HiRDB server. If that is the case, wait for a while, and then retry the operation. For details about the actions to take, see Listen queue specified values in the HiRDB Version 9 Installation and Design Guide.

#: (WSA) is the name of a Winsock error code.

The table below lists the function names shown in aa....aa and typical errors displayed for cc....cc. Note that in the Windows edition of HiRDB, WSA precedes the error indicator.

Function name (aa....aa)
Typical error indicator (cc....cc)

accept
EAGAIN, EMFILE, ENFILE, ENOMEM, ENOTSOCK, EWOULDBLOCK

bind
EACCES, EADDRINUSE, EADDRNOTAVAIL, EAFNOSUPPORT, EINVAL, ENETDOWN, ENOBUFS, ENOMEM, ENOTSOCK

close
EBADF, EINTR, ENOSPC

closesocket,
soclose
WSANOTINITIALISED, WSAENETDOWN, WSAENOTSOCK, WSAEINPROGRESS, WSAEINTR, WSAEWOULDBLOCK

connect,
non-block connect
EADDRINUSE, EADDRNOTAVAIL, EAFNOSUPPORT, EALREADY, ECONNREFUSED, EINTR, ENETDOWN, ENOBUFS, ENOMEM, ENOSPC, ETIMEDOUT

fcntl
EBADF, EMFILE, EMFILE, EINVAL, EINTR, EACCES, ENOLCK, EAGAIN, ENOTSOCK

gethostbyaddr
HOST_NOT_FOUND, TRY_AGAIN, NO_RECOVERY, NO_ADDRESS

gethostbyname

gethostname
EFAULT

getsockname
EBADF, ENOTSOCK, ENOBUFS, EFAULT, EINVAL, EOPNOTSUPP

ioctl
EBADF, ENOTTY, EINVAL, EINTR, EPERM

ioctlsocket
WSANOTINITIALISED, WSAENETDOWN, WSAEINPROGRESS, WSAENOTSOCK, WSAEFAULT, WSAEINVAL

listen
EBADF, EDESTADDRREQ, ENOTSOCK, EOPNOTSUPP, EINVAL

mkfifo
EACCES, EEXIST, EFAULT, ELOOP, ENAMETOOLONG, ENOENT, ENOSPC, ENOTDIR, EROFS

open
EACCES, EAGAIN, EEXIST, EFAULT, EINTR, EINVAL, EISDIR, EISDIR, ELOOP, EMFILE, ENAMETOOLONG, ENFILE, ENOENT, ENOTDIR, ENOSPC, EROFS

readv
EAGAIN, EBADF, EBADMSG, EINTR, EINVAL, EIO, EISDIR

recv
EAGAIN, EBADF, ECONNRESET, EFAULT, EINTR, EINTR, EINVAL, EMSGSIZE, ENOBUFS, ENOTCONN, ENOTSOCK, EOPNOTSUPP, ETIMEDOUT, EWOULDBLOCK

recvfrom

select,
xa_select
EBADF, EINTR, EINVAL

send
EACCES, EAFNOSUPPORT, EAGAIN, EBADF, ECONNRESET, EDESTADDRREQ, EFAULT, EINTR, EINVAL, EIO, EISCONN, EMSGSIZE, ENETDOWN, EHOSTUNREACH, ENETUNREACH, ENOBUFS, ENOMEM, ENOTCONN, ENOTSOCK, EOPNOTSUPP, EPIPE, EWOULDBLOCK

sendto

setsockopt
EFAULT, EINVAL, ENOBUFS, ENOPROTOOPT, ENOTSOCK, EOPNOTSUPP

socket,
socket2
EAFNOSUPPORT, EHOSTDOWN, EINVAL, EMFILE, ENFILE, ENOBUFS, ENOMEM, EPROTONOSUPPORT, EPROTOTYPE, ESOCKTNOSUPPORT, ETIMEDOUT

writev
EAGAIN, EBADF, EFBIG, EINTR, EIO, ENOSPC, EPIPE, ERANGE, EINVAL

KFPZ02445-I R

Client information, Type=aa....aa, Inf=bb....bb

Outputs client information.

aa....aa: Type of client information (see Action below)

bb....bb: Client information (see Action below)

S: Continues processing.

Action

Take action according to the following client information.

Type of client information (aa....aa)
Client information (bb....bb)
Description
Action

Reconnect
MAX_USERS_OVER, time=cc....cc
Reconnection processing has began because the number of connected users exceeded the maximum value. Reconnection is attempted for cc....cc seconds.
If reconnection fails, re-evaluate the value specified for the pd_max_users operand in the system definition.

MAINTENANCE, time=cc....cc
Reconnection processing has begun, due to either updating of the HiRDB program, execution of the system reconfiguration command (pdchgconf command), or transaction queuing. Reconnection is attempted for cc....cc seconds.
If you are updating the HiRDB program or executing the system reconfiguration command (pdchgconf command), wait until it finishes, and then retry the operation.
In the case of transaction queuing, release the transaction queuing facility, and then retry the operation.

AUTO_RECONNECT, number=cc....cc, interval=dd....dd
Reconnection processing has begun by means of the automatic reconnect facility. Reconnection is attempted cc....cc times at dd....dd second intervals.
If reconnection fails, eliminate the cause of the communication error, and then re-execute the command.

KFPZ02470-E R

Invalid parameter, parameter number=aa....aa

An argument of the COMMAND EXECUTE statement is invalid.

aa....aa: Argument number:

#1: Command line variable

#3: Execution results receiving area size variable

#4: Execution results size receiving variable

#5: Execution results receiving variable

#6: Execution command return code receiving variable

#7: Environment variable group name variable

#8: Execution unit variable

S: Continues processing.

P: Check the argument, correct it if it is incorrect, and then re-execute.

KFPZ02471-E R

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

An error occurred during communication with HiRDB Control Manager - Agent.

aa....aa: Error detail:

INIT ERROR,CODE=bbb

HiRDB Control Manager - Agent initialization error

NETWORK

Network error

Assist-Server NOT UP

HiRDB Control Manager - Agent not active

Assist-Server BUSY

Timeout occurred during communication

bbb: HiRDB Control Manager - Agent error detail code

S: Terminates processing.

P: Inform the HiRDB administrator of the error detail, correct the error, and then re-execute.

Action

Eliminate the cause of the error based on the detail information output to the execution results receiving area and command trace, and then re-execute. If the error detail is Assist-Server NOT UP, check and modify the values specified for PDASTHOST and PDASTPORT in the client environment definition if necessary.

The following are the error detail codes and actions for HiRDB Control Manager - Agent errors:

Error detail code | Cause | Action
-7001 | Invalid internal argument in the HiRDB Control Manager - Agent | Contact the customer support center.
-7002 | Either an error occurred in a system call executed internally on the HiRDB Control Manager - Agent or data that a client requested is invalid. | Re-execute the command. If this error recurs, acquire all information in the HiRDB Control Manager - Agent directory, and then contact the customer support center.
-7003 | There is a shortage of process-private memory. | Re-execute the command when there is sufficient free memory in the overall system.
-7007 | An error was found in the HiRDB system definition. | Correct the system definition of HiRDB, and then re-execute the command.
-7008 | There is no HiRDB system definition. | Correctly set up the HiRDB Control Manager - Agent.
-7009 | Initialization failed when connecting to the HiRDB Control Manager - Agent. | Check the initerr information returned to the client, and then take appropriate action for the error code.
-7014 | The specified authorization identifier/password is invalid. | Correctly specify the identifier/password, and re-execute.
-7015 | An error was found in the PDDIR environment variable in the HiRDB system. | Correctly set the PDDIR environment variable, and then re-execute the command.
-7016 | An attempt was made to connect to a unit other than the HiRDB system manager. | Connect to the HiRDB Control Manager - Agent in the unit on the system manager.
-7017 | The specified user does not belong to the group as the HiRDB administrator ID. | Connect to the server as a user of the same group as the HiRDB administrator ID.
-7019 | Failed to connect to the temporary file name. | Re-execute the command. If this error recurs, acquire all information in the HiRDB Control Manager - Agent directory, and then contact the customer support center.
-7023 | Failed to open a temporary file.
-7039 | An error was found in the HiRDB Control Manager - Agent definition. | Correct the definition of the HiRDB Control Manager - Agent, and then re-execute the command.
-7041 | Cannot make a dynamic link to the HiRDB library or DLL. | Correctly set up the HiRDB Control Manager - Agent, and then re-execute the command.
Others | See the Release Notes for HiRDB Control Manager - Agent.

KFPZ02472-E R

Error occurred in Assist - Server, code=aaaaa

An error occurred on the HiRDB Control Manager - Agent.

aaaaa: Error detail code of the HiRDB Control Manager - Agent

S: Terminates processing.

P: Report details of the error to the HiRDB administrator, eliminate the cause of the error, and then re-execute the command.

Action

See the error detail codes of the HiRDB Control Manager - Agent to eliminate the cause of the error, and then re-execute the command.

The following are the HiRDB Control Manager - Agent error detail codes and actions:

Error detail code | Cause | Action
-7001 | Invalid internal argument in the HiRDB Control Manager - Agent. | Contact the customer support center.
-7002 | Either an error occurred in a system call executed internally on the HiRDB Control Manager - Agent or data that a client requested is invalid. | Re-execute the command. If this error recurs, acquire all information in the HiRDB Control Manager - Agent directory, and then contact the customer support center.
-7003 | There is a shortage of process-private memory. | Re-execute the command when there is sufficient free memory in the overall system.
-7019 | Failed to acquire a temporary file name. | Re-execute the command. If this error recurs, acquire all information in the HiRDB Control Manager - Agent directory, and then contact the customer support center.
-7023 | Failed to open a temporary file.
Others | See the Release Notes for HiRDB Control Manager - Agent.

KFPZ02473-E R

Reset environment definition error, envname=aa....aa, variable=bb....bb, reason=cc....cc

An error was found in the specification of the client environment definition dynamically changed by the p_rdb_mth_ChgEnv function.

aa....aa: Environment variable name in the client environment definition

bb....bb: Specification value aa....aa (displays the first 30 bytes when the value exceeds 30 bytes)

cc....cc: Character strings output as a reason:

OUT OF RANGE: The value is out of range.

INVALID CHAR: There is a value that cannot be specified.

INVALID IDENTIFIER: The identifier is invalid.

S: Terminates processing.

P: Correct the error, and then re-execute the command.

KFPZ03000-I R

Error information, type=aa....aa, inf=bb....bb

An error was detected between the HiRDB server and a HiRDB client. This message is output to the client error log file when there is an error to provide detailed information that can be used to investigate the cause of the error.

aa....aa: Type of error information

bb....bb: Error information

Type of error information | Error information | Description
INNER OPERATION | Internal processing sequence | Displays information on the internal processing sequence when the error occurred.
SQL STREAM | Executed SQL statement | Displays the SQL statement executed when the error occurred.
CONNECT STATUS | Version information, and connection destination server information | Displays information on the client library associated with the SQL execution error, and information on the connection destination server.
SERVER INFO | Reconnection information | Displays information on the HiRDB server that was reconnected after the SQL was canceled.
KeepAlive | KeepAlive error information | Displays internal error information for the KeepAlive function.
TRANSFER SIZE | Transfer size change | If a WSAENOBUFS error occurs while sending or receiving data, and you change the data transfer size, and then retry sending or receiving, this displays the data transfer sizes before and after the change.

S: Resumes processing.

P: Appropriate action should be taken according to the message that is output before or after this message.

O: Appropriate action should be taken according to the message that is output before or after this message.

Action

This message provides maintenance information when an error occurs. When contacting the customer support center, the contents of this message as well as those of any other messages that may be generated should be supplied as maintenance data.

KFPZ04001-E R

SQLVAR information, type:aa....aa, reason:bb....bb

This message provides details of the KFPA11311-E message which reports an error detected by the client library. If the error was detected by the server, this message is not output.

aa....aa: Type of event resulting in the error:

real length: Invalid real length for variable-length data

data length: Invalid data length

decimal: Invalid precision or decimal places for decimal data

data type: Invalid data type

bb....bb: Variable information for aa....aa, consisting of the following information:

number: Parameter's ordinal number (beginning with 1)

sqlcod: Value of sqlcod

sqllen: Value of sqllen

real length: Parameter's real length

sqlprcsn: Value of sqlprcsn

sqlscale: Value of sqlscale

S: Resumes processing.

P: Correct the parameter on the basis of this message and the KFPA11311-E message, then execute the UAP.

KFPZ04002-E R

SQLDA information, type:aa....aa, reason:bb....bb

This message provides details of the KFPA11310-E message that reports an error detected by the client library. If the error was detected by the server, this message is not output.

aa....aa: Type of event resulting in the error:

sqln: Invalid number of sqlvar instances

sqld: Invalid number of ? parameters or retrieval items

bb....bb: Variable information for aa....aa, consisting of the following information:

sqln: Value of sqln

sqld: Value of sqld

S: Resumes processing.

P: Correct the value for the SQLDA area on the basis of this message and the KFPA11310-E message, then execute the UAP.

KFPZ13000-E S

Required uap program file name missing

Name of the file to be preprocessed was not specified.

S: Terminates processing.

P: Specify the file name and re-execute the preprocessor.

KFPZ13001-E S

Too many uap program file

There are too many files to be preprocessed.

S: Terminates processing.

P: Reduce the number of files and re-execute the preprocessor.

KFPZ13002-E S

Too long path name

The path name specified for retrieving a registered text is too long.

S: Terminates processing.

P: Shorten the path name specified to the PDCBLLIB environment variable and re-execute the preprocessor.

KFPZ13010-E S

Invalid message file

The path name specified for retrieving a registered text is too long.

S: Terminates processing.

P: Reinstall the same version of the message file as for the preprocessor.

KFPZ13020-E S

Unable to edit message, id=aa....aa

Message aa....aa cannot be edited, because an error occurred during error message editing.

aa....aa: ID of the message resulting in the error

S: Terminates processing.

P: Eliminate the cause of the error according to the error message output before this message.

KFPZ13050-E S

Insufficient process local memory, size=aa....aa

Attempt was made to allocate a work area, but specified size aa....aa could not be allocated.

aa....aa: Size (in bytes) of the area that could not be allocated

S: Terminates processing.

P: Add more memory, or terminate another program and re-execute the preprocessor.

KFPZ13051-E S

Memory free error occurred

A work area cannot be released.

S: Terminates processing.

P: Contact the customer support center.

KFPZ13060-E S

Too many errors, preprocessing terminated

Preprocessing was cancelled, because many SQL statement errors were detected.

S: Terminates processing.

P: Eliminate the causes of the errors according to the already output messages and re-execute the preprocessor.

KFPZ13100-E S

Invalid string "aa....aa" in SQL

Character string "aa....aa" is invalid in an SQL statement.

aa....aa: Invalid character string

S: Ignores this SQL statement; cancels preprocessing of the source program at this point and executes syntax checking only.

P: One of the errors listed below may have occurred:

A reserved word was misspelled.

The SQL statement was immediately followed by an extra character string.

Correct the error and re-execute the preprocessor.

KFPZ13102-E S

Invalid string "aa....aa" in data description

Character string "aa....aa" is invalid in a variable definition.

aa....aa: Invalid character string

S: Ignores this error and resumes preprocessing.

P: Correct the erroneous variable definition and re-execute the preprocessor.

KFPZ13104-E S

Invalid data attribute of variable "aa....aa"

The specified data attribute is not permitted for the indicated variable.

S: Ignores this error and resumes preprocessing.

P: Correct the data attribute and re-execute the preprocessor.

KFPZ13105-E S

Invalid data length of variable "aa....aa"

The following error was found in the data length of embedded variable "aa....aa":

Length of BINARY type data is not a multiple of 4.

S: Aborts generation of post source, and then executes syntax checking only.

P: Correct the error in the data length of the embedded variable, and then re-execute the preprocessor.

KFPZ13106-E S

Invalid use of structure or pointer variable "aa....aa"

The structure or usage of a pointer is invalid.
The pointer cannot be used in SQL embedded language that manipulates connection handles.
Structures can be used only in the following specified locations as an embedded variable:

FETCH statement or INTO clause in a single-row SELECT statement

VALUES clause of an INSERT statement

USING clause or INTO clause of an EXECUTE statement

aa....aa: Name of the erroneous embedded variable or indicator variable.

S: Aborts generation of a post source, and then executes syntax checking only.

P: Re-evaluate the embedded variable or indicator variable, and then re-execute the preprocessor.

KFPZ13107-E S

Number of members in indicator structure unmatch with embedded structure "aa....aa"

The member counts of the embedded variable structure and the indicator variable structure do not match.

aa....aa: Name of the erroneous indicator variable

S: Aborts generation of a post source, and then executes only syntax checking.

P: Make the member counts of the embedded variable structure and indicator variable structure match, and then re-execute the preprocessor.

KFPZ13108-E S

Invalid identifier "aa....aa" in SQL

Invalid name aa....aa was found in an SQL statement.

aa....aa: Invalid name:

{  cursor name|SQL statement identifier
|indicator variable|embedded variable
|host identifier|SQL description area name
|authorization identifier|table identifier
|column name|column name description area }

S: Ignores this SQL statement; cancels preprocessing of the source program at this point and executes syntax checking only.

P: Correct the SQL statement and re-execute the preprocessor.

KFPZ13110-E S

Invalid string "aa....aa" in bb....bb program

Character string "aa....aa" cannot be used in program bb....bb.

aa....aa: Unusable character string

bb....bb: Language: { C|COBOL|C++|OOCOBOL }

S: Ignores this SQL statement; cancels preprocessing of the source program at this point and executes syntax checking only.

P: Correct the SQL statement and re-execute the preprocessor.

KFPZ13112-E S

Invalid "aa....aa" following "bb....bb"

Character string "aa....aa" in an SQL statement cannot be specified after character string "bb....bb".

aa....aa: Character string specified at an invalid location in terms of the SQL syntax rules

bb....bb: SQL character string

S: Ignores this SQL statement; cancels preprocessing of the source program at this point and executes syntax checking only.

P: One of the following errors may have occurred. Correct the error, and then re-execute preprocessing:

A reserved word was misspelled.

"aa....aa" was specified at a location that is not permitted by the SQL syntax rules.

KFPZ13114-E S

Incomplete SQL

An SQL statement is incomplete.

S: Ignores this SQL statement; cancels preprocessing of the source program at this point and executes syntax checking only.

P: Correct the SQL statement and re-execute the preprocessor.

KFPZ13116-E S

Semicolon missing

The end of an SQL statement was detected before a semicolon (;).

S: Ignores this SQL statement; cancels preprocessing of the source program at this point and executes syntax checking only.

P: Specify the semicolon at the correct location and re-execute the preprocessor.

KFPZ13118-E S

Closing quotation mark missing

A closing quotation mark (") or apostrophe (') is missing from the end of a character string literal.

S: Ignores this SQL statement; cancels preprocessing of the source program at this point and executes syntax checking only.

P: Specify a quotation mark or apostrophe at the end of the character string literal and re-execute the preprocessor.

KFPZ13122-E S

Invalid use of "aa....aa" parameter

Invalid embedded variable name "aa....aa" was used.

S: Ignores this SQL statement; cancels preprocessing of the source program at this point and executes syntax checking only.

P: Correct the embedded variable and re-execute the preprocessor.

KFPZ13131-E S

Data description entry with TYPEDEF clause not level 1

The data description entry level with the TYPEDEF clause specification is not 1.

S: Continues processing.

P: Change the data description entry level with TYPEDEF clause specification to 1.

KFPZ13132-E S

Unable to specify subordinate element or level 88 entry after data description entry with TYPE clause

The data description entry with a TYPE clause specification is followed by either a subordinate data description entry or a level-88 description entry.

S: Continues processing.

P: Delete the subordinate data description entry or level-88 description entry after the data description entry with TYPE clause specification.

KFPZ13133-E S

Unable to specify "aa....aa" in bb....bb clause, due to data description entry subordinated to group item

A group item to which this description entry belongs is specified in aa....aa of the bb....bb clause.

aa....aa: Type name or the data name in the SAME AS clause

bb....bb: TYPE or SAME AS

S: Continues processing.

P: Review the declaration of the data description entry so that either the type name or the data name in the SAME AS clause does not specify the group item to which the description entry belongs.

KFPZ13134-E S

Level 77 item "aa....aa" not elementary

The type name or the data name "aa....aa" specified in level number 77 is not an elementary item.

aa....aa: Type name or the data name in the SAME AS clause

S: Continues processing.

P: If the left-hand side of a description entry is a level-77 item, the type name or the data name in the SAME AS clause should be an elementary item.

KFPZ13135-E S

Invalid type-name "aa....aa"

Either type name "aa....aa" is not declared or it is declared in duplicate.

aa....aa: Type name

S: Continues processing.

P:A type name should be declared once before the TYPE clause.

KFPZ13136-E S

Unable to specify subordinate element or level 88 entry after data description entry with SAME AS clause

The data description entry with a SAME AS clause specification is followed by either a subordinate data description entry or a level-88 description entry.

S: Continues processing.

P: Delete the subordinate data description entry or level-88 description entry after the data description entry with SAME AS clause specification.

KFPZ13138-E S

Data-name "aa....aa" in SAME AS clause contain OCCURS clause

The coding of the data name "aa....aa" specified in the SAME AS clause contains an OCCURS clause.

aa....aa: Data name

S: Continues processing.

P: Review the declaration of the data description entry so that the OCCURS clause is not specified in the coding of the data name specified in the SAME AS clause.

KFPZ13139-E S

Data-name "aa....aa" in SAME AS clause neither elementary nor level 1 group item

The data name "aa....aa" specified in the SAME AS clause is not an elementary item or a level-1 group item.

aa....aa: Data name

S: Continues processing.

P: The data name specified in the SAME AS clause should be either an elementary item or a level-1 group item.

KFPZ13141-E S

Invalid data-name "aa....aa" in SAME AS clause

In the SAME AS clause, either the data name "aa....aa" is not specified or it is not unique.

aa....aa: Data name

S: Continues processing.

P: The data item referenced by the data name in the SAME AS clause should be coded before this specification. Or, the data name in the SAME AS clause should be qualified so that it is unique.

KFPZ13142-E S

Length of identifier "aa....aa" exceeds bb character

A name length exceeds the permitted maximum number of characters.

aa....aa: Invalid name:

{  cursor name|SQL statement identifier
|indicator variable|embedded variable
|host identifier|SQL description area name
|authorization identifier|table identifier
|column name|column name description area }

bb: Permitted maximum number of characters

S: Ignores this SQL statement; cancels preprocessing of the source program at this point and executes syntax checking only.

P: Correct the name so that it does not exceed the maximum length, and then re-execute the preprocessor.

KFPZ13144-E S

Length of character string exceeds aa....aa

An SQL statement contains a character string literal whose length is greater than the maximum of aa....aa.

aa....aa: Permitted maximum length

S: Ignores this SQL statement; cancels preprocessing of the source program at this point and executes syntax checking only.

P: Correct the character string literal so that it does not exceed the maximum length, and then re-execute the preprocessor.

KFPZ13146-E S

Length of SQL exceeds 2M bytes

The length of an SQL statement exceeds 2 MB.

S: Ignores this SQL statement; cancels generation of the post source of this source program at this point and executes syntax checking only.

P: Correct the SQL statement so that its length does not exceed 2 MB, and then re-execute the preprocessor.

KFPZ13150-E S

Number of cursor exceeds 1023 in a program

More than 1023 cursors were used in a program.

S: Ignores this SQL statement; cancels generation of the post source of this source program at this point and executes syntax checking only.

P: Reduce the number of cursors to no more than 1023 and re-execute the preprocessor.

KFPZ13152-E S

Number of aa....aa exceeds bb....bb in SQL

The total number of embedded variables and indicator variables or the number of table identifiers or column names exceeds the maximum value per SQL statement.

aa....aa: Variable, table identifier, or column name

bb....bb: Permitted maximum value

S: Ignores this SQL statement; cancels generation of the post source of this source program at this point and executes syntax checking only.

P: Correct the value of aa....aa to no more than the displayed maximum and re-execute the preprocessor.

KFPZ13156-E S

Cursor "aa....aa" already used in "bb....bb" statement

Cursor "aa....aa" is already in use by another OPEN, FETCH, or CLOSE statement.
aa....aa: Cursor name

bb....bb: Duplicated SQL statement:

CLOSE: CLOSE statement

FETCH: FETCH statement

OPEN: OPEN statement

S: Ignores this SQL statement; cancels generation of the post source of this source program at this point and executes syntax checking only.

P: Change the cursor name and re-execute the preprocessor.

KFPZ13160-E S

Variable "aa....aa" already defined

Specified embedded variable or indicator variable has already been defined.

aa....aa: Embedded variable or indicator variable

S: Ignores this error and resumes generating the post source.

P: Specify another embedded variable or indicator variable and re-execute the preprocessor.

KFPZ13162-E S

Cursor "aa....aa" already defined

Specified cursor has already been defined.

aa....aa: Cursor name

S: Ignores this error; cancels generation of the post source of this source program at this point and executes syntax checking only.

P: Specify another cursor name and re-execute the preprocessor.

KFPZ13166-E S

SQL statement identifier "aa....aa" already defined

Specified SQL statement identifier "aa....aa" has already been defined.

aa....aa: SQL statement identifier

S: Ignores this SQL statement; cancels generation of the post source of this source program at this point and executes syntax checking only.

P: Specify another SQL statement identifier and re-execute the preprocessor.

KFPZ13168-E S

SQL statement identifier "aa....aa" already used for another cursor

Specified SQL statement identifier "aa....aa" has already been defined for another cursor. The same SQL statement identifier cannot be specified for more than one cursor.

aa....aa: SQL statement identifier

S: Ignores this SQL statement; cancels generation of the post source of this source program at this point and executes syntax checking only.

P: Specify another SQL statement identifier and re-execute the preprocessor.

KFPZ13170-E S

Colon missing before variable "aa....aa" in user program

A colon (:) is missing from embedded variable or indicator variable "aa....aa" in a UAP.

aa....aa: Embedded variable or indicator variable

S: Ignores this error and resumes processing; cancels generation of the post source of this source program at this point and executes syntax checking only.

P: Add a colon to the embedded variable or indicator variable and re-execute the preprocessor.

KFPZ13174-E S

Read only cursor specified UPDATE or DELETE statement

A read-only cursor was specified in the UPDATE or DELETE statement.

S: Ignores this SQL statement; cancels generation of the post source of this source program at this point and executes syntax checking only.

P: Specify a cursor other than a read-only cursor in the UPDATE or DELETE statement and re-execute the preprocessor.

KFPZ13200-E S

PREPARE statement missing for SQL statement identifier "aa....aa"

No PREPARE statement that corresponds to the SQL statement indicated in the SQL statement identifier is defined.

aa....aa: SQL statement identifier

S: Ignores this SQL statement; cancels generation of the post source of this source program at this point and executes syntax checking only.

P: Define a PREPARE statement corresponding to the indicated SQL statement.

KFPZ13201-E S

DECLARE CURSOR statement missing for cursor name "aa....aa"

Specified cursor name "aa....aa" has not been declared.
aa....aa: Cursor name

S: Ignores this SQL statement; cancels generation of the post source of this source program at this point and executes syntax checking only.

P: Declare the indicated cursor ("aa....aa").

KFPZ13202-E S

Variable "aa....aa" undefined

Specified embedded variable "aa....aa" is undefined.

aa....aa: Embedded variable

S: Ignores this SQL statement; cancels generation of the post source of this source program at this point and executes syntax checking only.

P: Define the indicated embedded variable ("aa....aa").

KFPZ13203-E S

Invalid attribute of variable "aa....aa"

The attribute defined for embedded variable "aa....aa" is invalid.

aa....aa: Embedded variable

S: Ignores this SQL statement; cancels generation of the post source of this source program at this point and executes syntax checking only.

P: Correct the attribute of the embedded variable.

KFPZ13204-E S

Indicator variable or parameter "aa....aa" not defined

Specified indicator variable "aa....aa" is undefined.

aa....aa: Indicator variable

S: Ignores this SQL statement; cancels generation of the post source of this source program at this point and executes syntax checking only.

P: Define the indicated indicator variable ("aa....aa").

KFPZ13205-E S

Invalid attribute of indicator variable "aa....aa"

The attribute defined for indicator variable "aa....aa" is invalid.

aa....aa: Indicator variable

S: Ignores this SQL statement; cancels generation of the post source of this source program at this point and executes syntax checking only.

P: Correct the attribute of the indicator variable.

KFPZ13206-E S

Unable to identify variable "aa....aa"

An embedded variable or indicator variable cannot be identified because the specification of the variable is incorrect.

aa....aa: Embedded or indicator variable

S: Aborts generation of the post source and only checks the syntax.

P: Correct the source program so that the embedded or indicator variable can be identified uniquely and re-execute the preprocessor.

KFPZ13207-E S

Length of variable "aa....aa" exceeds bb....bb bytes

The definition length of embedded variable "aa....aa" of CHAR, VARCHAR, NCHAR, NVARCHAR, MCHAR, MVARCHAR, BLOB, CLOB, or BINARY is greater than bb....bb bytes.

aa....aa: Name of embedded variable

bb....bb: Definition length

S: Resumes processing; cancels generation of the post source at this point and executes syntax checking only.

P: Reduce the definition length of the embedded variable to bb....bb bytes or less.

KFPZ13208-E S

Number of variables in "INTO" clause must be equal to output columns

The number of columns to be retrieved does not match the number of embedded variables specified in the INTO clause for setting column data.

S: Converts this SQL statement to the post source as is and resumes processing.

P: Specify the same number of columns and embedded variables.

KFPZ13210-E S

Invalid DECLARE CURSOR statement

If a cursor is used with a data manipulation SQL statement, specify DECLARE CURSOR in the following format:

DECLARE cursor-name CURSOR [WITH HOLD] FOR SELECT statement

In the case of cursor declaration in format 2, the format must be the same for all cursors that use the same SQL statement identifier.

S: Ignores this SQL statement; cancels generation of the post source of this source program at this point and executes syntax checking only.

P: Correct DECLARE CURSOR.

KFPZ13212-E S

Number of SQL exceeds 4095 in a program

More than 4095 SQL statements were used in the program.

S: Terminates processing.

P: Reduce the number of SQL statements to no more than 4095 and re-execute the preprocessor.

KFPZ13214-E S

Number of variables in "USING" clause must be equal to number of input variables in DECLARE CURSOR statement

The number of embedded variables entered with DECLARE CURSOR does not match the number of embedded variables specified in the USING clause.

S: Ignores this SQL statement; cancels generation of the post source of this source program at this point and executes syntax checking only.

P: Specify the same number of embedded variables.

KFPZ13222-E S

Invalid structure of indicator variable "aa....aa" for its corresponding variable

One of the following inconsistencies between an embedded variable and an indicator variable was detected:

An array structure is used for the embedded variable but not for the indicator variable.

The embedded variable has a simple structure, but the indicator variable has an array or repetition structure.

The embedded variable has a repetition structure, but the attribute of the indicator variable is not a repetition structure.

aa....aa: Name of indicator variable

S: Ignores this SQL statement, cancels preprocessing of this source program, and executes syntax checking only.

P: Use the same structure for both the indicator variable and the embedded variable.

KFPZ13223-E S

Number of elements of indicator variable "aa....aa" not equal to number of elements of array or multi-value variable

The number of elements is not the same in an array-type embedded variable and the indicator variable. Or, the number of elements in the indicator variable associated with the embedded variable is inconsistent.

aa....aa: Name of indicator variable

S: Resumes processing.

P: Specify the same number of elements for both the indicator variable and the embedded variable.

KFPZ13224-E S

Update columns not specified in "FOR UPDATE" clause of DECLARE CURSOR statement

A column name that was not specified in the FOR UPDATE clause of the cursor declaration was specified in the SET, ADD, or DELETE clause of the UPDATE statement using the same cursor.

S: Ignores this SQL statement; cancels generation of the post source of this source program at this point and executes syntax checking only.

P: Specify in the FOR UPDATE clause the column name that was specified in the UPDATE statement but omitted from the FOR UPDATE clause of the cursor declaration.

KFPZ13225-I S

Length of variable "aa....aa" exceeds 30000 bytes

The data length of embedded variable "aa....aa" that was used with the row interface for the FIX table exceeded 30,000 bytes.

aa....aa: Name of embedded variable

S: Resumes processing; cancels generation of the post source at this point and executes syntax checking only.

P: Reduce the data length of the embedded variable to no more than 30,000 bytes and re-execute the preprocessor.

KFPZ13226-I S

Invalid attribute "aa....aa" corresponding to row

The data attribute is invalid for embedded variable "aa....aa" for a row.

aa....aa: Name of embedded variable

S: Resumes processing; cancels generation of the post source at this point and executes syntax checking only.

P: Define the correct data attribute for the embedded variable and re-execute the preprocessor.

KFPZ13227-E S

Length of variable "aa....aa" exceeds 2M bytes

Defined embedded variable length exceeded 2 MB.

aa....aa: Name of embedded variable

S: Ignores this SQL statement; cancels generation of the post source of this source program at this point and executes syntax checking only.

P: Correct the embedded variable length to no more than 2 MB and re-execute the preprocessor.

KFPZ13228-E S

Number of elements of array variable "aa....aa" exceeds 4096

Number of embedded variable or indicator variable elements exceeds 4,096.

aa....aa: Name of embedded variable or indicator variable

S: Ignores this SQL statement, cancels preprocessing of this source program, and executes syntax checking only.

P: Reduce the number of embedded variable or indicator variable elements to no more than 4,096.

KFPZ13229-E S

Invalid usage of array variable "aa....aa"

Embedded variables with different structures (array structure and simple structure) are used at the same time. Or, an embedded variable of an array structure is specified together with an embedded variable of a repetition structure.

aa....aa: Name of embedded variable

S: Ignores this SQL statement, cancels preprocessing of this source program, and executes syntax checking only.

P: Use the same structure (array structure or simple structure) for the embedded variables specified in this SQL statement. Or, make the embedded variable used in the SQL statement into a simple structure and a repetition structure.

KFPZ13233-E S

Specified table different from that in DECLARE CURSOR statement

The table specified in this SQL statement differs from the table specified with DECLARE CURSOR.

S: Ignores this SQL statement; cancels generation of the post source of this source program at this point and executes syntax checking only.

P: Correct the SQL statement and re-execute the preprocessor.

KFPZ13234-E S

Specified SQL statement before DECLARE CONNECTION HANDLE SET

When multi-connection facilities are being used with the COBOL language, the only SQL statements you can use before you code DECLARE CONNECTION HANDLE SET are those for allocating or acquiring a connection handle.

S: Terminates processing.

P: Correct the SQL statement, and then re-execute the preprocessor.

KFPZ13236-W S

"Block transfer facility" not applied for cursor "aa....aa", because of FETCH using array variable

Cursor "aa....aa" is used in both FETCH statements, one using an array and the other not using an array. Block transfer cannot be achieved by the FETCH statement without using an array even if the block transfer facility is used during execution.

aa....aa: Cursor name

S: Resumes processing.

P: To use the block transfer facility, correct the UAP and re-execute preprocessing.

KFPZ13511-E S

Error occurred in preprocessor, inf1=aa....aa, inf2=bbbb

An internal conflict occurred in the SQL preprocessor.

aa....aa: Name of the erroneous source file

bbbb: Erroneous location (line number)

S: Terminates processing.

P: Contact the HiRDB administrator.

Action

Contact the customer support center.

KFPZ13570-E S

"aa....aa" option missing

Preprocess option "aa....aa" was not specified.

aa....aa: Preprocess option

S: Terminates processing.

P: Specify the indicated preprocess option and re-execute the preprocessor.

KFPZ13572-E S

Invalid option "aa....aa"

Operand "aa....aa" specified for a preprocess option is invalid.

aa....aa: Invalid operand

S: Terminates processing.

P: Correct the operand value of the preprocess option and re-execute the preprocessor.

KFPZ13574-E S

Invalid keyword "aa....aa"

Operand keyword "aa....aa" is invalid in a preprocess option.

aa....aa: Invalid keyword

S: Terminates processing.

P: Correct the operand keyword of the preprocess option and re-execute the preprocessor.

KFPZ13575-E S

Preprocess option "aa....aa" conflict with "bb....bb"

Preprocess option "aa....aa" cannot be specified concurrently with "bb....bb".

aa....aa: Preprocess option that caused the error

bb....bb: Specified preprocess option

S: Terminates processing.

P: Correct the preprocess option and then re-execute the preprocessor.

KFPZ13576-E S

Error occurred during internal compiler processing "aa....aa"

An error occurred during internal compiler process "aa....aa".

aa....aa: Internal compiler process that caused the error (displays the first 150 bytes if the length exceeds 150 bytes)

S: Terminates processing.

P: See the message output before this message to eliminate the cause of the preprocess option error, and then re-execute the preprocessor.

KFPZ13577-E S

Duplicate option "aa....aa"

Preprocess option "aa....aa" was specified more than once.

aa....aa: Preprocess option that caused the error

S: Terminates processing.

P: Correct the preprocess option and then re-execute the preprocessor.

KFPZ13580-E S

File "aa....aa" not found

Specified UAP source file "aa....aa" was not found.

aa....aa: File name

S: Terminates processing.

P: Correct the file name and re-execute the preprocessor.

KFPZ13581-E E

Code conversion error occurred, return code=aa....aa

An error occurred during character code conversion of the SQL statement embedded in the UAP.

aa....aa: Return code

S: Terminates processing.

P:

If -1 is displayed in the return code:

Detected invalid character encoding from the SQL statement embedded in the UAP source. Check whether JIS X0213 3rd / 4th level kanji encoding text is included in the SQL statement. If JIS X0213 3rd / 4th level kanji encoding text is not included in the SQL statement, make a note of the return code and contact the customer support center.

If a value other than -1 is displayed in the return code:

Make a note of the return code and contact the customer support center.

KFPZ13584-E S

Read error occurred on file "aa....aa",errno=bb

An error occurred while reading the specified UAP source file "aa....aa".

aa....aa: File name

bb: Error number

S: Terminates processing.

P: Check the value of the error indicator, refer to errno.h and to the applicable OS manual to eliminate the cause of the error, then re-execute.

KFPZ13586-E S

Invalid file name file "aa....aa"

Specified file name "aa....aa" is invalid.

aa....aa: File name

S: Terminates processing.

P: Refer to the system message to eliminate the cause of the error, and then re-execute the preprocessor.

KFPZ13600-E S

END DECLARE SECTION missing

End of program was detected before END DECLARE SECTION.

S: Terminates processing.

P: Specify END DECLARE SECTION and re-execute the preprocessor.

KFPZ13601-E S

BEGIN DECLARE SECTION missing

BEGIN DECLARE SECTION is missing.

S: Terminates processing.

P: Specify BEGIN DECLARE SECTION and re-execute the preprocessor.

KFPZ13602-E S

SQL statement not found after EXEC SQL

No SQL statement follows EXEC SQL.

S: Ignores this EXEC SQL and resumes processing.

P: Specify an SQL statement and re-execute the preprocessor.

KFPZ13603-E S

WORKING-STORAGE SECTION missing

WORKING-STORAGE SECTION is missing. Or, a work area required for execution cannot be generated.

S: Terminates processing.

P: Specify WORKING-STORAGE SECTION and re-execute the preprocessor.

KFPZ13610-E S

Incomplete data description

Variable definition is incomplete.

S: Ignores this variable definition statement and resumes processing.

P: Correct the variable definition and re-execute the preprocessor.

KFPZ13611-E S

Incorrect margin used for EXEC SQL

Invalid null character string was detected before or after EXEC SQL.

S: Ignores this SQL statement.

P: Correct the SQL statement and re-execute the preprocessor.

KFPZ13612-E S

Invalid string "aa....aa" before EXEC SQL

Character string "aa....aa" was detected before EXEC SQL.

aa....aa: Character string detected before EXEC SQL

S: Ignores this character string and resumes processing.

P: Either delete the character string preceding EXEC SQL or use two lines to specify the information and re-execute the preprocessor.

KFPZ13635-E S

SQL object not generated

Post source cannot be generated.

S: Terminates processing.

P: Refer to the system message to eliminate the cause of the error, and then re-execute the preprocessor.

KFPZ13706-E S

Open error occurred on file "aa....aa",errno=bb

A file open error occurred.

aa....aa: Name of the file resulting in the error

bb: Error number

S: Resumes processing, but does not output data to the corresponding file.

P: Check the value of the error indicator, refer to errno.h and to the applicable OS manual to eliminate the cause of the error, then re-execute.

KFPZ13707-E S

Write error occurred on file "aa....aa",errno=bb

A file write error occurred.

aa....aa: Name of the file resulting in the error

bb: Error number

S: Terminates processing.

P: Check the value of the error indicator, refer to errno.h and to the applicable OS manual to eliminate the cause of the error, then re-execute.

KFPZ13708-E S

Too long line in user program

The length of a line in the UAP exceeds 32,000 bytes.

S: Terminates processing.

P: Divide the line in which the error occurred into several lines so that the length of each line is less than the maximum length, then re-execute the preprocessor.

KFPZ13709-E S

Open error occurred on file aa....aa

The specified UAP source file could not be opened.

aa....aa: File name

S: Terminates processing.

P: Eliminate the cause of the error, and then retranslate the file.

KFPZ13710-E S

Write error occurred on file aa....aa

An error occurred during writing to a file.

aa....aa: File name

S: Terminates processing.

P: Eliminate the cause of the error, and then retranslate the file.

KFPZ13711-E S

Read error occurred on file "aa....aa"

An error occurred during reading from the specified UAP source file.

aa....aa: File name

S: Terminates processing.

P: Eliminate the cause of the error, and then retranslate the file.

KFPZ13712-E S

Security error occurred on file "aa....aa", reason=bb....bb

A security error occurred during reading from the specified UAP source file.

aa....aa: File name

bb....bb: Reason

S: Terminates processing.

P: Eliminate the cause of the error, and then retranslate the file.

KFPZ13713-E S

Invalid directory "aa....aa"

The specified directory is invalid.

aa....aa: Directory name

S: Terminates processing.

P: Eliminate the cause of the error, and then retranslate the file.

KFPZ13800-E S

Invalid token or identifier aa....aa

An invalid token or identifier was specified.

aa....aa: Invalid token or identifier

S: Continues processing without generating post source.

P: Correct the program, and then re-execute the preprocessor.

KFPZ13801-E S

Too complicated expression: stack overflow

The stack used for interpreting overflowed because an expression was too complex.
Possible causes:

The order of the operator priorities is opposite the order of the description in many locations.

There are too many parenthesized nesting levels.

S: Continues processing without generating post source.

P: Correct the program, and then re-execute the preprocessor.

KFPZ13802-E S

Too complicated struct or union: stack overflow

The stack used for interpreting data overflowed because there were too many levels of structure or shared-item nesting.

S: Continues processing without generating post source.

P: Correct the program, and then re-execute the preprocessor.

KFPZ13803-E S

Illegal declaration aa....aa

An error was found in the declaration of variable aa....aa.

aa....aa: Variable name

S: Continues processing without generating post source.

P: Correct the program, and then re-execute the preprocessor.

KFPZ13804-E S

Illegal combination of type names "aa....aa"

An invalid combination of type specifiers was used.

aa....aa: Character string specified as a type specifier

S: Continues processing without generating post source.

P: Correct the program, and then re-execute the preprocessor.

KFPZ13805-E S

Illegal storage-class specification "aa....aa"

An error was found in the storage class specification.

aa....aa: Character string specified as a memory storage class

S: Continues processing without generating post source.

P: Correct the program, and then re-execute the preprocessor.

KFPZ13806-E S

Illegal type qualifier specification "aa....aa"

An error was found in the type qualifier specification.

aa....aa: Character string specified as a type qualifier

S: Continues processing without generating post source.

P: Correct the program, and then re-execute the preprocessor.

KFPZ13807-E S

Unable to specify SQL statement or SQL TYPE IS declare statement in included file

Declaration of an SQL statement or an SQL TYPE IS type embedded variable cannot be specified in the include file.

S: Continues processing without generating post source.

P: Correct the program, and then re-execute the preprocessor.

KFPZ20002-E A

Memory shortage, inf1=aa....aa, inf2=bbbb

A memory shortage occurred.

aa....aa: Maintenance information 1

bbbb: Maintenance information 2

S: Terminates processing.

P: Terminate unneeded processes, then re-execute.

KFPZ20003-E A

Function sequence error for HiRDB ODBC Driver

An error was found in the sequence of the request codes.

S: Terminates processing.

P: Use the SQLFreeStmt function to release the statement handle being processed or disconnect the server connection.

KFPZ20004-E A

Environment definition error in ODBC.INI,variable=aa....aa, value=bb....bb, datasource=cc....cc

In Windows:
There is an error in the specified value bb....bb of connection information aa....aa for data source cc....cc specified in the Data Source Administrator.
In UNIX:
There is an error in the specified value bb....bb of connection information aa....aa for data source cc....cc specified in odbc.ini.

aa....aa: Connection information in the data source

bb....bb: Value specified in aa....aa

cc....cc: Name of data source

S: Terminates processing.

P: Correct the specified value bb....bb of connection information aa....aa for data source cc....cc.

KFPZ20005-W A

Warning flag (aa....aa) detected

A warning flag for an SQL Communications Area (SQLWARN) was set when HiRDB was accessed.

aa....aa: Warning flag type (SQLWARN1 to SQLWARNF)

S: Terminates processing.

P: See the HiRDB Version 9 SQL Reference or the HiRDB Version 9 UAP Development Guide and take appropriate action.

KFPZ20006-E A

System call error, func=aa....aa, errno=bbbb

An error occurred in the multi-thread library.

aa....aa: Name of the function in which the error occurred

bbbb: Error code that was obtained using the GetLastError function (a Windows error code get function)

S: Terminates processing; returns an error code to the UAP.

P: Correct the cause of the error by referring to the errno.h file and the user OS manual, and then re-execute.

KFPZ20007-E A

HiRDB API error, func=aa....aa, error code=bbbb

An error occurred in a HiRDB API.

aa....aa: Name of the function in which the error occurred

bbbb: Return code from HiRDB API

p_rdb_RC_MEMERR (-70): Insufficient memory

p_rdb_RC_SIMERR (-80): Simultaneous requests under the same connection

S: Terminates processing; returns an error code to the UAP.

P: Correct the cause of the error indicated by the return code and re-execute. Contact the customer support center if a return code other than the previous one is output in bbbb.

KFPZ20999-E A

Internal Error occurred, inf1=aa....aa, inf2=bbbb

An internal contradiction occurred in the ODBC driver.

aa....aa: Maintenance information 1

bbbb: Maintenance information 2

S: Terminates processing.

Action

Record the error message and contact the customer support center.

If a client error log file was output, make a backup of it.

KFPZ22001-E A

Profile aa....aa not found, Java error class name bb....bb

Profile aa....aa could not be found.

aa....aa: Profile name

bb....bb: Error class name

S: Terminates processing.

P: Check for the specified profile, and then re-execute the command.

If this message is output when the profile was found, the profile may be corrupted. In this case, retranslate the UAP, and then re-create the profile.

KFPZ22002-E A

Unable to load profile aa....aa

Profile aa....aa could not be read.

aa....aa: Profile name

S: Terminates processing.

P: Because the profile may be corrupted, re-create the profile, and then re-execute the command. Alternatively, because the profile may not be the profile created by the SQLJ translator in the HiRDB system, re-create the profile using the SQLJ translator of the HiRDB system, and then re-execute the command.

KFPZ22003-E A

Unable to convert data type aa....aa to bb....bb

A combination between which data types cannot be converted was specified.

aa....aa: Database type name

bb....bb: UAP variable type name

S: Terminates processing.

P: Re-evaluate the SQL statement or the UAP, retranslate, and then re-create the profile.

KFPZ22004-E A

Invalid method aa....aa

An invalid method was called.

aa....aa: Method name

S: Terminates processing.

P: aa....aa cannot be used by the HiRDB system. Re-evaluate UAP, and then re-execute the command.

KFPZ22005-E A

Unable to fetch null value into primitive data type

A null value cannot be read as a primitive data type (tried to acquire the null value data using the get-NoNull method).

S: Terminates processing.

P: Re-evaluate the SQL statement or UAP, retranslate, and then re-create the profile.

KFPZ22006-E A

No rows found in single row select

No rows were found in a single-row SELECT statement search.

S: Terminates processing.

P: Re-evaluate the SQL statement, and then re-execute.

KFPZ22007-E A

Cardinality violation in single row select

More than one row was found in a single-row SELECT statement search.

S: Terminates processing.

P: Re-evaluate the SQL statement, and then re-execute the command.

KFPZ22008-E A

Number (aa....aa) of items in iterator or INTO clause unmatch (bb....bb) number of select items

The number of interator fields or the number of embedded variables in the INTO clause do not match the number of selected items.

aa....aa: Number of columns in the ResultSet that the UAP specifies (estimates)

bb....bb: Number of ResultSet columns

S: Terminates processing.

P: Re-evaluate the SQL statement or the iterator declaration, and then re-execute the command.

KFPZ22009-E A

Null connection context

The connection context is a null value.

S: Terminates processing.

P: Re-evaluate the UAP to see if the connection context is generated correctly, and then re-execute the command.

KFPZ22010-E A

Null execution context

The execution context is a null value.

S: Terminates processing.

P: Re-evaluate the UAP to see if the execution context is generated correctly, and then re-execute the command.

KFPZ22011-E A

Null JDBC connection

The JDBC connection object is a null value.

S: Terminates processing.

P: Re-evaluate the UAP to see if the JDBC connection object is generated correctly, and then re-execute the command.

KFPZ22012-E A

Memory shortage,size=aa....aa

A memory shortage occurred during execution of SQLJ.

aa....aa: Area length of the area that could not be allocated (in bytes)

S: Throws the SQLException.

P: If a HiRDB data type (HiRDBCHAR, HiRDBVARCHAR, HiRDBNCHAR, HiRDBNVARCHAR, HiRDBMCHAR, HiRDBMVARCHAR, HiRDBBLOB, HiRDBBINARY, or HiRDBDECIMAL) and byte[] are used, review the length of the specified area. Close any unneeded processes, and then re-execute the command.

KFPZ22013-E A

Failed character convert.

The character code in HiRDB is a character code not available in SQLJ.

S: Throws the SQLException.

P: The following character codes can be used in SQLJ: SJIS (shift JIS kanji code), UJIS (EUC Japanese kanji code) LANG-C (an 8-bit code), and UTF-8. Change the character code for HiRDB, and then re-execute the command.

KFPZ22014-E A

Not found java or HiRDB data classes aa....aa.

A class of the Java data type (Short, Integer, Float, Double, String, or BigDecimal) or of the HiRDB data type (HiRDBCHAR, HiRDBVARCHAR, HiRDBNCHAR, HiRDBNVARCHAR, HiRDBMCHAR, HiRDBMVARCHAR, HiRDBDECIMAL, HiRDBBLOB, or HiRDBBINARY) is not found. Or, a class could not be loaded due to a memory shortage.

aa....aa: Class name

S: Throws the SQLException.

P: Close any unneeded processes. Check to see if SQLJ is properly installed and if the correct class path is set up, and then re-execute the command.

KFPZ22015-E A

Unable to allocate connection handle due to lack of memory.

The allocation of a connection handle failed due to a memory shortage.

S: Throws the SQLException.

P: Close any unneeded processes, and then re-execute the command. Or, check the memory environment for the execution environment, and then re-execute the command.

KFPZ22016-E A

Iterator aa....aa already defined.

When the SQLJ native interface is used, different SQL statements cannot be executed by using the same iterator object.

aa....aa: Iterator object name

S: Terminates processing.

P: Revise the UAP so that the iterator object used in each SELECT statement is unique, and then re-execute the translation process.

KFPZ22017-E A

Internal error occurred in method aa....aa during execution of SQLJ native interface, code=bb....bb.

An internal conflict occurred in the SQLJ native interface.

aa....aa: Name of the method for the SQL native interface in which the error was detected

bb....bb: Internal information

S: Throws the SQLException.

P: Re-execute the command after retranslating the UAP. If the error persists, notify the customer support center.

KFPZ22019-E A

Invalid port number aa....aa for connection to HiRDB server.

The port number of the HiRDB server to be connected to is invalid. Specifiable port numbers are: 5001 through 65535.

aa....aa: Invalid port number

S: Throws the SQLException.

P: Revise the port number, translate the UAP, and then re-execute the command.

KFPZ23000-E S

Parentheses missing

Parentheses or brackets ( ( ), [ ], or { }) were not coded at a required position.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23001-E S

Equal symbol missing

The equal sign (=) was not coded at a required position.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23002-E S

Invalid expression in user program

There is an invalid expression in the program that is not inside a #SQL clause.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23003-E S

Invalid word "aa....aa" in user program

There is an invalid word in the program that is not inside a #SQL clause.

aa....aa: Invalid word

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23004-E S

Invalid named iterator aa....aa

The definition of the named iterator is invalid.

aa....aa: Iterator name

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23005-E S

Duplicate withkey aa....aa

A WITH clause was specified more than once.

aa....aa: Keyword of the WITH statement

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23006-E S

Invalid data type aa....aa

A data type that cannot be used was specified.

aa....aa: Data type name

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23007-E S

Unclosed Parentheses

Parentheses or brackets ( ( ), [ ], { } ) were not closed.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23008-E S

Dot missing

A dot (.) is not coded at a required position.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23009-E S

Duplicate field definition aa....aa

A field was defined more than once.

aa....aa: Field name

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23010-E S

No field in positioned iterator

No field is defined in an unnamed iterator.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23011-E S

Identifier missing

No identifier is coded at a required position.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23012-E S

INTO clause missing

No INTO clause is coded.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23013-E S

Invalid SQLJ statement

An error was found in the SQLJ statement.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23014-E S

Too many execution contexts for one SQL statement

Multiple execution contexts were specified for a single SQL statement.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23015-E S

Too many connection contexts for one SQL statement

Multiple connection contexts were specified for a single SQL statement.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23016-E S

Duplicate class definition aa....aa

The class was defined more than once.

aa....aa: Class name

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23017-E S

Unclosed quotation

A single or double quotation mark pair (' or ") enclosing a character string literal were not closed.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23100-E S

Invalid SQLJ statement declared

The description of the SQLJ statement is invalid.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23101-E S

Unable to identify class aa....aa

Class aa....aa could not be identified.

aa....aa: Class name

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23102-E S

Not Array type aa....aa

aa....aa is not an array type.

aa....aa: Data type name

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23103-E S

Unable to identify constructor aa....aa

A constructor could not be identified.

aa....aa: Constructor name

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23104-E S

Unable to identify field aa....aa

Field aa....aa could not be identified.

aa....aa: Field name

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23105-E S

Unable to identify method aa....aa

A method could not be identified.

aa....aa: Method name

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23106-E S

Numeric operands required

The operand type is not numeric.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23107-E S

Array index requires numeric type

A data type other than numeric is specified in the array subscript.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23108-E S

Invalid data type of operand for cast operator

An invalid data type was specified in the operand of the cast operator.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23109-E S

Invalid data type of operand for equality operator

The data type in the operand for the equality operator is invalid.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23110-E S

Invalid data type of operand for boolean or numeric operator

An invalid data type for a numeric operator or Boolean operator is specified in the operand.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23111-E S

Invalid data type of operand for boolean operator

An invalid data type for a Boolean operator is specified in the operand.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23112-E S

Invalid data type of operand for comparison operator

An invalid data type for a comparison operator is specified in the operand.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23113-E S

Invalid data type of operand for complement operator

An invalid data type for a complement operator is specified in the operand.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23114-E S

Invalid data type of operand for conditional operator

An invalid data type for the conditional operator is specified in the operand.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23116-E S

Constructor undefined

The constructor was not defined.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23117-E S

Field aa....aa not accessible

A field could not be accessed.

aa....aa: Field name

S: Terminates processing.

P: Re-evaluate the program, taking note of the variable qualifier, and then preprocess again.

KFPZ23118-E S

Invalid data type of operand for increment/decrement operator

An invalid data type was specified in an increment operator or a decrement operator operand.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23119-E S

Invalid data type of operand for instanceof operator

An invalid data type was specified in an instanceof operator operand.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23121-E S

Method not accessible

An invalid method is specified.

S: Terminates processing.

P: Re-evaluate the program, taking note of the method qualifier, and then preprocess again.

KFPZ23122-E S

Method aa....aa undefined

A method is not defined.

aa....aa: Method name

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23123-E S

Invalid identifier aa....aa

An invalid identifier was found.

aa....aa: Identifier

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23124-E S

Invalid data type of operand for negation operator

The data type of a negation operator operand is invalid.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23125-E S

Invalid data type of operand for shift operator

The data type of a shift operator operand is invalid.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23126-E S

Invalid data type of operand for sign operator

The data type of a sign operator operand is invalid.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23127-E S

Token aa....aa unexpected

An unexpected token was coded.

aa....aa: Token

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23128-E S

Undefined identifier aa....aa

An identifier not specified in the system was specified.

aa....aa: Identifier

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23130-E S

Undefined target type in cast expression aa....aa

The data type that a cast expression targets is undefined.

aa....aa: Name of data type and class name to cast

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23132-E S

Initiarization lists unexpected

An initial value is described in an invalid location.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23136-E S

Invalid SQLJ declaration

The SQLJ declaration statement is invalid.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23137-E S

Invalid SQLJ Iterator declaration

The declaration of the iterator is invalid.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23138-E S

Incomplete file

The UAP file is incomplete.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23139-E S

Invalid expression

The #SQL clause expression is invalid.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23140-E S

Invalid IN/OUT mode for INTO variables

An error was found in the specification of the IN/OUT mode of the embedded variable specified in the INTO clause.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23141-E S

Incomplete SQLJ statement

The SQLJ statement is incomplete.

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23142-E S

Invalid token aa....aa

An invalid token was coded.

aa....aa: Word

S: Terminates processing.

P: Correct the program, and then preprocess again.

KFPZ23143-E A

Invalid data length aa....aa

The length of a specified area is invalid.

aa....aa: Length of a specified area

S: Throws the SQLException.

P: Review the length, precision, and scale of the area specified in a HiRDB data type (HiRDBCHAR, HiRDBVARCHAR, HiRDBNCHAR, HiRDBNVARCHAR, HiRDBMCHAR, HiRDBMVARCHAR, HiRDBBLOB, HiRDBBINARY, or HiRDBDECIMAL).

KFPZ24000-E A

Invalid CommandTimeout property, please specify zero or more.

A negative value is assigned to the CommandTimeout property of the HiRDBCommand class.

S: Terminates processing.

P: Specify a value greater than or equal to 0.

KFPZ24001-E A

Invalid Connection property.

One of the following methods is executed in the Connection property of the HiRDBCommand class without assigning a HiRDBConnection class object: ExecuteNonQuery, ExecuteReader, ExecuteScalar, or Prepare method.

S: Terminates processing.

P: Assign the Connection property, and then execute the command.

KFPZ24002-E A

Prepare method performed before connection opened.

The Prepare method of the HiRDBCommand class is executed when the Open method of the HiRDBConnection class is not executed.

S: Terminates processing.

P: Open the connection to make it available.

KFPZ24003-E A

Invalid value of ArraySize property.

The argument ArraySize of the ExecuteNonQuery method in the HiRDBCommand class is 0 or less. Or, the argument value does not match the number of array data points assigned to the Value property of the HiRDBParameter class.

S: Terminates processing.

P: Make sure that ArraySize matches the number of array elements.

KFPZ24004-E A

Method for execution performed before connection opened.

One of the following methods in the HiRDBCommand class is executed when the Open method of the HiRDBConnection is not executed: ExecuteNonQuery, ExecuteReader, or ExecuteScalar method.

S: Terminates processing.

P: Open the connection to make it available.

KFPZ24005-E A

Invalid CommandText property.

When the CommandText property of the HiRDBCommand class is empty, one of the following methods in the class is being executed: Prepare, ExecuteNonQuery, ExecuteReader, or ExecuteScalar method.

S: Terminates processing.

P: Assign the SQL statement to be executed to the CommandText property.

KFPZ24006-E A

Invalid Transaction property.

When a transaction is being executed and the Transaction property in the HiRDBCommand class is null, one of the following methods in the class is being executed: ExecuteNonQuery, ExecuteReader, or ExecuteScalar method.

S: Terminates processing.

P: Set the Transaction property.

KFPZ24007-E A

Unsupported value specified for property of HiRDBCommand class.

When ReturnValue is specified in the Direction property of the HiRDBParameter class, one of the following methods in the HiRDBCommand class is being executed: ExecuteNonQuery, ExecuteReader, ExecuteScalar, or Prepare method. Or, Both/FirstReturnedRecord is specified in the UpdateRowSource property.

S: Terminates processing.

P: This value is not supported; another value should be specified.

KFPZ24008-E A

Unable to change ConnectionString property during connection opened.

When a connection is on, the ConnectionString property of the HiRDBConnection class is modified.

S: Terminates processing.

P: The property should be assigned when the connection is closed.

KFPZ24009-E A

Unable to change Pooling property during connection opened.

When a connection is on, the Pooling property of the HiRDBConnection class is modified.

S: Terminates processing.

P: The property should be assigned when the connection is closed.

KFPZ24010-E A

Unable to change LifeTime property during connection opened.

When a connection is on, the LifeTime property of the HiRDBConnection class is modified.

S: Terminates processing.

P: The property should be assigned when the connection is closed.

KFPZ24011-E A

BeginTransaction method performed before connection opened.

The BeginTransaction method of the HiRDBConnection class is being executed when the Open method of the HiRDBConnection class is not executed (when the connection is closed).

S: Terminates processing.

P: Open the connection to make it available.

KFPZ24012-E A

Transaction already executed.

The BeginTransaction method of the HiRDBConnection class is being executed when the transaction has already been executed.

S: Terminates processing.

P: The transaction has already been executed; the method should not be executed (parallel transactions cannot be used).

KFPZ24013-E A

ChangeDatabase method performed before connection opened.

The ChangeDatabase method of the HiRDBConnection class is being executed when the Open method of the HiRDBConnection class is not executed (when the connection is closed).

S: Terminates processing.

P: Open a connection to make it available (the ChangeDatabase method cannot be used).

KFPZ24014-E A

Connection already opened.

The Open method of the HiRDBConnection class is being executed when the connection is already open.

S: Terminates processing.

P: The connection is already open; the method should not be executed.

KFPZ24015-E A

SchemaTable method performed before record opened.

The GetSchemaTable method is executed when the IsClosed property of the HiRDBDataReader class is true.

S: Terminates processing.

P: Execute the HiRDBDataReader method of the HiRDBCommand class, open the record, and then execute the method.

KFPZ24016-E A

NextResult method performed before record opened.

The NextResult method is executed when the IsClosed property of the HiRDBDataReader class is true.

S: Terminates processing.

P: Execute the HiRDBDataReader method of the HiRDBCommand class, open the record, and then execute the method.

KFPZ24017-E A

Read method performed before record opened.

The Read method is executed when the IsClosed property of the HiRDBDataReader class is true.

S: Terminates processing.

P: Execute the ExecuteReader method of the HiRDBCommand class, open the record, and then execute the method.

KFPZ24018-E A

Unable to specify method for cast due to null value.

An attempt is made to acquire null data by using one of the following methods in the HiRDBDataReader class: GetBoolean, GetByte, GetBytes, GetChar, GetChars, GetDateTime, GetDecimal, GetDouble, GetFloat, GetInt16, GetInt32, GetInt64, or GetString method.

S: Terminates processing.

P: Acquire null data by using the GetValue method of the HiRDBDataReader class.

KFPZ24019-E A

Invalid value for column number of methods in HiRDBDataReader class.

Because an invalid column number has been used, one of the following methods in the HiRDBDataReader class is being executed: GetBoolean, GetByte, GetBytes, GetChar, GetChars, GetDataTypeName, GetDateTime, GetDecimal, GetDouble, GetFieldType, GetFloat, GetInt16, GetInt32, GetInt64, GetName, GetString, GetValue, IsDBNull, or GetFieldArrayCount method.

S: Terminates processing.

P: Check the column number, and execute the method.

KFPZ24020-E A

Invalid column name specified in GetOrdinal method.

The GetOrdinal method of the HiRDBDataReader class is being executed by specifying an invalid column name.

S: Terminates processing.

P: Check the column name, and execute the method.

KFPZ24021-E A

Invalid parameter name specified in method of HiRDBParameterCollection class.

Either the IndexOf or RemoveAt method of the HiRDBParameterCollection class is executed by specifying an invalid parameter name.

S: Terminates processing.

P: Check the parameter name, and execute the method.

KFPZ24022-E A

Unable to perform Commit method or Rollback method, because transaction already terminated.

Either the Commit or Rollback method of the HiRDBTransaction class is being executed when the transaction is complete.

S: Terminates processing.

P: The transaction is already complete; the method should not be executed.

KFPZ24023-E A

Invalid DataAdapter property.

When the DataAdapter property of the HiRDBCommandBuilder class is not yet set, one of the following methods is executed: GetDeleteCommand, GetInsertCommand, GetUpdateCommand, or RefreshSchema method.

S: Terminates processing.

P: Set and execute the DataAdapter property.

KFPZ24024-E A

Invalid SelectCommand property of HiRDBDataAdapter class object.

When the SelectCommand property of the DataAdapter object of the HiRDBCommandBuilder class is not yet set, one of the following methods is executed: GetDeleteCommand, GetInsertCommand, GetUpdateCommand, or RefreshSchema method.

S: Terminates processing.

P: Set the SelectCommand property of the DataAdapter object, and then execute the method.

KFPZ24025-E A

Unable to specify Null for specified property or argument.

null is specified in a property, constructor argument, or method argument for which null cannot be specified.

S: Terminates processing.

P: Specify a non-null value.

KFPZ24026-E A

Specified value not convertible into HiRDB Type aa....aa

A value that cannot be converted into the type specified in the HiRDBType property of the aa....aa-th HiRDBParameter class is specified in the Value property.

aa....aa: Parameter number

S: Terminates processing.

P: In the Value property, specify either the value of a convertible type or the value of the type specified in the HiRDBType property.

KFPZ24027-E A

Missing Specification of table name in HiRDBDataAdapter.Update method.

No table name is specified in HiRDBDataAdapter.Update method processing.

S: Terminates processing.

P: Specify a table name in HiRDBDataAdapter.Update method processing.

KFPZ24028-E A

Invalid value for Size property in HiRDBParameter class.

An invalid value was set for the Size property of the HiRDBParameter class.

S: Terminates processing.

P: Set a valid value for the Size property.

KFPZ24029-E A

Invalid value,property=aa....aa,value=bb....bb.

There is an invalid property specification value.

aa....aa: Property name

bb....bb: Property specification value

S: Terminates processing.

P: Revise the property specification value.

KFPZ24031-E A

aa....aa closed.

Processing cannot be accepted because the aa....aa class instance is already closed.

aa....aa: Class name

S: Terminates processing.

P: Regenerate the instance, and then re-execute.

KFPZ24033-E A

Invalid cursor position,reason=aa....aa.

Processing cannot be accepted because the cursor is not in an enabled row.

aa....aa: One of the following character strings is displayed.

BEFORE FIRST ROW: The cursor is before the first row.

AFTER LAST ROW: The cursor is after the last row.

S: Terminates processing.

P: Position the cursor in an enabled row, and then re-execute.

KFPZ24034-E A

Invalid argument,number=aa....aa,value=bb....bb,method=cc....cc.

An argument value is invalid.

aa....aa: Argument sequence number (1, 2, ..., n)

bb....bb: Argument value

cc....cc: Method name

S: Terminates processing.

P: Revise the argument value, and then re-execute.

KFPZ24036-E A

Unsupported data type exists in update table, datacode=aa....aa.

There is a column in the table to be updated whose data type is not supported by the HiRDB.NET data provider.

aa....aa: Data code

S: Terminates processing.

P: Check the data types that are supported by HiRDB.NET data provider, and revise the table definitions. For details about HiRDB.NET data provider data types, see the HiRDB Version 9 UAP Development Guide.

KFPZ24039-E A

Unable to generate SQL command automatically, reason=aa....aa.

Could not automatically generate the updated SQL statement by way of the HiRDBCommandBuilder.

aa....aa: One of the following is output as a reason.

INVALID SERVER VERSION: The HiRDB server version is earlier than the 08-04 version.

INVALID SELECTCOMMAND: The retrieval SQL statement specified in the DataAdapter property SelectCommand does not meet the conditions for automatically generating an updated SQL statement in the HiRDBCommandBuilder.

S: Terminates processing.

P: Correct the error and re-execute.

For INVALID SERVER VERSION, use the 08-04 or more recent version of the HiRDB server.

For INVALID SELECTCOMMAND, revise the retrieval SQL statement specified in the DataAdapter property SelectCommand. For details about DataAdapter properties, see the HiRDB Version 9 UAP Development Guide.

KFPZ24100-E A

Invalid connection string.

An invalid connection string argument was specified. Or, the required connection string argument is not specified.

S: Terminates processing.

P: Check the connection string, and then execute the command.

KFPZ24101-E A

Unable to allocate connection handle due to lack of memory.

Allocation of a connection handle failed due to a memory shortage.

S: Terminates processing.

P: Check the available memory for the execution environment.

KFPZ24102-E A

Unable to release connection handle due to lack of memory.

Release of a connection handle failed due to a memory shortage.

S: Terminates processing.

P: Check the available memory for the execution environment.

KFPZ24103-E A

Connection handle not allocated.

A connection handle is not allocated.

S: Terminates processing.

P: Allocate a connection handle.

KFPZ24104-E A

Error occurred in environment variable for connection.

An error occurred when an environment variable was being set.

S: Terminates processing.

P: Check the environment variable, and then execute the command.

KFPZ24105-E A

Too many SQL prepared and executed concurrently.

The number of sections in which HiRDB.NET Data Provider is executing SQL statements (the number of executing SQL statements) has exceeded the maximum allowable number (4,090).

S: Terminates processing.

P: For the SQL statements that have terminated, release their HiRDBCommand objects and HiRDBDataReader objects. After these objects are released, the corresponding sections can be reused. HiRDBCommand objects can be released using the Dispose() method, and HiRDBDataReader objects can be released using the Close() method.

KFPZ24106-E A

Invalid value for input ? parameter of DATETIME or INTERVAL data type.

The format of the value specified in the input ? parameter of the date, time, date interval, or time interval type is invalid.

S: Terminates processing.

P: Specify a valid character string representation value for a specified date, time, date interval, or time interval type.

KFPZ24107-E A

Overflow error occurred for input ? parameter of DECIMAL or DATETIME or INTERVAL data type.

An overflow occurred during the type conversion of the value of the input ? parameter of Decimal, date, time, date interval, or time interval type.

S: Terminates processing.

P: Assign the value of a date, time, date interval, or time interval type with an appropriate character string representation.

KFPZ24108-E A

Unknown type specified in DbType property.

An unavailable data type was specified in the DbType property of the HiRDBParameter class.

S: Terminates processing.

P: The type should be checked and assigned.

KFPZ24109-E A

Unsupported type specified in DbType property.

One of the following types is specified in the DbType property of the HiRDBParameter class: Boolean, Currency, Guid, or VarNumeric.

S: Terminates processing.

P: These types, which are unsupported, cannot be used; another value should be specified.

KFPZ24110-E A

Unmappable character appeared in conversion to UTF8.

Character codes that cannot be converted to UTF8 codes were included.

S: Terminates processing.

P: Use UTF8 characters.

KFPZ30001-I S

Usage: pdtrcmgr -d pathname [-b|-e] [-k { [s] [u] [p] [r]|[a] }] [-n uapname] [-s size] [-o]

Displays the specification format of the pdtrcmgr trace acquisition command.

S: Continues processing.

P: Specify the pdtrcmgr command correctly and re-execute.

KFPZ30002-E S

Command option error, option=-a, reason=bb....bb

Option specification is invalid.

a: Option specified incorrectly

bb....bb: Reason:

NOT TARGET: No target argument exists.

OUT OF RANGE: Specifiable range has been exceeded.

NO OPTION: Required option is missing.

INVALID CHAR: Invalid character is used.

ALREADY USED: Already being used

S: Terminates processing.

P: Correct the error and re-execute.

KFPZ30003-E S

End Request failed, pathname=aa....aa, bb....bb

The SQL trace output request cannot be stopped because the files used by the system could not be deleted.

aa....aa: Path name with the error (last 30 bytes only if the name is longer than 30 bytes)

bb....bb: Error cause or error number:

{ reason=cc....cc |errno=dd....dd }

cc....cc: Error cause:

INVALID PATH: Invalid path name

PERMISSION DENIED: Permission error

dd....dd: Error number

S: Terminates processing.

P: Correct the error and re-execute.

If the error cause is INVALID PATH, the specified path name may be incorrect or a trace acquisition request may have not been entered.

If the error cause is PERMISSION DENIED, the permission for the specified path may not be valid.

If an error number is displayed, refer to errno.h.

KFPZ30004-E S

Begin request failed, pathname=aa....aa, func=bb....bb, cc....cc

The SQL trace output request cannot be started because files to be used by the system could not be created (updated).

aa....aa: Path name with the error (last 30 bytes only if the name is longer than 30 bytes)

bb....bb: Name of the function in which the error occurred:

{ fopen|fclose }

cc....cc: Error cause or error number:

{ reason=dd....dd |errno=ee....ee }

dd....dd: Error cause:

INVALID PATH: Invalid path name

PERMISSION DENIED: Permission error

FILE TABLE OVERFLOW: Overflow

TOO MANY OPEN FILES: Open control over

ee....ee: Error number

S: Terminates processing.

P: Correct the error and re-execute.

If the error cause is INVALID PATH, the specified path name may be incorrect or a trace acquisition request may have not been entered.

If the error cause is PERMISSION DENIED, the permission for the specified path may not be valid.

If an error number is displayed, refer to errno.h.

KFPZ30005-E S

Trace information file error, pathname=aa....aa, func=bb....bb, errno=cc....cc

The SQL trace cannot be output because the trace information file (.#pdtrc) cannot be opened or closed.

aa....aa: Path name with the error (last 30 bytes only if the name is longer than 30 bytes)

bb....bb: Name of the function in which the error occurred: {fopen|fclose}

cc....cc: Error number

S: Terminates processing.

P: Correct the error based on the path name, function name, and error number, and then re-execute. For the error numbers, refer to errno.h.

KFPZ40001-I E

Usage:pdclttrc [-s server_name] [-p process_id] [-e] [-l PDUAPREPLVL_values] [-m ?parameter_max_data_size] [-n number_of_output_operation_codes] [-o sqltrace_file_size]

A pdclttrc command option is specified in invalid format.

S: Terminates processing.

O: Revise the option specification format, and then re-execute the command.

KFPZ40002-W S

-l option ignored, because server_process performing memory communication, server_name=aa....aa, process_id=bb....bb

The server process is conducting memory communications; any specification of the -1 option is ignored.

aa....aa: Server name

bb....bb: Server process ID

S: Continues processing.

KFPZ40003-E S

Server_process already executed for pdclttrc command, server_name=aa....aa, process_id=bb....bb

The server process is already dynamically acquiring SQL traces.

aa....aa: Server name

bb....bb: Server process ID

S: Terminates processing.

O: To re-execute, terminate the acquisition of SQL traces.

KFPZ40004-E S

Server_process not connected with client, server_name=aa....aa, process_id=bb....bb

The server process is not connected to a client.

aa....aa: Server name

bb....bb: Server process ID

S: Terminates processing.

O: Specify a server process that is connected to a client.

KFPZ40005-E E

Specified server_process not exist, server_name=aa....aa, process_id=bb....bb

The specified server process does not exist.

aa....aa: Server name

bb....bb: Server process ID

S: Terminates processing.

O: Specify a server process that exists.

3. ABORT Codes

This chapter explains the causes of ABORT codes (abnormal termination cause codes) and the actions to be taken.

Organization of this chapter

3.1 ABORT Codes

3.1 ABORT Codes

It includes the following lists of abort codes:

Table 3-1 ABORT codes (PaXXXXX)

Table 3-2 ABORT codes (PbXXXXX)

Table 3-3 ABORT codes (PdXXXXX)

Table 3-4 ABORT codes (PeXXXXX)

Table 3-5 ABORT codes (PhXXXXX)

Table 3-6 ABORT codes (PkXXXXX)

Table 3-7 ABORT codes (PoXXXXX)

Table 3-8 ABORT codes (PrXXXXX)

Table 3-9 ABORT codes (PsXXXXX)

Table 3-10 ABORT codes (PtXXXXX)

Table 3-11 ABORT codes (PuXXXXX)

Table 3-12 ABORT codes (PxXXXXX)

Table 3-13 ABORT codes (PyXXXXX)

Table 3-14 ABORT codes (PiXXXXX)

Table 3-15 ABORT codes (EhiXXXXX)

Table 3-16 ABORT codes (EhmXXXXX)

Table 3-17 ABORT codes (EhxXXXXX)

Table 3-1 ABORT codes (PaXXXXX)

ABORT Code
Cause
Action

Pab1001
Allocation of combuf communication field failed for one of the following reasons:

Allocation of communication field or header failed.

Requested size was invalid.

Back up all files in %PDDIR%\spool and contact the customer support center.

Pab1005
Value returned from the dic manager was invalid for because the table ID lock failed.

Pab1113
Transmission of SQL object transfer request information failed during normal communication.
Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute. This error may occur when the workload at the destination (FES, BES, DIC) is high. In such a case, reduce the workload at the destination.
This abort code can also be generated by an SQL object buffer shortage, in which case increase the value of the pd_sql_object_cache_size operand of the system definition or server definition. This error can also occur if the execution of the pdcancel command eliminates the transmission destination server process.

Pab1114
Reception of SQL object transfer request information failed during normal communication.
Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute. This error may occur when the workload at the destination (FES) is high. In such a case, reduce the workload at the destination.

Pab1500
An invalid object was transferred from the front-end server. When HiRDB is operated in a multi-FES environment, this error may occur if the total number of front-end server processes is greater than the number of individual back-end server processes (value of pd_max_bes_process in server definition).
Back up all files in %PDDIR%\spool and contact the customer support center.

Pab1501
SQL object transfer failed.

Transaction was terminated at the front-end server due to an error.

Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute.

Pab1502
A conflict was detected during SQL object transfer processing using the routine.
Back up all files in %PDDIR%\spool and contact the customer support center.

Pab2001
Thread suspense lock failed.

Pab2002
Release of thread suspense lock failed.

Pab2003
Resource lock failed.
Correct the error that occurred in object creation and object transfer processing and re-execute.

Pab2004
Release of resource lock failed.
Back up all files in %PDDIR%\spool and contact the customer support center.

Pab2010
Lock control on SQL object management information using the routine failed.

Pab2011
Release of lock control on SQL object management information using the routine failed.

Pab2012
Lock control on SQL object get management information using the routine failed.
Check the error cause from the error message that was output before the processing was aborted, take corrective action, and then re-execute.

Pab2013
Release of lock control on SQL object get management information using the routine failed.
Back up all files in %PDDIR%\spool and contact the customer support center.

Pab2350
Length of module requested for release is invalid.

Pab2351
Address of module requested for release is invalid.

Pab2352
Information returned from dic to sqa is invalid.

Pab2353
Length of module requested for allocation is invalid.

Pab2354
An SQL object is invalid.

Pac1001
A connect request was rejected by the dictionary manager, but rpc chain cannot be disconnected.

Pac2001
Return code of dbh function call is invalid. (p_f_dbh_drop_list)

Pac2004
0 was specified for pd_max_access_tables.

Pac2008
Lock control on user management information failed.
Check the error cause from the error message that was output before processing was aborted, take corrective action, and then re-execute.

Pac2009
Release of lock control on user management information failed.
Back up all files in %PDDIR%\spool and contact the customer support center.

Pac2050
Output outhead length is invalid for RPC from client.

Pac2051
SQL to be executed without creating an SQL object (definition SQL) has an invalid SQL object.

Pac2052
Requested static compilation has the same section number as the already compiled dynamic SQL. Or, requested dynamic compilation has the same section number as the already compiled static SQL.

Pac2053
Number of p_code's obtained from optimization processing (zipsncls) is invalid ( 0).

Pac2054
Parameter is invalid in a statistics log acquisition request (log address is 0, log size is 0).

Pac2055
Process private area necessary for SQL execution cannot be allocated.
Reduce the number of resident processes in the server for which this message was output.

Pac2056
Input data format is invalid for RPC from client (offset count is 0, sqlioa offset is 0).
Back up all files in %PDDIR%\spool and contact the customer support center.

Pac2352
Return code of DIC function call is invalid. (p_f_dic_freecache)

Pac2354
Check the error message that was output before the abort (the error indicated in this message) occurred. If an error message was not output before the abort, the following causes can be suspected:

When a UAP under OLTP is the client and the multi-connection facility is used in a HiRDB server that does not support the multi-connection facility:
within a single transaction branch under OLTP, an SQL statement was executed using different connection handles on the same HiRDB.

The upper limit on the number of transactions that can be executed concurrently was exceeded. It is possible that transactions that cannot be committed or rolled back in the system are waiting for settlement.

A temporary memory shortage occurred.

The upper limit on the number of files that can be opened concurrently has been reached.

Check the cause of the problem based on the error message that was output before the abort. If an error message was not output before the abort, take one of the following actions:

Within a single transaction branch under OLTP, different connection handles cannot be used on the same HiRDB. One of the following actions should be taken:
Check to see whether the HiRDB server supports the multi-connection facility.
Check the UAP processing method.

Execute the pdls -d trn command. If a transaction with a value greater than or equal to pd_max_users is indicated, wait awhile, and then re-execute the command. To provide for the possibility that the error cannot be recovered, prepare to settle the transactions by using either the pdcmt or pdrbk command.

Wait awhile, and then re-execute the command.

Review the upper limit on the number of files that can be opened in a process. Also review the kernel parameter if necessary. If the problem persists after the above actions are taken, save the information to be acquired in the event of an error, and contact the customer support center. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.

Pac2355
Internal conflict occurred in the controller.
Back up all files in %PDDIR%\spool and contact the customer support center.

Pac2358
Shared memory size (module pool) to be allocated is invalid.

Pac2359
Characters type code is invalid.

Pac2360
Execution with a section number not found in the object was requested during stored procedure execution.

Pac2361
An operation code that cannot be executed was requested during stored procedure execution.

Pac2362
A section that cannot be executed was found in a stored procedure object.

Pac2363
Transaction request is invalid.

Pac2364
UAP client libraries forming a global transaction have different versions.
Match the versions of the UAP client libraries forming the global transaction.

Pac2365
A process private area required for SQL execution cannot be allocated, or memory is insufficient.
Check the load on the system and re-execute the UAP. Alternatively, re-estimate memory.

Pac2366
An error was returned because a system error occurred during reception processing (front-end server) of the trigger execution request.
Check the error cause from the error message that was output before processing was aborted, take corrective action, and then re-execute.
This error may also occur when there is a heavy load on the transmission source (back-end server). If this is the case, reduce the load on the transmission source.

Pac2367
Transmission processing of the trigger execution result returned an error. Possible causes are that either the transmission destination server (back-end server) or the unit is down, or that the system could not respond due to a heavy load.
Check the error cause from the error message that was output before processing was aborted, take corrective action, and then re-execute.

Pac2368
A trigger execution request failed.

An error occurred; then the front-end server terminated the transaction.

Check the error cause from the error message that was output before processing was aborted, take corrective action, and then re-execute.

Pac2369
Message editing failed when setting SQLCA.
Contact the customer support center.

Pac2370
Send processing to the client returned an error. The client at the destination has either shut down or cannot respond due to a heavy load.
Check the cause of the error from the error message that was output before the process aborted, take corrective action, and then re-execute.

Pac2501
Attempt was made to execute Auto Commit in the XA environment.
Back up all files in %PDDIR%\spool and contact the customer support center

Pac2502
Invalid prepare request was issued from client.

Pae2250
Argument in high-order module is invalid during SQL object execution.
Back up all files in %PDDIR%\spool and contact the customer support center. If HiRDB does not restart automatically, restart it manually.

Pae2251
System error occurred during SQL object execution (invalid return code).

Pae2252
SQL object is invalid.

Pae2253
Return code of a low-order module is invalid during SQL object execution.

Pae2255
System error occurred during SQL object execution (invalid internal code).

Pae2257
Memory shortage or system error occurred during SQL object execution (internal conflict).
If a memory shortage occurred, wait a while and then re-execute. Otherwise, contact the customer support center.

Pae2258
Internal system contradiction was detected during SQL object execution.
Contact the customer support center.

Pae2259
Allocation of system private area failed or a memory shortage occurred.
Check the system load and re-execute the UAP. Or, re-estimate the memory size.

Pae2354
Return code of SYSM function call is invalid.
Check the error cause from the error message that was output before processing was aborted, take corrective action, and then re-execute. If an error message is output, save the files under %PDDIR%\spool, %PDDIR%\conf, and %PDDIR%\tmp, save the event log (in UNIX, syslogfile), and contact the customer support center.

Pae2355
Null characters are not included in the C-language character string received from the C routine.
The length of the character string may have exceeded the SQL data type definition length that was specified when the routine was defined.
Check whether a character string exceeding the definition length has been written.
In addition, append null characters to the end of the character string when a character string type value is returned.

Pae3001
Reply text receive processing resulted in an error.
Contact the customer support center.

Pae3002
HiRDB-specified information is missing from reply text.

Pae3003
Unexpected reply text was received from the server.

Pae3004
The results of SQL statements executed between HiRDB servers were not received within the specified PDCWAITTIME. A server-to-server communication error may have occurred.
HiRDB executes multiple server-to-server communications or database accesses for a single request from a client. Because the client monitors the cumulative processing time using the value of PDCWAITTIME, it is usually the client that first detects a timeout and sends a recovery instruction to the server. If the client is unable to send a recovery instruction due to a communication error between the client and server, the server also detects the error.
Check the error cause from the OS and HiRDB error messages that were displayed prior to the abort, take appropriate action, then re-execute.

Pae3005
Timeout occurred in a HiRDB/Parallel Server while a back-end server or dictionary server was waiting for an SQL execution request library to be received from a front-end server.
An error, such as a memory shortage, may have occurred in the unit in which the back-end server process or dictionary server process is located, making SQL execution impossible. Determine the cause of the error in the applicable unit, and re-execute after taking appropriate action.
Until the action is completed, keep intact the files under %PDDIR%\spool, \conf, and \tmp.

Pae3010
Retrieval result send processing resulted in an error. The destination server or unit may be shut down or unable to reply due to high workload.
Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute.

Pae3100
An error occurred during analysis of the following operands:

pd_max_list_users

pd_max_list_count

pd_java_runtimepath

pd_java_libpath

pd_sql_send_buff_size

Save the files under %PDDIR%\spool, %PDDIR%\conf, and %PDDIR%\tmp, save the event log (in UNIX, syslogfile), and contact the customer support center.

Pae3101
Shared memory could not be released while processing an error that had occurred at server startup or while stopping the server.

Pae3110
An unrecoverable error occurred during thread lock.

Pae4000
Either of the following possibilities should be investigated:

The sending of an abstract data type get request returned an error. Possibly the destination server or unit is down or unable to respond due to high load.

An internal conflict occurred in the operation for the abstract data type.

Check the error cause from the error message that was output before processing was aborted, take corrective action, and then re-execute. If the problem is other than a transmission error, contact the customer support center.

Pae4001
The information returned from the plug-in implementation function is invalid.
Contact the customer support center. For the name of the plug-in implementation function in which the error occurred, see the preceding error message.

Pae5000
An unrecoverable error occurred during a transaction commit or rollback.
Save the files under %PDDIR%\spool, %PDDIR%\conf, and %PDDIR%\tmp, save the event log (in UNIX, syslogfile), and contact the customer support center.

Pag1660
Invalid data type was detected during data comparison.
Back up all files in %PDDIR%\spool and contact the customer support center. If HiRDB does not restart automatically, restart it manually.

Pag1670
Internal system conflict was detected during regular expression comparison.

Pag1671
Internal system conflict was detected during regular expression comparison.

Pag1672
Internal system conflict was detected during regular expression comparison.

Pag1680
Internal system conflict was detected during data conversion.

Pao0002
Internal conflict occurred during optimization processing.
Back up all files in %PDDIR%\spool and contact the customer support center.

Pao2001
SQL object was invalid.
Back up all files in %PDDIR%\spool and contact the customer support center.

Pao2002
Internal conflict occurred during optimization processing at the time of execution.

Pao3001
An internal conflict occurred while the definition file was being read.
Back up all files in %PDDIR%\spool and %PDDIR%\conf, and contact the customer support center.

Pao3002
A memory shortage occurred while the definition file was being read.
Take corrective action as indicated by the memory shortage error message output immediately before this message, and restart the unit that shut down.

Pap2255
There is not enough stack data area.
Contact the customer support center.

Par2400
Attempt was made to create a free chain in an area other than the control block area.
Back up all files in %PDDIR%\spool and contact the customer support center.

Par2401
Conflict occurred while creating a free chain for a control block.

Par2402
Attempt was made to release a control block that was already released.

Par2410
Terminated abnormally.
Back up all files in %PDDIR%\spool and contact the customer support center. If HiRDB does not restart automatically, restart it manually.

Par2412
Detachment of main thread failed in the same section.
Back up all files in %PDDIR%\spool and contact the customer support center.

Par2413
Drop list processing terminated abnormally while releasing the SCB control block.

Par2414
End next processing terminated abnormally while releasing the PCB control block.
Back up all files in %PDDIR%\spool and contact the customer support center. If HiRDB does not restart automatically, restart it manually.

Par2415
Attempt was made to allocate an area of 1 GB or more.
Back up all files in %PDDIR%\spool and contact the customer support center.

Par3100
An error occurred during analysis of the pd_max_tmp_table_rdarea_no operand of the system common definition.
Save the files under %PDDIR%\spool, %PDDIR%\conf, and %PDDIR%\tmp, save the event log (in UNIX, syslogfile), and contact the customer support center.

Par3101
A conflict was detected when checking the number of RDAREAs for the temporary table being defined against the value specified in the pd_max_tmp_table_rdarea_no operand of the system common definition.

If there is a mismatch between the pd_max_tmp_table_rdarea_no operands specified in the system common definitions of the units, specify the same values in each unit, and then restart the unit with the abnormally terminated front-end server.

For cases other than the above, save the files under %PDDIR%\spool, %PDDIR%\conf, and %PDDIR%\tmp, save the event log (in UNIX, syslogfile), and contact the customer support center.

Pas2100
An analysis tree was invalid during semantic analysis.
Back up all files in %PDDIR%\spool and contact the customer support center.

Pas2101
Contradiction was detected during SQL analysis processing.
Back up all files in %PDDIR%\spool and %PDDIR%\tmp and contact the customer support center.

Pas2352
Invalid information was returned from dic to sqa.
Contact the customer support center.

Table 3-2 ABORT codes (PbXXXXX)

ABORT Code | Cause | Action
Pba0101 | Internal conflict occurred. | Contact the customer support center.
Pba0201 | Parameter is invalid.
Pba0202 | Execution sequence of functions is invalid.
Pba0301 | Return code is invalid.
Pba0401 | Contents of input buffer from SQA are invalid.
Pba0402 | Contents of output buffer from SQA are invalid.
Pba0501 | Non-execution of the XA interface function was detected.
Pba0601 | SQL statement's execution function was called incorrectly.
Pbb0200 | An input parameter of a memory management function is invalid.
Pbb0201 | An input address of a memory management function is invalid.
Pbb0204 | A status error occurred in a memory management function.
Pbb0290 | A return code for a memory management function is invalid.
Pbb0300 | No base address is set for CMT.
Pbb0301 | No base address is set for PMT.
Pbb0400 | An input parameter of an error reporting function is invalid.
Pbb0401 | An event type of an error reporting function is invalid.
Pbb0402 | An event type of an error reporting function is not supported.
Pbb0403 | An error type of an error reporting function is invalid.
Pbb0404 | An error type of an error reporting function is not supported.
Pbb0405 | No table creation area exists for an error reporting function.
Pbb0490 | An internal conflict occurred in an error reporting function.
Pbb0500 | A conflict occurred in an internal table of an XA request processing function.
Pbb0590 | An internal conflict occurred in an XA request processing function.
Pbb0600 | A conflict occurred in an internal table of an SQLplug function.
Pbb0601 | An SFD/SQL conflict occurred in an SQLplug function.
Pbb0690 | An internal conflict occurred in an SQLplug function.
Pbb0700 | A input parameter of a sequence check function is invalid.
Pbb0790 | A return code of a sequence check function is invalid.
Pbb1000 | A conflict occurred in an internal table of an SQL conversion function.
Pbb1001 | An SFD/SQL conflict occurred in an SQL conversion function.
Pbb1090 | An internal conflict occurred in an SQL conversion function.
Pbb2090 | An SQA return code is invalid.
Pbc0001 | Error occurred during abort code editing.
Pbc0002 | Internal contradiction occurred.
Pbc0101 | Invalid address was specified for memory reallocation or release.
Pbc0102 | Destruction of a memory area was detected.

Table 3-3 ABORT codes (PdXXXXX)

ABORT Code
Cause
Action

Pd00001
Error occurred during lock acquisition processing.
The KFPD00004-E message is output. If this message displays pdi_olk_thdlock as the name of the function resulting in the error and -20023 as the value of errno, the number of FIFOs per process has exceeded the OS's limit; increase the value for the OS. If the message displays pdi_olk_thdlock as the name of the function resulting in the error and -20024 as the value of errno, the number of FIFOs per system has exceeded the OS's limit; increase the value for the OS. If any other information is displayed in the KFPD00004-E message, contact the customer support center.

Pd00003
File I/O error occurred.
Refer to the KFPD00003 message to check the cause of the I/O error, and take appropriate action.

Pd00004
System call error occurred.
Refer to the KFPD00004 message to check the cause of the system call error, and take appropriate action.

Pd00005
Error occurred during server initialization.
If the KFPD00005-E, KFPD00020-E or KFPD00021-E message was output, take corrective action based on the message that was output.
If none of these messages was output, contact the customer support center.

Pd00008
Internal system conflict occurred.
During an abort, a KFPD00008-E or KFPD00020-E message is output. Take action according to the message that has been output.

Pd00030
Internal system conflict occurred.

If this abort code was output when the DEALLOCATE MEMORY TABLE statement was executed
A change might have been made to the server name specified in the pdxds operand in the system common definition for the XDS that supports the BES or SDS stored in the table to be added to the memory database. Therefore, check whether the XDS server name specified in the pdxds operand in the system common definition matches the XDS server name stored in the XDS_NAME column of the dictionary table SQL_TABLES. If the XDS server names do not match, change the XDS server name specified in the pdxds operand in the system common definition to the XDS server name stored in the XDS_NAME column of the dictionary table SQL_TABLES. Then, restart HiRDB and re-execute the DEALLOCATE MEMORY TABLE statement.

For cases besides the one mentioned above
An internal conflict was detected. Contact the customer support center.

Pd00777
Dictionary contents are invalid.
Contact the customer support center.

Pd10000
Registry thread activation failed.
If the KFPD00021-E message was output, take corrective action based on that message.
If this message was not output, contact the customer support center.

Pd10001
Registry thread stop failed.
Contact the customer support center.

Pd10002
An error occurred during access to the registry.
Check the error cause from the error message that was output before processing was aborted, take the corrective action, and then re-execute.

Pd17001
An error occurred during object cache control processing.
Contact the customer support center.

Table 3-4 ABORT codes (PeXXXXX)

Abort code
Cause
Action

Peama01
An internal error occurred after the command received by the HiRDB Assist - Server was executed; the HiRDB Assist - Server process terminated.
In UNIX:
Save all files under the setup directory for the HiRDB Assist - Server and also the syslog file, and then notify the customer support center.
In Windows:
There may have been a request for multiple commands to be executed consecutively. Provide a one-second interval between command executions, and then re-execute the command. If the Peama01 abort problem still persists after this action is taken, save all files under the HiRDB Assist - Server installation directory and the event log, and notify the customer support center.

Table 3-5 ABORT codes (PhXXXXX)

ABORT Code
Cause
Action

Phb0001
Message output error occurred.
Back up all files in %PDDIR%\spool and restart HiRDB. Or, notify the customer support center.

Phb0002
Semaphore handling error occurred.

Phb0003
ENQ counter error occurred.

Phb0004
Invalid put request was issued.

Phb0005
Function code is invalid.

Phb0006
Internal function error occurred.

Phb0007
Internal conflict was detected in the HiRDB file system.

Phb0008
Invalid free request was issued.

Phb0009
Log output error occurred.

Phb0010
Resource shortage occurred while opening a HiRDB file.
Reduce the number of users, and start HiRDB.

Phb0011
Semaphore initialization error occurred.
Resolve the cause of the error indicated in the KFPH23015-E message, and then restart HiRDB. If the cause of the error cannot be determined, contact the customer support center.

Phb0012
Shared memory detachment error occurred.

Phb0013
In UNIX, an ordinary file close error occurred. In Windows, a file close error occurred.

Phb0014
Shared memory release error occurred.

Phb0015
Shared memory allocation error occurred.

Phb0016
Shared memory attachment error occurred.

Phb0017
There is no available entry in TCB buffer stack.
Back up all files in %PDDIR%\spool and restart HiRDB. Or, contact the customer support center.

Phb0018
Lock error occurred.

Phb0019
Unlock error occurred.

Phb0020
A thread wait error was detected.
Save the file under %PDDIR%\spool, and contact the customer support center.

Phb0021
A thread post error was detected.

Phb0022
A message queue reception error was detected.
Eliminate the cause of the error that was output in the KFPH23015-E message, and then restart HiRDB. If the cause of the error cannot be determined, contact the customer support center.

Phb0024
An error was detected during transaction branch control.

Phb0025
An internal function error was detected.
Save the files under %PDDIR%\spool, and contact the customer support center.

Phb0026
Status file input/output processing failed.
Eliminate the cause of the error that was output in the KFPH23015-E message, and then restart HiRDB. If the cause of the error cannot be determined, contact the customer support center.

Phb0032
An error occurred during allocation of status file records.
Take the action indicated in the immediately preceding KFPH23033-E message, and restart HiRDB.

Phb0100
A critical release omission was detected.
Save the files under %PDDIR%\spool, and contact the customer support center.

Phb0101
A spin lock timeout was detected.
Eliminate the cause of the error that was output in the KFPH23015-E message, and then restart HiRDB. If the cause of the error cannot be determined, contact the customer support center.

Phb0102
A thread wait timeout was detected.

Phb0103
An error was detected during area management of the global buffers.
Save the files under %PDDIR%\spool, and contact the customer support center.

Phb0104
Status file input/output processing failed.
Eliminate the cause of the error that was output in the KFPH23015-E message, and then restart HiRDB. If the cause of the error cannot be determined, contact the customer support center.

Phb0106
A memory shortage occurred.
Take corrective action per the KFPH23003-E message output immediately before this message, and restart HiRDB.

Phb0107
Mapping of the global buffer failed.
Take corrective action per the KFPH23003-E or KFPH23005-E message output immediately before this message, and restart HiRDB.

Phb0108
A message queue sending error was detected.
Eliminate the cause of the error that was output in the KFPH23015-E message, and then restart HiRDB. If the cause of the error cannot be determined, contact the customer support center.

Phb0109
A system switchover timeout was detected.
Save the files under %PDDIR%\spool, and contact the customer support center.

Phb1001
Buffer definition analysis termination error occurred.
Resolve the cause of the error indicated in the KFPH23015-E message, and then restart HiRDB. If the cause of the error cannot be determined, contact the customer support center.

Phb1002
Invalid argument was detected while starting buffer definition analysis.

Phb1003
Invalid argument was detected during buffer definition analysis.

Phb1004
Invalid option was detected during buffer definition analysis.
Back up all files in %PDDIR%\spool and restart HiRDB. Alternatively, contact the customer support center.

Phb1006
The rollback process does not have the system resources needed to access a table.
Take corrective action according to the KFPH23042-E message that was just output, and then restart HiRDB.

Phb1007
A shortage of open resources was detected.
Save the files under %PDDIR%\spool, and contact the customer support center.

Phb1008
The user process does not have the system resources needed to access a table.
Take corrective action according to the KFPH23042-E message that was just output, and then restart HiRDB.

Phb1009
An internal function error occurred.
Eliminate the cause of the error that was output in the KFPH23015-E message, and then restart HiRDB. If the cause of the error cannot be determined, contact the customer support center.

Phb1012
There was no allocation buffer during startup of the guest BES in an environment that uses the standby-less system switchover (effects distributed) facility.
Save the files under %PDDIR%\spool, and contact the customer support center.

Phb1013
Buffer allocation failed in an environment that uses the standby-less system switchover (effects distributed) facility.

Phb1014
An invalid argument was detected in an internal function.

Phb1015
Shared memory allocation for the unit failed.
Eliminate the cause of the error that was output in the KFPH23015-E message, and then restart HiRDB. If the cause of the error cannot be determined, contact the customer support center.

Phb1016
Definition file analysis failed.
Save the files under %PDDIR%\spool, and contact the customer support center.

Phb1018
Acquisition of RDAREA information for global buffer creation failed.
Determine the cause from the error messages output before the ABORT code, take appropriate action, and then restart the unit. If return code=-310 is output in a KFPH22013-E message, the dictionary server is stopped; restart the dictionary server and then restart the unit. If the cause of the error cannot be determined from the error messages, contact the customer support center.

Phb1019
An internal function error occurred.
Save the files under %PDDIR%\spool, and then restart HiRDB. Also, contact the customer support center.

Phb1021
The number of pdbuffers exceeds the limit.
Take action as indicated in the immediately preceding KFPH23029-E message, and restart HiRDB.

Phb1022
The number of pdbuffers does not match the number when started previously.
Take action as indicated in the immediately preceding KFPH23031-E message, and restart HiRDB.

Phb1023
The pdbuffer option specification is invalid.
Take action as indicated in the immediately preceding KFPU00218-E message, and restart HiRDB.

Phb1025
The memory size was exceeded.
Take action as indicated in the immediately preceding KFPH23032-E message, and restart HiRDB.

Phb1026
The dynamic update of global buffer facility cannot be used.
Take action as indicated in the immediately preceding KFPH23034-E message, and restart HiRDB.

Phb1027
An invalid argument was detected in an internal function.
Save the file under %PDDIR%\spool, and contact the customer support center.

Phb1028

Phb2001
RDAREA ID or page number is invalid.
Restart HiRDB and recover the corresponding RDAREA. Also, contact the customer support center.

Phb2002
Shortage occurred in reserve buffer.
Back up all files in %PDDIR%\spool and restart HiRDB. Or, contact the customer support center.

Phb2003
Duplicate GET request was issued.

Phb2004
Chain error occurred.

Phb2005
An invalid argument was detected in an internal function.

Phb2006
An internal conflict was detected in the global buffer process.
Save the file under %PDDIR%\spool, and contact the customer support center.

Phb2007
Time stamp mismatch was detected while outputting data to a database.
Save the files under %PDDIR%\spool, and then restart HiRDB. Also, contact the customer support center.

Phb2008
Object ID mismatch within a page was detected during data output to the database.

Phb2009
Invalid parameter or invalid processing sequence was detected while forcibly outputting a log.

Phb2010
If unitdown is specified in the pd_db_io_error_action operand, an RDAREA I/O error has occurred, causing HiRDB (for HiRDB/Parallel Server, a unit) to terminate abnormally.
Referring to the error message output before the process aborted, determine the cause of the error. Then, either switch over the system again, or restart HiRDB.

Phb2011
A file access error was detected in the RDAREA while the unit shutdown facility was being used (with unitdown specified in the operand pd_db_access_error_action) during file access error detection. Therefore, the unit shut down.
Determine which file has the access error as well as the reason for the error from the error message output before the process aborted, take corrective action, and then restart HiRDB.
In Windows, if files are being copied by the COPY command, restart HiRDB after copying is finished.

Phb2012
An error shutdown was detected in the RDAREA while the unit shutdown facility was being used (with unitdown specified in the operand pd_db_hold_action) during file access error detection. Therefore, the unit shut down.
Determine the file associated with the error shutdown as well as the reason for the error from the error message that was output before processing was aborted, take corrective action, and then restart HiRDB.

Phb3001
Batch input occurred on index page.
Back up all files in %PDDIR%\spool and restart HiRDB. Alternatively, contact the customer support center.

Phb3002
Batch input request is invalid.

Phb3004
HiRDB file OPEN/CLOSE processing failed.

Phb3005
A read request page number is invalid.
Make sure that no errors were made in the database recovery procedure. If there is an unrecovered database, recover or re-create it. If there is no error, save the files under %PDDIR%\spool, and then restart HiRDB. Also, contact the customer support center.

Phb3006
An invalid pool number was detected in the batch input/output local buffer.
Save the files under %PDDIR%\spool, and then restart HiRDB. Also, contact the customer support center.

Phb3007
An invalid argument was detected in an internal function.

Phb3008
A server process terminated abnormally while a local buffer was being used. A page (update page) was detected that, temporarily, recovery processing could not recover.
Restart HiRDB.

Phb4000
An internal conflict was detected in deferred write processing.
Back up all files in %PDDIR%\spool, and restart HiRDB. Alternatively, contact the customer support center.

Phb4001
Internal conflict occurred.

Phb4002
Undefined value was returned.

Phb4003
Function parameter error occurred.

Phb4004
rpc open error occurred.

Phb4005
Phb4006
Phb4007
Internal function error occurred.

Phb4009
Memory shortage occurred.
Reduce the number of users, and then start HiRDB.

Phb4010
The message queue ID could not be obtained.
Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact the customer support center.

Phb4011
Message receive error occurred.

Phb4012
Message send error occurred.

Phb4020
Update flag is invalid.

Phb4022
Synchronization output flag is invalid.

Phb4023
Deferred write status is invalid.

Phb4030
HiRDB file initialization error occurred.

Phb4031
HiRDB file open error occurred.

Phb4032
HiRDB file close error occurred.

Phb4033
HiRDB file write error occurred.

Phb4034
A HiRDB file close error occurred.
Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact the customer support center.

Phb4035
Disk number is invalid.
Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact the customer support center.

Phb4041
Repeated attempts to open a HiRDB file failed due to a shortage of open resources.
Take action according to the preceding KFPH23201-W or KFPH23100-E message, and then restart HiRDB.

Phb4044
A semaphore operation error occurred in the deferred write process.
Check the cause of the error based on the error message (KFPO00107-E) preceding the abort, take appropriate action, and then re-execute the command. If an error message is not output, save the files under %PDDIR%\spool, and then restart HiRDB. Also, notify the customer support center.

Phb4045
An invalid argument was detected in an internal function.
Save the files under %PDDIR%\spool, and then restart HiRDB. Also, contact the customer support center.

Phb4109
A memory shortage occurred.
Take one of the following actions to provide additional memory, and then restart HiRDB:

Reduce the number of other processes running on the same machine.

Increase the swap area.

Provide additional real memory.

Phb4111
A thread unlock error occurred.
Save the files under %PDDIR%\spool, and then restart HiRDB. Also, contact the customer support center.

Phb4141
Despite repeated attempts to open the HiRDB file by using the parallel write process for the deferred write process, the HiRDB file could not be opened due to a shortage of open resources.
Take corrective action according to a previous KFPH23201-W or KFPH23100-E message, and then restart HiRDB.

Phb4144
A semaphore operation error occurred in the parallel write process for the deferred write process.
Check the cause of the error based on the error message (KFPO00107-E) preceding the abort, take appropriate action, and then re-execute the command. If an error message is not output, save the files under %PDDIR%\spool, and then restart HiRDB. Also, notify the customer support center.

Phb5001
An internal conflict was detected.
Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact the customer support center.

Phb5002
An invalid request was detected.

Phb6001
An internal conflict was detected during in-memory data processing.

Phb****
*: Variable character string
Internal contradiction was detected during DB buffer processing.

Phc0001
getarea return code is invalid.
Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute. If no error message was output, contact the customer support center.

Phc0002
Message editing failed.

Phd0002
RDAREA ID is invalid.
Check to see if there is an operation error on the applicable RDAREA. If there is an error, the RDAREA should be recovered.
If the RDAREA has been moved, restart HiRDB.
If there is no error, save the files under %PDDIR%\spool, and contact the customer support center.

Phd0003
Internal work file access error occurred.
Check the system operation and recover the database if an error was found. If there is no error, save the files under %PDDIR%\spool, and contact the customer support center.

Phd0004
Thread lock terminated abnormally.
Save the files under %PDDIR%\spool, and contact the customer support center.

Phd0005
File number is invalid.
Check the system operation and recover the database if an error was found. If there is no error, save the files under %PDDIR%\spool, and contact the customer support center.

Phd0006
Invalid log was detected during rollback.

Phd0007
Invalid log was detected during log collection.

Phd0008
Internal conflict was detected while a server transfer area was being created.
Save the files under %PDDIR%\spool, and contact the customer support center.

Phd0009
Internal conflict was detected during communication.

Phd0010
An internal function error was detected.

Phd0011
A memory shortage occurred. This problem generates a message in the following situation:

If it is detected in an internal function during rollback

Take corrective action following the instructions of the memory shortage error message that was just output. Then, if the unit has shut down, restart the shut down unit.

Phdt***
*: Variable character string
An internal conflict was detected during operations on a temporary table or a temporary table index.
Save the file under %PDDIR%\spool, and contact the customer support center.

Phi0002
Analysis of a definition file failed.

Phi0013
A thread lock error occurred.

Phi0014
A thread unlock error occurred.

Phi1001
Acquisition of environment definition variable failed.
Check the error message that was output before ABORT for the cause of the error, take appropriate action, then re-execute. If no error message was output, contact the customer support center.

Phi1002
Allocation of common control block failed.

Phi1003
Communication open error occurred.

Phi1006
Initialization error occurred in the SQL analysis component.

Phi1007
Initialization error occurred in the dictionary management component.

Phi1008
Initialization error occurred in the database management component.

Phi1010
Allocation of log server area failed.

Phi1011
Message editing failed.

Phi1012
Acquisition of a HiRDB database environment information file from the running system failed.
If all of the following conditions are satisfied, confirm that the HiRDB running system is active, and then restart the HiRDB standby system:

Hitachi HA Toolkit Extension is being used.

The rapid system switchover facility is being used.

A KFPS01861-E message was output to the event log (in UNIX, syslogfile) of the running system.

Otherwise, eliminate the cause of the error output in the KFPH20003-E message, and restart the HiRDB standby system. If you cannot determine the cause of the error, contact the customer support center.

Phl0001
Internal logical contradiction occurred.
Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact the customer support center.

Phl0002
Buffer allocation error occurred.

Phl0003
Function code was invalid during Build-List.

Phl0004
List ID (address) is invalid.

Phl0005
Return code is invalid.

Phl0006
read request page number is invalid.

Phl0007
Number of pages in string is invalid.

Phl0008
Work table buffer pool's contents are invalid.
Back up all files from %PDDIR%\spool and contact the customer support center.

Phl2355
Return code contradiction occurred.
If RPC trace information is being collected, back up the RPC trace information. Next, back up all files in %PDDIR%\spool and restart HiRDB. Also, contact the customer support center.

Phl3722
Phl3723
Internal conflict occurred.
Save the files under %PDDIR%\spool, and contact the customer support center.

Phl4002
Phl4003
Interface is invalid.

Phl4018
Return code of a list module is invalid.

Phl4023
Row address of a list is invalid.

Phl5301
I/O error occurred.

Phlb001
Internal contradiction was detected.

Phm0001
Return code of buffer management is invalid.
Use the database recovery utility to recover the database and restart.

Phm0002
Return code of directory management is invalid.
Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact the customer support center.

Phm0003
A memory shortage occurred when a shared table was being updated without issuing a LOCK TABLE statement in EXCLUSIVE mode.
Take corrective action according to the preceding memory shortage error message. If the unit is down, restart the unit that was shut down.

Phm0004
Buffer memory corruption was detected when a shared table was being updated without issuing a LOCK TABLE statement in EXCLUSIVE mode.
Save the files under %PDDIR%\spool, restart the abnormally terminated unit, and contact the customer support center.

Phm0999
Internal contradiction was detected.
Use the database recovery utility to recover the database and restart.

Phm1001
Attempt was made to insert a FIX table page that was greater than the defined length.
Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact the customer support center.

Phm1002
I/O area or offset list was not found.

Phm1003
Length of variable-length data is 0.

Phm1100
Phm1101
Internal conflict occurred during BLOB data I/O processing.
Contact the customer support center.

Phm1102
Invalid RDAREA number was specified for BLOB data.
If the RDAREA has been moved, restart HiRDB. If there is no operation error, contact the customer support center.

Phm1103
Internal conflict occurred while BLOB data was being updated.
Contact the customer support center.

Phm1104
File number was invalid.

Phm1105
Internal conflict occurred while BLOB data was being retrieved.

Phm1110
A return code indicating an error was returned from another component function.
Recover the database using the database recovery utility.

Phm2001
Format of a row to be updated is invalid.
Check the database recovery procedure for an error. If there is a database that has not been recovered, either recover it or re-create it. If there is no error, contact the customer support center.

Phm2002
Type of table to be updated is invalid.
Back up the files under %PDDIR%\spool and contact the customer support center.

Phm5001
An attempt was made to project a row identifier during row I/F for a non-FIX table.

Phm5002
Buffer management error occurred.
Use the database recovery utility to recover the database and restart.

Phm5003
Specified scan type is invalid.
Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact the customer support center.

Phm5004
Data projection is not available to specified server machine.

Phm5011
Page is invalid (branching destination page).
Check the database recovery procedure for an error. If there is a database that has not been recovered, either recover it or re-create it. If there is no error, contact the customer support center.

Phm5012
Page is invalid (branching source page).

Phm5013
Page number is invalid. Table ID in the database does not match the requested table ID during fetch processing.

Phm5014
Slot value is invalid. A row was deleted or a nonexisting row was fetched.

Phm5015
Page is invalid (page specified for fetch was not found).

Phm5016
Slot value is invalid. A row was deleted, or a nonexisting row was specified as the branching destination.

Phm5017
Row format is invalid. The format of the fetched row is not P/B/ F.

Phm5018
Row format is invalid. The format of the branching destination row is not B'/F'.

Phm5019
Invalid row format. The branching destination row is not in the B/B'/A format.
Make sure that no errors were made in the database recovery procedure. If there is an unrecovered database, either recover or re-create it. If there is no error, contact the customer support center.

Phm5020
The stored page for BINARY attribute data of the abstract data type is invalid.

Phm5021
Return value is invalid.
Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact the customer support center.

Phm5022
Work area shortage occurred while a suppress table was being retrieved.
Set the number of DECIMAL columns in the conditional expression to no more than 512 and re-execute. Back up all files in %PDDIR%\spool and contact the customer support center.

Phm5023
Phm5024
An internal conflict occurred during condition evaluation.
Save the file under %PDDIR%\spool, and contact the customer support center.

Phm5025
An internal conflict occurred during storage processing of compressed data.

Phm5026
Invalid compressed data was detected.

Phm5027
An internal conflict occurred during expansion processing of compressed data.

Phm6000
Invalid locking operation, or invalid RDAREA ID.
If the RDAREA has been moved, restart HiRDB.
If there is no operation error, save the files under %PDDIR%\spool, and contact the customer support center.

Phm6001
Phm6002
Phm6003
Phm6004
Lock processing is invalid.
Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact the customer support center.

Phm6005
Phm6007
Codes indicating an error was returned from another component's function.

Phm6008
A shortage of RDAREA locked resources occurred.

Phm6009
A shortage of replica group locked resources occurred.

Phm6100
The HiRDB restart memory size for the process native area used by all processes on the unit controller is insufficient.
Because recovery by restarting is not complete, complete the recovery using the following procedure:

Unload logs following the log displayed in the previous synchronization point completion message KFPS02183-I.

Use pdstart -r to start HiRDB.

Use the pdrstr command to recover the most recent synchronization point of the RDAREA used by the master directory.

Use pdstop to stop.

Use pdstart dbdestroy to start HiRDB.

Recover RDAREAs other than the RDAREA used by the master directory to the most recent synchronization point.

Use pdstop to stop.

After completing the recovery, revise the definition parameters or expand the memory, and then perform a normal startup of HiRDB. For details about the recovery procedure, see the section on recovering all RDAREAs to the most recent synchronization point in the manual HiRDB Version 9 System Operation Guide.

Phm7000
Attempt was made to output an invalid log.
Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact the customer support center.

Phm9000
Internal logical contradiction was detected.
Use the database recovery utility to recover the database and restart.

Phr0100
Contradiction was detected while updating page writing information.
Back up the files under %PDDIR%\spool and contact the customer support center.

Phr1110
Internal conflict occurred in the table for managing the RDAREA status.
Restart HiRDB.

Phr1111
Internal conflict occurred when RDAREA status information was being registered in the table for managing RDAREA status.

Phr1112
The number of RDAREAs exceeded the maximum system value when RDAREA status information was being registered.

Phr1113
A redo process was not found at the time of redo log allocation during restart.
Use the database recovery utility to recover the database and restart.

Phr1114
The number of REDO processes during restart is invalid.

Phr1115
An attempt was made to start a redo process without acquiring a log buffer during restart.

Phr1116
During restart, a log with the invalid redo log type was detected.

Phr1117
The number of RDAREAs contradicts the number of RDAREA status information items in the table for managing RDAREA status.

Phr1118
Internal conflict occurred in a restart write page information table.
Back up the files under %PDDIR%\spool, and contact the customer support center.

Phr1210
Internal conflict occurred in information on the number of log update pages during a restart redo process.
Use the database recovery utility to recover the database and restart.

Phr1212
During the restart redo process, an attempt was made to improperly update the transaction management table during the analysis of the transaction status.

Phr1213
During the restart redo process, the index log contains invalid lock recovery information.

Phr1214
During the restart redo process, the directory log contains invalid lock recovery information.

Phr1215
During the restart redo process, the log for recovering the lock contains invalid lock recovery information.

Phr1216
During the restart redo process, the log contains an invalid lock type.

Phr1217
During the restart redo process, processing instructions for the log contain an error.

Phr1218
The number of disks is invalid.

Phr1300
Code indicating an error was returned by another subcomponent function.
Check the error cause from the error message that was output before processing was aborted, take corrective action, and then re-execute. If an error message was not output before processing was aborted, save %PDDIR%\spool and contact the customer support center.

Phr1310
During the restart data page redo process, a return code indicating an error was returned.
Use the database recovery utility to recover the database and restart.

Phr1311
During the restart index page redo process, a return code indicating an error was returned.

Phr1312
During the restart directory page redo process, a return code indicating an error was returned.

Phr1320
During the restart redo processing, a return code indicating an error was returned when an attempt was made to recover a directory inconsistency.

Phr1321
During the restart redo processing, a return code indicating an error was returned when an attempt was made to recover an index inconsistency.

Phr1400
Code indicating an error was returned from another component function.
If an error message was output before the abort, determine the cause of the problem based on that message, take appropriate corrective action, and then re-execute the command. If there was no error message before the abort, save the files under %PDDIR%\spool, and contact the customer support center.

Phr1401
An attempt to obtain the shared memory segment address of the log buffer during restart failed.
Recover the database using the database recovery utility.

Phr1410
Recovery-related semaphore operation failed.

Phr1411
Retrieval of recovery-related semaphore value failed.

Phr1412
Allocation of recovery-related semaphore failed.

Phr1413
Recovery-related semaphore operation failed.

Phr1420
Allocation of area used for recovery-related processing (process private area) failed.
Check the number of processes, take appropriate action, and re-execute.

Phr1421
Phr1422
Phr1423
Phr1424
Allocation of area required for RDAREA status management table (process private area) failed.

Phr1425
Phr1426
Phr1427
Phr1428
Allocation of an area (process private area) required for management of page write information used in a restart redo failed.

Phr1430
A return code indicating an error was returned from the pd_lck_notrn_get function during lock recovery at restart.
Save the information to be acquired in the event of an error, and contact the customer support center. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.

Phr1431
A return code indicating an error was returned from the pd_lck_notrn_release function during lock release at restart.

Phr1440
A return code indicating an error was returned from the pdi_log_get_rerun_buff function during log input at restart redo.

Phr1441
Reception of a message from the pdi_log_get_rerun_buff failed during log input at restart redo.

Phr1442
Release of the log buffer failed at restart redo.

Phr1443
Code indicating an error was returned when attempt was made to obtain a log sequence number from the log server.

Phr1444
A return code indicating an error was returned from the log server in the processing for which the Isn by RDAREA was to be posted to the log server at restart redo.

Phr1450
Code indicating an error was returned when pdi_trn_sv_tran_ent function was issued to obtain the number of transactions.

Phr1451
During restart redo processing, the function pdi_tjl_chg_trnid was issued, which acquires a transaction identifier from the second header of log records, but a return code indicating an error was returned.

Phr1460
Phr1461
Status file read operation failed.
Use the database recovery utility to recover the database. Restart HiRDB.

Phr1462
Status file write operation failed.
Restart HiRDB.

Phr1463
Phr1464
Allocation of status file record failed.
Check the estimated status file size for an error. If it is correct, contact the customer support center.

Phr1465
Code indicating an error was returned when the pdi_sts_sys_iosize function was issued to obtain the status file record size.
Re-create the status file and restart HiRDB.

Phr1466
The pdi_sts_sys_iosize function was issued to obtain the status file record size, but the returned record size was outside the permitted range.

Phr1470
During restart redo processing, the function p_m_dhh_idx_gtngid was issued using multiple update pages as a design from the index log, but a return code indicating an error was returned.
Use the database recovery utility to recover the database.

Phr1471
During restart redo processing, the function p_m_dhh_idx_gtpgn was issued for acquiring update pages from the index log, but a return code indicating an error was returned.

Phr2100
Multiple identical transactions were detected during transaction analysis during restart redo processing.

Phr2200
Attempt was made to register more RDAREAs than the permitted maximum into the table for managing RDAREA status information.
Restart HiRDB.

Phr2210
A conflict was detected when writing status information for the RDAREA to the status file was attempted.
Back up all files in %PDDIR%\spool and contact the customer support center.

Phr2300
Phr2310
Phr2311
Internal conflict occurred in recovery processing.
Use the database recovery utility to recover the database.

Phr2350
An error occurred during execution of the database recovery utility. This problem can occur in the following cases:

The backup that was input does not match the log.

When the database was recovered using the log only, the database did not match the log.

There was an error in the operation.

If the input backup does not match the log:
Use the correct backup and log; re-execute the database recovery utility.

If the database does not match the log:
Re-execute the database recovery utility based on the backup and all valid log files that have been collected since the backup.

Other than the above:
Check for errors in the operation of the targeted RDAREA. Recover the RDAREA if you find an error. If you do not find an error, contact the customer support center.

Phr2400
Message editing failed.
Restart HiRDB.

Phr2401
Attachment of buffer shared memory failed.
Refer to the message that was output before this ABORT code.

Phr2402
First log for which rollback should have been completed cannot be found.
Use the database recovery utility to recover the database, back up all files in %PDDIR%\spool, and contact the customer support center.

Phs****
*: Variable character string
The return code of a low-order module is invalid.
Save the files under %PDDIR%\spool, and contact the customer support center.

Phu0001
Text area allocation error occurred.
Check for any unnecessary process.

Phu0002
Forced page output error occurred.
Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact the customer support center.

Phu0003
Status file update error occurred.

Phu0004
Commit failed.
Resolve the cause of the error based on the KFPH27000-E message, and then restart HiRDB. If the cause of the error cannot be determined, contact the customer support center.

Phu0005
Internal contradiction was detected.
Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact the customer support center.

Phu0006
System manager's function call failed.
Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute. If no error message was output, back up all files in %PDDIR%\spool and contact the customer support center.

Phu0007
More than 60 seconds passed while waiting for a response from the server, so a timeout occurred. A server indicates a single server, back-end server, or dictionary server.
For the action to take, see abort code Psrc039 in this table.
Save the files under %PDDIR%\spool, and contact the customer support center.

Phx0001
Phx0002
An interface error occurred during update processing of the substructure index.
Save the file under %PDDIR%\spool, and contact the customer support center.

Phx0003
Phx0004
Database corruption was detected in the update process of the substructure index.
Make sure that no errors occurred during the database recovery procedure. If there is an unrecovered database, recover or re-create it. If no errors occured during the database recovery procedure, contact the customer support center.

Phy1001
Invalid parameter.
Back up all files in %PDDIR%\spool and contact the customer support center.

Phy2001
Internal conflict occurred in the data directory.
Make sure that the indicated RDAREA is operating correctly. If there is an operation error, recover the RDAREA. If the problem persists even when there is no apparent error, contact the customer support center.

Phy2002
An RDAREA status conflict was detected.

Phy3001
An invalid return code was detected.
Back up all files in %PDDIR%\spool and contact the customer support center.

Phy4001
An internal logical conflict was detected.

Phz3011
Buffer management return code is invalid.
Back up all files in %PDDIR%\spool and restart HiRDB. If the same error recurs, contact the customer support center.

Phz3021
Internal contradiction occurred in the data directory.
Make sure that the indicated RDAREA is operating correctly. If there is an operation error, recover the RDAREA.
If Real Time SAN Replication with the log-only synchronous method is being used, perform preparation for log application. If the problem persists even when there is no apparent error, contact the customer support center.

Phz3033
Invalid code was returned from an internal subroutine.
Check the system operation and recover the database if an error was found. If no error was found, save the files under %PDDIR%\spool, and contact the customer support center.

Phz3101
Internal contradiction occurred in the directory.
Make sure that the indicated RDAREA is operating correctly. If there is an operation error, recover the RDAREA.
If Real Time SAN Replication with the log-only synchronous method is being used, perform preparation for log application. If the problem persists even when there is no apparent error, contact the customer support center.

Phz3510
The buffer management return code is invalid.
Back up all files in %PDDIR%\spool and restart HiRDB. If the same error recurs, contact the customer support center.

Phz3712
Error occurred in the master directory RDAREA.
Resolve the error, recover the RDAREA, and then restart HiRDB. If Real Time SAN Replication with the log-only synchronous method is being used, perform preparation for log application, and then restart.

Phz3714
Buffer request is invalid.
Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact the customer support center.

Phz3715
Request contradicts the buffer information.

Phz3716
Contradiction occurred in a directory macro.

Phz3717
Requested file ID is invalid.

Phz3722
Listing work file name cannot be created.
Contact the customer support center.

Phz3723
Listing work file I/O failed.

Phz3730
System RDAREA free request was issued.
Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact the customer support center.

Phz3760
Page was damaged (UTL environment).

Phz3771
Internal conflict occurred in the HiRDB file system.
Resolve the cause of the error based on the KFPH23100-E message, and then restart HiRDB.

Phz3785
Buffer shutdown request was issued for the master directory RDAREA.
Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact the customer support center.

Phz4002
Column ID list is invalid.
Contact the customer support center.

Phz4003
Internal logical conflict occurred.

Phz4018
Address selection failed in a list page.

Phz4020
Internal logical conflict occurred.

Phz4023
Database was damaged.
Check the database recovery procedure for an error. If there is a database that has not been recovered, either recover it or re-create it. If there is no error, contact the customer support center.

Phz4025
Return code is invalid.
Contact the customer support center.

Phz4100
Error was detected during exclusive processing.
Back up all files in %PDDIR%\spool and contact the customer support center.

Phz4107
An error was detected during locking processing.
If the RDAREA has been moved, restart HiRDB.
If there is no operation error, save the files under %PDDIR%\spool, and contact the customer support center.

Phz4113
Index contains the ID of an RDAREA that does not comprise the table.
Use the database recovery utility to recover the database and restart.

Phz4300
More retrieval conditions were specified than permitted.
Reduce the number of retrieval conditions and re-execute.

Phz4301
SQL object is invalid.
Contact the customer support center.

Phz4302
The table ID in the SQL object is invalid.
Contact the customer support center.

Phz4303
Return code is invalid.
Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact the customer support center.

Phz4304
Data contains the null value.
Use the database recovery utility to recover the database and restart.

Phz4500
Phz4501
Phz4502
Return code is invalid.
Save the file under %PDDIR%\spool, and contact the customer support center.

Phz4503
An invalid request was issued from a high-order module.

Phz4506
The return code is invalid.

Phz4508
Area allocation failed.

Phz4509
Index page information is invalid.

Phz4510
Error was detected in an index entry.

Phz4511
Row information is invalid.

Phz4512
Upper-level index key value is duplicated.

Phz4513
Index entry to be deleted was not found.
Make sure that no errors occurred during the database recovery procedure. If there is an unrecovered database, recover the database or re-create the index.
If there is no error, contact the customer support center.

Phz4514
Phz4515
Request code is invalid.
Back up all files in %PDDIR%\spool and contact the customer support center.

Phz4518
Table type is invalid.

Phz4520
Data type is invalid.

Phz4521
ENCODE result is invalid.

Phz4524
Termination condition code is invalid.

Phz4525
The address is invalid.

Phz4526
Page type retrieved based on a row identifier was invalid.
Make sure that no errors occurred during the database recovery procedure. If there is an unrecovered database, recover the database or re-create the index.
If there is no error, contact the customer support center.

Phz4532
Return code is invalid.
Back up all files in %PDDIR%\spool and contact the customer support center.

Phz4539
Index definition information is invalid.
Use the database recovery utility to recover the database and restart.

Phz4545
An internal conflict in an index was detected while searching it.
The KFPH00310-E message that was output simultaneously displays the RDAREA name, RDAREA ID, and index ID for the index in which the event occurred. This event is caused by damage to the index as a result of performing one of the following operations:

Startup using the pdstart dbdestroy command

Clearing the status file prior to starting a rerun

Performing a shutdown release without recovering the RDAREA that was shut down

If none of these operations was performed, or if it cannot be determined which, if any, was performed, save the file under %PDDIR%\spool and contact the customer support center.
When the index is damaged, use one of the following methods to recover it.

Recover the corresponding RDAREA migration using the database recovery utility

Re-create the corresponding index using the database reorganization utility.

Phz4547
Index type is invalid.
Back up all files in %PDDIR%\spool and contact the customer support center.

Phz4703
Function code is invalid.

Phz4704
The current position of the index was dropped during a search in which WITHOUT LOCK NOWAIT was not specified. Or, the return code from a lower module was invalid.
Check if, during a search, another SQL in the same transaction updated or dropped the same table, eliminate the cause of the error, and re-execute. If the same table was not updated or dropped during the same transaction, back up all files under %PDDIR%\spool, and contact the customer support center.

Phz4705
Return code from other module is invalid.
Back up all files in %PDDIR%\spool and contact the customer support center.

Phz4706
Return code from a subroutine is invalid.

Phz4707
Table type is invalid.

Phz4709
Shortage occurred in the area to be allocated.

Phz4710
Parameter is invalid.

Phz4711
An invalid character set was detected.

Phz4750
Table identifier and index identifier are invalid.

Phz4753
Return code from a low-order module is invalid.

Phz4754
Return code from other module is invalid.

Phz4760
RHF-UTL interface is invalid.

Phz4801
Return code is invalid.

Phz4802
Call parameter is invalid.

Phz4804
Column ID is invalid.

Phz4805
Multicolumn list is invalid.

Phz4806
An index identifier was not found.

Phz4807
Internal conflict occurred during the manipulation of an index information file.

Phz****
*: Variable character string
Allocation of internal area failed.

Table 3-6 ABORT codes (PkXXXXX)

ABORT Code
Cause
Action

Pk00001
Received an invalid message.
If a control statement file was specified when executing a file in %PDDIR%\spool or executing a utility, back up the control statement file and contact the customer support center.

Pk00002
Internal conflict was detected.

Pk00003
The RDAREA on which the status was being analyzed using the pddbst function was deleted.
Be careful not to delete the RDAREA when the pddbst command is running. If the RDAREA has not been deleted, save the files under %PDDIR%\spool, and the control statement file if a control statement file was specified during the execution of the utility, and then contact the customer support center.

Pk00004
The contents of the work file are invalid.
When a utility is executing, do not execute the following files in HiRDB-installation-drive\tmp (in UNIX, /tmp) or in the directory specified in the workdir statement:
Process ID.dbst.data
Process ID.bst.msg
Process ID.dbst.glaf
Process ID.dbst.stor
If operations such as file deletion have not been performed, collect the files under %PDDIR%\spool, as well as the above files, and then contact the customer support center.

Pk00005
Inter-process communications cannot be continued.
Refer to the error messages output to the event log (in UNIX, syslogfile) or to the message log file, and eliminate the cause of the communication error. If an unresolvable error occurred, collect the files under %PDDIR%\spool, and the control statement file if a control statement file was specified during the execution of the utility, and then contact the customer support center.

Pk00006
The database state analyzed table and database management table obtained before and after the database condition analysis do not match.
When executing the facility for accumulating condition analysis results, do not execute multiple pddbst commands against the same RDAREA. If these commands have not been executed simultaneously, save the data under %PDDIR%\spool and, if a control statement file is specified when a utility is executing, save the information (obtained by the pdfbkup command) on the RDAREA used by the data dictionary that stores the control statement file, database state analyzed table, and database management table, and contact the customer support center.

Pk00007
Due to a system call error, interval analysis could not be executed.
Save the data under %PDDIR%\spool and, if a control statement file is specified when a utility is executing, save that control file, and contact the customer support center. This error can be temporarily avoided by executing pddbst without specifying the -w option.

Pk00008
The table analyzed by pddbst does not match the index dictionary information.
During execution of pddbst, do not change tables or indexes. If the definitions have not been changed, acquire the data under %PDDIR%\spool and, if a control statement file is specified when a utility is executing, save the information (obtained by the pdfbkup command) on the RDAREA used by the data dictionary that stores the control statement file, database state analyzed table, and database management table, and contact the customer support center.

Table 3-7 ABORT codes (PoXXXXX)

ABORT Code
Cause
Action

Po*****
*: Variable character string
An error occurred in the OS library service function.
In UNIX:
If the HiRDB directory was removed without the pdcspool command being used, enter the pdsetup -d command to cancel setup, and then enter the pdsetup command to begin set up again. Otherwise, determine the cause of the error based on the error message output before the process aborted, take corrective action, and re-execute. If no error message was output, back up the error-related information, and contact the customer support center.
In Windows:
Determine the cause from the error messages output before the ABORT code, take appropriate action, and restart. If no error messages are output, save the information acquired when the error occurred, and contact the customer support center.
The information acquired in the event of an error includes the files under %PDDIR%\spool, the event log (in UNIX, syslogfile), and standard error output.

Polkcrt
A process was forcibly terminated while shared memory was being updated, meaning that operation can no longer be guaranteed. HiRDB (unit if HiRDB/Parallel Server) terminated abnormally. This abort code may appear in the following cases:

A pdstop -f command was executed.

A pdstop -z command was executed.

A system was switched over.

When forcibly terminating server processes and utility servers by using the Ctrl + C key combination, the kill command in UNIX, or the pdkill command in Windows.

Real Time SAN Replication with the log-only synchronous method is being used, and the pdrisedbto command was executed

If 1-4, there is no problem; recovery processing will be performed upon restart (including restart of the system switchover target).
If 5, see the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide, and take action on the basis of the database inheritance procedure for each site switchover format.
Otherwise, back up the error-related information and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool, the event log (in UNIX, syslogfile), and standard error output.

Table 3-8 ABORT codes (PrXXXXX)

ABORT Code
Cause
Action

Pr00001
Internal contradiction was detected in a common function.
Back up the error-related information, and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool, console messages, and standard error output.

Pr10001
Internal contradiction was detected in 0bcpy.

Pr20001
Internal contradiction was detected in 0rcopy.

Pr30001
Internal contradiction was detected in 0brstr.

Pr40001
Internal contradiction was detected in 0rrstr.

Pr50001
Internal contradiction was detected in 0lrstr.

Pr60001
Internal contradiction was detected in 0mrstr.

Pr70001
Internal contradiction was detected in 0wrstr.

Pr80001
Internal contradiction was detected in pdcopy.

Pr90001
Internal contradiction was detected in pdrstr.

Table 3-9 ABORT codes (PsXXXXX)

ABORT Code
Cause
Action

Psad***
*: Variable character string other than those in the Psad codes that follow.
Error occurred during system or server startup or termination processing.
Determine the cause of the error based on the error message output before the process aborted, take corrective action, and re-execute. If no error message was output, save the error-related information and contact the customer support center. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.

Psadc22
HiRDB has not been installed or set up correctly.
Check for the following possible reasons:

The setup was for the HiRDB installed at a remote host.

The HiRDB directory was created on an NFS-connected disk.

The disk containing the HiRDB directory was not mounted during OS initialization.

Psadci5
Acquisition of a network, host, or entry failed. Consider one of the following causes:

The host name specified in the system common definition is not in the hosts file.

The system does not have reference privileges to the hosts file.

If you are using DNS or WINS, the host name or IP address is not in the search database.

If you are using DNS or WINS, the system does not have reference privileges to the search database, or the setting is incorrect.

Eliminate the error and re-execute.

Psadh11
Error occurred in the file for HiRDB Datareplicator data linkage.
Correct the operating environment on the basis of the reason code displayed in the KFPS01801-E message that was output immediately previously, then re-execute.

Psadh71
Psadh73
Psadh75
Psadh78
Psadh82
Psadh85
Psadh88
Psadh8c
Psadh8q
Psadha3
Either the HA monitor or Hitachi HA Toolkit Extension has not been started. Or, a connection cannot be established to either the HA monitor or Hitachi HA Toolkit Extension. Therefore, HiRDB cannot be started in the server mode.
Either a KFPS01873-E message or KFPS01874-E message was generated before this abort code. Take corrective action according to these messages. If an HA monitor, Hitachi HA Toolkit Extension, or cluster software message is output, also take corrective action in reference to those messages.

Psadh79
Psadh7a
When the server was being started, it was aborted by the forced termination of the server (pdstop -s -z command). This message is output in some cases when the server being started is aborted by the forced termination command when the standby-less system switchover (effects distributed) facility is in effect.
This is not a problem if the server was aborted. If the server was not aborted, contact the customer support center. If an HA monitor, Hitachi HA Toolkit Extension, or cluster software message is output, also take appropriate corrective action by referring to the message.

Psadhf0
Consider the following causes:

If a system switchover facility is being used, after a normal termination or a planned termination was requested during termination processing of the system running HiRDB, a CPU error or a machine slowdown call tries to initiate a system switchover.

User server hot standby is applied, and Hitachi HA Toolkit Extension is being used.
(a) Before the Hitachi HA Toolkit Extension service process was activated (using the hateserve command), HiRDB was started using the pdstart command. If HiRDB is started before the Hitachi HA Toolkit Extension service process is activated, HiRDB will start in standby status, and activation of the Hitachi HA Toolkit Extension service process performs standby release processing.
(b) After starting the standby system HiRDB, start the running system HiRDB normally. At this time, startup of the running system HiRDB will fail, and a system switchover will occur.

The unit used for system switchover is a recovery-unnecessary front-end server unit.

If the running HiRDB system is in normal or planned termination status, stop the standby HiRDB system along with the running system. However, if a switchover occurred after normal or planned termination had been confirmed on the running system, the standby system aborts HiRDB and terminates because termination linkage has not been performed for the HA monitor or Hitachi HA Toolkit Extension. If you are using the HA monitor, and you start HiRDB after it terminates with this abort code, HiRDB startup might stop at some point. This is because once one HA monitor system has shut down, it may not be possible to determine whether the terminated HiRDB was the running system or the standby system. In this case, you must execute the following HA monitor command to so that the local system is treated as the running system.
1. Use the monshow command to verify that the status of the executing server is *SBY* (startup of the executing server is in standby).
2. Use the monact command to notify the HA monitor that the local server is the running server.
(a) If the pdstart command is executed before the Hitachi HA Toolkit Extension service process is activated, execute it after the Hitachi HA Toolkit Extension server process is activated, or specify the HiRDB activation command in the actcommand operand of the Hitachi HA Toolkit Extension server definition statement. If the pdstart command is executed from a shell, have the shell execute the pdstart command after the Hitachi HA Toolkit Extension service process is activated.
(b) Take action based on the cause of the error in starting the running system HiRDB, and then start the running system HiRDB.

Units that use system switchover cannot use recovery-unnecessary front-end servers. Change the system definition to use either the system switchover facility or recovery-unnecessary front-end servers.

If the cause at left is not applicable, contact the customer support center.

Psadhfe
Startup processing was suspended because both systems started up as standby systems while Hitachi HA Toolkit Extension was being used. The Hitachi HA Toolkit Extension service process may not be active.
To set up the primary system as the running system, start over with the following procedure:

On the primary system, start the Hitachi HA Toolkit Extension service process.

Start the primary system unit as the running system.

If the secondary system terminates abnormally, use the pdls command to check if startup of the running system unit is complete, and then start the secondary system unit as the standby system.

To set up the secondary system as the running system, start over with the following procedure:

Use the pdstop -z command (pdstop -f for HiRDB/Single Server) to forcibly terminate the secondary system unit.

Start the Hitachi HA Toolkit Extension service process on the secondary system unit.

Start the secondary system unit as the running system.

Use the pdls command to check if startup of the secondary system unit is complete, and then start the running system unit as the standby system.

Psadhff
Psadhfg
The HiRDB system could not be placed on wait status.
If memory is insufficient, determine the reason why memory is insufficient, take corrective action, and restart. If an error message was output before the process aborted, determine the cause of the error based on the error message, take corrective action, and restart. If no error message was output, save the error-related information and contact the customer support center. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, and the event log (in UNIX, syslogfile).

Psadhfh
System switchover occurred after normal or planned termination of HiRDB was confirmed.
If this abort code was output during system switchover, restart HiRDB on the switchover target.

Psadma2
Psadmaa
Psadmam
Psadman
Psadmaq
Psadmat
PsadmaC
PsadmaK
PsadmaL
PsadmaN
PsadmaO
PsadmbF
Psadmcr
Psadmmk
Psadmmm
The HA monitor, Hitachi HA Toolkit Extension, or the cluster software has not been started or is unavailable for connection. Therefore, HiRDB cannot be started in server mode.
Either a KFPS01873-E message or KFPS01874-E message was generated before this abort code. Take corrective action according to these messages. If an HA monitor, Hitachi HA Toolkit Extension, or cluster software message is output, also take corrective action in reference to those messages.

Psadnt1
The user authorization is invalid.
Confirm that the user executing an operating command has administrator privilege (other than a HiRDB administrator).

Psadp10
Psadp23
An attempt to obtain the default host name failed.
When the pdunit operand is omitted, make sure that the length of the default host name is no more than 32 bytes.

Psadp20

The host name specified in the system definition is not in the hosts file.

The hosts file cannot be referenced with the HiRDB administrator ID.

In UNIX:

If HiRDB is running on a server machine on which DNS or NIS is configured, operation is discontinued if the host name is not registered to the DNS or NIS in the host reference rules file (/etc/nsswitch.conf).

Register the host name specified in the system definition to the hosts file.

Set the hosts file reference privileges such that the hosts file can be referenced with the HiRDB administrator ID.

In UNIX:

If DNS or NIS is configured on the server machine, change the definitions in the /etc/nsswitch.conf file as follows:
hosts:dns [NOTFOUND=continue TRYAGAIN=continue] nis [NOTFOUND=continue TRYAGAIN=continue] files

Restart HiRDB after employing one of the preceding to correct the problem. If none of these is applicable, contact the customer support center.

Psadp25
It is not possible to use the gethostbyname system call to convert to the IP address corresponding to the system definition pd_hotstname.
Check for the following:

System definition pd_hostname setting error

Hosts file setting error

Hosts file invalid permissions

DNS or NIS setting files (such as nsswitch.conf and resolv.conf) setting error

Permissions for the various setting files (such as nsswitch.conf and resolv.conf) for DNS or NIS are invalid

Note that when using DNS or NIS, an sometimes an error may have occurred during communication with the DNS server or NIS server.

Psadp30
An attempt to obtain the default host name failed.
When the pdunit operand is omitted, the default host name must be registered to the hosts file or the DNS.
See the HiRDB Version 9 Installation and Design Guide for information on registering the host name.
In addition, make sure that the length of the default host name is no more than 32 bytes.

Psadp40
The PDDIR environment variable cannot be referenced.
If this error occurs in a command process, check whether the PDDIR environment variable is correctly set up.
If this error occurs in a HiRDB server process, memory shortage is a possible cause. In this case, take the following actions:

Close any processes or windows that are not needed.

Add a system swap area.

Psadp44
An error occurred while the HiRDB Staticizer Option management file was being accessed.
Back up the error-related information, and contact the customer support center. The information to back up is as follows:

All files under %PDDIR%

Event log (in UNIX, syslogfile)

Output of standard error

Psadp45
The definition analysis file set in the HiRDB system definitions cannot be opened.
Check if revocations or privileges for files under %PDDIR%\lib\sysconf and %PDDIR%\lib\sysdef have been changed.

If revocations or privileges have been changed:
In UNIX, specify y in the response message when the pdsetup -d command is executed. Then, re-execute the pdsetup command.
In Windows, re-install HiRDB.

If other than the preceding:
Back up the error-related information and contact the customer support center. The information to back up is as follows:
Files under %PDDIR%\spool
Files under %PDDIR%\tmp
Event log (in UNIX, syslogfile)
Output of standard error

Psadp47
An error occurred while the HiRDB Advanced High Availability management file was being accessed.
Back up the error-related information, and contact the customer support center. The information to back up is as follows:

All files under %PDDIR%

Event log (in UNIX, syslogfile)

Output of standard error

Psadp49
An error occurred during access to the HiRDB Non Recover FES management file.
Save the information acquired during the error, and contact the customer support center. The information to be acquired in the event of an error includes all files under %PDDIR%, the event log (in UNIX, syslogfile), and standard error output.

Psadp50
An error occurred while accessing the management file of the HiRDB Disaster Recovery Light Edition option program product.

Psadp51
An error occurred while accessing the management file of the optional program product HiRDB Accelerator.
Save the information acquired during the error, and contact the customer support center. The information to be acquired in the event of an error includes all files under %PDDIR%, the event log (in UNIX, syslogfile), and standard error output.

Psadr3C
Psadr3E
The HA monitor, Hitachi HA Toolkit Extension, or the cluster software has not been started or is unavailable for connection. Therefore, HiRDB cannot be started in server mode.
Either a KFPS01873-E message or KFPS01874-E message was generated before this abort code. Take corrective action according to these messages. If an HA monitor, Hitachi HA Toolkit Extension, or cluster software message is output, also take corrective action in reference to those messages.

Psadr5w
System server startup processing failed.
If there is a memory shortage, check the cause of the memory shortage, and restart HiRDB after taking corrective action. If there was an error message preceding the abort, check the cause of the problem based on the error message, and restart HiRDB after taking corrective action. If there is no error message, save the information to be saved in the event of an error, and contact the customer support center. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, and the event log (in UNIX, syslogfile).

Psadr62
Error was detected in the system manager's status information while restarting HiRDB.
If the HiRDB version had been changed before HiRDB was restarted, restore the previous version. Terminate HiRDB normally, and then restore the previous version.
If that is not the case, save the event log (in UNIX, syslogfile) and all files under %PDDIR%\spool, and contact the customer support center.

Psads01
The pdstart command was executed during OS initialization
Wait for OS initialization to complete, and then re-execute the command.
If this same error recurs even after OS initialization, contact the customer support center.
Note that this error also occurs when the pdstart command is specified in the OS environment file (/etc/localrc). HiRDB commands cannot be specified in the /etc/localrc or /etc/localshutrc files.
To start the OS and HiRDB at the same time, specify AUTO in the pd_mode_conf operand of the system common definition.

Psads3m
Psadsb2
An error occurred while obtaining shared memory.
Determine the cause from the error messages output before the ABORT code, take appropriate action, and then re-execute.

Psads3y
The number of servers in the unit exceeds the limit.
Reduce the number of servers defined for the unit, and then re-execute.

Psads47
An attempt to obtain the default host name failed.
When the pdunit operand is omitted, the default host name must be registered to the hosts file or the DNS.
See the HiRDB Version 9 Installation and Design Guide for information on registering the host name.
Also, make sure that the length of the default host name is no more than 32 bytes.

Psads6b
A server initialization error occurred.
Eliminate the cause of the error based on the error code in message KFPS01851-E and re-execute the pdstart command.

Psads73
Psads78
The HA monitor, Hitachi HA Toolkit Extension, or the cluster software has not been started or is unavailable for connection. Therefore, HiRDB cannot be started in server mode.
Either a KFPS01873-E message or KFPS01874-E message was generated before this abort code. Take corrective action according to these messages. If an HA monitor, Hitachi HA Toolkit Extension, or cluster software message is output, also take corrective action in reference to those messages.

Psads7e
The system server could not be placed on wait status.
If memory is insufficient, determine the reason why memory is insufficient, take corrective action, and restart. If an error message was output before the process aborted, determine the cause of the error based on the error message, take corrective action, and restart. If no error message was output, save the error-related information, and contact the customer support center. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, and the event log (in UNIX, syslogfile).

Psads8b
System server start processing failed.
Initialize the database at the transaction execution site and wait for normal termination. Then prepare for log application. For details about how to prepare for log application, see the HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide. After preparing for log application, start the log application site.

Psads9v
Start the preparation for log application before initializing the database.

Psads9w
The HiRDB addressing mode of the log application site does not match the database.
Set the HiRDB addressing mode of the transaction execution site to match that of the log application site, and then perform preparation for log application. If migrating from 32-bit mode to 64-bit mode, perform migration following the version upgrade procedure. For details about preparation for log application and the version upgrade procedure, see the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide.

PsadsA8
An error was detected in the integrity check on the RDAREA for the HiRDB system and master directory.
Take the action indicated in the last error message that was output before processing was aborted, and then restart HiRDB.
In a multiple-unit configuration using HiRDB/Parallel Server, check the status of each unit, forcibly terminate any units that are running, and then take the actions above.

PsadsAp
This message is generated in some cases during server startup processing if the server being started was aborted by an HA monitor, Hitachi HA Toolkit Extension, or server abort command (pdstop -s -z or pdstop -s -f).
A KFPS05617-I message is generated before stopping. The stoppage, which occurred due to a stop request, is not a problem.

PsadsBa
PsadsBb
The HiRDB version of the log application site does not match the database version.
Perform preparation for log application. For details about preparation for log application, see the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide. If the HiRDB versions of the transaction execution site and the log application site do not match, make them the same, and then perform preparation for log application. After performing preparation for log application, start the log application site.

Psadshz
The value specified in the pd_routine_def_cache_size operand is invalid.
Specify the correct value in the pd_routine_def_cache_size operand.

Psadsr8
An attempt was made to start a process that would result in the maximum number of startup processes per user being exceeded, or the maximum number of processes on the entire system being exceeded.
Check the value of the OS parameter.

Psadtlf
Psadt7h
Error occurred during server stop processing.
The server termination command was aborted because the server process terminated abnormally (including pdcancel) during server termination processing. This prevents the HiRDB system from being placed on an invalid status. Restart the HiRDB system and terminate it normally.
If the above event does not apply, check the error cause from the error message that was output before processing was aborted and take appropriate action.

Psadt1u
Psadt7G
The HA monitor, Hitachi HA Toolkit Extension, or the cluster software has not been started or is unavailable for connection. Therefore, HiRDB cannot be started in server mode.
Either a KFPS01873-E message or KFPS01874-E message was generated before this abort code. Take corrective action according to these messages. If an HA monitor, Hitachi HA Toolkit Extension, or cluster software message is output, also take corrective action in reference to those messages.

Psau***
*: Variable character string other than those in the Psau codes that follow.
An error occurred in the security audit facility.
Check the error message that was output before ABORT for the cause of the error, take appropriate action, and then re-execute.
If no error message was output, back up the error-related information and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.

Psau001
Writing of the status file failed.
Save the files under %PDDIR%\spool, and the event log (in UNIX, syslogfile), and contact the customer support center.

Psau099
Because output processing of the audit trail was centralized, all sectors of the asynchronous output buffer of the audit trail became completely full.
Determine the cause of the error from the error message that was just output, and take corrective action.
If no error message was output, save the information to be acquired in the event of an error, and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool and syslogfile.

Psaud0F
During a restart of HiRDB (including restart following planned termination), the value pd_aud_auto_loading in the system common definition was changed.
Return the value of pd_aud_auto_loading in the system common definition to the value specified during the previous startup, and then restart HiRDB.

Psaud0v
Psaud0w
Allocation of shared memory failed. This problem can occur when the following operations are performed successively in a standby-less system switchover configuration:

An alternate BES unit is started, and the accepting and the alternate portion are put in a standby status.

The alternate portion is terminated using the pdstop -q -c command without stopping the accepting unit.

After the following specification values for definitions of security audit on the unit control information definition (pdutsys) about the alternate portion are added or modified, the alternate portion is started using the pdstart -q -c command:
pd_aud_file_name
pd_aud_async_buff_size
pd_aud_async_buff_count

When the pd_aud_file_name definition specification is to be added to the alternate portion of the alternate BES unit in a standby-less system switchover configuration, stop the accepting unit as well as the alternate portion, and restart HiRDB. For a configuration other than a standby-less system switchover configuration, save the information to be saved in the event of an error, and contact the customer support center. Save the files under %PDDIR%\spool, and the event log (in UNIX, syslogfile).

Psaud11
Acquisition of a status file record failed.
Check the size of the status file. If the estimated size is correct, save the error-related information and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.

Psaud13
Psaud14
Psaud15
Writing of the status file failed.
Save the files under %PDDIR%\spool, and the event log (in UNIX, syslogfile), and contact the customer support center.

Psax219
Forced termination of XDS failed.
Check whether XDS has stopped. If it has, corrective action is unnecessary. Use the following procedure to check whether XDS has stopped.

Refer to the KFPQ80002-I message that was output in the syslogfile or XDS log file, and confirm the time when the displayed process ID and message were output.

Re-execute the ps command of the OS. Refer to the results of ps command execution, and check for the process ID that you checked for in step 1.
If there is no process ID, the XDS has stopped.
If there is a process ID, check the time when the process displayed in the ps command execution results was created. If the time when the process was created differs by several seconds from the time when the KFPQ80002-I message confirmed in step 1 was output, XDS may have stopped. In this case, forcibly terminate XDS by executing the pdxdsstop -f command again.

If the problem is not resolved using this corrective method, contact the customer support center.

Pscm***
*: Any character string other than those in the Pscm codes that follow.
Error occurred during operation command control processing.
Check the error message that was output before ABORT for the cause of the error, take appropriate action, then re-execute. If no error message was output, save the error-related information and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.

Pscm052
Psnd087
Psndm05
The HiRDB system or unit could not be started. For possible causes, refer to the error message that was output before the process aborted.

If an error message was not output, the following causes are possible: The unit with the system manager has not been started.

A memory shortage occurred.

A communication error occurred between the unit with the system manager and the unit without the system manager.

Determine the cause of the error from the error message that was output before the process aborted, and then take corrective action.
If no error message was output, investigate the error using checks (1) to (3) below, take corrective action, and then restart the HiRDB system or the unit. If checks (1) to (3) were not applicable, save the information acquired during the error and contact the customer support center.
The information to acquire in the event of an error is as follows.

In UNIX:
Files under $PDDIR/spool
Files under $PDDIR/tmp
syslogfile

In Windows:
Files under %PDDIR%\spool
Files under %PDDIR%\tmp
Event log

(1) Check the startup status of the unit with the system manager.
If the unit with the system manager has stopped, start it.
(2) Check whether there is enough memory capacity.
(3) Check whether a network error occurred between the unit with the system manager and the unit without the system manager.

Pscm05c
Input/output processing on a status file failed.
Investigate the cause of the problem and take corrective action with reference to the preceding status file error message.
After taking corrective action, restart the abnormally terminated unit.
If there is a KFPS05190-E message, restart the abnormally terminated unit.
If there is no error message, it is possible that either a memory shortage or a network error has occurred. Check to see if a memory shortage or a network error has occurred, take appropriate action, and then restart the abnormally terminated unit.
If these possibilities do not apply, contact the customer support center.

Pscm05d
Pscm05f
Pscm05g
Pscm05h
Due to a disk error, uninstallation of the option program product using the pdopsetup -d command failed.
Determine the cause from the immediately preceding KFPO00107-E message, and take appropriate action. Then, re-execute the pdopsetup -d command, and uninstall the option program product.

Pscm05i
Pscm05j
Pscm05k
It is not possible to confirm completion of all forced termination processes for a unit to which a system manager (MGR) is not allocated.
For possible causes, refer to the error message that was output before the process aborted.
If an error message was not output, the following are possible causes:

A memory shortage occurred.

A communication error occurred between the unit that allocates the system manager and the unit that does not allocate the system manager.

Check the cause of the problem from the error message that was output before the process aborted, and then take corrective action.
If no error message was output, perform checks 1 and 2 below, take corrective action, and then execute the pdstart -R or pdstart -R -t command again.

Check whether there is enough memory capacity.

Check whether a network error occurred between the unit that allocates the system manager and the unit that does not allocate the system manager.

If 1 to 2 do not apply, save the information acquired during the error, and contact the customer support center. The information to acquire in the event of an error is as follows.

In UNIX:
Files under $PDDIR/spool
Files under $PDDIR/tmp
syslogfile

In Windows:
Files under %PDDIR%\spool
Files under %PDDIR%\tmp
Event log

Psf****
*: Variable character string
An internal conflict was detected.
Save the information to be acquired in the event of an error, and contact the customer support center. The information to be acquired in the event of an error includes the files under %PDDIR%\spool, the event log (in UNIX, syslogfile), and standard error output.

Psit***
An error occurred during interval timer processing.
Check the error message that was output before ABORT for the cause of the error, take appropriate action, then re-execute. If no error message was output, save the error-related information and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.

Psji***
Psjj***
Psjk***
Psjl***
Psjm***
Psjn***
*: Variable character string other than applicable codes that follow.
An error occurred during interval timer processing. Error occurred during log processing.
If memory is insufficient, determine the reasons, take corrective action, and then restart.
If any of the error messages KFPS011xx-E, KFPS012xx-E, KFPS013xx-E, KFPS021xx-E, KFPS041xx-E, or KFPS043xx-E (xx corresponds to values between 00 and 99) were output before the process aborted, determine the cause of the error based on the error message(s), take corrective action, and then restart.
If an error message was output before the process aborted, determine the cause of the error based on that error message, take corrective action, and then restart. If no error message was output, save the error-related information and contact the customer support center. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.

Psjie42
The log swapper process failed to start. The following are possible causes:

The system log file specified as the swap target does not exist.

Memory was insufficient.

A problem occurred in the synchronization point dump file.

An error occurred in the system log file.

Psjih18
Psjih24
Psjns08
Shortage occurred in message resources.
Reconfigure the kernel (increase the values of msgtql and msgmnb).

Psjiza2
The HiRDB Datareplicator hdestart -i command was executed while the HiRDB Datareplicator linkage facility was being used, and the data linkage file was initialized. Then, the pdrplstop command was used to stop HiRDB Datareplicator.
Take the following actions:

Use the pdrplstop -f command to terminate data interlock processing.

When there is an unreplicated system log, use the data linkage recovery facility of HiRDB Dataextractor or HiRDB Datareplicator to recover consistency between extraction and replication of the data linkage.

Execute the hdestart -i command provided by the HiRDB Datareplicator linkage facility, and re-create and initialize the data linkage file.

Use the pdrplstart command to start data interlock processing.

Psjiz09
Consider the following causes:

An error preventing access to the HiRDB Datareplicator installation directory occurred, such as an error on the disk on which HiRDB Datareplicator is installed.

The addressing modes of HiRDB and HiRDB Datareplicator differ.

HiRDB Datareplicator is not installed.

Take corrective action based on the results of the following checks:

Check whether an error has occurred that prevents access to the HiRDB Datareplicator installation directory, such as an error on the HiRDB Datareplicator installation disk in the server machine with the unit that output the message. If so, eliminate the error and re-execute.

Check if the addressing mode used by the unit that output the message is the same as the addressing mode used by HiRDB Datareplicator. If the HiRDB addressing mode differs from that of HiRDB Datareplicator, replace the addressing mode of HiRDB Datareplicator with that of HiRDB, and re-execute.

Check if HiRDB Datareplicator is installed on the server machine with the unit that output the message. If it is not installed, install HiRDB Datareplicator and re-execute.

If none of the preceding reasons is applicable, contact the customer support center.

Psjjd0c
The acquisition of a synchronization point dump file could not be continued due to a network problem; the system terminated abnormally.
Eliminate the cause of the error, and then restart HiRDB.

Psjjt36
Memory is insufficient.
The process private area is insufficient. Set the memory allocation to the estimated value. Alternatively, quit unneeded processes.

Psjke01
A temporary memory shortage occurred.
Check the cause of the memory shortage, take corrective action, and then restart HiRDB.

Psjmg01
Shortage occurred in memory or system file table.
Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute.
If no error message was output, back up the error-related information and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.

Psjmg60
The aio library cannot be used.
Determine whether the OS is in a status in which it can use the aio library. Check the specification value for the pd_log_dual_write_method for server definitions.

Psjmg62
Not enough memory.
There is not enough memory for the process-private area. The memory requirements should be reviewed.

Psjmk05
Psjmk12
Psjmk22
Psjmk34
Psjmk35
Psjmk56
The pdlogunld command (including when the automatic log unloading facility is executing the log) or the pdlogchg command was forcibly terminated.
This problem can occur in the following situations, depending on the status of HiRDB:

When the pdstop -f command is executed

When the pdstop -z command is executed

When the system is switched over

During forcible termination of the command process using the Ctrl+C or OS kill (pdkill on Windows) command

For cases 1 to 4 at left, recovery processing will be performed upon restart or as a result of restart at the system switchover destination, so there is no problem.
Using the pdlogls command and pdlogucat command, check the status of the system log file and contents of the unload log file. If processing is not complete, re-execute the pdlogunld or pdlogchg command.
For cases other than 1 to 4 at left, save the acquired information and contact the customer support center. The information to be acquired in the event of an error includes the files under %PDDIR%\spool, the event log (in UNIX, syslogfile), console messages, and standard error output.

Psjn022
Psjn031
Psjn039
An error occurred as the log swapper process was starting.
Based on the error message preceding the abort, take corrective action, and then re-execute the command.
If there is no error message, save the information to be saved in the event of an error, and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.

Psjn051
An error occurred while the log server process was stopped.
Files under %PDDIR%\lib\sysconf or %PDDIR%\lib\sysdef cannot be opened properly.
Check whether HiRDB was installed correctly.

Psjn052
Psjn053
An error occurred while the log server process was stopped.

Psjn060
System file required for log output cannot be opened.

Psjn094
Memory is insufficient.
Shortage occurred in the process private area. Re-estimate the memory.

Psjn0g5
The log server process failed to start. Memory may be insufficient.
If memory is insufficient, determine the reason why memory is insufficient, take corrective action, and restart. If an error message was output before the process aborted, determine the cause of the error based on that error message, take corrective action, and restart. If no error message was output, save the error-related information and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.

Psjn0g6
An error occurred as the status server process was starting.
Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute.
If no error message was output, back up the error-related information and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.

Psjn0gf
A status file update error occurred.
A shortage occurred in the process private area. Re-estimate the required memory.

Psjn140
An error occurred while the log server process was stopped.

Psjn189
Memory is insufficient.

Psjn308
The system log file specified as the swap target does not exist.
Take corrective action according to the message output immediately before KFPS01220-E.

Psjn320
Processing cannot be continued due to an error such as a communication error.
Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute.
If no error message was output, back up the error-related information and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.

Psjn321
Processing cannot be placed on wait status, because all management blocks have been used. Or, an error occurred while processing was on wait status.
Determine the reason code in the message log, take corrective action, and then restart the unit.

Psjn327
Memory shortage, network error, or timeout occurred.

Psjn328
A communication error occurred during the system log swapping process.
If the file under /dev/HiRDB/pth has been deleted, restart HiRDB.
If this does not resolve the problem, take the corrective action Psjn***.

Psjn329
Memory shortage or network error occurred.
Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute. If no error message was output, back up the error-related information and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.

Psjn335
Psjn336
Psjn338
Psjn341
Psjn345
Psjn347
Psjn349
Psjn352
Psjn354
Psjn355
Psjn357
Psjn359
Lock release wait status occurred, but processing cannot be placed on wait status because all management blocks have been used. A process area to be managed by the OS library cannot be allocated.
Re-estimate the memory.

Psjn381
The system log file specified as the swap target does not exist.
Take corrective action according to the message output immediately before KFPS01220-E.

Psjn625
System file required for log output cannot be opened.
Files in %PDDIR%\lib\sysconf or in %PDDIR%\lib\sysdef cannot be opened. Check if HiRDB has been installed correctly.

Psjnc20
Psjnd20
Psjne06
Psjne15
Psjnf04
Lock release wait status occurred, but processing cannot be placed on wait status because all management blocks have been used. A process area to be managed by the OS library cannot be allocated.
Re-estimate the memory.

Psjnf07
The system log file specified as the swap target does not exist.
Take corrective action according to the message output immediately before KFPS01220-E.

Psjnf16
Processing cannot be continued due to an error such as a communication error.
Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute. If no error message was output, back up the error-related information and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.

Psjng02
Psjng04
Lock release wait status occurred, but processing cannot be placed on wait status because all management blocks have been used. A process area to be managed by the OS library cannot be allocated.
Re-estimate the memory.

Psjng05
Memory shortage or network error occurred.
Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute. If no error message was output, back up the error-related information and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.

Psjng10
Memory shortage, network error, or timeout occurred.
If the HiRDB version changed around the time when HiRDB restarted, restore the previous version. Terminate HiRDB normally before restoring the previous version.
If this does not resolve the problem, save the event log (in UNIX, syslogfile) and the files under %PDDIR%\spool, and contact the customer support center.

Psjnh51
Error was detected in the log server's status information while starting HiRDB.

Psjnk03
Network error occurred.
Check the cause of the network error, take appropriate action, then restart HiRDB.

Psjnk04
Psjnk05
Memory is insufficient.
Shortage occurred in the process private area. Re-estimate the memory.

Psjnk11
Network error occurred.
Check the cause of the network error, take appropriate action, then restart HiRDB.

Psjlm25
System file required for log output cannot be opened.
Check if HiRDB has been installed correctly.

Psjlm52
Memory is insufficient.
Re-estimate the memory.

Psjnm27
Psjnm28
Psjnm29
Psjnm30
Memory shortage or network error occurred.
Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute. If no error message was output, back up the error-related information and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.

Psjnr31
Database recovery processing was invalid during restart.
Check the reason code in the KFPS01267-E message that was output immediately previously, and re-execute.

Psjnr38
Invalid data was detected in the event log file.
Save the files under %PDDIR%\spool as well as the system log file, and then take one of the following actions:

When the HiRDB version was changed even though HiRDB had not terminated normally during the previous operation:
Restore the previous HiRDB version.

When the contents of the previous version or the contents of other systems were changed inadvertently because the entire disk or the HiRDB file system area for the event log file was restored accidentally:
Restore the event log file. If this is not possible, first terminate HiRDB forcibly, then restore the database to the backup acquisition point (or to the last unload log acquisition point if an unload log file is available). Then, recover the database by re-executing the jobs that were entered after the backup was made.

When the event log was not loaded after synchronization point dumps had been enabled:
The contents of the status file or synchronization point dump file may be corrupt. First, terminate HiRDB forcibly, then restore the database to the backup acquisition point. Then, recover the database by re-executing the jobs that were entered after the backup was made.

When a log application site was running, paircreate or pairresync was executed against the pair volume that stores the system log file, and a form copy was executed
Restart the log application site HiRDB, and restart the log application. If the log application cannot be restarted, perform preparation for log application, and then restart the log application. If a site takeover for disasters was performed, see the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide, and take any required actions.

In all other cases:
Contact the customer support center.

Psjnr46
An error occurred in the creation of the transaction information file.
The primary causes are as follows:

Insufficient process native area

Access to the %PDDIR%\spool\pdtrninf directory failed

Insufficient volume on the disk where the %PDDIR%\spool\pdtrninf directory resides

The actions for items 1-3 to the left are as follows:

Take action based on the instructions given in the KFPO00106-E message.

Determine the cause of the failure to access the %PDDIR%\spool\pdtrninf directory, and take measures to enable the HiRDB administrator to read and write files in the %PDDIR%\spool\pdtrninf directory. If there is no %PDDIR%\spool\pdtrninf directory, set up HiRDB again.

Remove any unnecessary files to increase the free space on the disk.

If the error cannot be resolved, save the information acquired during the error, and contact the customer support center. The information to be saved includes the following:

All files under %PDDIR%\spool

Event log (in UNIX, syslogfile)

Psjnt04
Lock release wait status occurred, but processing cannot be placed on wait status because all management blocks have been used. A process area to be managed by the OS library cannot be allocated.
Re-estimate the memory.

Psjnu07
Processing cannot be placed on wait status, because all management blocks have been used. Or, an error occurred while processing was on wait status.
Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute. If no error message was output, back up the error-related information and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.

Psjnu08
Psjnu12
Psjnu17
Lock release wait status occurred, but processing cannot be placed on wait status because all management blocks have been used. A process area to be managed by the OS library cannot be allocated.
Re-estimate the memory.

Pslg***
*: Variable character string
Error occurred during message log output processing.
Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute. If no error message was output, back up the error-related information and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.

Pslk***
*: Variable character string
Error occurred during lock control processing.
If no error message was output, save the information to be acquired in the event of an error, and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp and the default error output.

Psna***
*: Variable character string other than the Psna code that follows.
Error occurred during name service processing.

Psna005
The port number allocated to HiRDB is being used by another program; or a previously activated HiRDB process (in UNIX, a zombie process) remains.
If a bind system call error occurred, take one of the following actions, as appropriate to the cause:

If the port is being used by another program
Revise the contents of the system common definition pd_name_port operand or the -p option of the pdunit operand, allocate port numbers that are not duplicates, and then restart.

If the previously activated process (zombie process in UNIX) remains behind
Use the pdkill command in Windows to cancel the process. In UNIX, use the kill command to cancel the zombie process.

Psnd***
*: Variable character string other than those in the Psnd codes that follow.
Error occurred during system operation control processing.
If no error message was output, back up the error-related information and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.

Psnd530
Psnd537
Psnd538
Psnd53a
Shortage occurred in the area that is used to store the identifiers of the users accessing this server.
Re-execute when there are fewer users accessing this server. Terminate any remaining transactions. If this error occurs frequently, terminate HiRDB normally and increase the following server-related definition values:

HiRDB/Single Server
pd_max_users

HiRDB/Parallel Server
If the error occurred at a front-end server: pd_max_users
If the error occurred at the back-end server: pd_max_bes_process
If the error occurred at the dictionary server: pd_max_dic_process

Psnd678
Psnd679
Because status information on a recovery unnecessary front-end server unit is STOP(A); even though an attempt was made to abort that unit and restart, the attempt failed, and the system terminated abnormally.
Restart the unit that terminated abnormally.

Psnda09
Process private area shortage occurred.
Re-estimate the memory requirement for the process private area.

Psndb22
The number of utilities executed concurrently has reached the upper limit.

Specify 1 in the pd_utl_exec_mode operand.

If 1 is specified in the pd_utl_exec_mode operand, check to see if utilities are executed concurrently in excess of the value of the pd_max_users operand.
If utilities are executed concurrently in excess of the value of the pd_max_users operand, reduce the number of concurrently running utilities.
If the value is not exceeded, save the information to be acquired in the event of an error, and contact the customer support center. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and the event log (in UNIX, syslogfile) on the system manager and the unit that output this ABORT code.

Psndc04
Psndc05
Psndc06
Psndc07
Psndc08
Psndh1a
Psndh2c
Psndh2e
Psndh2h
The unit with a system manager stopped or a network fault occurred, causing communications failure with the system manager. The affected unit is terminated.
If the unit with a system manager is stopped, check the cause of the stoppage of the system manager unit, based on the error message preceding the abort code, and resolve the error. After that, restart HiRDB.
If the error occurred even when the system manager unit was running, a network fault must be suspected. Investigate the problem by seeing 4.1 Detail codes for RPC-related errors.
If the cause of the problem cannot be identified, save the files under %PDDIR%\spool and the system log files for the system manager unit and the unit that generated the abort code, and contact the customer support center.

Psndc24
Psnds53
There is insufficient process native area.
Determine the cause of the insufficient process native area, take appropriate action, and then restart HiRDB. If the error cannot be resolved, save the information acquired during the error, and contact the customer support center.
The information to be acquired in the event of an error includes the files and event log (in UNIX, syslogfile) under %PDDIR%\spool on the system manager unit and the unit that output this abort code.

Psndd02
During transaction commit processing, either an error occurred in a unit with a transaction branch, or a transaction could not be determined because a network error occurred.
The transaction can be determined by forcibly terminating and restarting the applicable unit.
If a unit with a transaction branch is not running, start the unit.
If a network error occurred, eliminate the cause of the network error.
If the cause is none of the preceding, eliminate the cause of the error based on the message output immediately before this abort code. If no message was output, contact the customer support center.

Psndd04
Psndd05
Transaction, command, or utility recovery could not be communicated because the system manager unit had stopped or a network error occurred. Consequently, the unit was stopped.
If the system manager unit had stopped, determine the reason from the error message that was output before processing was aborted, correct the error, and restart HiRDB.
If a network error occurred, recover the network and then stop the HiRDB system forcibly with the pdstop -f command, and then restart the HiRDB system. Restart the system, not the unit.
If the cause cannot be determined, save the files under %PDDIR%\spool and the system log files in both the system manager unit and the unit where this abort code was output, and contact the customer support center.

Psndd18
Psnds42
An error occurred when a unit was being started.
Resolve the cause of the error based on the preceding message.
If there is no message output, contact the customer support center.

Psndm19
Master directory is being used by another HiRDB system.
Two HiRDB systems cannot be started concurrently if the first HiRDB file name in the master directory RDAREA is the same in both system common definitions. Recheck the system common definitions and restart.

Psndm20
A unit uses character codes that are not compatible with the character codes of the system manager.
The character code type for the unit and the character code type for system manager do not match; the HiRDB system cannot be started.
Refer to the information in the KFPS05206-E message, and set the same character codes type.
In UNIX:
To change the codes type, execute pdsetup -d, enter y in response to the response message, then specify the correct character codes type with pdsetup -c.
In Windows:
Refer to the related messages, eliminate the cause of the error, and then restart HiRDB.

Psndm80
The character codes used by the HiRDB that was started are not compatible with the character codes used by HiRDB when the database was initialized.
Take action appropriate to the KFPH20011-E message.

Psnd098
Psnd234
Psnde70
Psnde80
Psndsp0
Psndsp1
Psndsp2
Psndsp3
Error occurred during HiRDB unit termination processing.
If the termination processing is planned termination, all units are terminated forcibly.
Referring to the KFPS05111-E message output immediately before the abort code, determine the cause and eliminate the error. Then, restart HiRDB.
If the process aborted during planned termination processing, make sure that all units are stopped before restarting HiRDB. If there are any active units, stop all units by either executing the pdstop -f command from a server machine that has the system manager, or by executing the pdstop -z command from a server machine with an active unit. Then, restart HiRDB.
Use the following procedure to check if the units are stopped:

Check the event log (in UNIX, syslogfile) of each unit for KFPS01821-E messages or KFPS01841-I messages (termination mode of FORCE)

Refer to KFPS01850-I messages (termination mode of FORCE) output to the event log (in UNIX, syslogfile) of the unit where the system manager resides

If the cause cannot be determined even after referring to the KFPS05111-E message, save the files under %PDDIR%\spool, and the event log (in UNIX, syslogfile) for the unit, and contact the customer support center.

Psndv03
Communication with the system manager failed when upgrading a dictionary or when migrating an SQL object. To avoid malfunctioning due to communication failures, unit activation was suspended.

If the system manager unit is stopped:
Determine the reason why the unit stopped based on the error message output before the process aborted, and eliminate the error. Then, restart the HiRDB system. To restart, execute the pdstart command without any options.

If a unit without the system manager is stopped:
Determine the reason why the unit stopped based on the error message output before the process aborted, and eliminate the error. Then, forcibly terminate the HiRDB system with the pdstop -f command, and restart it. To restart, execute the pdstart command without any options.

If a network error occurred:
After recovering the network, forcibly terminate the HiRDB system with the pdstop -f command, and restart it. To restart, execute the pdstart command without any options.

Other than the above:
Restart the HiRDB system. If this error continues to occur, save the files under %PDDIR%\spool and the system log files on the system manager unit and on the unit that output this abort code, and then contact the customer support center.

Psp****
*: Variable character string other than those in the Psp codes that follow.
Error occurred during process control processing.
Check the error message that was output before ABORT for the cause of the error, take appropriate action, then re-execute.
If no error message was output, save the error-related information and contact the customer support center.
The error-related information includes the files under %PDDIR%\spool and the standard error output.

Psp0766
Psp0767
Psp5008
Psp5011
Pspk001
Pspk002
The HA monitor, Hitachi HA Toolkit Extension, or the cluster software has not been started or is unavailable for connection. Therefore, HiRDB cannot be started in server mode.
Either a KFPS00727-E message or KFPS00728-E message was generated before this abort code. Take corrective action according to these messages. If an HA monitor, Hitachi HA Toolkit Extension, or cluster software message is output, also take corrective action in reference to those messages.

Psp0777
This abort code is output if you execute the pdxdsstop -f command to forcibly terminate the XDS.
Corrective action is unnecessary due to the abort code that was output as a result of forcibly terminating the XDS.

Psp4017
If -prc terminated abnormally with this ABORT code during HiRDB startup, possible reasons are as follows:

Contents of the hosts file are invalid.

Default host was not set up correctly.

Network has not been started.

Correct the hosts file, default host, or network setup, then re-execute HiRDB.

The following causes are possible in UNIX:

There is no access privilege to the /dev/HiRDB/pth directory, or it does not exist

A device is mounted under the name /dev/HiRDB

If the directories /dev/HiRDB and /dev/HiRDB/pth exist, delete them and use the pdsetup command to perform setup. If a device is mounted to /dev/HiRDB, unmount /dev/HiRDB, and then use the pdsetup command to perform setup again.

In Linux ES 4 and AS 4, the following are possible causes:

Permissions for the directories /etc/udev/devices/HiRDB or /etc/udev/devices/HiRDB/pth are invalid

Both the /etc/udev/devices directory and the /lib/udev/devices directory exist

If there are directories for which you do not have valid permissions, delete those directories, and then use the pdsetup command to perform setup. In the case where the /etc/udev/devices directory and the /lib/udev/devices directory both exist, if the /etc/udev/devices/HiRDB directory and /etc/udev/devices/HiRDB/pth directory do not exist, create them as a superuser and then restart the OS. However, set the permissions for the /etc/udev/devices/HiRDB and /etc/udev/devices/HiRDB/pth directories as 755 and 777, respectively.

In Linux 5 and later, also check the following:

Permissions for the directories /lib/udev/devices/HiRDB or /lib/udev/devices/HiRDB/pth are invalid.

Delete the directories for which permissions are invalid, and then use the pdsetup command to perform setup.

Psp4084
Desktop creation failed.
Stop any other processes that are running. Also, calculate the amount of desktop heap memory being used by HiRDB, specify in the pd_max_server_process operand a value at or below the maximum value for the desktop heap memory, and then restart HiRDB.

Psp7013
The post-processing process of HiRDB aborted.
The following are possible causes:

The disk holding the HiRDB operation directory is too small, or there are insufficient i-nodes.

The HiRDB administrator user ID cannot log in.

A failure occurred during acquisition of a network, host, or entry.

Check the error cause from the error message that was output before processing was aborted, and then re-execute.
If an error message is not output and none of the causes listed on the left is applicable, save the information collected at error time and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool, the event log (in UNIX, syslogfile), and standard error output.

Psp7019
Because the number of times that the server process terminated abnormally while the abnormal termination monitoring facility was monitoring exceeded the value specified in the pd_down_watch_proc operand, HiRDB (or the applicable unit for HiRDB/Parallel Server) terminated abnormally.
To prevent HiRDB from terminating abnormally due to the server process terminating abnormally, either omit the pd_down_watch_proc operand, or specify 0. For details about the abnormal termination monitoring facility, see the HiRDB Version 9 System Operation Guide.

Psp7024
Error occurred during HiRDB shutdown processing.
The following are possible causes:

The pdstop command was forcibly terminated

HiRDB shutdown processing terminated abnormally

If another message was output before this message, take action based on that message. If no other messages were output, contact the customer support center.
Note that if one of the possible causes shown is applicable, the forced termination of HiRDB has been completed, and HiRDB can be restarted.

Psp8001
Request for forced termination of a server process was accepted, but the forced termination request was aborted after the process was released because it was a critical process.
Determine the reason why the request for forced termination of the process was accepted, based on the status of the executed transaction or on other messages that were output, and take corrective action as needed.
If you intentionally used the pdcancel or other command to forcibly terminate the process, you need not take any corrective action for this abort code.
On HiRDB/Parallel Server, if rollback processing on a back-end server requires 5 minutes or more to complete in response to a rollback request from a front-end server, the back-end server process may abort with this code (to speed up transaction commitment, the back-end server process is cancelled internally). You need not take any particular action when a large update for which rollback is expected to take a long time is being executed. However, if the rollback is not intentional, determine the cause of the rollback and take corrective action.

Pspc013
An error occurred during communication with the process server process.
If a command was entered during HiRDB termination processing, re-execute the command after termination processing is completed.
If timeout recurs, contact the customer support center.

Psph052
The HiRDB process server process stopped due to a user request from a source external to HiRDB. The following are possible requests by users from outside of HiRDB:

The kill command of the OS (pdkill command for Windows) was executed. This abort, however, only affects the SIGTERM signal.

Restart either HiRDB or the unit. Check to see if the kill command of the OS (or the pdkill command for Windows) has been executed. If the kill command of the OS (or the pdkill command for Windows) has not been executed, contact the customer support center.

Psrc***
Psrf***
Psrm***
Psrp***
Psrq***
Psrr***
*: Variable character string other than applicable codes that follow.
Error occurred during communication processing.
Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute. If no error message was output, back up the error-related information and contact the customer support center.
Error-related information is in files under %PDDIR%\spool and in the output from standard error.

Psrc039
During transaction processing
A timeout occurred while waiting for a response from the server during transaction startup processing.
The corresponding transaction is deactivated. Review the pd_watch_time operand value and re-execute.

While the utility was executing, during database import when XDS was started, during database export when XDS terminated, or while the command was executing
The system waited for a response from a single server, back-end server, or dictionary server, but a timeout occurred because the server did not respond within 60 seconds.
Possible reasons that a response was not returned within the server time period are as follows.

The number of processes already started on the server to which connection was being attempted has already reached the maximum number of processes that can be started, as specified in the system definitions. Therefore, new processes could not be started. As a result, the system waited for connection to the desired server but could not connect in time.

There is a heavy load on the system, so server processes could not be started in time.

The system kept waiting for a response because a network error or other issue caused communication with the server to fail.

In case 1, wait for the maximum number of processes to change or for the running processes to terminate, and then re-execute.
In cases 2 and 3, wait for the cause to be resolved and then re-execute.
When you re-execute, do so in one of the following ways according to the abort time.

If the utility is running, run it again.

If the problem occurred during database import at XDS startup, restart XDS.

If the database is being exported when XDS is terminating, use the pdqtrbwtor command to answer the KFPV56208-Q message.

If the command is running, run it again. Also, save %PDDIR%\spool and contact the customer support center.

The maximum number of processes that can be run here is specified in the pd_max_users operand for single servers, the pd_max_bes_process operand for back-end servers, and the pd_max_dic_process operand for dictionary servers.

Psrc191
Communication workload is high and data cannot be sent even when retry is executed. Or, the destination process is on a status that does not permit it to receive data for a long time.
If this does not apply, see 4.1 Detail codes for RPC-related errors.
The communication (LAN) load may be too high. Therefore, either reduce the load and re-execute the processing, or examine the SQL that was executing when the abort occurred, and consider using an SQL with a reduced processing time.
If this does not apply, see 4.1 Detail codes for RPC-related errors.
If the problem recurs after you have taken the above actions, save the information acquired during the error, and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.

Psrc304
Transaction did not terminate even though the fixed time from the previous chain RPC call elapsed.
Although the PDSWAITTIME specification time elapsed, the UAP did not issue a new SQL to the front-end server or single server being used by the UAP.
Re-execute the target service request because the request has been invalidated. Increase the time specified in PDSWAITTIME of the client environment definition and re-execute.

Psrc323
Psrc324
Attempt was made to report completion of a service to the service request source, but the service request source was not found. Or, reply cannot be sent due to a communication error.
Re-execute, because the corresponding service will be invalidated.

Psrc341
Psrc345
Psrc360
An SQL not supported by the HiRDB server was executed (this occurs when the HiRDB client version is newer than the HiRDB server version).
Determine in which SQL statement the error occurred from the HiRDB client's error log. This is the SQL statement that the HiRDB server cannot execute.
For details about the HiRDB client's error log, see the HiRDB Version 9 UAP Development Guide.

Psrc361
When executing a UAP, operation command, or utility, a failure occurred when receiving a communication message. Insufficient memory is the likely cause.
To release memory, stop all processes that can be stopped. Alternatively, set memory to the estimated value. If plenty of memory exists, consider another cause. If this is the case, save the error-related information, and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.

Psrc362
Psrc363
A failure occurred responding to an SQL query. Insufficient memory is the likely cause.
Eliminate the cause of the error and re-execute the utility.

Psrc397
Too much time elapsed between service completion and the next service request. Data will be recovered by terminating the process forcibly. (Some type of error may have occurred in the service-requesting process or in the network, preventing the next service request from being sent.)

Psrc398
Psrc399
Requested service response cannot be returned to the requesting source. Data will be recovered by terminating the process forcibly. (An error may have occurred in the network or there was no requesting process, preventing the response from being returned.)

Psrc661
Allocation of process private memory for storing information received from the UAP (for example, INSERT data) failed.
Either reduce the number of processes in the system or review the memory requirements.

Psrc712
When a UAP was being processed in a server selected by a chained RPC, the system detected a failure at the host executing the UAP or a network disconnection while waiting for a service request from the UAP.
Re-execute the target service request because the request has been invalidated.

Psrc752
When a UAP was being processed in a server selected by a chain RPC, the system detected cancellation of UAP execution while waiting for a service request from the UAP.

Psrc780
An error occurred during processing of inbound communication. No requests can be accepted for a period of 3 minutes.
Take corrective action by seeing the preceding KFPS00353-E message.

Psrd***
*: Variable character string other than those in the Psrd codes that follow.
Error occurred during system operation control processing.
Check the error message that was output before ABORT for the cause of the error, take appropriate action, then re-execute. If no error message was output, back up the error-related information and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool, the event log (in UNIX, syslogfile), and standard error output.

Psrd111
Psrd112
Psrd121
An error occurred during unit termination processing.
If the error occurs during log application site termination or during a planned termination, all units are terminated forcibly.
Referring to the KFPS05111-E message output immediately before the abort code, determine the cause and eliminate the error. Then, restart HiRDB.
If the error occurred during a planned termination or during log application site termination, confirm that all units were terminated, and then restart HiRDB. If some units were not terminated, execute the pdstop -z command on the servers where all units were to be terminated, and then restart HiRDB.
Check the following to make sure the units are stopped:

Check the event log (in UNIX, syslogfile) of each unit for KFPS01821-E messages or KFPS01841-I messages

Refer to KFPS01850-I messages (termination mode of FORCE) output to the event log (in UNIX, syslogfile) of the unit where the system manager resides

If the cause cannot be determined even after referring to the KFPS05111-E message, save the files under %PDDIR%\spool, and the event log (in UNIX, syslogfile) for the unit, and contact the customer support center.

Psrda31
Memory allocation failed when starting the process that monitors activation status of the other host (server machine).
Re-estimate memory. Alternatively, reduce the number of processes running on the system and re-execute.

Psrda58
Psrdp11
Psrdp12
Psrdp15
Psrdp16
Psrdp17
Psrdp18
Psrdp19
An error occurred during HiRDB system termination processing.
If termination was planned, all units other than the system manager unit are forcibly terminated.
Possible causes include a termination processing error occurring on a non-system manager unit, or a communication error.
Check the message output before the KFPS05221 message, eliminate the error, and restart HiRDB.
If the process aborted during planned termination processing, make sure that all units are stopped before restarting HiRDB. If there are any active units, stop all units by either executing the pdstop -f command from a server machine that has the system manager, or by executing the pdstop -z command from a server machine with an active unit. Then, restart HiRDB.
Check the following to make sure the units are stopped:

Check the event log (in UNIX, syslogfile) of each unit for KFPS01821-E messages or KFPS01841-I messages (termination mode of FORCE)

If the cause cannot be determined, save the files under %PDDIR%\spool, and the event log (in UNIX, syslogfile) for the unit, and contact the customer support center.

Psrda65
Psrdi54
Psrdi55
Psrdi56
Input/output processing on a status file failed.
Investigate the cause of the problem and take corrective action by seeing the preceding status file error message. After taking corrective action, restart the abnormally terminated unit.
If the cause of the problem cannot be identified, contact the customer support center.

Psrdas1
The unit with a system manager stopped or a network fault occurred, causing communications failure with the system manager. The affected unit is terminated.
If the unit with a system manager is stopped, check the cause of the stoppage of the system manager unit, based on the error message preceding the abort code, and resolve the error. After that, restart HiRDB.
If the error occurred even when the system manager unit was running, a network fault must be suspected. Investigate the problem by seeing 4.1 Detail codes for RPC-related errors.
If the cause of the problem cannot be identified, save the files under %PDDIR%\spool and the system log files for the system manager unit and the unit that generated the abort code, and contact the customer support center.

Psrdg04
Psrdt81
Psrdt83
Psrdu31
Psrdu33
Psrdu35
Psrdu39
There is insufficient process native area.
Determine the cause of the insufficient process native area, take appropriate action, and then restart HiRDB. If the error cannot be resolved, save the information acquired during the error, and contact the customer support center.
The information to be acquired in the event of an error includes the files and event log (in UNIX, syslogfile) under %PDDIR%\spool on the system manager unit and the unit that output this abort code.

Psrf201
Psrr606
An error occurred while executing the UAP, utility, or operation command. The following are possible causes:

A communication error occurred during communication between servers.

The process could not be executed because of a heavy load on the server.

Check the cause of the problem from the error message that was output before the process aborted, and then take corrective action.
If no error message was output, perform checks (1) and (2) below, take corrective action, and then re-execute the UAP, utility, and operation command.
(1) Make sure that a network error has not occurred.
(2) Make sure that the server does not have a heavy load.

Psrf203
Allocation failed for process private memory to be used to store information received from UAPs (SQL information such as INSERT data).
Either reduce the number of processes in the system or re-estimate the memory size.

Psrf301
The allocation of a received message area failed during the reception of a message. To prevent the occurrence of a no-response status due to the inability to receive messages, the system is aborted.
Free memory by terminating any processes that are running in the system that can be terminated. Or, re-estimate memory requirements.

Psrf302
The allocation of an internal communication logging information area failed. This problem is detected at process startup time. To prevent the continued execution of a process under insufficient memory conditions, the system is aborted.

Psrm107
The server processes were shut down as a result of client processes being shut down during connection processing from the client.
When the client environment variable PDCWAITTIME is omitted or when 0 is specified, incomplete transactions may remain.
Cancel any such transactions by following the instructions in Actions to be taken when a UAP does not terminate itself under When a UAP does not execute correctly in the HiRDB Version 9 System Operation Guide.

Psrp491
Data transmission failed due to the following possible reasons:

Not enough socket descriptors

Invalid contents of the hosts file

If these reasons do not apply, see 4.1 Detail codes for RPC-related errors.
The indicated service is invalidated. Either execute the command when the load is light, or take action by referring to 4.1 Detail codes for RPC-related errors.

Psrp506
Not enough internal tables

If this error occurred frequently when HiRDB was running and at the same time utilities were executed successively or executed on a multiple basis, either increase the execution interval or reduce the level of multiplicity, or increase the value of the pd_max_server_process operand.

If the error occurred while HiRDB was down, start HiRDB, and then re-execute the command.

If the problem persists after these measures are taken, contact the customer support center.

If the pdcancel command is used to cancel a high-capacity UAP while HiRDB is operating, a transaction recovery process will start for the part of the UAP that was cancelled. As a result, the total number of processes started by HiRDB will temporarily exceed the value specified for the pd_max_server_process operand.
If the pdcancel command is used to cancel a high-capacity UAP while HiRDB is operating, either reduce the number of running UAP processes until the transaction recovery process terminates, or wait until that time to execute the UAP. For the status of transaction recovery processing, it is possible to confirm whether or not the status of the second transaction of the output results of the pdls -d trn command is r or p.
If the problem recurs even after taking these corrective actions, contact the customer support center.

Psrp507
Insufficient memory
There is not enough process-private area. Review the memory requirements. Also, terminate any unneeded processes.

Psrp616
The allocation of a received message area for inter-thread communications failed. To prevent the occurrence of malfunction due to the inability to receive messages, the system is aborted.
Free memory by terminating any processes that are running in the system that can be terminated. Or, re-estimate memory requirements.

Psrq016
Psrq017
Attempt was made to report completion of a service to the service request source, but the service request source was not found. Or, reply cannot be sent due to a communication error.
Re-execute, because the corresponding service will be invalidated.

Psrq801
A failure occurred when referencing the host name used by HiRDB, or when acquiring an address. Consider the following causes:

There is no host name or IP address in the hosts file.

The system does not have reference privileges to the hosts file.

The standard host name has been changed to an incorrect one not specified in the hosts file.

If you are using DNS or WINS, the host name or IP address is not in the search database.

If you are using DNS or WINS, the system does not have reference privileges to the search database.

HiRDB uses the host name that is specified in the pdunit operand of the system common definition (%PDCONFPATH%\pdsys), which is the standard host name of the applicable server machine.
Eliminate the cause of the error and re-execute.

Psrq809
In UNIX:
The value set in the OS parameter (kernel parameter) maxfiles_lim is too small; HiRDB cannot be started.
In Windows:
Due to insufficient capacity on the installation drive, shared memory work files cannot be allocated.
In UNIX:
Reset the value of maxfiles_lim to 1024 or more.
In Windows:
On the HiRDB installation drive, allocate at least as much free space as is required for the shared memory size.

Psrq810
The maximum number of HiRDB processes defined for the unit has been exceeded.
If this error occurs frequently when commands or utilities are being executed successively or at the same time while HiRDB is running, either increase the execution interval, reduce the number of processes executing simultaneously, or increase the value of the pd_max_server_process operand.

If the pdcancel command is used to cancel a high-capacity UAP while HiRDB is operating, a transaction recovery process will start for the part of the UAP that was cancelled. As a result, the total number of processes started by HiRDP will temporarily exceed the value specified for the pd_max_server_process operand.
If the pdcancel command is used to cancel a high-capacity UAP while HiRDB is operating, either reduce the number of running UAP processes until the transaction recovery process terminates, or wait until that time for the UAP to execute. For the status of transaction recovery processing, it is possible to confirm whether or not the status of the second transaction of the output results of the pdls -d trn command is r or p.

Pssc***
*: Variable character string other than those in the Pssc codes that follow.
Error occurred during schedule processing.
Refer to the error message that was output before ABORT to check the cause of the error, take appropriate action, then re-execute.
If no error message has been output, save the error-related information and contact the customer support center.
Error-related information is in files under %PDDIR%\spool and in the output from standard error.

Pssc009
Communication resources failed to initialize.

When specifying scheduler process port numbers (-s option in the pd_service_port operand, pd_scd_port operand, or pdunit operand of the system definitions), the specified port number might be a duplication of the following port numbers. If it is a duplication, revise the contents of the scheduler process port numbers and allocate unique port numbers.
1. Port numbers that other HiRDB systems or HiRDB units operating on the same machine are using
2. Port number being used by other programs

If the above does not apply, investigate the cause by referring to 4.1 Detail codes for RPC-related errors.

Pssc410
The back-end server that is the target of the standby-less system switchover was forcibly stopped by system switchover or the pdstop command.
If this occurred while the back-end server was being forcibly terminated by system switchover or the pdstop command, there is no need to take corrective action. If it occurred in cases besides those listed above, contact the customer support center.

Pssc412
A shortage of process-private memory occurred during back-end server processing when the standby-less system switchover (effects distributed) facility was being used.
Reduce the number of processes in the system and then re-execute the command. Or, review the amount of available process-private memory.

Pssc60b
Process private memory shortage occurred while initializing the message queue.
Reduce the number of processes within the system and re-execute, or re-estimate the process private memory size.

PsscZ01
Even though the message queue monitoring duration (value of pd_queue_watch_time operand) of the message queue monitoring facility was exceeded, messages are not being flushed from the message queue. For details about the message queue monitoring facility, see the HiRDB Version 9 System Operation Guide.
For causes of message queue hold-up and corrective actions that can be taken, see the HiRDB Version 9 System Operation Guide. If these possibilities do not apply, contact the customer support center.

PsscZ70
An internal error occurred.
If there is a preceding error message, take corrective action according to that message. If there is no message output, save the information to be acquired in the event of an error, and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool and the event log (in UNIX, syslogfile) of the system manager and the unit that output this ABORT code.

Pssp***
*: Variable character string other than applicable codes that follow.
An error occurred during synchronization point dump processing.
Determine the cause based on the error message output before the process aborted, take corrective action, and re-execute. If no error message was output, back up the error-related information, and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.

Psspc01
An error occurred during automatic computing of the pd_spd_syncpoint_skip_limit operand.
Quit using automatic computing, and estimate a value for this operand. For details about how to estimate system resources, see the description of the skipped effective synchronization point dump monitoring facility in the HiRDB Version 9 System Operation Guide.

Psss***
*: Variable character string
Error occurred during status file processing.
Refer to the error message that was output before ABORT to check the cause of the error, take appropriate action, then re-execute.
If no error message has been output, save the error-related information and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.

Psss372
See Psss***.
For a HiRDB/Parallel Server, check to see if the system manager is running normally or if there has been an error on the network. If the system manager is not running normally or there has been an error on the network, check the cause of the error, resolve the error, and restart HiRDB. If the above possibilities do not apply, see the action under Psss***.

Psst***
*: Variable character string
Error occurred during statistics log processing.
Check the cause of the error based on error messages preceding the abort, take corrective action, and then re-execute the command. If there is no error message, save the information to be acquired in the event of an error, and contact the customer support center. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.

Pst***
Pstd***
Psth0r*
Psti0r*
Pstj***
Pstm0r*
Pst****
*: Variable character string other than applicable codes that follow.
Error occurred during transaction processing.
Refer to the error message that was output before ABORT to check the cause of the error, take appropriate action, then re-execute.
If no error message has been output, save the error-related information and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.

Pst80rq
The system server could not be placed on wait status.
If memory is insufficient, determine the reason why memory is insufficient, take corrective action, and restart. If an error message was output before the process aborted, determine the cause of the error based on the error message, take corrective action, and restart. If no error message was output, save the error-related information and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.

Pst86r4
An error was detected during transaction server processing.

Determine the cause of the error based on the message that was just output, and then take corrective action.

When scheduler port numbers are specified (pd_service_port operand, pd_scd_port operand, or pdunit operand -s option of the system definitions), a specified port number might be a duplication of the following port numbers. If it is a duplication, revise the contents of the scheduler port numbers and allocate unique port numbers.
1. Scheduler port numbers specified in other HiRDB systems or HiRDB units operating on the same machine.
2. Port number being used by other programs

If the error cannot be resolved by taking the corrective actions listed above, save the information acquired during the error and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.

Pst87r2

A synchronization point was not acquired during normal startup processing; the startup process is cancelled.

A synchronization point was not acquired during normal termination or planned shutdown; the termination process is cancelled.

Check the cause of the error based on the reason code indicated in the preceding KFPS02178-E message, and take corrective action.

If the system aborted during normal startup processing, resolve the error, and then restart HiRDB.

If the system aborted during normal termination or planned shutdown, it is an indication that the normal termination or planned shutdown of HiRDB failed. In this case, take corrective action, restart HiRDB as necessary, and execute the normal termination or planned shutdown of HiRDB again.

Pst8br0
A receive timeout occurred when information for recovering related transactions was being transmitted during transaction recovery processing. In UNIX, the files under /dev/HiRDB/pth were deleted while HiRDB was running.
If there is a machine for which the power is off (or the network is down), turn on the power (or bring up the network). In addition, reduce the level of multiple access to HiRDB.

PstA0m0
PstAlm7
Pst80r7
Pstf0r0
Pstclrd
Pstclr2
Pstclr3
Pstclrf
Memory allocation failed.
Re-estimate the memory. Or, reduce the number of processes in the system and re-execute. If this error recurs, contact the customer support center.

Pstb0r6
Pstb0rB
The buffer size is too small; the transaction processing is terminated.
Change the value specified in the pd_log_max_data_size operand of the server common definition for each server to the target specification value.

Pstc2r1
Unable to continue transaction recovery due to a network error; the system is abnormally terminated.
Resolve the error, and then restart HiRDB.

PstD2m1
Unrecoverable error, such as a communication error, occurred during transaction processing.
If the KFPS00992-I message was output after the process was aborted, take action based on that message. If the KFPS00990-I message was output, check its message completion type.
If no message has been output, the transaction was committed in accordance with the requested commit type.

PstD2m9
A communication error occurred during commit processing.
Check the status of the system and the network. If the transaction is not settled, use the pdcmt or pdrbk command to settle it.

Pste4p0
Due to network failure, there were continuous failures to retransmit rollback instructions to the back-end server or dictionary server within the rollback instruction retransmission time limit specified in the pd_trn_rollback_watch_time operand in the system common definition.
Determine the cause of the error based on the message that was output before this message, and then take corrective action.

Pstf0r1
An attempt was made to modify a system definition that cannot be changed during restarting.
Restart the system by resetting the values of pd_max_users, pd_max_bes_process, and pd_max_dic_process.

Pstf0ra
An attempt was made to input a record exceeding the record length stored in the status file and recorded during the last system operation. It is possible that a specification value in one of the following parameters was significantly changed: pd_max_users, pd_max_bes_process, and pd_max_dic_process.

Pstf0rc
Operation directory environment is invalid.
Check that the operation directory is set up correctly and that no change has been made to the file privilege or file contents after setup. If the error recurs after setting up the environment again, contact the customer support center.

Psth0ra
Different OLTP identifiers were set in an OLTP.
For OpenTP1, the OLTP identifier specified in the user service or user service default definition differs from the OLTP identifier specified in the transaction service definition.
Use the same OLTP identifier in both the transaction service definition and the user service default definition or user service definition.

Psth0r1
Psth0rb
Psth0rd
Psth1r0
PstD5m3
PstD6m5
PstD6mg
PstD7m4
Pst93m3
A timeout occurred due to processes contending for system resources. If transaction recovery processing is being performed, you can release the resource contention and continue transaction recovery by forcibly terminating and then restarting the applicable unit.
Reduce the number of concurrent accesses to HiRDB and re-execute. If the unit is stopped, restart it. If this error occurs frequently, contact the customer support center.

Psti***
*: Variable character string other than the Psti code that follows.
Error occurred during timer processing.
Check the error message that was output before ABORT for the cause of the error, take appropriate action, then re-execute.
If no error message was output, save the error-related information and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.

Psti0rf
Transaction service function cannot be used because the PDUSER environment variable is defined incorrectly in the OpenTP1 definition.
Check if putenv PDUSER authorization identifier/password is specified in a definition other than OpenTP1's user service definition or user service default definition, take appropriate action (delete PDUSER from OpenTP1's transaction definition), then restart OpenTP1 and HiRDB.

Pstj14j
A synchronization point was not acquired during normal startup processing; the startup process is cancelled.
Check the cause of the problem and take corrective action based on the reason code indicated in the preceding KFPS02178-E message. After corrective action is taken, restart HiRDB.

Pstj14k
A synchronization point was not acquired during normal termination or planned shutdown; the termination process is cancelled.
Check the cause of the problem and take corrective action based on the reason code indicated in the preceding KFPS02178-E message. Also, because the normal termination or planned shutdown of HiRDB failed, take corrective action, and if necessary, restart HiRDB, and execute the normal termination or planned shutdown of HiRDB.

Pstj14m
Pstj14n
A temporary memory shortage occurred.
Check the cause of the memory shortage, take corrective action, and then restart HiRDB.

Pstjf97
There is insufficient process native area.
Take action based on the instructions given in the KFPO00106-E message.

Pstmex1
Error occurred during transaction processing.
Save the files in %PDDIR%\spool, and the event log (in UNIX, syslogfile) of the unit where the error occurred, and contact the customer support center.

Pstmex2
A request for forced termination of a server process was accepted, but the request was aborted because the process was a critical one.
Determine the reason why the request for forced termination of the process was accepted, based on the status of the executed transaction or on other messages that were output, and take corrective action as needed.
If you intentionally used the pdcancel or other command to forcibly terminate the process, you need not take any corrective action for this abort code.
On HiRDB/Parallel Server, if rollback processing on a back-end server requires 5 minutes or more to complete in response to a rollback request from a front-end server, the back-end server process may abort with this code (to speed up transaction commitment, the back-end server process is cancelled internally). You need not take any particular action when a large update for which rollback is expected to take a long time is being executed. However, if the rollback is not intentional, determine the cause of the rollback, and take corrective action.

Pstu0r2
In an environment using user server hot standby or the rapid system switchover facility
While the standby system was starting, standing by, or switching over, its post-processing process detected a failure in the user server process and shut down.
In an environment using the standby-less system switchover (1:1) facility
While the alternate portion was alternating, and the normal BES unit was starting, standing by, or switching over, the normal BES unit's post-processing process detected a failure in the user server process and shut down.
If an error message was output before message KFPS01820-E indicating that the user server process is down, check the error cause from that message, take corrective action, and then restart the unit.
If no error message was output before message KFPS01820-E, the user server process might have gone down due to external factors such as the OS's kill command (the pdkill command in Windows). Check whether the user server process was forcibly terminated in this way, and then restart the unit. If the user server process was forcibly terminated by such an action, take steps to prevent such actions in the future.

Table 3-10 ABORT codes (PtXXXXX)

ABORT Code | Cause | Action
Pt00000 | An invalid data code was detected (self-contradictory). | If an error message was output immediately before the process aborted, take corrective action based on that message. If no message was output, save the files under %PDDIR%\spool and %PDDIR%\conf, and the event log (in UNIX, syslogfile), and contact the customer support center.
Pt00001 | A transmission error occurred (send).
Pt00002 | A reception error occurred. (recv).
Pt00003 | Sent text is invalid (process start).
Pt00004 | Reply text is invalid (process start).
Pt00005 | Sent text is invalid (SQL execution).
Pt00006 | Reply text is invalid (SQL execution).
Pt00007 | A communication sequence is invalid.
Pt00008 | A log block is invalid.
Pt00009 | A log record is invalid.
Pt00010 | A pdorend replication process start error occurred (pd_com_call).
Pt00011 | A pdorend replication process stop error occurred (pd_com_poll_any_replies).
Pt00012 | Branch registration failed.
Pt00013 | Branch deletion failed.
Pt00014 | An attempt to acquire the host name of the primary system failed.
Pt00015 | Assertion failed.
Pt00016 | An attempt to build table definition information failed.
Pt00017 | An attempt to deserialize table definition information failed.
Pt00018 | An attempt to start the pdorend replication process failed (connect).
Pt00019 | An attempt to stop the pdorend replication process failed (disconnect).
Pt00020 | An abnormal termination was detected on the communication target.

Table 3-11 ABORT codes (PuXXXXX)

ABORT Code
Cause
Action

Pu****
*: Variable character string
An error occurred in a utility process.
Check the error message that was output before ABORT for the cause of the error, take appropriate action, then re-execute.
If no error message was output, save the error-related information and contact the customer support center.
The information to be acquired in the event of an error includes the files under %PDDIR%\spool and standard error output.

Pu00000
Invalid data code was detected.
Contact the customer support center.

Pu00001
Transmission error occurred.

Pu00002
Management table is invalid (send).

Pu00003
Management table is invalid (receive).

Pu00004
Transmission error occurred.

Pu00100
Invalid reply text was received.

Pu00200
An internal conflict was detected during input data edit processing.
Save the files under %PDDIR%\spool, and the contents of the control information file that was specified when the utility was executed, as data, and contact the customer support center.

Pu01000
Request code is invalid (input data receive processing).

Pu01001
Request code is invalid (error message send processing).

Pu01002
Request code is invalid (index information send processing).

Pu02000
Receive error occurred (pdi_com_recv).
In the case of server termination, there is no need to contact the customer support center.

Pu02001
Preparations for communication cannot be performed.
Take action appropriate to the error message.

Pu02002
Transmission is not available due to the status.

Pu02003
Index information cannot be received.

Pu02004
Timeout occurred while waiting for a message from the server.
If the KFPA11770-I message was output by the event log (in UNIX, syslog) prior to abnormal termination, execute the utility again after termination of the definition SQL statement that was executing concurrently.
For cases other than the above, follow the corrective action described in the error messages that were output in the event log (In UNIX, syslogfile) prior to abnormal termination.

Pu02005
The utility process terminated abnormally in order to terminate the back-end server.
Take the corrective action described in the error message that was output before the process aborted.

Pu02100
COMMIT cannot be issued due to the status.
Take the corrective action described in the error message.

Pu03000
RDAREA ID is invalid.

Pu04000
An invalid server activation request was received.
Save the files under %PDDIR%\spool, and the contents of the control information file that was specified when the utility was executed, as data, and contact the customer support center.

Pu04010
An interface conflict was detected.

Pu04100
An area was destroyed by the UOC.
Correct the UOC error.

Pu04500
The status of the audit trail file is unknown.
Save the files under %PDDIR%\spool, and contact the customer support center.

Pu04600
An error occurred that prevents processing from continuing when outputting to the audit trail file.

Pu05000
An invalid plug-in function was detected.
Save the files under %PDDIR%\spool, and the contents of the control information file that was specified when the utility was executed, as data, and contact the customer support center.

Pu05100
An error was detected in the plug-in function that prevented the continuation of processing.
Correct the cause of the error by referring to the KFPY99999-E message that was output before the abnormal termination. If there is no message output, or if an error that cannot be resolved at the user level occurs, save the files under %PDDIR%\spool, and contact the customer support center.

Pu06000
An invalid utility work file was created.
Take the following actions by referring to the KFPL00703-I message:

If the number of data items stored is equal to the number of data items in the input data file, data need not be recovered.

If the number of data items stored is less than the number of data items in the input data file or no messages are output, it is impossible to determine which data items failed to be stored. In this case, reset the utility to the condition that existed before it was executed and re-execute.

This event occurs as a result of corruption in the work file under the temporary directory (%PDDIR%\tmp) created by the utility.
During the execution of the utility, do not operate on any of the files belonging to the HiRDB administrator that are stored under this directory.

Pu07000
A reception error occurred (pdi_com_recv).
Take corrective action based on the KFPL20005-E and KFPL20100-E messages output immediately before the system terminated abnormally.

Pu07001
A communication message could not be sent.
Take corrective action based on the KFPL20100-E message output immediately before the system terminated abnormally.

Pu07002
An internal conflict occurred.
Save the files under %PDDIR%\spool, and the contents of the control information file that was specified when the utility was executed, as data, and contact the customer support center.

Pu07003
An internal conflict occurred (invalid line ID).

Pu07004
An error occurred during transaction processing (start, terminate, commit, or rollback).
Take corrective action based on the KFPL20020-E message output immediately before the system terminated abnormally.

Pu07005
A process cannot be started.
Eliminate the cause of the error based on the message output immediately before the system terminated abnormally. If an error that cannot be resolved occurs, save the files under %PDDIR%\spool, and contact the customer support center.

Pu10000
Requested code is invalid (startup information receive processing).
Contact the customer support center.

Pu10001
Requested code is invalid (parameter information receive processing).

Pu10002
Contradiction was detected during row data retrieval processing.

Pu10003
Requested code is invalid (parameter information send processing).

Pu10004
Message log cannot be output.

Pu10005
Invalid data was detected in the table to be unloaded.
The database is damaged.
Check whether there is any conflict in the operation of the database. If the cause of damage cannot be found in the operating method, save the RDAREA in which the table is stored and the log for the affected server, and then contact the customer support center. Recover the database from its backup, and then unload the table.

Pu10006
An internal conflict occurred (invalid content in DAT format data conversion buffer).
Save the files under %PDDIR%\spool, and the contents of the control information file that was specified when the utility was executed, as data, and contact the customer support center.

Pu11000
An internal error occurred on reception of an unexpected request code.
Contact the customer support center.

Pu11111
A commit cannot be performed.
Eliminate the cause of the error based on the KFPL20020-E message output immediately before the system terminated abnormally. If an error that cannot be resolved occurs, save the files under %PDDIR%\spool, and contact the customer support center.

Pu12002
Processing results cannot be reported due to a communication error.
The system terminated abnormally because processing results could not be reported. However, free pages have been released, and the database can be accessed. If any unreleased free pages remain when you execute the pddbst command, eliminate the cause of the error by referring to any communication-related error message output immediately before the system terminated abnormally. Then, re-execute the command. If an error that cannot be resolved occurs, save the files under %PDDIR%\spool, and contact the customer support center. Note that this abort code will also cause the server to terminate abnormally if the utility server that outputs the results list terminates abnormally following a system switchover while the utility is running.

Pu13000
There is a mistake in the startup parameter of the pdreclaim command.
If you are currently doing so, do not specify a table or an index with the -k option of the pdrorg command. In other cases, save the files under %PDDIR%\spool, and contact the customer support center.

Pu15100
Error was detected in the plug-in function that prevented the further continuation of processing.
Correct the cause of the error by referring to the KFPY99999-E message that was output before the abnormal termination. If there is no message output or if an error that cannot be resolved at the user level occurs, save the files under %PDDIR%\spool, and contact the customer support center.

Pu20000
Open processing was attempted on a file with an invalid path name.
Determine whether the path name of the file is a null value. If the specification of the path name is correct, save the files under %PDDIR%\spool, and contact the customer support center.

Pu20001
An error occurred during transaction processing (startup, termination, commit, or rollback).
Save the files under %PDDIR%\spool, and contact the customer support center.

Table 3-12 ABORT codes (PxXXXXX)

ABORT Code
Cause
Action

Pxe7500
Error that prevents continued processing was detected during execution of the dictionary export/import utility.
The error cause is output in the KFPX18430-E message.
Contact the customer support center.

Pxi0002
HiRDB file write error occurred.
Save the files under %PDDIR%\spool and contact the customer support center.

Pxi0007
RPC communication ID is invalid.

Pxj0001
JAR file transfer between hosts failed.
Re-execute the command. If the error occurs again after re-execution, contact the customer support center.

Pxj0002
Invalid interface was detected while analyzing the definition file.
Contact the customer support center.

Pxj0003
Contradiction was detected while analyzing pd_java_archive_directory.

Pxj0004
Contradiction was detected while analyzing the pdstart command parameters.

Pxm0001
Allocation of text area failed.
Communication area cannot be allocated. Take action appropriate to the KFPX24201-E message.

Pxm0002
HiRDB file write error occurred.
Save the files under %PDDIR%\spool and contact the customer support center.

Pxm0003
Internal conflict occurred in the dictionary.
Ensure that the dictionary table recovery and reorganization procedures are correct. If the procedures are correct, save the files under %PDDIR%\spool, back up the data dictionary RDAREA by specifying -Mr in pdcopy, and contact the customer support center.

Pxm0004
Error occurred during global buffer allocation.
Save the files under %PDDIR%\spool and contact the customer support center.

Pxm0005
Internal conflict occurred in the directory.
Ensure that the master directory RDAREA recovery procedure and the data dictionary RDAREA recovery and reorganization procedures are correct.
If the procedures are correct, save the files under %PDDIR%\spool and \dbenv, back up the master directory RDAREA and data dictionary RDAREA by specifying -Mr for pdcopy, and contact the customer support center.

Pxm0006
Internal conflict occurred in the global buffer.
Save the files under %PDDIR%\spool and \dbrv and contact the customer support center.

Pxm0009
Transaction commit or rollback failed.
Eliminate the cause of the error based on the KFPX24214-E message output immediately before the system terminated abnormally. If an error that cannot be resolved occurs, save the files under %PDDIR%\spool, and contact the customer support center.

Pxv0001
Transaction commit or rollback processing failed.
Eliminate the cause of the error based on the KFPX24400-E message output immediately before the system terminated abnormally. If an error that cannot be resolved occurs, save the files under %PDDIR%\spool, and contact the customer support center.

Pxv0002
Internal conflict occurred in the dictionary.
Ensure that the dictionary table recovery and reorganization procedures are correct. If the procedures are correct, save the files under %PDDIR%\spool and the backup of the data dictionary RDAREA obtained before the version upgrade, and contact the customer support center.

Table 3-13 ABORT codes (PyXXXXX)

ABORT Code
Cause
Action

Pyp1101
A plug-in requested abnormal termination.
Take action based on the KFPY03001-E message.

Pysf001
Internal conflict was detected.
Contact the customer support center.

Pysf002

Pysf007
An error occurred in a plug-in call during transaction processing.
If the KFPY99999-I message is output, take action according to this message. If HiRDB is terminated after an action was taken, restart HiRDB.
If no KFPY99999-I message was output, save the files under %PDDIR%\spool, %PDDIR%\tmp, and %PDDIR%\plugin, and the event log (in UNIX, syslogfile), and contact the customer support center.

Pysf008
An error occurred in a plug-in call triggered by the termination of the transaction recovery process.

Pysf009
An error occurred in a plug-in call triggered by the start of the pdrstr process or user server process.

Pysf00a
An error occurred in a plug-in call triggered by the termination of the pdrstr process or user server process.

Pysf00b
An error occurred in a plug-in call triggered by the start of the redo process.

Pysf00c
Internal conflict was detected.
Contact the customer support center.

Pysf00d
An error occurred in a plug-in call triggered by the termination of the redo process.
If the KFPY99999-I message is output, take action according to this message. If HiRDB is terminated after an action was taken, restart HiRDB.
If no KFPY99999-I message was output, save the files under %PDDIR%\spool, %PDDIR%\tmp, and %PDDIR%\plugin, and the event log (in UNIX, syslogfile), and contact the customer support center.

Pysf00e
Internal conflict was detected.
Contact the customer support center.

Pysf00f
An error occurred in a plug-in call triggered by the termination of the transaction recovery process.
If the KFPY99999-I message is output, take action according to this message. If HiRDB is terminated after an action was taken, restart HiRDB.
If no KFPY99999-I message was output, save the files under %PDDIR%\spool, %PDDIR%\tmp, and %PDDIR%\plugin, and the event log (in UNIX, syslogfile), and contact the customer support center.

Pysf010
Internal conflict was detected.
Contact the customer support center.

Pysf012
An error occurred in a plug-in call at the thread startup timing.
If the KFPY99999-I message is output, take action according to this message. If HiRDB is terminated after an action was taken, restart HiRDB.
If no KFPY99999-I message was output, save the files under %PDDIR%\spool, %PDDIR%\tmp, and %PDDIR%\plugin, and the event log (in UNIX, syslogfile), and contact the customer support center.

Pysf013
An error occurred in a plug-in call at the thread termination timing.

Pysf015
An error occurred in a plug-in call triggered by the start of the transaction recovery process.

Pysf016
An error occurred in a plug-in call at the transaction prepare processing timing.

Pysf017
An error occurred in a plug-in call at the transaction commitment processing timing.

Pysf018
An error occurred in a plug-in call at the transaction commitment processing timing.

Pysf019
An error occurred in a plug-in call triggered by the start of the pdstr process thread.

Pysf01a
An error occurred in a plug-in call triggered by the termination of the pdstr process.

Pysf01b
An error occurred when the front-end server was being started.
If the message KFPY01001-E, KFPY01002-W, KFPY01003-E, KFPY01004-E, KFPY01005-E, or KFPY01012-E is output, take action according to the message. If a unit is already started, normally terminate it and then restart HiRDB.
If the above messages were not output, save the files under %PDDIR%\spool, %PDDIR%\tmp, and %PDDIR%\plugin, and the event log (in UNIX, syslogfile), and contact the customer support center.

Pysf01c
An error occurred when the back-end server was being started.

Pysf01d
An error occurred when the dictionary server was being started.
If the message KFPY01002-W, KFPY01005-E, or KFPY01007-E is output, take action according to the message. After that, restart HiRDB if it has been terminated. If a unit is already started, normally terminate it and then restart HiRDB.
If the above messages were not output, save the files under %PDDIR%\spool, %PDDIR%\tmp, and %PDDIR%\plugin, and the event log (in UNIX, syslogfile), and contact the customer support center.

Pysf01e
An error occurred in a plug-in call that triggers start or termination of the rollback process.
If the KFPY99999-I message is output, take action according to this message. If HiRDB is terminated after an action was taken, restart HiRDB.
If no KFPY99999-I message was output, save the files under %PDDIR%\spool, %PDDIR%\tmp, and %PDDIR%\plugin, and the event log (in UNIX, syslogfile), and contact the customer support center.

Pysf01f
Error occurred while calling a server startup process plug-in.

Pysf020
Internal conflict was detected.
Contact the customer support center.

Pys0001
Pys0002
Pys0003
Pys0004
Pys0005
Pys0006
Pys0007
Pys0008
Pys000b
Pys000c
Pys000d
Pys000e
Pys000f
Pys0010
Pys0011
Pys0012
Pys0013
Pys0014
Pys0015
Pys0016
Pys0017
Pys0018
Pys0019
Pys001a
Pys001b
Pys001c
Pys001d
Pys001e
Pys001f
Pys0020
Pys0021
Pys0022
An internal conflict was detected
Save the files under %PDDIR%\spool, %PDDIR%\tmp, and %PDDIR%\plugin, and the event log (in UNIX, syslogfile), and contact the customer support center.

Table 3-14 ABORT codes (PiXXXXX)

ABORT Code
Cause
Action

Pia4010
An attempt was made to create a message queue identifier, but the system-determined number of message queue identifiers for the entire system has exceeded the limit.
Revise the message queue estimation formula to increase the number of message queue identifiers, and restart HiRDB.

Pia4011
A message send/receive error has occurred.
If message queue identifiers for users have been removed from the system, restart HiRDB. If that is not the case, save the files under %PDDIR%\spool, and then restart HiRDB. Also, contact the customer support center.

Pia*****
*: Variable character string
An internal conflict was detected.
Save the files under %PDDIR%\spool, and restart HiRDB. Also, contact the customer support center.

Table 3-15 ABORT codes (EhiXXXXX)

ABORT Code | Cause | Action
Ehi0001 | An error occurred during limit count setting for concurrent processing of database import or export. | Save the file under %PDDIR%\spool, and contact the customer support center.
Ehi0002 | An error occurred during registration of the database import or export processing queue.

Table 3-16 ABORT codes (EhmXXXXX)

ABORT Code | Cause | Action
Ehm0001 | Invalid interface information was found inside the XDS during a search of the memory database. | Save the file under %PDDIR%\spool and the syslogfile, and contact the customer support center.

Table 3-17 ABORT codes (EhxXXXXX)

ABORT Code
Cause
Action

Ehx0003
An invalid return value was detected during index information file operations.
Save the file under %PDDIR%\spool and the syslogfile, and contact the customer support center.

Ehx0006
An invalid index page was detected in the memory database.
Save the following files, and contact the customer support center.

Files under %PDDIR%\spool

syslogfile

XDS database definitions

Ehx0010
An invalid index page was detected in the memory database.
Save the following files, and contact the customer support center.

Files under %PDDIR%\spool

syslogfile

XDS database definitions

Ehx0011
The interface information in the XDS during indexing is invalid.
Save the file under %PDDIR%\spool and the syslogfile, and contact the customer support center.

Ehx0012
An invalid data page was detected in the memory database.
Save the following files, and contact the customer support center.

Files under %PDDIR%\spool

syslogfile

XDS database definitions

4. Error Detail Codes

This chapter describes detail codes for RPC-related errors and system-related errors, as well as system call return codes and communication error codes.

Organization of this chapter

4.1 Detail codes for RPC-related errors

4.2 Detail codes for system-related errors

4.3 System call return codes

4.4 Communication error codes

4.1 Detail codes for RPC-related errors

RPC-related errors are output in cases such as the following:

During communication between the HiRDB server and HiRDB client

During communication between HiRDB servers

During the initialization of communication resources when a process is started

If an RPC-related error is output, check the detail codes in Table 4-2, as well as the contents of frequently occurring causes in Table 4-1. Also, if an error message caused by a communication error is output, in some cases RPC-related detail error codes do not appear in the message. In this case, too, contents of frequently occurring causes in Table 4-1 should be checked.

Note that even when a detail code for RPC-related errors is output, the problem can sometimes be resolved through an internal retry. The problem should be investigated and corrective action should be taken in the following cases:

The UAP, the utility, or the command encounters an error and terminates abnormally or fails to respond.

The unit or server terminates abnormally or fails to respond.

Error messages are always output, rather than temporarily.

The following table shows frequently occurring causes and the required corrective action to take for RPC-related errors.

Table 4-1 Frequently occurring causes and required action for RPC-related errors

No.
Error description
Meaning
Action

1
Host name or port number error

The host name or port number specified in the client environment definition contains an error.

The host name or port number specified in the system definition contains an error.

Review the following definitions, and revise as necessary:

Client environment definitions:
PDHOST
PDFESHOST
PDCLTRCVADDR
PDNAMEPORT
PDSERVICEPORT
PDCLTRCVADDR
PDCLTRCVPORT
PDFESGRP

System definitions:
pd_name_port
pd_service_port
pd_scd_port
pd_trn_port
pd_mlg_port
pd_alv_port
The -x, -c, -p, -s, -t, -m, and -a options of the pdunit operand
pd_hostname
pd_registered_port
The -x, -m, and -n options of the pdstart operand
pd_security_host_group

2
System resources shortage

Not enough ports

Not enough memory

Not enough files that can be opened by the system

Not enough files that can be opened by processes

Message queue operation error

Take one of the following actions:

Not enough ports:
Take corrective action according to the contents of the preceding KFPS00349-E message.

Not enough memory:
There is not enough process-private area. Review the memory requirements. Terminate any unneeded processes.

Not enough files that can be opened by the system (the limit on files that can be opened has been exceeded):
In UNIX:
Increase the value specified for the maximum number of files that can be opened by the system, using the operating system parameter (kernel parameter) (nfile for HP-UX, maxuproc nofiles number of fixed licenses for AIX, or NR_FILE or fs.file-max for Linux). Also, terminate any unneeded processes and windows.
In Windows:
On the installation drive, allocate at least as much free space as is required for the shared memory size.

Not enough files that can be opened by a process (the limit on the number of files that can be opened has been exceeded):
In UNIX:
Increase the maximum number (maxfiles_lim for HP-UX, rlim_fd_max for Solaris, nofiles_hard for AIX, or NR_OPEN for Linux) of files that can be opened by a process, using the OS parameter (kernel parameter). If the specification value for pd_max_open_fds is too small, it should be increased.
In Windows:
On the installation drive, allocate at least as much free space as is required for the shared memory size.

Message queue manipulation error:
In UNIX:
Review message queue-related parameters in terms of OS parameters (kernel parameters).
In Windows:
On the installation drive, allocate at least as much free space as is required for the shared memory size. Or, assign the required number of resources to the system environment variable PDUXPLMSGMNI (number of message queue identifiers) or to the system environment variable PDUXPLMSGTQL (number of message queue tables). For making estimates, see the HiRDB Version 9 Installation and Design Guide.

3
Unresolvable host name or IP address
In the gethostbyname or gethostbyaddr system call, a conversion failure occurred from host name to IP address or from IP address to host name.
Check the following items and revise as necessary:

hosts file settings error

Invalid privilege for the hosts file

Settings errors on various DNS and NIS settings files (nsswitch.conf, resolv.conf, etc.)

Invalid privilege for various DNS and NIS settings files (nsswitch.conf, resolv.conf, etc.)

Note that if DNS or NIS is used, errors can occur during communications with the DNS or NIS server. Also, an error can occur in a multiple-unit configuration if the host name used by HiRDB is given the loopback address (127.0.0.1).

4
Invalid /dev/HiRDB/pth
The /dev/HiRDB/pth directory is invalid.

inode shortage

Directory not found

Invalid privilege

Other

Check to see if HiRDB is correctly installed. If HiRDB is correctly installed, terminate all copies of HiRDB running on the indicated unit, and take the following actions:

inode shortage:
Delete the files under the path /dev/HiRDB/pth.

Directory not found, invalid privilege, etc.:
Execute the pdsetup -d command, followed by the pdsetup command.
After running the pdsetup -d command, run the pdsetup command again. If you do not have valid permissions, delete the /dev/HiRDB and /dev/HiRDB/pth directories prior to running the pdsetup command.

For Linux ES 4 and AS 4, check for the following problems:

If you do not have permissions to the /etc/udev/devices/HiRDB or /etc/udev/devices/HiRDB/pth directories:
Delete the directories for which you do not have valid permissions, and then run the pdsetup command again.

If both the /etc/udev/devices and /lib/udev/devices directories exist:
If the /etc/udev/devices/HiRDB and /etc/udev/devices/HiRDB/pth directories do not exist, create them as a superuser and restart the OS. However, set the permissions for the /etc/udev/devices/HiRDB and /etc/udev/devices/HiRDB/pth directories as 755 and 777, respectively.

In Linux 5 and later, also check the following:

If you do not have permissions to the /lib/udev/devices/HiRDB or /lib/udev/devices/HiRDB/pth directories:
Delete the directories for which you do not have valid permissions, and then run the pdsetup command again.

5
Unit or server errors
The communication destination unit or server is not running.
There has been a spike in the CPU usage rate of the machine where the HiRDB client or server is allocated.
Take the following corrective action:
Start the communication destination unit or the server. If the unit or the server has abnormally terminated, check the preceding message, resolve the cause of the error, and then restart the unit or server. If the online status can be maintained in this condition (such as during reduced operation), the problem can be ignored.
Determine the reason for the spike in the CPU usage rate of the machine where the HiRDB client or HiRDB server is allocated, and then take corrective action.

6
Network error
A network error occurred.

Hardware error

Software error in a layer below the OS level

Insufficient Listen queue

There may be a set period of time for communication.

This is true even for temporary network errors related to network load.
Take one of the following actions:

Use the ping command of the OS to determine if the network for the host being used is operating normally.

Refer to the OS manual to determine if there is a network error.

It is possible that the Listen queue is full due to the occurrence of too many requests for connection to the HiRDB server. If that is the case, wait for a period of time and then re-execute. In UNIX, increase the value specified for the Listen queue.

Determine the cause of the heavy network load, and take corrective action.

You might not be able to confirm the cause of a temporary network error. If the network still doesn't work even after some time has passed, and an RPC-related error details code is output, forcibly terminate the HiRDB system# and then restart it.

7
Firewall settings
The firewall is preventing communication.

Between the HiRDB client and server

Between the HiRDB servers

In this case, take the following actions:

Revise the firewall settings between the HiRDB client and HiRDB server, and do likewise for the HiRDB settings.
For information on operation when you have set the HiRDB settings and firewall settings between the HiRDB client and HiRDB server, see Settings when a firewall and NAT are installed in the HiRDB Version 9 Installation and Design Guide.

If firewall settings between the HiRDB servers were set, remove the firewall settings.

#

If you forcibly terminate a HiRDB system consisting of two or more units, perform the following procedure:

Run the pdstop -z command in all units where the MGR is not allocated, and forcibly terminate those units.

Run the pdstop -z or pdstop -f command in units where the MGR is allocated, and forcibly terminate those units.

The following table lists the detail codes for RPC-related errors.

Table 4-2 Detail codes for RPC-related errors

Detail Code
Name
Explanation
Action

-301
PDRPCER_INVALID_ARGS
Argument is invalid
See Table 4-1 Frequently occurring causes and required action for RPC-related errors to determine if there are applicable errors.
If there are no applicable errors, refer to the event logs (in UNIX, syslogfile) of all server units and the OS log files (such as the hard disk logs) to determine whether any error messages were output immediately before the error. If there is an error message, take corrective action according to the message. If no error messages were output and no corrective action can be taken, save the event logs (in UNIX, syslogfile) for all server units and the files under %PDDIR%\spool, and contact the customer support center.

-302
PDRPCER_PROTO
Protocol error occurred (function sequence is invalid).
Take corrective action for detail code -301.

-303
PDRPCER_FATAL
The following are possible causes:
(1) Not enough memory.
(2) Invalid system definition.
(3) Error in a system file.
(4) Not enough communication resources.

A shortage of ports

The number of files that can be opened in the system or process exceeds the limit.

(5) In UNIX, the volume (disk) where /dev/HiRDB/pth resides is invalid (insufficient inode, invalid privilege, or non-existing directory, etc.).
(6) The number of activated processes exceeded the value specified in the pd_max_server_process operand.
(7) Error in the host name or port number.
(8) Unable to resolve the host name.
For other than the above, a fatal or unexpected error occurred.
If the cause is (1), (4), (5), (7) (8), see Table 4-1 Frequently occurring causes and required action for RPC-related errors, and take corrective action.
If the cause is (2), execute the pdconfchk command to revise the operand in error.
If the cause is (6), either reduce the number of startup processes (pd_max_users, pd_process_count, etc.) or increase the maximum number of startup processes (pd_max_server_process).
In other cases, see the corrective action for detail code -301.

-304
PDRPCER_NO_BUFS
The following are possible causes:
(1) Not enough memory.
(2) The number of files that can be opened in the system exceeds the limit
(3) The number of files that can be opened in the process exceeds the limit.
(4) The server is terminating.
(5) The service is not registered.
(6) The number of ports is insufficient (in Windows only)
If the cause is (1), (2), (3), or (6), see Table 4-1 Frequently occurring causes and required action for RPC-related errors, and take corrective action.
If the cause is (4), restart the server and rerun the command.
If the cause is (5), it is possible that the value of the client environment definition PDSERVICEGRP is in error (a server name other than a single server or a front-end server is specified).
In other cases, see the corrective action for detail code -301.

-306
PDRPCER_NET_DOWN
An error occurred during communication processing or communication resource allocation processing. The following are possible causes:
(1) Not enough memory
(2) Not enough communication resources.

Not enough ports.

The number of files that can be opened in the system or process exceeds the limit.

(3) In UNIX, the volume (disk) where /dev/HiRDB/pth resides is invalid (insufficient inode, invalid privilege, or non-existing directory, etc.).
(4) Invalid host name or port number.
(5) Unable to resolve the host name.
(6) A network error occurred.
(7) The communication destination unit or the server is not running.
See Table 4-1 Frequently occurring causes and required action for RPC-related errors, and take corrective action.

-307
PDRPCER_TIMED_OUT
Timeout occurred.
If an error occurs in the UAP, command or utility, or an error occurs in the system server, preventing further online operations, the following possible causes should be suspected:
(1) A network error occurred.
(2) The communication destination unit or the server terminated abnormally.
(3) The specification value for the pd_watch_time operand of the system definitions was exceeded.
This message can be ignored. However, if an error occurred in the UAP, command, or utility, or in the system server, preventing further execution of online operations, see Table 4-1 Frequently occurring causes and required action for RPC-related errors, and take corrective action.
If the cause is (3), see the manual HiRDB Version 9 System Definition, and revise the specification value for the pd_watch_time operand.

-308
PDRPCER_MESSAGE_TOO_BIG
Input parameter length exceeds the limit.
See the corrective action for detail code -301.

-309
PDRPCER_REPLY_TOO_BIG
Reply length exceeds the length of the area provided by the calling source.

-310
PDRPCER_NO_SUCH_SERVICE_GROUP
The communication destination unit or the server is not running.
See Table 4-1 Frequently occurring causes and required action for RPC-related errors, and take corrective action.

-311
PDRPCER_NO_SUCH_SERVICE
Service has not been registered.
It is possible that a server name other than a single server or a front-end server is specified in the client environment definition PDSERVICEGRP.
In other cases, see the corrective action for detail code -301.

-312
PDRPCER_SERVICE_CLOSED
The communication destination unit or the server is not running.
See Table 4-1 Frequently occurring causes and required action for RPC-related errors, and take corrective action.

-313
PDRPCER_SERVICE_TERMINATING
Service is engaged in termination processing.
See the corrective action for detail code -301.

-314
PDRPCER_SERVICE_NOT_UP
An error occurred during communication processing or communication resource allocation processing. The following are possible causes:
(1) Not enough memory.
(2) Not enough communication resources.

Not enough ports.

The number of files that can be opened in the system or process exceeds the limit.

(3) In UNIX, the volume (disk) where /dev/HiRDB/pth resides is invalid (insufficient inode, invalid privilege, or non-existing directory, etc.).
(4) Invalid host name or port number.
(5) Unable to resolve the host name.
(6) A network error occurred.
(7) The communication destination unit or the server is not running.
See Table 4-1 Frequently occurring causes and required action for RPC-related errors, and take corrective action.

-315
PDRPCER_OLTF_NOT_UP
The communication destination unit or the server is not running.

-316
PDRPCER_SYSERR_AT_SERVER
A system error occurred.
See the corrective action for detail code -301.

-317
PDRPCER_NO_BUFS_AT_SERVER
The following are possible causes:
(1) Not enough memory.
(2) The number of files that can be opened by the system exceeded the limit.
(3) The number of files that can be opened by the process exceeded the limit.
(4) The server is terminating.
(5) The service is not registered.
If the cause is (1), (2), or (3), see Table 4-1 Frequently occurring causes and required action for RPC-related errors, and take corrective action.
If the cause is (4), restart the server and rerun the command.
If the cause is (5), it is possible that the value of the client environment definition PDSERVICEGRP is in error (a server name other than a single server or a front-end server is specified).
In other cases, see the corrective action for detail code -301.

-318
PDRPCER_SYSERR
System error occurred.
See the corrective action for detail code -301.

-319
PDRPCER_INVALID_REPLY
Length of reply is invalid after execution of service function.

-320
PDRPCER_OLTF_INITIALIZING
The communication destination unit or the server is not running.
See Table 4-1 Frequently occurring causes and required action for RPC-related errors, and take corrective action.

-321
PDRPCER_ALL_RECEIVIED
All text has been received.
See the corrective action for detail code -301.

-323
PDRPCER_NO_BUFS_RB
The following are possible causes:
(1) Not enough memory.
(2) The number of files that can be opened in the system exceeds the limit.
(3) The number of files that can be opened in the process exceeds the limit.
(4) The server is terminating.
(5) The service is not registered.
If the cause is (1), (2), or (3), see Table 4-1 Frequently occurring causes and required action for RPC-related errors, and take corrective action.
If the cause is (4), restart the server and rerun the command.
If the cause is (5), it is possible that the value of the client environment definition PDSERVICEGRP is in error (a server name other than a single server or a front-end server is specified).
In other cases, see the corrective action for detail code -301.

-324
PDRPCER_SYSERR_RB
A system error occurred.
See the corrective action for detail code -301.

-325
PDRPCER_SYSERR_AT_SERVER_RB

-326
PDRPCER_REPLY_TOO_BIG_RB
The reply length exceeds the length of the area provided by the calling source.

-330
PDRPCER_NO_POOL_AT_SERVER
There are not enough shared memory buffers to store the required telegraphic messages during process allocation. The following are possible causes:
(1) The pdchprc command was used to request service from the server for which the maximum number of startup processes had been set to 0.
(2) Service was requested from refreshing servers by using the pdpfresh command.
(3) Too many UAPs were executed concurrently.
(4) Too many utilities were executed concurrently.
If the cause is (1), use the pdchprc command to increase the maximum number of startup processes.
If the cause is (2), re-execute after the pdpfresh command terminates.
If the cause is (3), revise the number of UAPs executed concurrently.
If the cause is (4), revise the number of utilities executed concurrently. To find out the maximum number of utilities that can be executed concurrently, see manual HiRDB Version 9 Command Reference.

-335
PDRPCER_ROLLBACK_INTR
An internal rollback request was received.
This message is generated when the pdstop command is executed while a utility is running or when a process related to the transaction or utility goes down.
If a message indicating an internal rollback as the cause was output before this message, take corrective action according to that message. If there is no message, contact the customer support center.

-344
PDRPCER_NO_DEVPTH
Directory /dev/HiRDB/pth is invalid.
See Table 4-1 Frequently occurring causes and required action for RPC-related errors, and take corrective action.

-350
PDRPCER_UNLOAD_FRAGMENT
Fragment was damaged.
See the corrective action for detail code -301.

-351
PDRPCER_NO_SUCH_TYPES
Representation format specified for type conversion is not supported.

-352
PDRPCER_NO_SUCH_ADDR
The specified IP address is not defined, or the IP address cannot be converted.
See Table 4-1 Frequently occurring causes and required action for RPC-related errors, and take corrective action.

-353
PDRPCER_NO_SUCH_NODENAME
The specified host name is not defined, or the host name cannot be converted.

-354
PDRPCER_TOO_MANY_HANDLERS
The number of handlers exceeded the permitted value per process.
See the corrective action for detail code -301.

-355
PDRPCER_NOT_FOUND
Specified thread was not found or is a control thread.

-356
PDRPCER_SERVER_BUSY
The following are possible causes:
(1) There is too much load on the server, making it unable to perform service.
(2) A memory shortage occurred.
If the cause is (1), rerun the command after a period of time. If this does not resolve the problem, see the corrective action for detail code -301.
If the cause is (2), see Table 4-1 Frequently occurring causes and required action for RPC-related errors, and take corrective action.

-357
PDRPCER_SERVICE_INITIALIZING
RPC environment has not been started.
See the corrective action for detail code -301.

-359
PDRPCER_ALREADY_REPLIED
A reply has already been issued.
If the UAP, command, or utility is not in error, ignore this message. If there is an error in the UAP, command, or utility, see the corrective action for detail code -301.

-360
PDRPCER_NOT_UPP_STARTED
The pdi_upp_start operand is not issued.
See the corrective action for detail code -301.

-361
PDRPCER_NO_SERVICE_CLAUSE
A service clause is not defined in the user service definition.

-362
PDRPCER_WRONG_NUMBER
Data other than nam was specified when registering, deleting, or retrieving service information in nam.

-363
PDRPCER_UPP_FAILED
Acquisition of the system definition failed. The following are possible causes:
(1) The system definition contains an error.
(2) A memory shortage occurred during the acquisition of the system definition.
If the cause is (1), revise the system definition.
If the cause is (2), see Table 4-1 Frequently occurring causes and required action for RPC-related errors, and take corrective action.

-364
PDRPCER_ERROR_REPLIED
Error occurred at the server.
See the corrective action for detail code -301.

-365
PDRPCER_TRACE_FILE_EMPTY
Trace file contains no data.

-371
PDRPCER_PROFILE
The value of the pd_registered_port operand is invalid.
Take corrective action according to the preceding KFPS00346-E and KFPS00348-E messages.

-372
PDRPCER_RETRY_CONNECT
It is one of the following situations:

The pdchgconf command is running

The pdprgrenew command is running

A transaction is queuing due to the pdtrnqing command

If the UAP generated a connection error, the following possible causes should be suspected:
(1) The client library being used is older than Version 07-01.
(2) Either the pdchgcnf or pdprgrenew command failed, preventing HiRDB from starting.
(3) Transaction queuing was not released after it was started by the pdtrnqing command.
If the UAP has not generated a connection error, disregard this message.

If the cause is (1):
Wait until the pdchgcnf and pdprgrenew commands terminate, and then re-execute the commands.
During transaction queuing due to the pdtrnqing command, release transaction queuing, and then re-execute the command.

If the cause is (2):
Resolve the cause of the error, restart HiRDB, and then re-execute the command.

If the cause is (3):
Release transaction queuing, and then re-execute the command.

-373
PDRPCER_RETRY_TRANSACTION

-374
PDRPCER_RETRY_STOPPING

-375
PDRPCER_RETRY_STARTING

-376
PDRPCER_TRNPAUSE
The new transaction scheduling suppressed status is on.
Use the pdls -d svr command to identify the server in a new transaction scheduling suppressed status and resolve the cause of the error. If there is no server in a new transaction scheduling suppressed status, rerun the UAP or the utility.

Other
--
--
See the corrective action for detail code -301.

4.2 Detail codes for system-related errors

The following table lists the detail codes for system-related errors.

Table 4-3 Detail codes for system-related errors

Detail Code
Description
Explanation

-104
Not enough process-private memory
In Table 4-4, see System call = malloc, Mnemonic = ENOMEM to check the cause of the error, and take corrective action.

-147
Shortage of shared memory
If abnormal termination of a unit occurs by starting a unit server (executed by specifying the -s option in the pdstart command) other than the back-end server to which the standby-less system switchover (effects distributed) facility was applied, specify server in the pd_shmpool_control operand of the system common definition, and then restart the unit.

-152
The number of shared memory segments is over the limit.
Increase the value specified in the SHMMAX and SHMMAX operands of the OS parameters.

-164
-201
Not enough process-private memory
In Table 4-4, see System call = malloc, Mnemonic = ENOMEM to check the cause of the error, and take corrective action.

-203
-206
The value specified for the operand is invalid
Refer to the messages output immediately before the error, identify the invalid operand, and specify a valid value.

-204
An error occurred in the HiRDB system definition
Consider the following causes:

A required HiRDB system definition was not created
Refer to the section on HiRDB system definition types in the manual HiRDB Version 9 System Definition, and create any uncreated HiRDB system definitions.
Eliminate any errors due to required HiRDB system definitions that cannot be referenced by entering HiRDB system definitions that can be referenced.

Files under %PDDIR%\lib\sysconf cannot be referenced
Make sure the files under %PDDIR%\lib\sysconf can be referenced.

-205
An error occurred in the definition analysis files of the HiRDB system definition
The files under %PDDIR%\lib\sysconf cannot be referenced. Make sure the files under %PDDIR%\lib\sysconf can be referenced.

-202
-208
-209
-210
HiRDB system internal error
Contact the customer support center.

-301 to -399
HiRDB internal communication error (See 4.1 Detail codes for RPC-related errors.)

-401
to
-465
Lock error
Refer to the KFPS004** message that was output immediately before this error. If the KFPS004** message was not just output, contact the customer support center.
*: Variable character string

-600
Internal error in the HiRDB system
If there is an error message, take corrective action according to the message. If there is no error message, contact the customer support center.

-601
Communication destination server not found

-604
Not enough process-private memory
In Table 4-4, see System call = malloc, Mnemonic = ENOMEM to check the cause of the error, and take corrective action.

-605
Version mismatch in service request test detected
Review the environment to determine whether the HiRDB client and the HiRDB server are in versions that can be interconnected and whether there are any invalid libraries on a mixed basis.

-632
Communication destination server not found
If there is an error message, take corrective action according to the message. If there is no error message, contact the customer support center.

-640
-641
Communication error

-642
Name service facility not started.
Check to see if HiRDB has started. If it has started normally, contact the customer support center.

-700
Inter-process communication error
Check to see if either HiRDB or the server process has started.

-702
Invalid status
HiRDB is undergoing the following processing; if necessary, restart it, and then rerun the command:

System termination processing

Abnormal termination processing

Forced termination processing

-706
Server startup already reported
Contact the customer support center.

-714
Maximum number of processes exceeded
The maximum number of active server processes per unit was exceeded. Re-execute the process after another command has terminated. Or, increase the value of the pd_max_server_process operand after terminating HiRDB.

-718
Undefined local domain name
Register the host name comprising the HiRDB system in the hosts file.

-723
Mismatch between command and server versions
Check to see, for example, if HiRDB files %PDDIR%\bin of different versions are used through linking, and check the version of the entered command to ensure version consistency.

-724
Lock error
Contact the customer support center.

-725
Server engaged in termination processing
HiRDB is undergoing termination processing. Start HiRDB, if necessary, and execute the command.

-726
Process not found
HiRDB is not active. Restart HiRDB, and then execute the command.

-727
Communication environment not started
Contact the customer support center.

-734
Shared memory not allocated

-816
Server startup failure
If the problem is on the server side, appropriate corrective action should be taken. If a problem has not occurred, contact the customer support center.

-821
Server shut down

-830
Not enough process-private memory
In Table 4-4, see System call = malloc, Mnemonic = ENOMEM to check the cause of the error, and take corrective action.

-832
Not enough memory
If there is a KFPS00854-W message from the server, take corrective action according to the message. If there is no error message, contact the customer support center.

-839
Server process terminating
After terminating HiRDB, start HiRDB.

-840

The group specified in the client environment definition PDSERVICEGRP is in one of the following conditions:
Not started
Starting
Stopped

Error in the name of service group specified in the client environment definition PDSERVICEGRP

Review the status of the server and the specification value in the pd_max_server_process operand, and take corrective action.

-856
Message queue manipulation (msgget) failure
If there is a KFPS00850-W message from the server, take corrective action according to the message.

-879
Error in server type specified in the client environment definition PDSRVTYPE
Start the HiRDB/Single Server, and then rerun the command. For a HiRDB/Parallel Server, start the front-end server at the connection destination, and then rerun the command.

-880
Message queue manipulation (msgget) failure
If there is a KFPS00850-W message from the server, take corrective action according to the message.

-888
HiRDB server not started (startup process not completed)
Restart HiRDB after the server startup processing is complete.

-889
The single-server or the front-end server to connect to is not started
Start the HiRDB/Single Server, and then rerun the command. For a HiRDB/Parallel Server, start the front-end server at the connection destination, and then rerun the command.

-892
Limit on the number of concurrent connections exceeded
Either review the value of the pd_max_users operand or reduce the number of concurrent connections to the HiRDB server.

-893
HiRDB server undergoing termination processing
After terminating HiRDB, start HiRDB.

-894
Lock processing failed during connection
If the problem persists after the command is executed repeatedly, contact the customer support center.

-895
Mismatch in service request text versions
Review the HiRDB client and HiRDB server environments.

-897
Server process either starting or terminating
If HiRDB is being activated, wait until the activation process is complete, and then rerun the command. If HiRDB is undergoing termination processing, activate HiRDB after it has stopped. In addition, this message can be generated if HiRDB abnormally terminates or is aborted. If there is no abnormal termination or aborting, take corrective action according to the preceding error message. If there is no error message, save the information to be acquired in the event of an error, and then contact the customer support center. The information to be acquired in the event of an error includes the files under %PDDIR%\spool, and the event log (in UNIX, syslogfile) of the system manager and the unit that output this detail code.

-902
-903
-904
-905
-906
-907
-908
-909
-910
-912
-915
HiRDB system internal error
If an error message was output before this message, take action appropriate to that message. If no error message was output, contact the customer support center.

-916
Library version incompatible with process version
Check the media versions comprising the HiRDB system. Use matching versions and re-execute.

-917
-918
-919
HiRDB system internal error
If an error message was output before this message, take appropriate action according to that message. If no error message was output, contact the customer support center.

-921
Transaction not settled
After the transaction undergoing recovery processing has been settled, rerun the error-flagged transaction or the command.

-943
Due to a recovery unnecessary front-end server, utility transactions cannot be generated.
Rerun the utility on a front-end server other than the recovery unnecessary front-end server.

-944
Connection is established to a recovery unnecessary front-end server from a UAP that uses the X/Open XA interface.
Reconnect to a front-end server other than the recovery unnecessary front-end server, and rerun the command.

-945
-946
-947
Either the pdchgconf or pdprgrenew command is currently running, or the pdtrnqing command resulted in transaction queuing
If the error occurred in a utility or command:
If the command is pdchgconf or pdprgrenew, terminate it and then re-execute it. If the error occurred during transaction queuing caused by the pdtrnqing command, release transaction queuing and then re-execute the utility or command.
If the error occurred in a UAP:

If the client library is version 07-00 or later:
The pdchgconf or pdprgrenew command might have failed. Request HiRDB status confirmation from the HiRDB manager, and once HiRDB is operational, re-execute the UAP.
During transaction queuing caused by the pdtrnqing command, release transaction queuing and then re-execute the UAP.

If the client library version is earlier than 07-00:
If the command is pdchgconf of pdprgrenew, terminate the command and then re-execute the UAP. During transaction queuing caused by the pdtrnqing command, release transaction queuing and then re-execute the UAP.

-948
Scheduling of new transactions is being suppressed.
Scheduling of new transactions is being suppressed. Using the pdls -d svr command, locate the server on which scheduling of new transactions is being suppressed, and eliminate the error. If no server is suppressing the scheduling of new transactions, re-execute the utility or UAP.

-949
HiRDB system engaged in termination processing
Rerun the command when HiRDB is active.

-1006
Error in status file input/output processing
Take corrective action in reference to the preceding KFPS01040-E message.

-1012
Not enough process-private memory
In Table 4-4, see System call = malloc, Mnemonic = ENOMEM to check the cause of the error, and take corrective action.

-1018
Status file size not large enough
Review the size of the status file and check to see if the required size is met.

-1021
Input of required information from a server status file failed
This code is sometimes generated if all server status files are initialized before HiRDB is restarted. In this case, HiRDB cannot be restarted. If this problem occurs, cancel the restart process, and recover the database from a backup file.

-1024
Status file access failure
This code can be ignored if it is generated during the abnormal termination or aborting of HiRDB or a unit, or when HiRDB or a unit is stopped. If the message is generated in other cases, contact the customer support center.

-1033
Communication error
See Table 4-1 Frequently occurring causes and required action for RPC-related errors and take appropriate corrective action. If corrective action cannot be taken, contact the customer support center.

-1039
No swap-destination status file found (no backup file)
Either resolve the error in the status file that generated KFPS01040-E and KFPS01042-E messages, or create a backup file.

-1110
Invalid log point information detected
For pdi_jnl_show_recovery_fg():
The following problems are suspected. Determine the cause of the error based on information output to the event log (in UNIX, syslogfile), and take corrective action.

Cause 1:
The record length for the system log file is different from the value specified in the pd_log_rec_leng operand. The record length for the system log file can be determined by executing the pdlogls -e command.
If this is the problem, make the record length for the system log file equal to the value specified in the pd_log_rec_leng operand.

Cause 2:
The system log file indicated in the log point information file has been overwritten. In this case, the database cannot be recovered using the system log file. If this is the problem, restore the database to the condition that existed when a backup was made and re-execute the transactions that have occurred since the backup was made.

Cause 3:
The system log file indicated in the log point information file is missing. Or, the user's access privilege to the system log file is invalid. In this case, check to see whether the system log file name specified in the pdlogadpf operand is the correct one.
If the system log file created during the backup creation process has been removed from the pdlogadpf operand, add the file to the pdlogadpf operand and re-execute.
Whether the user's access privilege is valid can be determined by executing the pdfls command. Check to see whether the access privilege to HiRDB files has been improperly modified.

Cause 4:
The log point information itself contains an error. If this is the case, contact the customer support center.

For other functions:
Contact the customer support center.

-1113
Not enough process-private memory
In Table 4-4, see System call = malloc, Mnemonic = ENOMEM to check the cause of the error, and take corrective action.

-1117
-1118
Log input starting failure

For pdi_jnl_org_get_start():
Take corrective action by seeing the preceding KFPS01170-E and KFPS01171-E messages.

For other functions:
Contact the customer support center.

-1143
Log positioning failure

For pdi_jnl_org_point_set():
If there is a preceding KFPS01040-E message, take corrective action according to the message. If there is no message, contact the customer support center.

For pdi_jnl_org_get_block():
If there are preceding KFPS01170-E or KFPS01171-E messages, take corrective action according to those messages. If there is no message output, updatable online reorganization cannot be continued. If the cause of the problem needs to be investigated, contact the customer support center.

For other functions:
Contact the customer support center.

-1144
Log input failure

For pdi_jnl_org_get_block():
If there are preceding KFPS01170-E or KFPS01171-E messages, take corrective action according to those messages. If there is no message output, updatable online reorganization cannot be continued. If the cause of the problem needs to be investigated, contact the customer support center.

For other functions:
Contact the customer support center.

-1801
Internal error in the HiRDB system
Contact the customer support center.

-1802
Definition analysis error
If there is a definition error message output before this message, revise the system definition according to the error message. If there is no error message, contact the customer support center.

-1807
-1817
Not enough process-private memory
In Table 4-4, see System call = malloc, Mnemonic = ENOMEM to check the cause of the error, and take corrective action.

-1811
Internal error in the HiRDB system
Contact the customer support center.

-1850
File I/O error
Check the file privilege and confirm that the disk can be accessed. If an error message was output immediately before the error, take the indicated corrective action. If no message was output, contact the customer support center.

-1851
Inter-process communication error
If there is an error message output, take corrective action according to the message.
Another possibility is that the server process has stopped. Check whether the server process has started.
In other cases, contact the customer support center.

-1852
Internal error in the HiRDB system
Contact the customer support center.

-1854
Internal error in the HiRDB system
This message is sometimes generated when HiRDB terminates abnormally or it is aborted. If there is no abnormal termination or aborting, take corrective action according to the preceding error message. If there is no error message, save the information to be acquired in the event of an error, and then contact the customer support center. The information to be acquired in the event of an error includes the files under %PDDIR%\spool, and the event log (in UNIX, syslogfile) of the system manager and the unit that output this detail code.

-1859
System call error
If an error message was output immediately before the error, take the indicated corrective action. If no message was output, contact the customer support center.

-1900
HiRDB system internal error
Check to see if the unit containing the system manager has started normally. The problem is sometimes caused by an error in the unit containing the system manager.
In other cases, contact the customer support center.

-1901
HiRDB internal communication error

-1902
Not enough process-private memory
In Table 4-4, see System call = malloc, Mnemonic = ENOMEM to check the cause of the error, and take corrective action.

-1903
-1904
-1905
-1906
-1907
-1908
Internal error in the HiRDB system
Check to see if the unit with the system manager has started normally. The problem can be caused by an error in the unit with the system manager.
In other cases, contact the customer support center.

-1909
File %PDDIR%\lib\msgtxt not found
In UNIX:
Recover the HiRDB execution environment according to the following procedures:

Terminate HiRDB.

Use the pdsetup -d command to release the HiRDB setup. In this operation, reply Y to the KFPS00036-Q message.

Use the pdsetup command to re-set up HiRDB.

In Windows:
Re-install HiRDB.

-1910
File %PDDIR%\lib\msgtxt corrupt
In UNIX:
Recover the HiRDB execution environment according to the following procedures:

Terminate HiRDB.

Use the pdsetup -d command to release the HiRDB setup. In this operation, reply Y to the KFPS00036-Q message.

Use the pdsetup command to re-set up HiRDB.

In Windows:
Re-install HiRDB.

-1911
File %PDDIR%\lib\msgtxt not accessible
In UNIX:
Check the access privilege for the file $PDDIR/lib/msgtxt and grant the necessary access privilege to the HiRDB administrator. If the problem persists when the valid access privilege is in place, recover the HiRDB execution environment according to the following procedures:

Terminate HiRDB.

Use the pdsetup -d command to release the HiRDB setup. In this operation, reply Y to the KFPS00036-Q message.

Use the pdsetup command to re-set up HiRDB.

In Windows:
Re-install HiRDB.

-1912
Internal error in the HiRDB system
Check to see if the unit with the system manager has started normally. The problem can be caused by an error in the unit with the system manager.
In other cases, contact the customer support center.

-5100
HiRDB system internal error
Contact the customer support center.

-5101
Communication error between servers within HiRDB
If HiRDB was aborted or has terminated abnormally, the command or utility may terminate due to this error. In this case, restart HiRDB, and then rerun the command or utility.
Also, if you cannot execute the service because the server has a heavy load, or if a memory shortage occurs, this error might cause the command or utility to terminate abnormally.
If that happens, refer to the corrective action described in detail code -356, which is listed in Table 4-2 Detail codes for RPC-related errors.
In other cases, contact the customer support center.

-5103
HiRDB system internal error
Contact the customer support center.

-5105
Shared memory or temporary file access error

-5108
HiRDB system engaged in termination processing
Execute the command when HiRDB is running.

-5110
Too many concurrently executing users
Wait until other users terminate. Or, increase the value of the pd_max_users operand. If the pdchprc command was used to change the maximum number of server processes for a single-server or front-end server, use the pdchprc command to increase the maximum value.

-5112
Lock timing error
Re-execute.

-5116
HiRDB is in start processing, or HiRDB is running as a log application site.
Re-execute after HiRDB start processing completes. If HiRDB is running as a log application site, convert the connection target HiRDB to a transaction execution site, and then re-execute.

-5125
Other utilities or operation commands cannot be executed because the pdvrup command is executing or was requested.
Rerun the command after HiRDB startup processing is complete.

-5137
Invalid HiRDB status
This message is sometimes generated when HiRDB terminates abnormally or it is aborted. If there is no abnormal termination or aborting, take corrective action according to the preceding error message. If there is no error message, save the information to be acquired in the event of an error, and then contact the customer support center. The information to be acquired in the event of an error includes the files under %PDDIR%\spool, and the event log (in UNIX, syslogfile) of the system manager and the unit that output this detail code.

-5142
-5143
-5144
Either the pdchgconf or pdprgrenew command is currently executing, or the pdtrnqing command resulted in transaction queuing
If the error occurred in a utility or command:
If the command is pdchgconf or pdprgrenew, terminate it and then re-execute it. If the error occurred during transaction queuing caused by the pdtrnqing command, release transaction queuing and then re-execute the utility or command.
If the error occurred in a UAP:

If the client library is version 07-00 or later:
The pdchgconf or pdprgrenew command might have failed. Request HiRDB status confirmation from the HiRDB manager, and once HiRDB is operational, re-execute the UAP.
During transaction queuing using the pdtrnqing command, release the transaction queuing command and then re-execute the UAP.

If the client library version is earlier than 07-00:
If the command is pdchgconf of pdprgrenew, terminate the command and then re-execute the UAP. If it is during transaction queuing caused by the pdtrnqing command, release transaction queuing and re-execute the UAP.

-5301
HiRDB system internal error
Contact the customer support center.

-5302
HiRDB not active (activation process being initialized)
Wait until completion of activation of HiRDB (completion of initialization), and then rerun the command.

-5303
HiRDB system internal error
Check the cause based on the error message that was output before this message and take appropriate action. If necessary, re-execute the command.

-5304
Definition file open error

Check if the PDDIR or PDCONFPATH environment variable has been set.

Check if the read privilege has been defined for %PDDIR%\conf\pdsys.

If the error cannot be corrected by actions 1 and 2 above, contact the customer support center.

-5305
Communication error
If HiRDB is operating normally, contact the customer support center. If HiRDB has not started, wait until its activation is complete (completion of the activation-time process initialization), and then rerun the command.

-5324
Error acquiring the value of the PDDIR environment variable
The PDDIR environment variable is not set, or the directory cannot be referenced. Revise the setting of the PDDIR environment variable.

-5400
Internal error in the HiRDB system
Contact the customer support center.

-5401
Communication error between HiRDB servers
If HiRDB is aborted or has terminated abnormally, this error can cause the command or utility to terminate.
In this case, check the reasons for the communication error based on the preceding message, and take corrective action.
If necessary, restart HiRDB, and then rerun the command or utility.
If the condition in which HiRDB is unable to terminate persists due to the pdstop command causing this error, use the kill-6 command of the OS (in Windows, the pdkill command) to delete the pdrdmd process of HiRDB, forcibly terminate the unit. Save the data under the path %PDDIR%\spool, and then contact the customer support center.

-5419
Definitions cannot be changed because no unit is stopped

-5800
There is no HiRDB file system for audit trail files or there is no audit trail file.
Check if the audit trail file name specified in the control statement file used when the pdload command was executed is correct.
If the problem occurs in command other than the pdload command, it is an indication of an internal HiRDB system error. If that is the case, contact the customer support center.

-5801
-5805
-5810
-5825
HiRDB system internal error.
Save the files under %PDDIR%\spool, and the event log (in UNIX, syslogfile), and contact the customer support center.

-5802
HiRDB system internal communication error.

-5803
There is no audit trail file that can be swapped.
Take the following corrective action to secure a file that can be swapped.

Contact the auditor so that the file whose data is waiting to be loaded can be loaded into an audit trail table.

For details about how to handle errors that occur in audit trail files, see the HiRDB Version 9 System Operation Guide.

-5804
Audit trail file I/O error
Take the corrective action described in the KFPS05704-E message, which was just displayed.

-5806
-5807
An error occurred when an audit trail file was opened.
Data loading cannot be performed because the audit trail file specified in the control statement file used when the pdload command was executed is in one of the following states:
Shutdown status
Current
Data loading completed
Not created
To resolve the error, correct the control statement file and re-execute the pdload command. If this method does not resolve the problem, save the files under %PDDIR%\spool, and the event log (in UNIX, syslogfile), and contact the customer support center.

-5809
Not enough process-private memory
In Table 4-4, see System call = malloc, Mnemonic = ENOMEM to check the cause of the error, and take corrective action.

-5817
Audit facility stopped; unable to acquire audit trail
If the audit facility was running, check the reason for its stoppage based on the preceding message.
If necessary, use the pdaudbegin command to run the audit facility.

-20****: Any numeric character
System call error
(The value obtained when the detail code is subtracted from -20000 is the system call errno.)
See Table 4-4 to check the cause of the system call error, and take corrective action.

-20999
Other system call error
Contact the customer support center.

Other
--

--: Not applicable

4.3 System call return codes

Table 4-4 shows the causes and required actions for return codes from representative system calls. For errors that are not listed in Table 4-4, see the applicable OS manual.

In UNIX:

Unless otherwise noted, Table 4-4 shows the errno used in HP-UX. Because the table lists only the principal system calls, to determine the exact nature of the error, check the mnemonic associated with the value or errno indicated in the message in the errno definition file (the contents defined in (/usr/include/sys/errno.h for HP-UX or Solaris) of the OS being used. Regarding a system call that has resulted in an error, check it in the manual and identify the cause of the error associated with the mnemonic.

In Windows:

Because Table 4-4 only lists the principal system calls, to determine the exact nature of the error, check the mnemonic associated with the value of errno indicated in the message in the errno definition file of the OS being used. If a system call has resulted in an error, refer to the manual to identify the cause of the error associated with the mnemonic.

Table 4-4 System call return codes

System Call
errno
Mnemonic
Possible Cause
Action

fcntl
22
EINVAL
If you are using the raw I/O facility in Windows, a partition format that cannot be used was specified.
Specify a partition format that can be used by the raw I/O facility. For information on partition formats that can be used by the raw I/O facility, see the HiRDB Version 9 Installation and Design Guide.

fork
11
EAGAIN
Either there are too many processes or a temporary memory shortage has occurred.
If this error occurs repeatedly when the command is rerun, terminate any unneeded processes.

12
ENOMEM
One of the following problems is suspected:

The swap area (in Windows, virtual memory) is too small for the process to be newly created.

There are too many processes or some processes are using too much memory.

If the swap area (in Windows, virtual memory) is too small, increase it.
If this is not possible, terminate the processes that are not needed. If some of the processes are using too much memory, determine whether they can be terminated.

malloc
12
ENOMEM
One of the following problems is suspected:

The swap area (in Windows, virtual memory) is too small for the process native area to be allocated.

There are too many processes or some processes are using too much memory.

If the swap area (in Windows, virtual memory) is too small, increase it.
If this is not possible, terminate the processes that are not needed. If some of the processes are using too much memory, determine whether they can be terminated.

22
EINVAL
Invalid memory management information was detected.
Contact the customer support center.

mkdir
13
EACCESS
An access privilege is invalid.
Check if access privileges to files under the HiRDB directory are correct.

28
ENOSPC
There is not enough free space for the file system.
Either delete files that are no longer needed from the file system or move files to a file system that has adequate free space.

msgget
28
ENOSPC
In UNIX:
The value specified in msgmni (number of message queue identifiers) is too small.
In Windows:
The capacity of the installation drive or the number of resources in use is insufficient.
In UNIX:
Estimate the memory requirements of all programs that are running on the server machine indicated by msgmni, change the specified value, and then reboot the applicable server machine.
In Windows:
On the installation drive, allocate at least as much free space as is required for the shared memory size.
Or, specify the required number of resources (message queue identifiers) in the PDUXPLMSGMNI system environment variable.
For the formula for determining the number of message queue identifiers, see the HiRDB Version 9 Installation and Design Guide.
The default value of the PDUXPLMSGMNI system environment variable is 50.

msgrcv
22
36
EINVAL
EIDRM
In UNIX:
The ipcrm command of the OS or the pdsetup command of HiRDB was incorrectly executed when HiRDB was running, which resulted in the deletion of the message queue used by HiRDB.
In Windows:
It is possible that the work files in the HiRDB installation directory were deleted when HiRDB was running.
If HiRDB has not terminated abnormally, terminate it.
After that, reboot the applicable server machine. (In the case of Windows, restart the HiRDB service.)

msgsnd
11
EAGAIN
The value specified in msgmni (number of message queue identifiers) or msgtql (number of messages) is too small.
In UNIX:
Estimate the memory requirements of all programs that are running on the server machines indicated by msgmni or msgtql, change the specified values, and then reboot the applicable server machine.
In Windows:
Set the value for the number of required resources (number of message queue tables) in the PDUXPLMSGTQL system environment variable.
For the formula for determining the number of message queue tables, see the HiRDB Version 9 Installation and Design Guide.
The default for the PDUXPLMSGTQL system environment variable is 80.

22
EINVAL
The ipcrm command of the OS or the pdsetup command of HiRDB was incorrectly executed when HiRDB was running, which resulted in the deletion of the message queue used by HiRDB.
If HiRDB has not terminated abnormally, terminate it. After that, reboot the applicable server machine.

open
2
ENOENT
The indicated file or directory is not found.
If the file logblib.c is output to the calling module for a KFPO00107-E message, a message text file cannot be found. If that is the case, the cause is as follows:
In UNIX:
Consider one of the following:

A HiRDB command was executed before the pdsetup command terminated normally.

The PDDIR environment variable is not correctly set up.

A HiRDB version that is not currently used is registered in the OS.

In Windows:
The PDDIR environment variable might not be set correctly.
In UNIX:
Take the following actions according to the cause of the error:

Execute the HiRDB command after confirming the normal return of the pdsetup command.

Confirm that the PDDIR environment variable is correctly set up.
For a user shell, use the env command to confirm that the value of PDDIR is correctly assigned. If the PDDIR environment variable is set when export is leaking or by using the set command, assigned values are not transferred to the HiRDB command process, which causes this error.
If the OpenTP1, HA Monitor, Hitachi HA Toolkit Extension, cluster software, JP1, DBPARTNER,HiRDB Datareplicator, HiRDB CM, and other products are used, check to see if the PDDIR environment variable for those products is correctly set.

Use the pdsetup -d command to delete from the OS the HiRDB version that is not being used. To delete all execution environments, specify y in response to the pdsetup -d command.

In Windows:
Ensure that the PDDIR environment variable is set correctly. If the command was executed from the command prompt, use the set command to determine whether the PDDIR environment variable was set correctly. If using a product such as OpenTP1, JP1, DBPARTNER, HiRDB Datareplicator, or HiRDB CM, confirm that the PDDIR environment variable has been set correctly for these products.

6
ENXIO
No access privilege for the file.
Confirm that the device exists and that the device is validated. If the device is not validated, validate it. If the error still cannot be resolved, refer to the manual for the OS in use and take corrective action.

13
EACCES
No access privilege for the file.

Review the privilege for the target file, directory, or HiRDB operation directory.

Check to see if the person executing the command has the access privilege for the target file, directory, or HiRDB operation directory.

17
EEXIST
The file to be created already exists.
Either rerun the command by renaming the file or, if the existing file is not needed, delete the file, and then rerun the command.

23
ENFILE
In UNIX:
The number of open files exceeds the maximum for the system.
In Windows:
There is insufficient capacity on the installation drive.
In UNIX:
Increase the specification value for the maximum number of OS operating system parameter (kernel parameter) files that can be opened by the system (For HP-UX: nfile. For AIX: maxuproc nofiles number of fixed licenses. For Linux: NR_FILE or fs.file-max). Stop any processes or windows that are not needed.
In Windows:
On the installation drive, allocate at least as much free space as is required for the shared memory size.

24
EMFILE
In UNIX:
Too many files are open in the indicated process.
In Windows:
There is insufficient capacity on the installation drive.
In UNIX:
If the error occurred in a HiRDB command or utility process, increase the value for the maximum number of OS operating system parameter (kernel parameter) files that can be opened by the system (For HP-UX: maxfiles. For Solaris: rlim_fd_cur. For AIX: nofiles. For Linux: INR_OPEN). If this problem occurs in a HiRDB server process, contact the customer support center.
In Windows:
On the installation drive, allocate at least as much free space as is required for the shared memory size.

999
ENOENT
For Windows, HiRDB work files may have been destroyed.
After confirming that HiRDB has stopped, delete all the files listed below and then restore them.
Note that the files from No. 4 on may not exist in all cases.

%PDDIR%\uxpldir\spool\system\filmng.dat

%PDDIR%\uxpldir\spool\system\flg.dat

%PDDIR%\uxpldir\spool\system\shmmng.dat

%PDDIR%\spool\...pdatmode

%PDDIR%\spool\...pdipcid

%PDDIR%\spool\oslmqid

%PDDIR%\spool\oslsmid

%PDDIR%\spool\pdprcsts

%PDDIR%\spool\scdqid1

%PDDIR%\spool\scdqid2

%PDDIR%\tmp\pdommenv

All files under %PDDIR%\uxpldir\spool\shm

%PDDIR%\uxpldir\spool\system\semmng.dat

%PDDIR%\uxpldir\spool\system\msgmng.dat

When starting HiRDB after deleting all these files, make sure other applications, such as Explorer, are not accessing %PDDIR%\tmp.

semget
12
ENOMEM
Shortage occurred in the number of resources used.
Specify the number of resources required (the number of semaphore identifiers) in the PDUXPLSEMMAX system environment variable. For details on how to compute the number of semaphore identifiers, see the HiRDB Version 9 Installation and Design Guide. The default for the PDUXPLSEMMAX system environment variable is 64.

28
ENOSPC
In UNIX:
The value specified in semmni (number of semaphore identifiers) or semmns (number of semaphores in the system) is too small.
In Windows:
There is insufficient capacity on the installation drive.
In UNIX:
Estimate the memory requirements of all programs that are running on the server machines indicated by semmni or semmns, change the specified values, and then reboot the applicable server machine.
In Windows:
On the installation drive, allocate at least as much free space as is required for the shared memory size.

semop
22
EINVAL
In UNIX:
The ipcrm command of the OS or the pdsetup command of HiRDB was incorrectly executed when HiRDB was running, which resulted in the deletion of the semaphore used by HiRDB.
In Windows:
It is possible that the work files in the HiRDB installation directory were deleted when HiRDB was running.
If HiRDB has not terminated abnormally, forcibly terminate it. After that, reboot the applicable server machine (for Windows, restart the HiRDB service).

shmat
12
ENOMEM
Consider one of the following:

The number of available resources is insufficient. This includes the case in which a contiguous free area cannot be allocated in the process space to which shared memory is to be attached.

In Windows, an error occurred while referencing the Windows registry.

In Windows, the HiRDB service is not started (when shared memory is allocated to the paging file).

Take the following corrective action according to the cause of the error:

For Windows, assign the number of required resources (size of required shared memory) in the system environment variable PDUXPLSHMMAX. For details on how to compute the size of the shared memory to be used, see the Determining Environment Variables Related to the Number of Resources section in the HiRDB Version 9 Installation and Design Guide. The PDUXPLSHMMAX default is 4096. If usable memory cannot be made available, change the HiRDB system definition (for example, by reducing the number of global buffers) to reduce the shared memory requirements.

Check the specification value for the -shmfile option of the pdntenv command. If the specification value is other than regular, page, or blank, the Windows registry might have been corrupted. If that is the case, contact the customer support center.

If the shared memory is allocated to the paging file, confirm that the HiRDB service started. If the HiRDB service has stopped, start it.

22
EINVAL
In UNIX:
Shared memory for HiRDB is missing. It is possible that a HiRDB command was entered before the OS was fully started (during the execution of /etc/rc) or a HiRDB command was coded in an environment file, such as /etc/localrc, which is executed upon completion of the startup of the OS.
In Windows:
It is possible that the work files in the HiRDB installation directory were deleted when HiRDB was running.
Or, it is possible that the command was executed before the activation of HiRDB was complete.
In UNIX:
If a HiRDB command was entered before the OS was fully started, reenter the command after the startup of the OS is complete. Also, be careful not to code a HiRDB command in the /etc/localrc OS environment file.
If activation of HiRDB is not complete, wait until HiRDB is complete, and then execute the command.
In Windows:
If HiRDB activation has not been completed, complete HiRDB activation and then re-execute. If HiRDB did not terminate abnormally, terminate it forcibly. After that, restart the HiRDB service.

shmdt
12
ENOMEM
In Windows, consider one of the following causes:

An error occurred while referencing the Windows registry.

The HiRDB service is not started (when shared memory is allocated to the paging file).

Check the value specified for the pdntenv command's -shmfile operand. If it is other than regular, page, or blank, the Windows registry might be corrupt. If that is the case, contact the customer support center.

If the shared memory is allocated to the paging file, confirm that the HiRDB service is started. If the HiRDB service is stopped, start the service.

shmctl
1
EPERM
Because the user is not an owner, the shared memory cannot be processed.
If a KFPH23015-E or KFPO00107-E message is output, see that message.

12
ENOMEM
In Windows, consider one of the following causes:

An error occurred while referencing the Windows registry.

The HiRDB service is not started (when shared memory is allocated to the paging file).

Check the value specified for the pdntenv command's -shmfile operand. If it is other than regular, page, or blank, the Windows registry might be corrupt. If that is the case, contact the customer support center.

If the shared memory is allocated to the paging file, confirm that the HiRDB service is started. If the HiRDB service is stopped, start the service.

shmget
12
ENOMEM
In UNIX:
The required shared memory capacity is not available on the server unit.
In Windows:
Refer to Table 4-5.
In UNIX:
Reduce memory usage on the server unit. Or, increase the real memory under the operating system.
In Windows:
Refer to Table 4-5.

22
EINVAL
In UNIX:
There was an attempt to acquire a shared memory volume that exceeds the value specified in the shmmax operating system parameter (kernel parameter).
In Windows:
It is possible that the work files in the HiRDB installation directory were deleted when HiRDB was running.
In UNIX:
Increase the value specified in the shmmax operating system parameter (kernel parameter). After changing the specified value, reboot the server machine.
In Windows:
If HiRDB did not terminate abnormally, terminate it forcibly. After that, restart the HiRDB service.

28
ENOSPC
In UNIX:
The number of shared memory identifiers exceeds the OS limit.
In Windows:
There is insufficient capacity on the installation drive. Also, if the paging file is allocated as shared memory, the process native memory used by the HiRDB service to manage the shared memory might be insufficient.
In UNIX:
Take one or more of the following actions:
(1) Reduce the number of shared memory segments set up on the same machine.
(2) Increase the specification value in the operating system parameters (kernel parameter) shmmni and shmall.
In Windows:
On the installation drive, allocate at least as much free space as is required for the shared memory size. Also, if the paging file is allocated as shared memory, check the maximum available memory for the entire system, and increase either the physical memory or the size of the paging file.

vfork
-1800 level#
--
Refer to Table 4-6.

waitpid
-1800 level#
--
Refer to Table 4-6.

write
5
EIO
An input/output error has occurred.
Take corrective action according to OS and hardware information.

14
EFAULT
An attempt was made to write to an inaccessible area. It is possible that the disk on which a write operation was attempted has been detached.
The problem can be ignored if it occurred during disk switching associated with system switchover. If the disk was detached by mistake when HiRDB was still running, either back up or restore the affected file, and initialize it before using. In other cases, contact the customer support center.

27
EFBIG
The file is greater than the system-imposed limit.
Change the file size limit for the HiRDB administrator and the root user either to a size greater than required in HiRDB or to unlimited size. Alternatively, reduce the size of the file to be used.

28
ENOSPC
The file system does not have enough area.
Either delete files that are not needed from the file system or move to a file system that has more space.

abort
creat
execl
execle
execlp
execv
execvp
fopen
fork
gethostbyaddr
gethostbyname
mmap
msgctl
msgget
msgrcv
msgsnd
open
read
readv
select
semctl
semget
semop
shmat
shmctl
shmdt
shmget
signal
sigrelse
sigset
sigsetmask
sigvector
stat
system
write
writev
etc.
22
EINVAL
For the Windows edition of HiRDB, there may be insufficient memory.
For the Windows edition of HiRDB, take corrective action from among the following options:

Specify Y in the pd_ntfs_cache_disable operand.

Decrease the total size of the databases on the server machine.

Decrease the size of the global buffer.

Decrease the values specified in the following operands:
pd_max_users
pd_process_count
pd_max_bes_process
pd_max_dic_process
pd_max_server_process
pd_max_rdarea_no
pd_max_file_no
pd_max_access_tables
pd_lck_pool_size
pd_fes_lck_pool_size

Set the default size and the maximum size of system virtual memory to the same value (a fixed size).

Do not collect statistical information and various trace information if you are currently doing so.

tempnam
12
ENOMEM
In UNIX:
The following possibilities should be investigated.

Process private memory cannot be allocated due to a shortage of swap area.

There are too many processes, or some of the processes are consuming an excessive amount of memory.

In Windows:
The following possibilities should be investigated.

Process private memory cannot be allocated due to a shortage of virtual memory.

There are too many processes, or some of the processes are consuming an excessive amount of memory.

In UNIX:
If the swap area is insufficient, expand it. If it cannot be expanded, terminate any unneeded processes.
If some processes are consuming a large amount of memory, see whether you can turn them off once.
In Windows:
If there is a shortage of virtual memory, expand the virtual memory. If it cannot be expanded, terminate any unneeded processes.
If some processes are consuming a large amount of memory, see whether you can terminate them for a while.

13
EACCES
You do not have access privileges to this directory path.
Check whether you have administrative access privileges to the directory path for the file name created by tempnam. If you do not have access privileges, assign them. Directory paths are indicated as follows.
In UNIX:

/tmp or /var/tmp

Directory path set in the TMPDIR environment variable

tmp directory under the HiRDB Entier directory

Setting value P_tmpdir defined in the OS. Include header file stdio.h

In Windows:

%PDDIR%\tmp

Directory path set in the TEMP or TMP environment variable

tmp directory under HiRDB Entier directory

24
EMFILE
In UNIX:
The following possibilities should be investigated.

The number of temporary files is equivalent to or exceeds the TMP_MAX value.

There are too many open files in the corresponding process.

In Windows:
The following possibilities should be investigated.

There are 32,767 or more temporary files.

There is a shortage of drive space set in the install drive, the environment variable TEMP, or TMP.

In UNIX:

If the number of temporary files is equivalent to or exceeds the TMP_MAX value, delete any unnecessary temporary files that have been created under the directory path listed in the EACCES section. Temporary files include the following files.
- Results file when an operation command or utility was executed
- Files that start with the prefix pd

If there is a large number of open files and an error occurs in a HiRDB command or utility process, increase the maxfiles value of the operating system parameters (kernel parameters) of the OS.

If the above corrective actions are not applicable, contact the customer support center.

In Windows:

If there are 32,767 or more temporary files, delete any unnecessary temporary files that have been created under the directory path listed in the EACCES section. Temporary files include the following files.
- Results file when an operation command or utility was executed
- Files that start with the prefix pd

If there is a shortage of drive space set in the install drive, environment variable TEMP, or TMP, then allocate to the appropriate drive free space that is at least as large as the shared memory.

If the above corrective actions are not applicable, contact the customer support center.

bind
In UNIX:
226 (HP-UX),
67 (AIX),
125 (Solaris),
98 (Linux)
In Windows:
10048
EADDRINUSE
WSAEADDRINUSE
The port number set in HiRDB might have been a duplicate of another port code used for a different program, or it could be a duplicate of multiple port numbers set in HiRDB.
Re-examine the port numbers set in HiRDB, and make sure there are no duplicates.

#

Because of the return value of the function that issues internal system calls, the system call errno does not remain as is.

Table 4-5 Corrective action when an error occurs in the shmget system call (in Windows)

Item
Location of shared memory allocation#1
Cause
Determination
Action

1
Shared between files and the paging file
Insufficient memory
Check the value specified for the PDUXPLSHMMAX system environment variable.
Set the number of required resources (number of shared memories) in the PDUXPLSHMMAX system environment variable. For details about the formula for calculating the number of shared memories, see the manual HiRDB Version 9 Installation and Design Guide. If the PDUXPLSHMMAX system environment variable is omitted, 4,096 is assumed.

2
Files
Insufficient free space on the installation disk
Determine whether there is sufficient free space on the drive where HiRDB is installed.
If there is insufficient free space, delete unnecessary files.

3
Because the initial and maximum values specified for the virtual memory are different, there is no free space on the disk that allocated the disk paging file
Determine whether there is free space on the disk that allocated the disk paging file.
If there is no free space on the disk, re-allocate the virtual memory. When re-allocating the virtual memory, specify the same initial value and maximum value (fixed value), so as to be able to create a contiguous area on the drive.

4
There is insufficient memory
Check whether there is enough free space in the virtual memory (paging file).
Expand or re-allocate the virtual memory. When expanding or re-allocating the virtual memory, specify the same initial value and maximum value (fixed value), so as to be able to create a contiguous area on the drive.

5
Determine whether there is sufficient free space on the disk that holds the paging file.
If the virtual memory needs to be expanded, expand it. At this time, specify the same initial value and maximum value for the virtual memory.

6
The installation information cannot be referenced correctly
Check the installation information. The installation information can be displayed using the pdntenv command. For details about the pdntenv command, see the manual HiRDB Version 9 Command Reference.
Use the pdntenv command to check the value of ShmFile. If the value of ShmFile is other than regular, page, or blank, the Windows registry might be corrupt. If that is the case, contact the customer support center.

7
If memory page locking fails
Check in either the HiRDB system definitions or command line whether there is a setting for locking memory pages.
If you are locking pages in the memory, the location for shared memory must be a paging file. Change the location for allocating shared memory to the paging file.

8
Paging file
There is insufficient free space on the installation drive
Determine whether there is sufficient free space on the drive where HiRDB was installed.
If there is insufficient space, delete any unnecessary files.

9
Because the initial and maximum values specified for the virtual memory are different, there is no free space on the disk that allocated the disk paging file
Determine whether there is free space on the disk that allocated the disk paging file.
If there is no free space on the disk, re-allocate the virtual memory. When re-allocating the virtual memory, specify the same initial value and maximum value (fixed value), so as to be able to create a contiguous area on the drive.

10
There is insufficient memory
Check whether there is enough free space in the virtual memory (paging file).
Expand or re-allocate the virtual memory. When expanding or re-allocating the virtual memory, specify the same initial value and maximum value (fixed value), so as to be able to create a contiguous area on the drive.

11
Determine whether there is sufficient free space on the disk that holds the paging file.
If the virtual memory needs to be expanded, expand it. At this time, specify the same initial value and maximum value for the virtual memory.

12
The installation information cannot be referenced correctly
Check the installation information. The installation information can be displayed using the pdntenv command. For details about the pdntenv command, see the manual HiRDB Version 9 Command Reference.
Use the pdntenv command to check the value of ShmFile. If the value of ShmFile is other than regular, page, or blank, the Windows registry might be corrupt. If that is the case, contact the customer support center.

13
The HiRDB service is not started
Confirm that the HiRDB service is started.
If the HiRDB service is stopped, start it.

14
If memory page locking fails
Check whether the disk where the virtual memory or paging file was allocated has enough free space. If this error occurs despite there being enough free space, page locking has failed due to the absence of contiguous space in the physical memory.
Take one of the following corrective actions.

Do not lock the page in the memory.

Revise the specification value for the SHMMAX operand so that there is enough contiguous space in the physical memory in order to allocate shared memory.

Restart the OS in order to enable allocation to the contiguous space in the memory.#2

Increase the physical memory and the space where the shared memory can be allocated.

see the manual HiRDB Version 9 System Definition for information on the SHMMAX operand.

15
You do not have valid permissions to be able to lock shared memory to pages in the memory.
Take one of the following corrective actions.

Set HiRDB administrator permissions by going to OS -> Local security settings -> Local Policies -> User Rights Assignment -> Lock pages in memory.

On HiRDB/single server, if you do not use the system switchover facility, which does not take on an IP address, set the log-on account that you use when services are running to the local system account.

#1

The location where the shared memory is allocated can be determined by referring to the value of ShmFile obtained by the pdntenv command. The following table shows where the shared memory is allocated for each value displayed using the pdntenv command.

Item | ShmFile value | Allocation location
1 | regular | Files under the HiRDB directory
2 | page | Paging file
3 | blank | Files under the HiRDB directory

#2

If the physical memory becomes fragmented, the fragmented areas might not be joined until the OS is restarted. Therefore, you must restart the OS to ensure that contiguous area is created.

Table 4-6 Causes and corrective actions to take when a -1800 number level error occurs in vfork, waitpid

System call
errno
Main possible causes
Corrective action

vfork
-1818
Communication with the command execution process failed (disconnection was detected).
Check whether the command execution process has started.#
If it has not started, contact the customer support center.
If it has started, make sure that there is no shortage of file descriptors in the system as a whole.

-1819
A resource shortage occurred during the XDS process.
The main possible causes are as follows:

Shortage of file descriptors

Perform either of the following actions:

Check the specification value of the pdq_max_descriptors operand in the XDS server definitions.

Check whether there is a shortage of file descriptors in the system as a whole.

-1871
A resource shortage occurred during the command execution process.
The main possible causes are as follows:

There are too many processes.

A memory shortage occurred.

Perform either of the following actions:

Check whether the number of processes in the system has reached the maximum limit.

Check whether there is a shortage of memory in the system.

-1872
An attempt to establish a connection with the command execution process failed.
Check whether the command execution process has started.#
If it has not started, contact the customer support center.
If it has started, make sure that there is no shortage of file descriptors in the system as a whole.

waitpid
-1818
Communication with the command execution process failed
(disconnection was detected).
Check whether the command execution process has started.#
If it has not started, contact the customer support center.
If it has started, check whether there is a shortage of file descriptors in the system as a whole.

-1871
A resource shortage occurred during the command execution process.
The main possible causes are as follows:

There are too many processes.

A memory shortage occurred.

Perform either of the following actions:

Check whether the number of processes in the system has reached the maximum limit.

Check whether there is a shortage of memory in the system.

-1873
The connection with the command execution process was disconnected, and response waiting was canceled.
Check whether the command execution process has started.#
If it has not started, contact the customer support center.
If it has started, check whether there is a shortage of file descriptors in the system as a whole.

#

It is possible to check whetherthe command execution process has started by executing the pdls -d prc -a command to check whether a process with server name cmdd exists.

4.4 Communication error codes

The error message output during a communication error includes the communication error code as additional information. You can eliminate the communication error by taking corrective action according to the communication error code.

The tables below show combinations of message IDs and reason codes output during communication errors, as well as additional information on the meanings of the communication error codes.

Table 4-7 List of messages containing communication error codes

Section number | Message ID | Reason code | Additional information on the meaning of communication error codes
1 | KFPQ48301-W | 0201 | The communication error code is output as detail-code in this message. For information on the meanings of the communication error codes, refer to Table 4-8.
2 | 0202
3 | 0301
4 | 0302
5 | 0303
6 | KFPQ58204-E | 0201
7 | 0301
8 | 0302
9 | 0304
10 | 0305
11 | KFPQ58303-E | 0001
12 | 0002
13 | Other than those above
14 | KFPQ40365-E | 2000 | The communication error code is output as maintenance-information-1 in this message. For information on the meanings of the communication error codes, refer to Table 4-8.

The following table shows the meaning of the communication error codes.

Note that causes of communication errors that can potentially occur online as a result of a heavy network load or other causes are listed in Table 4-9 under Major category 1, Minor category 7, as well as under Major categories 2 and 3.

Table 4-8 Meanings of communication error codes

Communication error codes
Meaning
Cause and corrective action

In Linux:
In AIX:

-306
-306
Connection with the processes of other systems failed as a result of one of the following causes:

Invalid definitions

Invalid network configuration

A temporary heavy load on the network or a slowdown

Refer to 1 under Major category in Table 4-9. Alternatively, refer to 3 under Major category in Table 4-9.

-307
-307
A timeout while waiting for a sending port to become available occurred as a result of one of the following causes:

Communication performance is poor.

There are no ports for sending.

Refer to refer to 3 under Major category in Table 4-9.

-317
-317
There is a shortage of receiving buffers in the processes of other systems as a result of one of the following causes:

The maximum memory of the XDS has been exceeded.

The maximum memory of the machine has been exceeded.

Refer to refer to 2 under Major category in Table 4-9.

-339
-339
The maximum number of retries has been exceeded as a result of one of the following causes:

Communication performance is poor.

Communication parameters are invalid.

Refer to 3 under Major category in Table 4-9.

-341
-378
-341
-378
The processes of the other party were disconnected as a result of the following cause:.

The processes of the other party are down or have slowed down.

Refer to 1 under Major category in Table 4-9.

-40090
-40059
The maximum message length for the UDP protocol was exceeded as a result of the following cause:

Invalid definitions

-40100
-40101
-40113
-40070
-40078
-40081
Network errors occurred due to one of the following causes:

NIC error

Invalid network settings

-41390
-41390
Packet sizes do not match, due to the following cause:

Invalid definitions

-41391
-41391
The processes of the other party cannot be received as a result of the following cause:

Invalid timing

Other than those above
Not applicable
Contact the customer support center.

The following table shows the causes and corrective actions to take for communication errors.

Table 4-9 Causes and corrective actions to take for communication errors

Classification
Cause
Corrective action

Major category
Minor category

1
1
Host names of the running system or standby system vary.
Re-examine the LAN host name specified in the -n option of the pdqclgrpdef operand, and correct any errors.

2
Port numbers vary between the running system and the standby system.
Specify the same value for the port number of the -p option of the pdqclgrpdef operand.

3
Communication between the running system and the standby system is not possible.
Re-examine network devices (NIC, router, cable, etc.) and network settings (routing information, ifconfig, etc.), and check communication by using the ping command and the like.#1

4
Multicast send/receive communication failed.#2
Possible causes are as follows:

The LAN specifications are wrong.

Different LANs have been specified for sending and receiving.

In a multi-homed host configuration, one LAN is used for multicast send/receive communication, so select from the following methods.
For a LAN used for sending

When automatically selected by the OS:
Omit the -a option of the pdqmyudpsnddef operand

When explicitly specified in the XDS server definitions:
Specify the host name of the LAN adapter in the -a option of the pdqmyudpsnddef operand

For a LAN used for receiving

When automatically selected by the OS:
Omit the host name of the LAN adapter in the -m option of the pdqclgrpdef operand

When explicitly specified in the XDS server definitions:
Specify the host name of the LAN adapter in the -m option of the pdqclgrpdef operand

Re-examine the -a option of the pdqmyudpsnddef and the -m option of the pdqclgrpdef operand, and set appropriate values.

5
The router between the running system and the standby system does not support multicast.#²
Check whether the router supports multicast. If it does not, change to a router that does.

6
The number of routers between the running and standby systems is greater than the value specified for the -T option of the pdqmyudpsnddef operand.#²
For the -T option of the pdqmyudpsnddef operand, specify a value larger than the number of routers.

7
Processes of the other system have not started, are shut down, have just started up, or are slowed down.
Check the status of other system processes.

8
Packet sizes vary between the running system and the standby system.
Specify the same value in the pdq_rpc_udp_packet_size operand.

9
The maximum UDP message length has been exceeded.
For the pdq_rpc_udp_packet_size operand, set a value equal to or less than the maximum UDP message length#1 of the applicable machine.

10
Route information has not been set correctly. The following two conditions overlap.#2

There was an omission of the -a option of the pdqmyudpsnddef operand in the XDS server definitions (host name of the LAN adapter)

There is no route information for the host name of the host group specified in the -m option of the pdqclgrpdef operand in the XDS server definitions

Perform one of the following corrective actions.

Set the default route information in the OS routing table.

In the routing table, specify the route information for the host name of the host group specified in the -m option of the pdqclgrpdef operand.

Specify the -a option of the pdqmyudpsnddef operand.

2
1
The XTC pool size being used exceeds the maximum value.
Increase the specification value for the pdq_memory_xtc_limit_size operand, or specify it as 0.

2
There is a shortage of OS memory.
Expand real memory or swapping size.

3
1
The performance of the network devices being used (NIC, router, etc.) is poor.
Use high-speed network devices.

2
Communication overhead is large because the MTU size is small.
If the network supports jumbo frames, change to jumbo frames#1, and increase the pdq_rpc_udp_packet_size operand.

3
The socket receiving buffer size is too small, so multiple receiving packets have been lost (buffer overflow).
Increase the specification value for the -B option of the pdqclgrpdef operand. Note that you cannot increase socket receiving buffers past the maximum for the OS, so expand the maximum for the OS as needed.#1

4
The socket receiving buffer size is too small, so multiple instances of waiting for available sending buffers have occurred.
Increase the specification value for the -b option of the pdqmyudpsnddef operand. Note that you cannot increase socket sending buffers past the maximum for the OS, so expand the maximum for the OS as needed.#1

5
Because there are few sending ports, there are multiple incidences of waiting for sending ports to become available between processing threads.
Increase the value of -p in pdqmyudpsnddef operand or the value of the -P operand.

6
Network performance is poor, so retries are repeated in the current resend count and resend interval.
Increase the specification value for the -R, -w, and -W options in the pdqmyudpsnddef operand.

7
Multiple processing threads are concurrently performing mass updates of the memory database.
Increase the specification value for the -p option of the pdqclgrpdef operand. Note that if you increase the receiving threads, resources increase and processing conflict may occur between receiving threads.

8
The delivery check size is too large, so multiple receiving packets have been lost (buffer overflow).
Decrease the specification value for the pdq_rpc_udp_lmsg_deliverychk_sz operand or the pdq_rpc_udp_msg_deliverychk_sz operand.

9
Overhead is large due to line trace acquisition.
Re-examine the pdq_rpc_udp_linetrace operand, and restrain the acquisition of unnecessary line traces.

#1

For details, refer to the OS documentation.

#2

Applies only when specifying the -m option for the pdqclgrpdef operand in the XDS server definitions to perform multicast communication between the running system and the standby system.

5. HiRDB File System Error Codes

This chapter explains the error codes output by the HiRDB file system.

Organization of this chapter

5.1 Error codes returned from HiRDB file system access requests

5.1 Error codes returned from HiRDB file system access requests

The following table lists the error cause codes returned from HiRDB file system access requests.

Table 5-1 Error cause codes returned from HiRDB file system access requests

Error Code
Description
Action

-1511
Specified path name is invalid:

The path name contains an invalid character.

The length of the path name exceeds the maximum (167 characters).

The length of the HiRDB file system area name exceeds the limit (165 characters).

The length of the HiRDB file name exceeds the maximum (30 characters).

Review the path name specified in the control statement, command line, and system definition file.
In a facility in which HiRDB automatically generates HiRDB files, in some cases the path length exceeds the limit, depending on the length of the HiRDB file system area length. HiRDB file system areas should be specified in conformance to the respective limits, as follows:

Work table file (server definition pdwork operand): 141 characters maximum

Plug-in index delay batch updating (server definition pd_plugin_ixmk_dir operand): 136 characters maximum

If there are no problems in this regard, but the error persists, contact the customer support center.

-1514
The sector length specification is invalid.

The HiRDB file system area created with the specified sector length is not supported.

The RDAREA page length is not an integral multiple of the HiRDB file system area sector length.

Use a HiRDB file system area created without specifying a sector length.

Correct the RDAREA page length.

-1532

A file other than a regular file or a character-type special file (for Windows, direct disk access) was specified.

HiRDB file system area is not found.

Review the path name specified in the control statement, command line, or system definition file to be sure that it is not in error.

Files other than a regular file or a character-type special file (direct disk access for Windows) cannot be used as a HiRDB file system area.

Check to see if the HiRDB file system area indicated in the message has been deleted or the symbolic link is broken.

-1534
Lock error occurred.

Execute the pdfls-L command on the HiRDB file system area or the HiRDB file indicated in the message to check for any process exercising lock control. If a process exercising lock control is identified, execute the affected command after that process has terminated. If a process exercising lock control is not identified, re-execute the command after a period of time.

If the HiRDB file system area indicated in the message is being used by a command, wait until that command terminates, and then re-execute the affected command.

If this error occurs because of the execution of a command, terminate HiRDB, and then re-execute the command (provided that the command can be executed while HiRDB is stopped).

If the above measures fail to resolve the problem, contact the customer support center.

-1535

There is not enough free space in the HiRDB file system area.

There is not enough free space on the disk on which the HiRDB file system area was created, and the disk is full.

In automatic extension of the RDAREA, it is not possible to increase the HiRDB file size to 64 GB or greater.

Use the pdfstatfs command to check the amount of free space in the HiRDB file system area that was specified in the control statement, the command line, and the system definition file. If there is not enough free space to accommodate the size of the file to be created, specify another HiRDB file system area.

If the disk became full when operations were performed on the HiRDB file system area for regular files, either delete other files or expand the disk to increase the amount of free space.

In UNIX, if a character special file HiRDB file system area is in use, the disk will not become full. However, if operations are performed using a symbolic link, check to see if a link is established to regular files.

In UNIX, if you use regular files, either set the limit value of the system resources for the HiRDB administrator and root user to a value greater than that specified for the -n option, or set it to have no limit. Also, in AIX, take corrective action according to Notes on the /etc/security/limits file specification values under Estimating AIX 5L OS parameter values in the HiRDB Version 9 Installation and Design Guide.

Set the disk so that you can use large files. For details on setting the disk, refer to the documentation that corresponds to that OS and disk.

If an extension error occurs during automatic extension of the RDAREA because the size of the HiRDB file exceeds 64 GB, investigate the usage condition of that RDAREA by using the database condition display command (pddbls) or the database condition analysis utility (pddbst). Depending on the usage condition of the RDAREA, reorganize in units of RDAREA or tables, or add a HiRDB file by expanding the RDAREA (expand rdarea) of the database structure modification utility (pdmod).

-1536
The limit on the number of files that can be created in the HiRDB file system area has been exceeded.

Increase the maximum number of files (specified in the pdfmkfs -l command) and recreate the HiRDB file system area.

In the control statement, the command line, and the system definition file, specify another HiRDB file system area that has more space for file creation.

-1538
Specified area is not a HiRDB file system area.

Determine whether the file initialized as a HiRDB file system area is specified in the control statement, the command line, and the system definition file.

It is possible that the HiRDB file system area is corrupt. Execute the pdfls command on the indicated path to determine whether the HiRDB file system area has been destroyed.

-1539
HiRDB file was not found.

Determine whether the correct HiRDB file is specified in the path name specified in the control statement, the command line, and the system definition file. HiRDB file names can be verified by using the pdfls command.

If an error occurred in a HiRDB file that is a part of the RDAREA during HiRDB operations, a possible cause of the problem may be that the RDAREA was recovered from a backup taken before RDAREA reorganization, or the HiRDB file was forcibly removed through the use of the pdfrm command. If this is the case, either recover the RDAREA using the proper recovery procedures or reinitialize the RDAREA.

If neither possibility applies, contact the customer support center.

-1540
Access privilege is undefined.

Review the access privileges for the HiRDB file system area specified in the control statement, the command line, and the definition file, and re-execute as a user with access privileges or re-execute after changing access privileges using the OS chmod command.

In Windows, perform the following actions.

If the error occurred in an area on which direct disk access was used, check to see if a formatted disk was specified.

Use the Windows COPY command to double-check whether copying is currently being performed. If copying is currently being performed, wait until it finishes.

-1541
HiRDB file has already been defined.
The HiRDB file specified in the control statement, the command line, and the system definition file already exists. Specify a HiRDB file in a manner that avoids duplication.
If there are no duplicate HiRDB files, but the error persists, contact the customer support center.

-1543
Versions do not match.

The version of HiRDB currently running is older than the version that created the HiRDB file system area. Areas created using a new version of HiRDB cannot be used with an older version of HiRDB.

If HiRDB with more than one version is installed, review the absolute path name specified in command execution.

-1544
I/O error occurred.
Take corrective action corresponding to errno in the KFPO00107-E message in the event log (in UNIX, syslogfile).
If there is no KFPO00107-E message, contact the customer support center.

-1548
There are not enough lock segments.
Take corrective action corresponding to errno in the KFPO00107-E message in the event log (in UNIX, syslogfile). If the errno is 46 (ENOLCK), it is an indication that there are not enough OS lock segments.
Refer to the description about estimating OS operating system parameters in the HiRDB Version 9 Installation and Design Guide.
For HP-UX, review the nflock operand.
If any other OS is being used, wait for the other process that is using the lock to terminate, and then reexecute.
If the above measures fail to resolve the problem, contact the customer support center.

-1549
The system open count exceeds the limit. Or the process open count exceeds the limit.
Take corrective action corresponding to errno in the KFPO00107-E message in the event log (in UNIX, syslogfile).
In UNIX, refer to the description about estimating OS operating system parameters in the HiRDB Version 9 Installation and Design Guide, and raise the limit if it is too low.
Review the following values:

HP-UX:
nfile, maxfiles_lim

Solaris:
rlim_fd_max

AIX:
nofiles_hard

Linux:
NR_FILE, NR_OPEN

-1550
Memory is insufficient.
Review the memory requirements. If there is a problem, take corrective action such as increasing the memory or reducing the number of resident processes.
If the corrective action fails to resolve the problem, contact the customer support center.

-1555
There are insufficient log segments, the number of open files exceeded the limit, or there is insufficient memory.
Take the corrective action indicated in error codes -1548, -1549, and -1550.
If these actions do not solve the problem, contact the customer support center.

-1556

An attempt was made to allocate multiple, fragmented free spaces to a file; however, allocation failed either because of the lack of a specification for a maximum increment count (pdfmkfs -e) for the HiRDB file system area or the specified value is too low.

Allocation of new free space to a file failed due to one of the following causes.

(1) The maximum increment count (pdfmkfs -e) or the automatic extension (pdfmkfs -a) of the HiRDB file system area was not specified.
(2) If the maximum increment count (pdfmkfs -e) of the HiRDB file system area was specified, then the specified number is too small.

The number of HiRDB file allocation extents is greater than the limit of 24; extents cannot be allocated.

HiRDB file for RDAREA
Take one of the following actions:
(1) Follow the procedures outlined below to consolidate the extents and the fragmented free spaces in the HiRDB file system area:

Normally terminate HiRDB#.

Use the pdfbkup command to back up the area.

Use the pdfmkfs command to initialize the area.
Before taking these actions, execute the pdfstatfs command on the area that generated the error to check the difference between the total increment count (current expand count) and the increment count limit (available expand count). If the difference is less than 23, it is an indication that the maximum increment count is too low. If this is the case, increase the maximum increment count (the -e option) when the area is initialized.

Use the pdfrstr command to recover the area.

Normally start HiRDB#.

#: Items 1 and 5 can also be accomplished by the following procedures:

1. Put the RDAREA allocated to the area in command shutdown and closed states, and then refresh (pdpfresh) the corresponding server process.

5. Put the RDAREA allocated to the area in shutdown release and open states.

(2) When creating an RDAREA, allocate the files that compose the RDAREA to another HiRDB file system area. When expanding an RDAREA, specify a HiRDB file in another file system area, and expand the RDAREA using that file.
HiRDB file for work tables
Execute the pdfstatfs -d command on the HiRDB file system area for work tables, and check the value of the maximum user area (peak capacity). If there is adequate space in the total capacity (user area capacity) of the area, increase the specified value in the maximum increment count (the -e option), and initialize the area using the pdfmkfs command. If the maximum user area is close to the total capacity, increase the size of the HiRDB file system area (the -n option), and reinitialize the area using the pdfmkfs command.
HiRDB file for utilities
Take one of the following actions:
(1) Increase the specified value in the maximum increment count (the -e option), and reinitialize the area using the pdfmkfs command.
(2) For a utility in which an initial allocation size and an increment size can be specified, increase the initial allocation size and the increment size.

-1562
The purpose of the file being created does not match the purpose of the HiRDB file system area.

Check to see if the purpose of use of the HiRDB file system area specified in the control statement, the command line, and the system definition file is correct. The pdfstatfs command can be used to verify the purpose of use of the HiRDB file system area.

For a Linux version, there are HiRDB files that cannot be created on a character-type special file. In this case, the HiRDB file system area set up on a regular file should be used.

An attempt was made to create a shared RDAREA in a HiRDB file system area for which the purpose is not SDB. When using a shared RDAREA, specify SDB as the purpose, and create the shared RDAREA in an initialized HiRDB file system area.

-1565
A large file is being used (in Windows, this means a file exceeding 2 GB), despite N having been specified in the pd_large_file_use operand.
When using large files (in Windows, files exceeding 2 GB), specify Y in the pd_large_file_use operand or omit the specification.
Alternatively, re-create a HiRDB file system area that is less than 2 GB. However, do not specify the pdfmkfs -a command to recreate the area.

Other
--
Contact the customer support center.

--: Not applicable

6. Lock Control Errors

This chapter describes resource types, resource names, and resource information output for lock control errors.

Organization of this chapter

6.1 Resource types, resource names, and resource information for lock control errors

6.1 Resource types, resource names, and resource information for lock control errors

The following table lists resource types, resource names, and resource information for lock control errors. For details about how to refer to the resource information, see the HiRDB Version 9 System Operation Guide.

Table 6-1 Resource types, resource names, and resource information for lock control errors

Resource Type
Type Name
Resource Name 1#1
Resource Name 2#1
Resource Information
Description

0001
RDAR
RDAREA name
--
Digits 1-8: RDAREA number
Digits 9-28: Fixed at 00
RDAREA

0002
TABL
Table name or sequence generator name
--
In UNIX:
Digits 1-8: Table number or sequence generator number
Digits 9-16: Generation number
Digits 17-28: Fixed at 00
In Windows:
Digits 1-8: Table number or sequence generator number
Digits 9-28: Fixed at 00
Table or sequence generator

0003
INDX
Index name
RDAREA name
Digits 1-8: Index number
Digits 9-16: RDAREA number
Digits 17-28: Fixed at 00
Index

0004
PAGE
Table name or index name
RDAREA name
In HP-UX, Solaris, and AIX:
Digits 1-6: RDAREA number
Digits 7-8: File number
Digits 9-16: Page number
Digits 17-24: Table number or index number
Digits 25-28: Fixed at 00
In Linux and Windows:
Digits 1-2: File number
Digits 3-8: RDAREA number
Digits 9-16: Page number
Digits 17-24: Table number or index number
Digits 25-28: Fixed at 00
Page

0007
ROW
Table name
RDAREA name
In HP-UX, Solaris, and AIX:
Digits 1-6: RDAREA number
Digits 7-8: File number
Digits 9-14: Page number
Digits 15-16: Slot number
Digits 17-24: Table number
Digits 25-28: Fixed at 00
In Linux and Windows:
Digits 1-2: File number
Digits 3-8: RDAREA number
Digits 9-10: Slot number
Digits 11-16: Page number
Digits 17-24: Table number
Digits 25-28: Fixed at 00
Row

0008
NWROW
Table name
RDAREA name
In HP-UX, Solaris, and AIX:
Digits 1-6: RDAREA number
Digits 7-8: File number
Digits 9-14: Page number
Digits 15-16: Slot number
Digits 17-24: Table number
Digits 25-28: Fixed at 00
In Linux and Windows:
Digits 1-2: File number
Digits 3-8: RDAREA number
Digits 9-10: Slot number
Digits 11-16: Page number
Digits 17-24: Table number
Digits 25-28: Fixed at 00
Row (WITHOUT LOCK NOWAIT retrieval control)

000B
TABN
Table name
--
In UNIX:
Digits 1-8: Table number
Digits 9-16: Generation number
Digits 17-28: Fixed at 00
In Windows:
Digits 1-8: Table number
Digits 9-28: Fixed at 00
Table (for NO WAIT search)

000C
NKEY
Index name
--
Digits 1-8: Index number
Digits 9-28: Fixed at 00
Key value (NULL)

000D
DKEY
Index name
--
Digits 1-8: Index number
Digits 9-8: Key value or encoded key value
Key value (non-NULL)

000E
LFID
RDAREA name
Logical file number
Digits 1-8: RDAREA number
Digits 9-16: Logical file number
Digits 17-28: Fixed at 00
Logical file

000F
IXIF
Index name
RDAREA name
Digits 1-8: Index number
Digits 9-16: RDAREA number
Digits 17-28: Fixed at 00
Index information file

0010
TRWT
Table name
RDAREA name for index
Digits 1-8: Table number
Digits 9-16: RDAREA name for index
Digits 17-28: Fixed at 00
Transaction completion standby

0011
SHWT
Table name (if waiting for completion of RDAREA update, **** is output)
RDAREA name
In HP-UX, Solaris, and AIX:
Digits 1-6: RDAREA number
Digits 7-8: File number
Digits 9-14: Page number
Digits 15-16: Slot number
Digits 17-24: Table number
Digits 25-28: Fixed at 00
In Linux and Windows:
Digits 1-2: File number
Digits 3-8: RDAREA number
Digits 9-10: Slot number
Digits 11-16: Page number
Digits 17-24: Table number
Digits 25-28: Fixed at 00
If waiting for completion of RDAREA update, all other than the RDAREA number are 0.
Shared RDAREA transaction settlement pending

0102
RRAMB
RDAREA name
--
Digits 1-8: RDAREA number
Digits 9-28: Fixed at 00
RDAREA management information

0111
MFCB
--
--
Digits 1-8: Page number
Digits 9-12: File number
Digits 13-28: Fixed at 00
Master directory segment information

0112
MTCB
Table name
--
Digits 1-8: Table number
Digits 9-28: Fixed at 00
Master directory table information

0113
MICB
Index name
--
Digits 1-8: Index number
Digits 9-28: Fixed at 00
Master directory index information

0121
RATM
Table name
RDAREA name
Digits 1-8: RDAREA number
Digits 9-16: Table number or table management number
Digits 17-28: Fixed at 00
Dictionary table information or user directory table information

0122
RAIM
RDAREA name
--
Digits 1-8: RDAREA number
Digits 9-16: Index number or index management number
Digits 17-28: Fixed at 00
Dictionary index information or user directory index information

0132
SBMB
RDAREA name
--
Digits 1-8: RDAREA number
Digits 9-16: Segment number
Digits 17-20: File number
Digits 21-28: Fixed at 00
Dictionary segment information or user directory segment information

0143
RDLF
RDAREA name
Last file number
Digits 1-8: RDAREA number
Digits 9-12: Last file number
Digits 13-28: Fixed at 00
RDAREA extension

0152
SGMB
RDAREA name
--
Digits 1-8: RDAREA number
Digits 9-16:
Page number
Digits 17-20: File number
Digits 21-28: Fixed at 00
Database copy utility

0300
MENT
RDAREA name
--
Digits 1-8: RDAREA number
Digits 9-16: Page number
Digits 17-20: File number
Digits 21-24: Entry number
Digits 25-28: Fixed at 00
User LOB RDAREA management information

0301
LOBID
RDAREA name
--
Digits 1-8: RDAREA number
Digits 9-16: LOB number
Digits 17-28: Fixed at 00
User LOB RDAREA management information

0502
TEMP
Server name
--
The first 8 bytes are reserved for the server name. If the server name is less than 8 bytes, the remaining bytes are padded with NULL codes.
Temporary table instantiation management information

0503
TPID
--
--
Digits 1-8: User-specific number
Digits 9-28: Fixed at 00
User-specific ID management (temporary table)

0601
RDAS
RDAREA name
--
Digits 1-8: RDAREA number
Digits 9-28: Fixed at 00
Database condition analysis utility

0602
HOLD
RDAREA name
--
Digits 1-8: RDAREA number
Digits 9-28: Fixed at 00
Backup hold RDAREA

0603
INRP
Server name
--
Limited to UNIX:
The first 8 bytes are reserved for the server name. If the server name is less than 8 bytes, the remaining bytes are padded with NULL codes.
Configuration management information for the inner replica facility

0604
RPGP
Original RDAREA name
--
Limited to UNIX:
Digits 1-8: RDAREA number
Digits 9-28: Fixed at 00
Replica group configuration management information

0605
MDBS
RDAREA
--
Digits 1-8: RDAREA number
Digits 9-28: Fixed at 00
Synchronous processing information of in-memory data processing

0900
PLGR
--
--
Digits 1-8: Plug-in ID
Digits 9-28: Plug-in's unique resource number
Plug-in resource number

2002
ROMB
--
--
Digits 1-14: SQL object number
Digits 15-28: Fixed at 00
SQL object management information

2003
SPCH
--
--
Fixed to SPCH
Remainder is zero-filled.
SQL object cache

2004
TRAL
****
****
Fixed to TMPRDAREA
Remainder is zero-filled.
RDAREA management information for temporary table

2005
TRAI
****
****
Digits 1-8: RDAREA management block number for temporary table
Digits 9-28: Fixed at 00
RDAREA information for temporary table

3001
PTBL
****
****
Digits 1-8: Table number
Digits 9-28: Fixed to 00
Preprocessing table

3005
DICT
****
****
Fixed to DICT
Remainder is zero-filled.
Dictionary table

3006
VIEW
****
****
Digits 1-8: Viewed table number
Digits 9-28: Fixed to 00
Viewed table

3008
TBPL
****
****
First 5 bytes#2 are an authorization identifier.
Bytes 6-14#3 are a table identifier.
Table definition information buffer

3010
AUTH
****
****
First 14 bytes are an authorization identifier.
User privilege information buffer

3011
OBJI
****
****
Routine object number
Routine object

3012
DTYP
****
****
Fixed to DTYP
Remainder is zero-filled.
Data type definition information

3013
RTPL
****
****
First 12 bytes are a routine identifier.
Bytes 13-14 are a parameters count.
Routine definition information buffer

3014
TPPL
****
****
First 5 bytes#2 are an authorization identifier.
Bytes 6-14#3 are a data type identifier.
User definition type information buffer

3015
DICR
****
****
Fixed to DICR
Remainder is zero-filled.
Dictionary RDAREA change

3016
CONS
****
****
Fixed to CONSEC
Remainder is zero-filled.
CONNECT-related security definition information

3017
SQID
****
****
Digits 1-8: Sequence generator number
Digits 9-28: Fixed at 00
Sequence generator

3018
SQPL
****
****
The first 5 bytes#2 are the authorization identifier.
The first 14 bytes#3 are the sequence generator identifier.
Sequence generator definition information

5001
DICU
--
--
Fixed to DICTMODUTL
Remainder is zero-filled.
Database structure modification utility

5002
LCBF
RDAREA name
--
Digits 1-8: RDAREA number
Digits 9-28: Fixed to 00
--

5003
EXP1
--
--
Fixed to EXPIMPMDL
Remainder is zero-filled.
Database export/import utility

5004
RBAL
Table name
--
Digits 1-8: Table number
Digits 9-28: Fixed to 00
Rebalancing utility

5005
RRAMB
Server name
--
Digits 1-16: Server name
Digits 17-28: Fixed at 00
ZRRAMB update

5006
RCLM
RDAREA name
Table or index name
Digits 1-8: RDAREA number
Digits 9-16: Table or index number
Digits 17-28: Fixed at 00
Free page release utility

--: Not Applicable

Notes

The resource type is output in hexadecimal (4 digits)

The resource information is output in hexadecimal (28 digits).

In UNIX, the RDAREA name that corresponds to the RDAREA number can be determined using the pddbls command.

In UNIX, the generation number is displayed if a table has been replicated by the inner replica facility.

#1

If the table name or RDAREA name under Resource Name 1 or Resource Name 2 cannot be displayed, four asterisks (****) are displayed. In this case, use the table number or RDAREA number from the resource information to identify the target resource.

#2

An authorization identifier of 6 or more bytes is output in the following format:

first-3-bytes-of-authorization-identifier + last-2-bytes-of-authorization-identifier

For example, if the authorization identifier is k87m341, k8741 is output. Note that the output is in ASCII code and 1 byte is output as 2 digits.

#3

Table identifiers, data type identifiers, or sequence generator identifiers that are 10 bytes or more are output in the following format.

first-5-bytes-of-table-identifier, data-type-identifier, or sequence-generator-identifier + last-4-bytes-of-table-identifier, data-type-identifier, or sequence-generator-identifier

For example, if the table identifier is TABLE002498, TABLE2498 is output.

Note that the output is in ASCII code and one byte is expressed as two digits.

7. Messages Related to Sort Processing

This chapter explains messages related to sort processing.

Organization of this chapter

7.1 Messages related to sort processing (Windows edition)

7.2 Messages related to sort processing (UNIX edition)

7.1 Messages related to sort processing (Windows edition)

This section explains messages related to sort processing in the Windows edition of HiRDB.

Organization of this section

7.1.1 Message format

7.1.2 Messages

7.1.1 Message format

Organization of this subsection

(1) Message types

(2) Format of message explanations

(3) End code types

(1) Message types

Two types of messages are output:

Messages at normal termination
If the sorting, selection, or summing terminates normally, these messages are displayed.

Messages at abnormal termination
If an error occurs during the sorting, selection, or summing, these messages are displayed.

(2) Format of message explanations

Messages are described in the following format.

Message ID

Message text

Message explanation

S: System operation

O: Indicates the user or operator operation.

If any of the following messages are output, contact the customer support center:

KBLS201-E, KBLS203-E, KBLS204-E, KBLS205-E, KBLS206-E, KBLS207-E, KBLS208-E, KBLS212-E

(Description of message ID)

The message ID is shown in the KBLSnnn-x format.

KBLS: Program identification code

nnn: Message number

x: Message types

I: Message when processing ends normally

E: Message when an error occurs

(3) End code types

Besides the two types of messages, the following three end codes are used to indicate the status of the end of sorting, selection, or summing. The following table shows the end code types.

Table 7-1 End code types

End status | End code
Normal end | 0
Abend | When messages other than KBLS300-E are output | 1
When the KBLS300-E message is output or there is no message of the SORT program | The abend code of the system is set.

7.1.2 Messages

KBLS201-E

Invalid sort or merge key data was detected.
xx...x yy...y zz

The key data format of a numeric item is invalid.
xx...x indicates the name of the file that contains an error, yy...y indicates an error record number, and zz indicates the number of the key that contains an error.

S: Closes all open files and cancels processing.

O: Check whether the key attribute is correct. If it is incorrect, correct it, and then re-execute the command. Alternatively, correct the format of the key, and re-execute the command.

KBLS202-E

cannot obtain memory of this size.

cannot obtain memory of this size.

S: Closes all open files and cancels processing.

O: Correct the memory size, and re-execute the command.

KBLS203-E

invalid number of keys.

The number of keys is less than 1 or more than 64.

S: Closes all open files and cancels processing.

O: Correct the number of keys, and re-execute the command.

KBLS204-E

invalid key item attribute specification.

An invalid key item attribute is specified.

S: Closes all open files and cancels processing.

O: Correct the key item attribute, and re-execute the command.

KBLS205-E

invalid starting byte position of key.

The position of the start byte of a key is invalid. For example, a smaller value than the minimum record length of an input file is specified.

S: Closes all open files and cancels processing.

O: Correct the position of the start byte of the key, and re-execute the command.

KBLS206-E

invalid byte length for key.

The key byte length is invalid. For example, a larger value than the record length was specified.

S: Closes all open files and cancels processing.

O: Correct the key byte length, and re-execute the command.

KBLS207-E

sum of key position and length is greater than record length.

The length of the key position plus the key length exceeds the minimum record length of an input file. Alternatively, the input file contains too short data.

S: Closes all open files and cancels processing.

O: Correct the position of the start byte of the key and the key byte length, and re-execute the command. Alternatively, correct the data in the input file, and re-execute the command.

KBLS208-E

total key length exceeds 4096 bytes.

Total key length exceeds 4096 bytes.

S: Closes all open files and cancels processing.

O: Correct the number of keys and the byte length, and re-execute the command.

KBLS209-E

I/O error on input file.
xx...x yy...y zz...z

An I/O error occurred in the input file.
xx...x indicates the name of the file that contains an error. yy...y indicates an error record number, and zz...z indicates a system error code.

S: Closes all open files and cancels processing.

O: Correct the error, and re-execute the command.

KBLS210-E

I/O error on temporary file.
ee...e

An I/O error occurred in the temporary file.
ee...e indicates a system error code.

S: Closes all open files and cancels processing.

O: Correct the error, and re-execute the command.

KBLS211-E

I/O error on output file.
xx...x zz...z

An I/O error occurred in the output file.
xx...x indicates the name of the file that contains an error. zz...z indicates a system error code.

S: Closes all open files and cancels processing.

O: Correct the error, and re-execute the command.

KBLS212-E

cannot input because data is shorter than record length.

When an input file is a standard input file, input data is shorter than the specified record length.

S: Closes all open files and cancels processing.

O: Make the length of the input data an integer multiple of the record length, and re-execute the command.

KBLS213-E

invalid organized file or corrupted file.
xx...x

The input file organization and the specified file organization (/gs, /gv, /gr, /gw, /gi, /gx, /ga, or file_org=) do not match. Alternatively, the record length area of an input file is destroyed.
xx...x indicates the name of the file that contains an error.

S: Closes all open files and cancels processing.

O: Correct the input file organization and re-execute the command. If the error persists, re-create an input file and re-execute the command.

KBLS214-E

I/O error on debugging information file.

An I/O error occurred in the debugging information file.

O: Contact the customer support center.

KBLS216-E

file name is specified in directory of temporary file.

In the /w parameter, a file name was specified as a directory for allocating a temporary file for sorting.

S: Cancels processing.

O: Correct the directory name, and re-execute the command.

KBLS217-E

cannot open input file: already in use.

The input file cannot be opened because another process is using it. For example, the file may be opened by the SORT program in another process.

S: Closes all open files and cancels processing.

O: Wait for the other process to terminate, and re-execute the command.

KBLS218-E

cannot open output file: already in use.

The output file cannot be opened because another process is using it. For example, the file may be opened by the SORT program in another process.

S: Closes all open files and cancels processing.

O: Wait for the other process to terminate, and re-execute the command.

KBLS219-E

output file already exists.

When existing files were prevented from being overwritten by using the /i sort option, the file name that already exists was specified as an output file name.

S: Cancels processing.

O: Specify an output file name that does not exist, and re-execute the command.

KBLS220-E

cannot find input file.
xx...x

The specified file name does not exist. xx...x indicates the entered file name.

O: Specify a file name that exists, and re-execute the command.

KBLS221-E

insufficient memory to create output file.

Because there is insufficient disk space, an output file cannot be allocated.

O: Increase the free space, and re-execute the command.

KBLS222-E

I/O error on ISAM file.
xx...x zz...z

An I/O error occurred in the indexed file. xx...x indicates the name of the file that contains an error, and zz...z indicates a system error code.

S: Closes all open files and cancels processing.

O: Correct the error, and re-execute the command.

KBLS225-E

drive is not ready.

A floppy disk is not mounted in the disk drive.

O: Mount the floppy disk, and re-execute the command.

KBLS226-E

drive is not ready.

A floppy disk is not mounted in the disk drive.

O: Mount the floppy disk, and re-execute the command.

KBLS227-E

drive is not ready.

A floppy disk is not mounted in the disk drive.

O: Mount the floppy disk, and re-execute the command.

KBLS228-E

media is read only.

The floppy disk may be write-protected.

O: Unlock the disk, and re-execute the command.

KBLS229-E

media is read only.

The floppy disk may be write-protected.

O: Unlock the disk, and re-execute the command.

KBLS230-E

insufficient memory to create temporary file.

The area for a temporary file cannot be allocated.

S: Closes all open files and cancels processing.

O: Change the directory to allocate the temporary file, and re-execute the command.

KBLS231-E

Input and output file names are the same.

The same name was specified for the input and output files.

O: Specify different file names, and then re-execute the command.

KBLS232-E

Cannot input because data is longer than the maximum record length.

When an input file is a text file, the data is longer than the maximum record length for input data.

S: Closes all open files and cancels processing.

O: Increase the maximum record length of the input file, and then re-execute.

KBLS290-E

A memory shortage occurred.

SORT cannot be executed, because the amount of memory specified in the SORT option is too small.

S: Closes all open files and cancels processing.

O: Increase the work buffer size specified in the /y operand of the wnsort command, the work_size operand of the parameter file specified in the wnsortex command, or the work_size parameter of the environment file. Then, re-execute the command.

KBLS300-E

invalid programming logic.
xxxx

The program error indicated by the detail code xxxx occurred.

S: Closes all open files and cancels processing.

O: Contact the customer support center to report the detail code.

7.2 Messages related to sort processing (UNIX edition)

This section explains messages related to sort processing in the UNIX edition of HiRDB.

Organization of this section

7.2.1 Message format

7.2.2 Messages

7.2.1 Message format

Organization of this subsection

(1) Message types

(2) Format of message explanations

(3) End code types

(1) Message types

Three types of messages are output:

Messages at normal termination
If the sorting, merging, selection, or summing terminates normally, these messages are displayed.

Messages at abnormal termination
If the sorting, merging, selection, or summing terminates abnormally, these messages are displayed.

Messages at system error
If an error by a system call occurs, these messages are displayed.

(2) Format of message explanations

Messages are described in the following format.

Message ID

Message text

Message explanation

S: System operation

O: Indicates the user or operator operation.

If any of the following messages are output, contact the customer support center:

KBLS201-E, KBLS203-E, KBLS204-E, KBLS205-E, KBLS206-E, KBLS207-E, KBLS208-E, KBLS212-E

(Description of message ID)

The message ID is shown in the KBLSnnn-x format.

KBLS: Program identification code

nnn: Message number

x: Message types

I: Message when processing ends normally

E: Message when an error occurs

(3) End code types

Besides the three types of messages, the following three end codes are used to indicate the status of the end of sorting, merging, selection, or summing. The following table shows the end code types.

Table 7-2 End code types

End status | End code
Normal end | 0
Abend | When messages other than KBLS300-E are output | 1
When the KBLS300-E message is output or there is no message of the SORT program | The abend code of the UNIX system is set.

7.2.2 Messages

KBLS201-E

invalid key data for sort.
xx...x yy...y zz

The key data format of a numeric item is invalid.
xx...x indicates the name of the file that contains an error, yy...y indicates an error record number, and zz indicates the number of the key that contains an error.

S: Closes all open files and cancels processing.

O: Check whether the key attribute is correct. If it is incorrect, correct it, and then re-execute the command. Alternatively, correct the format of the key, and re-execute the command.

KBLS202-E

cannot obtain memory of this size.

The specified memory size cannot be reserved.

S: Closes all open files and cancels processing.

O: Correct the memory size, and re-execute the command.

KBLS203-E

invalid number of keys.

The number of keys is less than 1 or more than 64.

S: Closes all open files and cancels processing.

O: Correct the number of keys, and re-execute the command.

KBLS204-E

invalid key item attribute specification.

An invalid key item attribute is specified.

S: Closes all open files and cancels processing.

O: Correct the key item attribute, and re-execute the command.

KBLS205-E

invalid starting byte position of key.

7 digits or more are specified in the start byte of a key.

S: Closes all open files, and cancels processing. Debugging information is generated.

O: Correct the position of the start byte of the key, and re-execute the command.

KBLS206-E

invalid byte length for key.

7 digits or more are specified in the key byte length.

S: Closes all open files, and cancels processing. Debugging information is generated.

O: Correct the key byte length, and re-execute the command.

KBLS207-E

sum of key position and length is greater than record length.

The length of the key position plus the key length exceeds the minimum record length of an input file. Or, the data in the input file is too short.

S: Closes all open files, and cancels processing.

O: Correct the position of the start byte of the key and the key byte length, and re-execute the command. Alternatively, correct the data in the input file, and then re-execute the command.

KBLS208-E

total key length exceeds 4096 bytes.

Total key length exceeds 4096 bytes.

S: Closes all open files and cancels processing.

O: Correct the number of keys and the byte length, and re-execute the command.

KBLS209-E

I/O error on input file.
xx...x yy...y

An I/O error occurred in the input file.
xx...x indicates the name of the file that contains an error. yy...y indicates an error record number.

S: Closes all open files, cancels processing, and generates a debugging information file (sortdmp).

O: Correct the error, and re-execute the command.

KBLS210-E

I/O error on temporary file.

An I/O error occurred in the temporary file.

S: Closes all open files, cancels processing, and generates a debugging information file (sortdmp).

O: Correct the error, and re-execute the command.

KBLS211-E

I/O error on output file.
xx...x

An I/O error occurred in the output file.
xx...x indicates the name of the file that contains an error.

S: Closes all open files, cancels processing, and generates a debugging information file (sortdmp).

O: Correct the error, and re-execute the command.

KBLS212-E

cannot input because data is shorter than record length.

When an input file is a standard input file, input data specified is shorter than the record length.

S: Closes all open files and cancels processing.

O: Make the length of the input data an integer multiple of the record length, and re-execute the command.

KBLS213-E

invalid organized file or corrupted file.
xx...x

The input file organization and the specified file organization (-S, -V, -R, -W, -I, -X, or -A) do not match. Alternatively, the record length area of an input file is destroyed.
xx...x indicates the name of the file that contains an error.

S: Closes all open files and cancels processing.

O: Correct the input file organization and re-execute the command. If the error persists, re-create an input file and re-execute the command.

KBLS214-E

I/O error on debugging information file.

An I/O error occurred in the debugging information file.

O: Contact the customer support center.

KBLS216-E

file name is specified in directory of temporary file.

In the -T or -T2 option, a file name was specified as a directory for allocating a temporary file for sorting.

S: Cancels processing.

O: Correct the directory name, and re-execute the command.

KBLS217-E

cannot open input file: already in use.

The input file cannot be opened because another process is using it. For example, the file might have been opened by the SORT program in another process.

S: Closes all open files and cancels processing.

O: Wait for the other process to terminate, and re-execute the command.

KBLS218-E

cannot open output file: already in use.

The output file cannot be opened because another process is using it. For example, the file might have been opened by the SORT program in another process.

S: Closes all open files and cancels processing.

O: Wait for the other process to terminate, and re-execute the command.

KBLS219-E

output file already exists.

While existing files were prevented from being overwritten using the -i option, a file name that already exists was specified as an output file name.

S: Cancels processing.

O: Specify an output file name that does not exist, and then re-execute the command.

KBLS232-E

cannot input because data is greater then max-record length

An attempt was made to input data longer than the specified maximum record length.

S: Cancels processing.

O: Correct the maximum record length, and then re-execute the command.

KBLS290-E

insufficient memory to execute

There is not enough used memory capacity specified in the SORT option, so processing cannot continue.

S: Closes all open files, cancels processing, and generates a debugging information file.

O: Increase the size of the used memory capacity specified in the SORT option, and then re-execute the command.

KBLS300-E

invalid programming logic, error code = xxxx

The program error indicated by the error code xxxx occurred.

S: Closes all open files and cancels processing.

O: Contact the customer support center to report the error code.

8. SQLSTATE

This chapter discusses the code SQLSTATE.

Organization of this chapter

8.1 SQLSTATE

8.1 SQLSTATE

SQLSTATE is one of the codes returned by HiRDB after execution of SQL statements.

This code consists of five digits, where the first two digits indicate the class and the remaining three digits indicate the subclass.

If you specify YES in the PDSTANDARDSQLSTATE client environment variable or Y in the pd_standard_sqlstate system common definition, detailed information is set in SQLSTATE.

Table 8-1 Classes of SQLSTATE returned by HiRDB and their explanations lists and describes classes of SQLSTATE returned by HiRDB and tells the user where in this chapter to find detailed information for each class. Tables 8-2 SQLSTATE class 00 through Tables 8-40 SQLSTATE class R2 list and explains the meanings of SQLSTATE returned by HiRDB for each class.

Table 8-41 Classes of SQLSTATE returned by HiRDB and their explanations lists and describes classes of SQLSTATE, and tells the user which of the following tables provide detailed information for each class. Tables 8-42 SQLSTATE class 00 through Tables 8-47 SQLSTATE class R2 list and explains the meanings of SQLSTATE returned by HiRDB for each class.

When SQLSTATE is returned, the user must reference the message or the information provided in the Explanation column of the applicable table, and take an appropriate action.

Organization of this section

8.1.1 When the PDSTANDARDSQLSTATE client environment variable is set to YES or the pd_standard_sqlstate system common definition is set to Y

8.1.2 When the PDSTANDARDSQLSTATE client environment variable is set to NO or the pd_standard_sqlstate system common definition is set to N

8.1.1 When the PDSTANDARDSQLSTATE client environment variable is set to YES or the pd_standard_sqlstate system common definition is set to Y

Table 8-1 Classes of SQLSTATE returned by HiRDB and their explanations

Class | Explanation | Reference
00 | Terminated normally. | Table 8-2
01 | A warning was issued. | Table 8-3
02 | There is no data. | Table 8-4
07 | An error occurred on a dynamic SQL statement. | Table 8-5
08 | A connection violation occurred. | Table 8-6
0A | The facility is not supported. | Table 8-7
0F | A locator exception occurred. | Table 8-8
0K | RESIGNAL was executed while the handler was disabled. | Table 8-9
21 | A base violation occurred. | Table 8-10
22 | A data exception occurred. | Table 8-11
23 | An integrity constraint violation occurred. | Table 8-12
24 | The cursor status is invalid. | Table 8-13
25 | The transaction status is invalid. | Table 8-14
26 | The SQL statement name is invalid. | Table 8-15
28 | The specified authorization identifier is invalid. | Table 8-16
2C | The character set name is invalid. | Table 8-17
2F | An SQL routine exception occurred. | Table 8-18
33 | The SQL descriptor name is invalid. | Table 8-19
34 | The cursor name is invalid. | Table 8-20
37 | A syntax error or access rule violation was detected in a dynamic SQL statement. | Table 8-21
38 | An external routine exception occurred. | Table 8-22
40 | The transaction rolled back. | Table 8-23
42 | A syntax error or access rule violation was detected. | Table 8-24
45 | An unprocessed user definition exception occurred. | Table 8-25
51 | An error related to a specific SQL facility occurred (error caused by a nonstandard specific SQL facility). | Table 8-26
52 | The environment is not ready for SQL execution (this status occurs when the environment refuses to execute SQL statements. The environment status much be changed). | Table 8-27
53 | The system resource status does not allow SQL execution (this status occurs when SQL execution is refused due to the system status, owing to a problem such as a shortage of memory or resources. The user might need to take some action on the system). | Table 8-28
54 | The application program status is invalid (error caused by application program settings, details of processing, attributes, status, etc.). | Table 8-29
55 | An error occurred on the remote system (such as an OS error or a communication error). | Table 8-30
56 | The maximum or limit value was reached (error based on the maximum or minimum value permitted by the processors or system). | Table 8-31
57 | The status of an SQL execution procedure object is invalid (error related to an SQL object, routine object, or SQL pool object). | Table 8-32
58 | The RDAREA specification or RDAREA status is invalid (error caused by the specification, status, and type of RDAREA). | Table 8-33
59 | The abstract data type or plug-in status is invalid (error caused by the abstract data type or plug-in registration status). | Table 8-34
5A | The list name or list status is invalid. | Table 8-35
5B | Processing was canceled by a user request (such as an interrupt). | Table 8-36
5C | A system error other than those described above or below occurred. | Table 8-37
5E | The view object status is invalid. | Table 8-38
IZ | An error specific to a utility or non-SQLAPI occurred. | Table 8-39
R2 | There is no data. | Table 8-40

Table 8-2 SQLSTATE class 00

SQLSTATE | Explanation | SQLCODE
00000 | Terminated normally. | 0

Table 8-3 SQLSTATE class 01

SQLSTATE | Explanation | SQLCODE
01000 | Terminated normally with a warning. | 0
0100C | A dynamic results set was returned. | +120
0100D | Another result set was returned. | +121
0100E | An attempt was made to return too many result sets. | +120
01R00 | Terminated normally with a warning. | Positive number other than 100 or 110

Table 8-4 SQLSTATE class 02

SQLSTATE | Explanation | SQLCODE
02000 | There is no data. | 100
02001 | There is no other result set to be returned. | 100

Table 8-5 SQLSTATE class 07

SQLSTATE
Explanation
SQLCODE

07001
One of the following errors is present:

The data type or data length of an input variable set in the SQL descriptor area is invalid.
For details, refer to the KFPA11311-E message.

The number of ? parameters in the SQL statement does not match the number specified in SQLD in the SQL descriptor area.
For details, refer to the KFPA11313-E message.

-311
-313

07002
The data type or data length of an output variable set in the SQL descriptor area is invalid.
For details, refer to the KFPA11311-E message.
-311

07003
Refer to the KFPA11506-E message.
-506

07005
Refer to the KFPA11507-E message.
-507

07006
One of the following errors is present:

The data type of the input variable cannot be converted, or the structure of the input variable does not match.
For details, refer to the KFPA11301-E message

The data type of the input variable cannot be converted, or the structure of the input variable does not match.
For details, refer to the KFPA11303-E message.

-301
-303

07008
Refer to the KFPA11310-E message.
-310

07501
Refer to the KFPA11308-E message.
-308

07502
Refer to the KFPA11340-E message.
-340

07503
Refer to the KFPA11901-E message.
-901

Table 8-6 SQLSTATE class 08

SQLSTATE
Explanation
SQLCODE

08000
The authorization identifier is invalid.
For details, refer to the KFPA11564-E message.
-564

08002
Refer to the KFPA11752-E message.
-752

08007
Refer to the KFPA11966-E message.
-966

08603
Refer to the KFPA11940-E message.
-940

08605
Refer to the KFPA11990-E message.
-990

08606
Refer to the KFPA19632-E message.
-1632

08620
Refer to the KFPA11932-E message.
-932

08621
Refer to the KFPA19521-E message.
-1521

08622
Refer to the KFPA11930-E message.
-930

Table 8-7 SQLSTATE class 0A

SQLSTATE | Explanation | SQLCODE
0A503 | Refer to the KFPA11948-E message. | -948
0A504 | Refer to the KFPA11950-E message. | -950
0A505 | Refer to the KFPA11988-E message. | -988
0A507 | Refer to the KFPA11899 message. | -899

Table 8-8 SQLSTATE class 0F

SQLSTATE | Explanation | SQLCODE
0F001 | Refer to the KFPA11364-E message. | -364

Table 8-9 SQLSTATE class 0K

SQLSTATE | Explanation | SQLCODE
0K000 | Refer to the KFPA19403-E message. | -1403

Table 8-10 SQLSTATE class 21

SQLSTATE | Explanation | SQLCODE
21501 | Refer to the KFPA11449-E message. | -449
21502 | Refer to the KFPA11450-E message. | -450

Table 8-11 SQLSTATE class 22

SQLSTATE
Explanation
SQLCODE

22001
One of the following errors is present:

An input data or a function argument is too long.
For details, refer to the KFPA11404-E message.

The length of a character string data item falls beyond the permitted value range.
For details, refer to the KFPA11420-E message.

Character truncation occurred.
For details, refer to the KFPA11453-E message.

Data in the RETURN statement is longer than the return value.
For details, refer to the KFPA11469-E message.

-404
-420
-453
-469

22002
A data value assigned to the locator is the null value, but no indicator variable is specified.
For details, refer to the KFPA11305-E and KFPA11366-E messages.
-305
-366

22003
One of the following errors is present:

Input data falls beyond the permitted value range.
For details, refer to the KFPA11302-E message.

The ength of data to be output exceeds the variable attribute.
For details, refer to the KFPA11304-E message.

An input variable falls beyond the permitted value range.
For details, refer to the KFPA11326-E message.

The source data falls beyond the convertible range.
For details, refer to the KFPA11453-E or KFPA19345-E message.

The operation resulted in an overflow because the value fell beyond the permitted range for the data type.
For details, refer to the KFPA11801-E message.

An overflow occurred during set function processing.
For details, refer to the KFPA11802-E message.

-302
-304
-326
-453
-801
-802
-1345

22004
One of the following errors is present:

The null value was specified for a column for which the null value is not permitted.
For details, refer to the KFPA11212-E message.

The null value was specified as a signal value.
For details, refer to the KFPA19294-E message.

-212
-1294

22007
The operation resulted in an overflow because the specified date representation is invalid. For details, refer to the KFPA11801-E message.
-801

22008
One of the following errors is present:

The value in the date field falls beyond the permitted range.
For details, refer to the KFPA11326-E message.

The character string representation is invalid in the date field.
For details, refer to the KFPA11416-E message.

A date field operation resulted in an overflow.
For details, refer to the KFPA11801-E message.

-326
-416
-801

2200A
Refer to the KFPA11938-E message.
-938

22011
In the SUBSTR scalar function, the end location falls before the start location.
For details, refer to the KFPA11427-E message.
-427

22012
A division by zero error occurred during an arithmetic operation.
For details, refer to the KFPA11800-E and KFPA19326-E messages.
-800
-1326

22014
Refer to the KFPA11367-E message.
-367

22015
The value of the time interval field falls beyond the permitted range.
For details, refer to the KFPA11326-E message.
-326

22018
The format of a character-string literal in the conversion source data or the value of the conversion source data is invalid.
For details, refer to the KFPA11453-E message.
-453

22019
The length of the escape character specified in the LIKE, XLIKE, or SIMILAR predicate is not one character.
For details, refer to the KFPA11424-E message.
-424

22025
An invalid method was used to specify the escape character or pattern character string in the LIKE, XLIKE, or SIMILAR predicate.
For details, refer to the KFPA11424-E message.
-424

22027
The length of the TRIM character is not one character.
For details, refer to the KFPA11425-E message.
-425

2202F
The number of elements in the input data is greater than the maximum number of elements for a repetition column.
For details, refer to the KFPA11302-E message.
-302

22501
The number of elements in the input data does not match the number of elements in the array.
For details, refer to the KFPA11302-E message.
-302

22503
Refer to the KFPA11306-E message.
-306

22504
Refer to the KFPA11310-E message.
-310

22505
Data in the input variable contradicts the information specified in the embedded variable, parameter variable declaration, or SQL descriptor area. (If the input variable is variable-length data, the input variable length exceeds the maximum value or is less than 0).
For details, refer to the KFPA11326-E message.
-326

22506
Data in the input variable contradicts the information specified in the embedded variable, parameter variable declaration, or SQL descriptor area. (If the input variable is LOB data, the input variable length exceeds the maximum value or is less than 0).
For details, refer to the KFPA11326-E message.
-326

22507
Data in the input variable contradicts the information specified in the embedded variable, parameter variable declaration, or SQL descriptor area. (If the input variable is a repetition column, the current number of elements for the input variable exceeds the maximum number of elements or is less than 0).
For details, refer to the KFPA11326-E message.
-326

22508
Refer to the KFPA11170-E message.
-170

22509
Refer to the KFPA11223-E message.
-223

2250G
One of the following errors is present:

The format specified in the scalar function is invalid.
For details, refer to the KFPA11360-E message.

A scalar function's representation using a character string does not match the specified format.
For details, refer to the KFPA11361-E message.

A required format element is missing in the format specified by the scalar function.
For details, refer to the KFPA11362-E message.

-360
-361
-362

2250J
Refer to the KFPA11316-E message.
-316

22510
Refer to the KFPA11381-E message.
-381

22511
Refer to the KFPA11430-E message.
-430

22512
Refer to the KFPA11993-E message.
-993

22513
Refer to the KFPA19183-E message.
-1183

22514
Refer to the KFPA19320-E message.
-1320

22515
Refer to the KFPA19325-E message.
-1325

22516
Refer to the KFPA19801-E message.
-1801

22520
A key value cannot be generated for the data type from the substructure value specified in the definition of substructure index.
For details, refer to the KFPA19311-E message.
-1311

22521
Refer to the KFPA19346-E message.
-1346

22522
Refer to the KFPA19347-E message.
-1347

22523
Refer to the KFPA19348-E message.
-1348

22524
Refer to the KFPA19349-E message.
-1349

22525
Refer to the KFPA19350-E message.
-1350

22526
Refer to the KFPA19351-E message.
-1351

22527
Refer to the KFPA19352-E message.
-1352

22528
Refer to the KFPA19353-E message.
-1353

22529
Refer to the KFPA19354-E message.
-1354

Table 8-12 SQLSTATE class 23

SQLSTATE
Explanation
SQLCODE

23001
A RESTRICT violation occurred.
For details, refer to the KFPA11451-E message.
-451

23502
A NOT NULL constraint violation occurred.
For details, refer to the KFPA11210-E message.
-210

23503
A violation of a referential constraint occurred.
Refer to the KFPA11451-E message.
-451

23505
One of the following errors is present:

An attempt was made to create an index with UNIQUE specified, but the table data contains duplicate column values.
For details, refer to the KFPA11603-E message.

An attempt was made to add a duplicate column value to an index with UNIQUE specified, or to the primary key. Alternatively, an attempt was made to update a column value to a duplicate value.
For details, refer to the KFPA11803-E message.

-603
-803

23506
Refer to the KFPA19582-E message.
-1582

23507
Refer to the KFPA19717-E message.
-1717

23514
A violation of a check constraint occurred.
For details, refer to the KFPA11451-E message.
-451

Table 8-13 SQLSTATE class 24

SQLSTATE
Explanation
SQLCODE

24000
This cursor cannot be used to update or delete rows due to one of the following errors:

The cursor is not open.

The row has not been fetched.

All rows at the cursor have already been searched.

An error occurred while a row was being fetched.

For details, refer to the KFPA11330-E and KFPA11332-E messages.
-330
-332

24501
Refer to the KFPA11500-E message.
-500

24502
Refer to the KFPA11711-E message.
-711

24504
Refer to the KFPA11501-E message.
-501

24505
Refer to the KFPA11502-E message.
-502

24506
Refer to the KFPA11505-E message.
-505

24507
Refer to the KFPA11994-E message.
-994

24509
Refer to the KFPA19508-E message.
-1508

24510
Refer to the KFPA19509-E message.
-1509

Table 8-14 SQLSTATE class 25

SQLSTATE | Explanation | SQLCODE
25501 | Refer to the KFPA11980-E message. | -980
25502 | Refer to the KFPA11998-E message. | -998
25503 | Refer to the KFPA19703-E message. | -1703

Table 8-15 SQLSTATE class 26

SQLSTATE | Explanation | SQLCODE
26000 | Refer to the KFPA11512-E message. | -512

Table 8-16 SQLSTATE class 28

SQLSTATE | Explanation | SQLCODE
28501 | Refer to the KFPA11560-E message. | -560
28502 | Refer to the KFPA11561-E message. | -561

Table 8-17 SQLSTATE class 2C

SQLSTATE | Explanation | SQLCODE
2C000 | Refer to the KFPA19104-E message. | -1104

Table 8-18 SQLSTATE class 2F

SQLSTATE | Explanation | SQLCODE
2F002 | Refer to the KFPA11495-E message. | -495

Table 8-19 SQLSTATE class 33

SQLSTATE | Explanation | SQLCODE
33501 | Refer to the KFPA19506-E message. | -1506
33502 | Refer to the KFPA19507-E message. | -1507

Table 8-20 SQLSTATE class 34

SQLSTATE | Explanation | SQLCODE
34501 | Refer to the KFPA11233-E message. | -233

Table 8-21 SQLSTATE class 37

SQLSTATE | Explanation | SQLCODE
37901 | Refer to the KFPA11331-E message. | -331

Table 8-22 SQLSTATE class 38

SQLSTATE | Explanation | SQLCODE
38501 | Refer to the KFPA11245-E message. | -245
38502 | Refer to the KFPA11246-E message. | -246
38503 | Refer to the KFPA11247-E message. | -247
38504 | Refer to the KFPA11248-E message. | -248
38507 | Refer to the KFPA19335-E message. | -1335
38508 | Refer to the KFPA19336-E message. | -1336

Table 8-23 SQLSTATE class 40

SQLSTATE
Explanation
SQLCODE

40000
Refer to the KFPA11716-E message.
-716

40001
Serialization failed due to one of the following causes:

Another user is using the resources of the specified table, and for this reason the lock prohibits execution of the SQL statement, DELETE (operation) command, or DELETE subcommand.
For details, refer to the KFPA11770-I message.

A deadlock occurred.
For details, refer to the KFPA11911-E message.

-770
-911

40501
Refer to the KFPA11713-E message.
-713

40503
Refer to the KFPA11756-E message.
-756

40505
Refer to the KFPA11806-E message.
-806

40506
Refer to the KFPA11809-I message.
-809

40507
Refer to the KFPA11822-E message.
-822

40508
Refer to the KFPA11879-E message.
-879

40509
Refer to the KFPA11487-E message.
-487

4050F
Refer to the KFPA11912-E message.
-912

4050G
Refer to the KFPA11913-E message.
-913

4050N
Refer to the KFPA11931-E message.
-931

4050I
Refer to the KFPA11925-E message.
-925

4050K
Refer to the KFPA11927-E message.
-927

4050L
Refer to the KFPA19940-E message.
-1940

4050M
Refer to the KFPA19941-E message.
-1941

40510
Refer to the KFPA11488-E message.
-488

40511
Refer to the KFPA11489-E message.
-489

40512
Refer to the KFPA11490-E message.
-490

40513
Refer to the KFPA11494-E message.
-494

40514
Refer to the KFPA11530-E message.
-530

40515
Refer to the KFPA11595-E message.
-595

40516
Refer to the KFPA11740-E message.
-740

40517
Refer to the KFPA11797-E message.
-797

40518
Refer to the KFPA11808-E message.
-808

40519
Refer to the KFPA11828-E message.
-828

40520
Refer to the KFPA11876-E message.
-876

40521
Refer to the KFPA11877-E message.
-877

40522
Refer to the KFPA11878-E message.
-878

40523
Refer to the KFPA11886-E message.
-886

40525
Refer to the KFPA11892-E message.
-892

40526
Refer to the KFPA11945-E message.
-945

40527
Refer to the KFPA11958-E message.
-958

40528
Refer to the KFPA11959-E message.
-959

40529
Refer to the KFPA11981-E message.
-981

40530
Refer to the KFPA11986-E message.
-986

40531
Refer to the KFPA11989-E message.
-989

40532
Refer to the KFPA11992-E message.
-992

40533
Refer to the KFPA19311-E message.
-1311

40534
Refer to the KFPA19313-E message.
-1313

40535
Refer to the KFPA19400-E message.
-1400

40537
Refer to the KFPA19455-E message
-1455

40538
Refer to the KFPA19703-E message.
-1703

40539
Refer to the KFPA19716-E message.
-1716

40540
Refer to the KFPA19633-E message.
-1633

40541
Refer to the KFPA11898-E message.
-898

40542
The following SQL statements cannot be executed on a shared table unless the LOCK statement with IN EXCLUSIVE MODE specified is executed:

INSERT statement

UPDATE statement that accompanies index updating

UPDATE statement specifying DEFAULT as the update value for the TIMESTAMP column for which the DEFAULT clause with USING BES specified is defined

DELETE statement

For details, refer to the KFPA11296-E message.
-296

40543
Refer to the KFPA19713-E message.
-1713

40544
Refer to the KFPA19721-E message.
-1721

40601
Refer to the KFPA11917-E message.
-917

40602
Refer to the KFPA11918-E message.
-918

40603
Refer to the KFPA11891-E message.
-891

40620
Refer to the KFPA11920-E message.
-920

40621
Refer to the KFPA11928-I message.
-928

40622
Refer to the KFPA19701-E message.
-1701

40623
Refer to the KFPA19702-E message.
-1702

40701
Refer to the KFPA11934-E message.
-934

40702
Refer to the KFPA11953-E message.
-953

40703
Refer to the KFPA11342-E message.
-342

40A01
The transaction rolled back due to an integrity error in the dictionary.
For details, refer to the message corresponding to the SQLCODE.
--

40A02
The transaction rolled back due to a basic unit error in SQL.
For details, refer to the message corresponding to the SQLCODE.
--

40B01
The transaction rolled back due to a list processing error.
For details, refer to the message corresponding to the SQLCODE.
--

40B02
The transaction rolled back due to an index processing error.
For details, refer to the message corresponding to the SQLCODE.
--

40B03
The transaction rolled back due to an inner replica error.
For details, refer to the message corresponding to the SQLCODE.
--

40B04
The transaction rolled back due to a cursor processing error.
For details, refer to the message corresponding to the SQLCODE.
--

40B05
The transaction rolled back due to a transaction error.
For details, refer to the message corresponding to the SQLCODE.
--

40B08
The transaction rolled back due to a resource release failure.
For details, refer to the message corresponding to the SQLCODE.
--

40B09
The transaction rolled back due to a routine processing error.
For details, refer to the message corresponding to the SQLCODE.
--

40B10
The transaction rolled back due to a privilege manipulation error.
For details, refer to the message corresponding to the SQLCODE.
--

40B11
The transaction rolled back due to an update processing error.
For details, refer to the message corresponding to the SQLCODE.
--

40B12
The transaction rolled back due to a constraint processing error.
For details, refer to the message corresponding to SQLCODE.
--

40B13
The transaction rolled back due to a preprocessing error.
For details, refer to the message corresponding to the SQLCODE.
--

40B14
The transaction rolled back due to an intermediate result acquisition failure.
For details, refer to the message corresponding to the SQLCODE.
--

40B15
The transaction rolled back due to an abstract data type error.
For details, refer to the message corresponding to the SQLCODE.
--

40B16
The transaction rolled back due to a communication processing error.
For details, refer to the message corresponding to the SQLCODE.
--

40B17
The transaction rolled back due to a lock error.
For details, refer to the message corresponding to the SQLCODE.
--

40B18
The transaction rolled back due to an array processing error.
For details, refer to the message corresponding to the SQLCODE.
--

40B19
The transaction rolled back due to a memory allocation failure.
For details, refer to the message corresponding to the SQLCODE.
--

40B20
The transaction rolled back due to an embedded language syntax error.
For details, refer to the message corresponding to the SQLCODE.
--

40C01
The transaction rolled back due to an error in the definition SQL.
For details, refer to the message corresponding to the SQLCODE.
--

40C02
The transaction rolled back because there is already a resource to be defined.
For details, refer to the KFPA11601-E message.
-601

40C03
One of the following errors is present:

The table, index, trigger, or sequence generator was not found in the HiRDB system.
For details, refer to the KFPA11204-E message.

The specified routine was not found in the HiRDB system.
For details, refer to the KFPA11529-E message.

-204
-529
-624

40C04
One of the following errors is present:

The table, index, trigger, or sequence generator was not found in the HiRDB system.
For details, refer to the KFPA11204-E message.

The specified user-defined type was not found in the HiRDB system.
For details, refer to the KFPA11224-E message.

The specified routine was not found in the HiRDB system.
For details, refer to the KFPA11529-E message.

-204
-224
-529
-624
-660

40C05
One of the following errors is present:

The table, index, trigger, or sequence generator was not found in the HiRDB system.
For details, refer to the KFPA11204-E message.

The specified user-defined type was not found in the HiRDB system.
For details, refer to the KFPA11224-E message.

The specified routine was not found in the HiRDB system.
For details, refer to the KFPA11529-E message.

The following SQL statements cannot be executed due to a missing schema:
ALTER PROCEDURE
ALTER ROUTINE
CREATE FUNCTION
CREATE INDEX
CREATE PROCEDURE
CREATE TABLE
CREATE TRIGGER
CREATE TYPE
CREATE VIEW
DROP SCHEMA
For details, refer to the KFPA11656-E message.

The audit event specified in AUDIT is not defined.
For details, refer to the KFPA11909-E message.

The SQL statement specified in the connection security facility cannot be executed.
For details, refer to the KFPA19633-E message.

-204
-224
-529
-624
-656
-721
-909
-1633

40C06
The transaction rolled back because the same index was already defined during a CREATE INDEX operation.
For details, refer to the KFPA11601-E message.
-601

40C07
One of the following errors is present:

The table identifier, index identifier, routine identifier, trigger identifier, constraint name, data type identifier, or index type identifier specified in the SQL statement has already been defined.
For details, refer to the KFPA11601-E message.

The specified schema has already been defined.
For details, refer to the KFPA11664-E message.

The audit event specified in CREATE AUDIT has already been defined.
For details, refer to the KFPA11908-E message.

The SQL statement specified in the connection security facility cannot be executed.
For details, refer to the KFPA19633-E message.

-601
-664
-721
-908
-1633

40C08
One of the following errors is present:

The user is not authorized to execute the SQL statement.
For details, refer to the KFPA11548-E message.

The executor cannot define or delete access privileges for the table because the executor is not the owner of the table.
For details, refer to the KFPA11551-E message.

Because the user does not have DBA privileges, the user cannot execute the following SQL statements:
GRANT DBA
GRANT CONNECT
GRANT RDAREA
GRANT SCHEMA
REVOKE DBA
REVOKE CONNECT
REVOKE RDAREA
REVOKE SCHEMA
For details, refer to the KFPA11552-E message.

The user cannot create schemas, delete schemas, re-create procedures, or re-create SQL objects as triggers for another user.
For details, refer to the KFPA11573-E message.

The user cannot define schemas because the user does not have schema definition privileges.
For details, refer to the KFPA11579-E message.

The user cannot define a table or an index that is owned by another user.
For details, refer to the KFPA11607-E message.

The following SQL statements cannot be executed due to a missing schema:
ALTER PROCEDURE
ALTER ROUTINE
CREATE FUNCTION
CREATE INDEX
CREATE PROCEDURE
CREATE SEQUENCE
CREATE TABLE
CREATE TRIGGER
CREATE TYPE
CREATE VIEW
DROP SCHEMA
For details, refer to the KFPA11656-E message.

Because the user does not have audit privileges, the user cannot execute the following operations:
CREATE AUDIT
DROP AUDIT
GRANT AUDIT
DROP TABLE for audit trail table
For details, refer to the KFPA11905-E message.

The SQL statement specified in the connection security facility cannot be executed.
For details, refer to the KFPA19633-E message.

-548
-551
-552
-573
-579
-607
-656
-905
-1633

40D01
Refer to the KFPA11940-E message.
-940

40D10
Refer to the KFPA19451-E message.
-1451

40D30
Refer to the KFPA11948-E message.
-948

40D31
Refer to the KFPA11950-E message.
-950

40D50
Refer to the KFPA11404-E message.
-404

40D51
Refer to the KFPA11801-E message.
-801

40D52
Refer to the KFPA11223-E message.
-223

40D53
Refer to the KFPA11321-E message.
-321

40D70
Refer to the KFPA11210-E message.
-210

40D71
Refer to the KFPA11603-E message.
-603

40D72
Refer to the KFPA11451-E message.
-451

40D73
One of the following errors is present:

A violation of a referential constraint or check constraint occurred.
For details, refer to the KFPA11451-E message.

The column cannot be deleted for one of the following reasons:
A check constraint is defined for the table that contains the column to be deleted.
A reference constraint (foreign key) is defined for the table that contains the column to be deleted.
The table containing the column to be deleted is the referenced table for the reference constraint.
For details, refer to the KFPA19582-E message.

-451
-1582

40D90
Refer to the KFPA11996-E message.
-996

40DB0
Refer to the KFPA11492-E message.
-492

40DB1
Refer to the KFPA11493-E message.
-493

40DD0
Refer to the KFPA11204-E message.
-204

40DD1
Refer to the KFPA11224-E message.
-224

40DD2
Refer to the KFPA11101-E message.
-101

40DD3
There is no column in a WITH clause or correlation name query of a table or of a derived table in the FROM clause.
For details, refer to the KFPA11205-E message.
-205

40DD4
Refer to the KFPA19727-E message.
-1727

40DH0
Refer to the KFPA11206-E message.
-206

40DH1
Refer to the KFPA11601-E message.
-601

40DH2
Refer to the KFPA11656-E message.
-656

40DH3
Refer to the KFPA11660-E message.
-660

40DH4
Refer to the KFPA11664-E message.
-664

40DH5
Refer to the KFPA11743-E message.
-743

40DH6
Refer to the KFPA11744-E message.
-744

40DH7
Refer to the KFPA11749-E message.
-749

40DH8
Refer to the KFPA11741-E message.
-741

40DH9
Refer to the KFPA11624-E message.
-624

40DHA
Refer to the KFPA11893-E message.
-893

40DHB
Refer to the KFPA11894-E message.
-894

40DHC
CLUSTER KEY, PRIMARY KEY, or PRIMARY CLUSTER KEY is not defined for the table.
For details, refer to the KFPA11207-E message.
-207

40DHD
The specified data type does not have the specified attribute.
For details, refer to the KFPA11228-E message.
-228

40DHE
PUBLIC, MASTER, HiRDB, or ALL is specified for the authorization identifier.
For details, refer to the KFPA11549-E message.
-549

40DHF
One of the following errors is present:

The same RDAREA name is specified more than once for the primary key, cluster key, RDAREA for table, RDAREA for LOB column, or RDAREA for LOB attribute in CREATE TABLE.

The same RDAREA name is specified more than once in CREATE INDEX.

An attempt was made to add the RDAREA that already contains this table by using ALTER TABLE.

For details, refer to the KFPA11574-E message.
-574

40DHG
A plug-in index cannot be applied to routines. A plug-in index can be applied to a plug-in function that has been implemented by a plug-in and for which SCAN TYPE is specified as the operation qualifier of the plug-in IDL.
For details, refer to the KFPA11583-E message.
-583

40DHH
The column specified as an index is not appropriate for the index type.
For details, refer to the KFPA11584-E message.
-584

40DHI
NULL cannot be specified in the column definition for a table with FIX specified.
For details, refer to the KFPA11591-E message.
-591

40DHJ
NULL cannot be specified in the column definition for a column for which a single column uniqueness constraint definition or a multicolumn uniqueness constraint definition is defined.
For details, refer to the KFPA11592-E message.
-592

40DHK
ALTER TABLE cannot delete a column for which BLOB or abstract is specified as its data type.
For details, refer to the KFPA11597-E message.
-597

40DHL
Another plug-in index has already been applied to the routine.
For details, refer to the KFPA11600-E message.
-600

40DHM
The total number of columns per table has already exceeded the permitted maximum value (30,000).
For details, refer to the KFPA11602-E message.
-602

40DHN
SUPPRESS cannot be specified for a table with the FIX attribute.
For details, refer to the KFPA11605-E message.
-605

40DHP
Neither a variable-length column, nor a column with a user-defined type, nor a repetition column can be defined for a table with the FIX attribute.
For details, refer to the KFPA11609-E message.
-609

40DHQ
Because this is not a hash row-partitioned table, the hash function cannot be renamed nor can an RDAREA be added.
For details, refer to the KFPA11611-E message.
-611

40DHR
The same column name cannot be defined more than once for the same table.
For details, refer to the KFPA11612-E message.
-612

40DHT
A FLOAT or SMALLFLT type column cannot be specified for a multicolumn index, multicolumn primary key, or multicolumn cluster key.
For details, refer to the KFPA11615-E message.
-615

40DHU
The column name or the column name constituting a primary key or cluster key specified in CREATE INDEX is duplicated.
For details, refer to the KFPA11619-E message.
-619

40DHV
Neither UNIQUE nor PRIMARY KEY can be specified for a flexible hash-partitioned table or a matrix partitioning table using flexible hash partitioning.
For details, refer to the KFPA11620-E message.
-620

40DHW
An index with UNIQUE specified cannot be defined for a repetition column.
For details, refer to the KFPA11621-E message.
-621

40DHX
One of the following errors is present with regard to the hash function name:

The specified hash function name does not exist.

The key length of the specified hash function is greater than the column length of the hash partitioning key.

For details, refer to the KFPA11622-E message.
-622

40DHY
The following table restriction definitions cannot be specified for a repetition column:

CLUSTER KEY: Cluster key

PRIMARY KEY: Primary key

FOREIGN KEY: Foreign key

For details, refer to the KFPA11625-E message.
-625

40DHZ
When a table is defined or a table definition is changed, neither a NOT NULL constraint nor a character set can be specified for a repetition column.
For details, refer to the KFPA11628-E message.
-628

40DI0
If the column type is not abstract data, neither change nor drop processing can be performed on the column.
If the column type is abstract data, neither change nor drop processing can be performed on the table that contains the column.
The column types are as follows:

CLUSTER KEY: Column constituting a cluster key

FOREIGN KEY: Column constituting a foreign key

PRIMARY KEY: Column constituting a primary key

PARTITION KEY: Column constituting a partitioning key

REFERENCED PRIMARY KEY: Column constituting a primary key of a referenced table

TRIGGER: Column in a trigger definition that is qualified and referenced by the old or new values correlation name

CHECK: Check constraint definition

abstract data: Abstract data type

For details, refer to the KFPA11631-E message.
-631

40DI1
The column cannot be deleted because it is the only column in the table.
For details, refer to the KFPA11632-E message.
-632

40DI2
The storage condition column, boundary-value partitioning column, or hash partitioning key column does not have the NOT NULL constraint.
For details, refer to the KFPA11633-E message.
-633

40DI3
ALL cannot be used for a table identifier.
For details, refer to the KFPA11658-E message.
-658

40DI4
The data type and data length specified in the CHANGE clause are invalid.
For details, refer to the KFPA11659-E message.
-659

40DI5
The index has already been defined in HiRDB.
For details, refer to the KFPA11661-E message.
-661

40DI6
The information specified in the CHANGE clause in ALTER TABLE (maximum number of elements in the repetition column, data type, data length, default value (WITH DEFAULT, SET DEFAULT clause, or DROP DEFAULT clause), or variable-length character string data storage method) is the same as before the change.
For details, refer to the KFPA11665-E message.
-665

40DI7
The maximum number of elements specified in the CHANGE clause in ALTER TABLE contains one of the following errors:

An attempt was made to reduce the maximum number of elements

An attempt was made to change a repetition column to a non-repetition column or a non-repetition column to a repetition column.

The maximum number of elements has not changed, but * is not specified.

For details, refer to the KFPA11667-E message.
-667

40DI8
A referenced table for a reference constraint cannot be deleted.
For details, refer to the KFPA11690-E message.
-690

40DI9
A cluster key clause cannot be specified together with a primary key clause for the same column structure.
For details, refer to the KFPA11693-E message.
-693

40DIA
When the attribute of a cluster key was changed, one of the following errors occurred:

An attempt was made to change a cluster key with UNIQUE already specified to UNIQUE, or to change a cluster key with UNIQUE not specified to non-UNIQUE.

An attempt was made, using flexible hash partitioning, to change a cluster key for a flexible hash-partitioned table or a matrix partitioning table to UNIQUE.

For details, refer to the KFPA11694-E message.
-694

40DIB
When a table is defined or a table definition is changed, WITH DEFAULT cannot be specified for a column without the NOT NULL constraint.
For details, refer to the KFPA11697-E message.
-697

40DIC
NOT NULL cannot be specified for a column configured for the abstract data type.
For details, refer to the KFPA11698-E message.
-698

40DID
WITH DEFAULT has already been specified for the column.
For details, refer to the KFPA11699-E message.
-699

40DIF
An index with UNIQUE specified cannot be defined for one of the following reasons:

In a table that is row-partitioned over multiple back-end servers, the columns comprising the index do not include all the columns specified as table partitioning keys.

In a rebalancing table with FIX hash partitioning in a single server or a single back-end server, the columns comprising the index do not include all the columns specified as table partitioning keys.

For details, refer to the KFPA11702-E message.
-702

40DIG
Neither BLOB nor BINARY can be specified as the data type for a table with the FIX attribute, nor can any character set be specified for an attribute name in a type definition.
For details, refer to the KFPA11704-E message.
-704

40DIH
The PCTFREE or SEGMENT REUSE option value exceeds the maximum value in CREATE TABLE, CREATE INDEX, or ALTER TABLE.
For details, refer to the KFPA11705-E message.
-705

40DII
The name of an attribute that constitutes a single data type must be unique in all abstract data types that have inheritance relationships.
For details, refer to the KFPA11712-E message.
-712

40DIJ
The table or column cannot be renamed for one of the following reasons:

A viewed table is created on the basis of the table to be changed.

A trigger is defined for the table to be changed.

A check constraint is defined for the table to be changed.

A column in the table to be changed is used in the search condition for a check constraint.

A reference constraint (foreign key) is defined for the table to be changed.

The column to be changed is a component of a foreign key.

The table to be changed is a referenced table for a reference constraint.

The column to be changed is a component of the primary key of a referenced table for a reference constraint.

The table to be changed is specified in a stored procedure or a triggered SQL statement.

An attempt was made to rename a column of a viewed table.

An attempt was made to rename a column specified in the trigger execution timing.

An attempt was made to rename a column referenced by using an old or new values correlation name in the search condition for a trigger action.

An attempt was made to rename a column referenced by using an old or new values correlation name in the triggered SQL statement.

An attempt was made to rename a falsification prevented table or its column.

For details, refer to the KFPA11717-E message.
-717

40DIK
The definition for column data control contains one of the following errors:

This definition is specified for a FIX table.

This definition is specified for a column whose data type is neither CHAR, nor MCHAR, nor NCHAR.

This definition is specified for a repetition column.

For details, refer to the KFPA11718-E message.
-718

40DIN
None of the following columns can be specified for a partitioning key:

CHAR, VARCHAR, MCHAR, or MVARCHAR with a definition length of 256 bytes or more

NCHAR or NVARCHAR with a definition length of 128 characters or more

For single column partitioning, a column that constitutes a cluster key other than the first column constituting the cluster key

For multicolumn partitioning or matrix partitioning, a column whose specification order for the partitioning key differs from that for the cluster key

BLOB

Column that duplicates a partitioning key for multicolumn partitioning or matrix partitioning

A repetition column

BINARY

TIMESTAMP whose precision in a fraction of a second is greater than 0

Column for which CURRENT_TIMESTAMP USING BES is specified as the default value

Column fo rwhich abstract data type is specified

For details, refer to the KFPA11745-E message.
-745

40DIO
The condition value for the storage condition specified for a column contains one of the following errors:

The data type of the condition value cannot be changed to the data type of the column specified in the storage condition.

The data length of the condition value exceeds the data length of the column specified in the storage condition.

The condition value is logically invalid.

Data for the condition value is invalid.

The data length of the condition value converted with a character set specified exceeds the data length of the column specified in the partitioning condition.

For details, refer to the KFPA11746-E message.
-746

40DIP
The storage condition specified for a partitioning key contains one of the following errors:

As a result of evaluating the storage conditions in the order specified, there is no row to be stored according to the storage condition.

The storage condition is specified for two or more columns.

The length of character string specified for the storage condition is 0.

For details, refer to the KFPA11747-E message.
-747

40DIQ
The ALLOCATE clause specified for a column is invalid.
For details, refer to the KFPA11750-E message.
-750

40DIR
The option specified for a column is invalid.
For details, refer to the KFPA11753-E message.
-753

40DIS
A duplicate routine name is specified in the FOR clause in CREATE INDEX.
For details, refer to the KFPA11754-E message.
-754

40DIT
The specified exceptional key value for the index contains one of the following errors:

NULL is specified as a value constituting the exceptional key value for a column with the NOT NULL constraint.

An exceptional key value is specified for the index for a repetition column.

For details, refer to the KFPA11758-E message.
-758

40DIU
That SQL statement cannot be executed because the plug-in has not been registered.
For details, refer to the KFPA11761-E message.
-761

40DIV
The number of columns constituting the index does not match the number of values constituting the exceptional key value.
For details, refer to the KFPA11764-E message.
-764

40DIW
One of the following errors is present:

For multi-value, the following columns cannot be specified:
BLOB columns of abstract data type or BINARY type

For no-split or split, the following columns cannot be specified:
Columns other than VARCHAR, MVARCHAR, or NVARCHAR

For collating-sequence, the following columns cannot be specified:
Columns other than CHAR, VARCHAR, MCHAR, MVARCHAR, NCHAR, or NVARCHAR

For trailing-space, the following columns cannot be specified:
Columns other than VARCHAR, MVARCHAR, or NVARCHAR

For recovery, non-BLOB columns and columns whose attribute is not BLOB cannot be specified.

For the with default clause, columns of the abstract data type cannot be specified.

For details, refer to the KFPA11766-E message.
-766

40DIX
The specified function cannot be defined because it has the same name and the same SQL parameter structure as a system-provided function.
For details, refer to the KFPA11775-E message.
-775

40DIY
There is an error in the number of RDAREAs specified for the index.
For details, refer to the KFPA11791-E message.
-791

40DIZ
The RDAREA in the index definition with partitioning specified does not correspond to the RDAREA for the boundary value-partitioned or hash row-partitioned table.
For details, refer to the KFPA11793-E message.
-793

40DJ0
The DEFAULT clause is invalid at one of the following locations:

Table definition

Table definition update (when the DEFAULT clause is specified or deleted)

SQL variable declaration in a routine definition

For details, refer to the KFPA11798-E message.
-798

40DJ1
The audit event specified in CREATE AUDIT has already been defined.
For details, refer to the KFPA11908-E message.
-908

40DJ2
The audit event specified in DROP AUDIT is not defined.
For details, refer to the KFPA11909-E message.
-909

40DJ3
The total length of attributes defined with abstract data types is too large.
For details, refer to the KFPA11939-E message.
-939

40DJ4
There is an error in the shared table or shared index definition.
For details, refer to the KFPA19575-E message.
-1575

40DJ5
There is an error in the reference constraint definition or check constraint definition.
For details, refer to the KFPA19581-E message.
-1581

40DJ6
In a reference constraint, the primary key of the same referenced table cannot be referenced from the same set of columns (the order might not be the same).
For details, refer to the KFPA19602-E message.
-1602

40DJ7
The column cannot be changed for one of the following reasons:

The corresponding column is referenced by using an old or new values correlation name in the search condition for a trigger action. This column cannot be changed or deleted.

The corresponding column is referenced by using an old or new values correlation name in the triggered SQL statement. This column cannot be changed or deleted.

For details, refer to the KFPA19603-E message.
-1603

40DJ8
The specified matrix partitioning table is invalid.
For details, refer to the KFPA19612-E message.
-1612

40DJ9
A definition SQL statement cannot be executed on a falsification prevented table that stores data.
For details, refer to the KFPA19615-E message.
-1615

40DJA
The insert history maintenance column specified in the deletion prevented duration for a falsification prevented table cannot be deleted.
For details, refer to the KFPA19616-E message.
-1616

40DJB
Only a column of DATE type with SYSTEM GENERATED specified can be specified for the insert history maintenance column of a falsification prevented table.
For details, refer to the KFPA19617-E message.
-1617

40DJC
The deletion prevented duration specified for a falsification prevented table is invalid.
For details, refer to the KFPA19620-E message.
-1620

40DJD
There is an error in the specified ALTER TABLE CHANGE RDAREA.
For details, refer to the KFPA19625-E message.
-1625

40DJH
A sequence generator cannot be created.
For details, refer to the KFPA19624-E message.
-1624

40DJI
The table cannot be set to be expanded to or released from the memory database.
For details, refer to the KFPA19864-E message.
-1864

40DJJ
The definition SQL statement cannot be executed because this table is to be expanded to the memory database.
For details, refer to the KFPA19865-E message.
-1865

40DJK
There is an error in the definition of a temporary table or temporary table index.
For details, refer to the KFPA19621-E or KFPA19622-E message.
-1621
-1622

40DJL
Refer to the KFPA19604-E message.
-1604

40DJM
There is an error specifying a reserved column definition, or adding, dropping, or excising a column.
For details, refer to the following messages:

KFPA11626-E

KFPA11632-E

KFPA11681-E

KFPA11682-E

KFPA11683-E

KFPA11684-E

KFPA11695-E

KFPA11696-E

-626
-632
-681
-682
-683
-684
-695
-696

40DJN
ALTER TABLE cannot be executed.
For details, refer to the KFPA19613-E message.
-1613

40DJO
ALTER TABLE cannot change the table definition due to the free space reusage facility.
For details, refer to the KFPA11751-E message.
-751

40DL0
Refer to the KFPA11552-E message.
-552

40DL1
Refer to the KFPA11559-E message.
-559

40DL2
Refer to the KFPA11576-E message.
-576

40DL3
Refer to the KFPA11577-E message.
-577

40DL4
Refer to the KFPA11578-E message.
-578

40DL5
Refer to the KFPA11579-E message.
-579

40DL6
Refer to the KFPA11580-E message.
-580

40DL7
Refer to the KFPA11562-E message.
-562

40DL8
Refer to the KFPA19683-E message.
-1683

40DL9
Refer to the KFPA11571-E message.
-571

40DLA
Refer to the KFPA11903-E message.
-903

40DLB
Refer to the KFPA11905-E message.
-905

40DLC
One of the following errors is present:

The SQL statement cannot be executed because the user does not have the required privileges for the corresponding table.

When the optimizing information collection utility (pdgetcst) was used, the user did not have SELECT privileges for the table to be processed.

For details, refer to the KFPA11548-E message.
-548

40DLD
Because the executor is not the owner of the table, the executor cannot execute the SQL statement or grant another user a privilege that the executor does not have.
For details, refer to the KFPA11551-E message.
-551

40DLE
The user cannot grant a privilege to him/herself.
For details, refer to the KFPA11554-E message.
-554

40DLF
The user cannot revoke his/her own privilege.
For details, refer to the KFPA11555-E message.
-555

40DLG
The list of authorization identifiers specified in the GRANT statement (defining privileges) or the REVOKE statement (revoking privileges) contains the table owner's authorization identifier.
For details, refer to the KFPA11556-E message.
-556

40DLH
One or more ofhe following cannot be executed:

Creation of a base table, a viewed table, or an index owned by another user

Dropping of a base table, a viewed table, or an index owned by another user

Changing the table definition for a table owned by another user

Adding comments to a base table or a viewed table owned by another user

Creation or deletion of a procedure owned by another user

Creation or deletion of a function owned by another user

Creation or deletion of a data type owned by another user

Creation or deletion of an index type owned by another user

Changing a data type owned by another user

Changing an index type owned by another user

Definition or deletion of a trigger owned by another user

Definition or deletion of a sequence generator owned by another user

For details, refer to the KFPA11607-E message.
-607

40DLJ
The following SQL statements cannot be executed because the rebalancing utility is executing:

ALTER TABLE

CREATE INDEX

For details, refer to the KFPA11823-E message.
-823

40DLK
The INSERT, UPDATE, and DELETE privileges for an audit trail table or a viewed table based on the audit trail table cannot be granted to a user who is not the auditor.
For details, refer to the KFPA11902-E message.
-902

40DLL
Usage privileges for an RDAREA storing an audit trail table cannot be granted to a user who is not the auditor.
For details, refer to the KFPA11904-E message.
-904

40DLM
The auditor's schema cannot be deleted because there is an audit trail table.
For details, refer to the KFPA11906-E message.
-906

40DLN
The auditor's schema definition privileges and CONNECT privileges cannot be revoked.
For details, refer to the KFPA11907-E message.
-907

40DLO
An error occurred in a definition related to a falsification prevented table. For details, refer to the KFPA19631-E message.
-1631

40DLP
The GRANT statement could not be executed due to one of the following password violations:
Minimum length in bytes, prohibition of authorization identifier specification, prohibition of specification in a single character type
For details, refer to the KFPA19634-E message.
-1634

40DLQ
The GRANT DBA statement cannot be used to grant DBA privileges or change the password, due to the password-invalid account lock state. For details, refer to the KFPA19635-E message.
-1635

40DLR
In the audit event definition, a combination of operation type, event type, and other operands is invalid. For details, refer to the KFPA19680-E message.
-1680

40DLS
The specified privilege cannot be granted or revoked. For details, refer to the KFPA19610-E message.
-1610

40DN0
Refer to the KFPA11307-E message.
-307

40DN1
Refer to the KFPA11209-E message.
-209

40DP0
Refer to the KFPA11787-E message.
-787

40DR0
No new update transaction is accepted while both-system operation is being restored. For details, refer to the KFPA19726-E message.
-1726

40DT0
Refer to the KFPA11692-E message.
-692

40DT1
Refer to the KFPA11777-E message.
-777

40DT2
Refer to the KFPA11930-E message.
-930

40DT3
Refer to the KFPA11929-E message.
-929

40DT4
Refer to the KFPA11811-E message.
-811

40DT5
Refer to the KFPA11814-E message.
-814

40DT6
Refer to the KFPA19718-E message.
-1718

40DT7
Refer to the KFPA11919-E message.
-919

40DT8
Refer to the KFPA11531-E message.
-531

40DT9
Refer to the KFPA19705-E message.
-1705

40DTA
Because the data dictionary LOB RDAREA is not defined, the following SQL statements cannot be executed:

ALTER PROCEDURE

ALTER ROUTINE

ALTER TRIGGER

CALL statement

CREATE FUNCTION

CREATE PROCEDURE

CREATE TRIGGER

CREATE TYPE

DROP FUNCTION

DROP PROCEDURE

Function invocation

For details, refer to the KFPA11596-E message.
-596

40DTB
None of the following operations can be executed on a table containing data:

add column: Addition of a column with a NOT NULL constraint or DEFAULT clause specified, or addition of a column to a FIX table

add rdarea: Addition of an RDAREA to a FIX hash-partitioned table that does not use the rebalancing facility

change no split or change split: Changing the no-split option

change set default: Specifying or changing a default value

change drop default: Deleting a default value

change cluster key: Changing the attribute of a cluster key

change hash: Changing the hash function for a FIX hash-partitioned table

drop column: Dropping columns

change insert only: Changing a non-falsification-prevented table to a falsification prevented table

For details, refer to the KFPA11613-E message.
-613

40DTC
Because the specified RDAREA is a shared RDAREA, none of the following operations can be performed:

Definition of a table other than the shared table

Definition of an index other than the shared index

Addition of an RDAREA

Changing the partition storage condition

For details, refer to the KFPA19576-E message.
-1576

40DTD
There is a shortage of shared memory for locking.
For details, refer to the KFPA11914-E message.
-914

40DTE
The resource cannot be accessed because one of the following resources is in use by a definition SQL statement or utility:

A table, routine, or sequence generator is in use. For details, refer to the KFPA19670-E message.

A table, routine, sequence generator, or abstract data type is in use. For details, refer to the KFPA19671-E message.

-1670
-1671

40DTG
Refer to the KFPA19724-E message.
-1724

40DTH
Refer to the KFPA19725-E message.
-1725

40DX0
Refer to the KFPA11812-E message.
-812

40DX1
Refer to the KFPA11657-E message.
-657

40DX2
Refer to the KFPA11827-E message.
-827

40DX3
Refer to the KFPA11952-E message.
-952

40DX4
Refer to the KFPA19706-E message.
-1706

40DX5
The key length of an index exceeds the maximum value.
For details, refer to the KFPA11616-E message.
-616

40DX6
The number of partitions exceeds the system limit (1,024 for a rebalancing table, 4,096 otherwise). Alternatively, the number of RDAREA names specified for storage exceeds the system limit (4,096).
For details, refer to the KFPA11634-E message.
-634

40DX7
The number of tables in an RDAREA, the total number of sequence generators, or the number of indexes exceeds the permitted maximum value.
For details, refer to the KFPA11654-E message.
-654

40DX8
changedata length or add rdarea cannot be executed because the key length of an index exceeds the permitted maximum value.
For details, refer to the KFPA11662-E message.
-662

40DX9
A single table cannot be partitioned and defined in 4,097 or more back-end servers.
For details, refer to the KFPA11703-E message.
-703

40DXA
The number of indexes specified for a single table exceeds the maximum value (255).
For details, refer to the KFPA11706-E message.
-706

40DXB
The ADT LEVEL value (number of generations of abstract data type) exceeds 30,000, which is the maximum value permitted for the system.
For details, refer to the KFPA11714-E message.
-714

40DXC
The number of foreign keys referencing the primary key of a referenced table exceeds the maximum value (255).
For details, refer to the KFPA11748-E message.
-748

40DXD
The number of RDAREAs with duplicates excluded that can be specified when a table or index is partitioned exceeds the maximum value.
For details, refer to the KFPA11795-E message.
-795

40DXE
The number of foreign keys that can be specified for a single table exceeds the maximum value (255).
For details, refer to the KFPA19583-E message.
-1583

40DXF
The check constraint cannot be defined because the number of check constraints defined for the table (total number of Boolean operators specified in the check constraint search condition (number of ANDs and ORs excluding the ANDs and ORs in the WHEN search condition in the CASE expression) and the total number of check constraints) exceeds the maximum value (254).
For details, refer to the KFPA19584-E message.
-1584

40E01
Refer to the KFPA11528-E message.
-528

40E02
Refer to the KFPA11529-E message.
-529

40E03
Refer to the KFPA11537-E message.
-537

40E20
Refer to the KFPA11652-E message.
-652

40E21
Refer to the KFPA11653-E message.
-653

40E22
Refer to the KFPA11358-E message.
-358

40E23
Refer to the KFPA11511-E message.
-511

40E24
Refer to the KFPA11737-E message.
-737

40E25
Refer to the KFPA11738-E message.
-738

40E26
Refer to the KFPA11815-E message.
-815

40E27
The table or index cannot be dropped or the table definition cannot be changed because a copied RDAREA is defined.
For details, refer to the KFPA11513-E message.
-513

40E28
The specified RDAREA is not a user LOB RDAREA.
For details, refer to the KFPA11599-E message.
-599

40E29
The user is not authorized to use the specified RDAREA. Therefore, the table, sequence generator, or index cannot be created.
For details, refer to the KFPA11608-E message.
-608

40E2A
There is no available public user RDAREA.
For details, refer to the KFPA11610-E message.
-610

40E2B
If the name of an RDAREA for a table is duplicated or an RDAREA for a table that is already in use for the target table is specified in ALTER TABLE ADD RDAREA, the specification for the RDAREA for the table does not match the specification for the following items:

RDAREA for LOB column

RDAREA for LOB attribute

For details, refer to the KFPA11707-E message.
-707

40E2C
The specified LOB RDAREA is not on the same server as the RDAREA for the table.
For details, refer to the KFPA11708-E message.
-708

40E2D
The specified LOB RDAREA is already in use for another table.
For details, refer to the KFPA11709-E message.
-709

40E2E
The specified RDAREA for the index is not on the server that contains the RDAREA for the table.
For details, refer to the KFPA11771-E message.
-771

40E2F
The same RDAREA as the immediately preceding RDAREA cannot be specified.
For details, refer to the KFPA11796-E message.
-796

40E2G
The specified RDAREA contains one of the following errors:

For error code=1
No other table or index can be stored in the specified user RDAREA because it contains a rebalancing table.

For error code=2
No rebalancing table can be stored in the specified user RDAREA because it already contains another table or index.

For error code=3
When an index is defined for a rebalancing table, specification of an RDAREA for the index cannot be omitted.

For details, refer to the KFPA11845-E message.
-845

40E2I
Refer to the KFPA19704-E message.
-1704

40E40
Refer to the KFPA11431-E message.
-431

40E41
Refer to the KFPA11897-E message.
-897

40E42
Refer to the KFPA11964-E message.
-964

40E43
No SQL statement other than ROLLBACK or DISCONNECT can be executed.
For details, refer to the KFPA11987-E message.
-987

40E60
Refer to the KFPA11810-E message.
-810

40E61
One of the following errors is present:

An attempt was made to perform batch creation of an index that had already been created.
For details, refer to the KFPA11875-E message.

Contents of the specified index information file do not match the data in the table. Therefore, the index information file cannot be used to perform batch creation of an index.
For details, refer to the KFPA11883-E message.

-875
-883

40E62
Refer to the KFPA11882-E message.
-882

40E63
Refer to the KFPA11884-E message.
-884

40E64
Refer to the KFPA19523-E message.
-1523

Legend:

--: Not applicable

Table 8-24 SQLSTATE class 42

SQLSTATE
Explanation
SQLCODE

42000
One of the following errors is present:

The specified viewed table was defined with duplicate elimination specified in the FROM clause in a subquery.
For details, refer to the Refer to the KFPA11639-E message.

For a derived table with a name that was derived by a query with the GROUP BY clause, HAVING clause, or a set function specified, a table join was specified in the view definition, the derived query expression in a query for the WITH clause, or the query with a value expression specified in the GROUP BY clause.
For details, refer to the KFPA11643-E message.

For a derived table with a name that was derived by a query with the GROUP BY clause, HAVING clause, or a set function specified, the GROUP BY clause, HAVING clause, or a set function is specified in the view definition, the derived query expression in a query for the WITH clause, or the query with a value expression specified in the GROUP BY clause.
For details, refer to the KFPA11644-E message.

A value expression other than the column specification is specified in a query (SELECT statement) for a viewed table that was defined with duplicate elimination (DISTINCT) specified.
For details, refer to the KFPA11645-E message.

A table join is specified in a query (SELECT statement) for a viewed table that was defined with duplicate elimination (DISTINCT) specified.
For details, refer to the KFPA11646-E message.

Duplicate elimination is specified in a query for a viewed table that was derived with duplicate elimination (DISTINCT) specified.
For details, refer to the KFPA11647-E message.

A query with a value expression other than the column specification specified in the GROUP BY clause, or a subquery for the WHERE clause in a query with a value expression other than the column specification specified in the GROUP BY clause, is specified as the query for creating an internal derived table.
For details, refer to the KFPA11648-E message.

The GROUP BY clause, HAVING clause, or a set function is specified for a derived table with a name that was derived with duplicate elimination (DISTINCT) specified.
For details, refer to the KFPA11649-E message.

The name of the base table for the viewed table or the viewed table name is invalid, or the name of the base table for the viewed table is the same as the name of the viewed table.
For details, refer to the KFPA11669-E message.

The lock option is omitted in the query for searching for the table to be expanded to the memory database, or a nonzero value is specified in the PDISLLVL client environment definition. For details, refer to the KFPA19198-E message.

ON COMMIT was specified when defining a permanent base table. For details, refer to the KFPA19522-E message.

-639
-643
-644
-645
-646
-647
-648
-649
-669
-1198
-1522

42501
The number of characters specified in the character string literal exceeds the permitted maximum value.
For details, refer to the KFPA11102-E message.
-102

42502
Refer to the KFPA11145-E message.
-145

42503
The number of characters specified in the national character string literal or the number of characters in the result of a concatenation operation between national character string literals exceeds the permitted maximum value.
For details, refer to the KFPA11104-E and KFPA11141-E messages.
-104
-141

42504
The number of characters specified in the mixed character string literal exceeds the permitted maximum value.
For details, refer to the KFPA11102-E and KFPA11140-E messages.
-102
-140

42505
The character string literal is not complete.
For details, refer to the KFPA11106-E message.
-106

42506
The hexadecimal character string literal is not complete.
For details, refer to the KFPA11106-E message.
-106

42507
Refer to the KFPA11140-E message.
-140

42508
The mixed character string literal is not complete.
For details, refer to the KFPA11106-E message.
-106

42509
Refer to the KFPA11144-E message.
-144

42510
There are one or more characters that violate the syntax rules.
For details, refer to the KFPA11104-E message.
-104

42511
Refer to the KFPA11410-E message.
-410

42512
Refer to the KFPA11103-E message.
-103

42513
The value of the specified numeric literal falls beyond the permitted value range.
For details, refer to the KFPA11405-E message.
-405

42514
Refer to the KFPA11142-E message.
-142

42520
Refer to the KFPA11107-E message.
-107

42529
The authorization identifier is longer than 8 characters.
For details, refer to the Refer to the KFPA11564-E message.
-564

42530
The identifier does not begin with an alphabetic character, or the delimited identifier is not complete.
For details, refer to the KFPA11104-E message.
-104

42539
There is a syntax error in the authorization identifier.
For details, refer to the KFPA11564-E message.
-564

42550
Refer to the KFPA11418-E message.
-418

42551
Refer to the KFPA11217-E message.
-217

42561
There is an error in the left-hand operand of the NULL predicate.
For details, refer to the KFPA11114-E message.
-114

42562
There is an error in the left-hand operand of the LIKE predicate.
For details, refer to the KFPA11114-E message.
-114

42563
The XMLEXISTS predicate is specified outside the WHERE clause.
For details, refer to the KFPA11114-E message.
-114

42570
The UPDATE or DELETE statement using the cursor cannot be preprocessed by the PREPARE statement.
For details, refer to the KFPA11157-E message.
-157

42572
Refer to the KFPA11149-E message.
-149

42573
Refer to the KFPA11164-E message.
-164

42580
The subscript specified for a repetition column is invalid.
For details, refer to the KFPA11186-E message.
-186

42581
In the column definition in CREATE TABLE or ALTER TABLE, there is an error in the maximum number of elements or the number of elements specified for a repetition column.
For details, refer to the KFPA11189-E message.
-189

42590
Refer to the KFPA11604-E message.
-604

42591
Refer to the KFPA11131-E message.
-131

425A0
The number of specified embedded variables, parameters, ? parameters, SQL variables, and SQL parameters exceeds the permitted maximum value.
For details, refer to the KFPA11129-E message.
-129

425A2
Refer to the KFPA11139-E message.
-139

425A4
The number of simple WHEN clauses or searched WHEN clauses and ELSE clauses specified in the CASE expression exceeds the permitted maximum value.
For details, refer to the KFPA11129-E message.
-129

425A6
The number of specified row value constructor elements exceeds the permitted maximum value.
For details, refer to the KFPA11129-E message.
-129

425B0
The number of tables specified in the query exceeds the permitted maximum value.
For details, refer to the KFPA11129-E message.
-129

425B1
The number of specified selection expressions exceeds the permitted maximum value.
For details, refer to the KFPA11129-E message.
-129

425B2
Refer to the KFPA11122-E message.
-122

425B3
Refer to the KFPA11124-E message.
-124

425B4
The number of column specifications in the FOR UPDATE clause exceeds the permitted maximum value.
For details, refer to the KFPA11129-E message.
-129

425B5
The number of specified insertion values exceeds the permitted maximum value.
For details, refer to the KFPA11129-E message.
-129

425B6
The number of columns to be inserted exceeds the permitted maximum value.
For details, refer to the KFPA11129-E message.
-129

425B7
The number of columns to be updated exceeds the permitted maximum value.
For details, refer to the KFPA11129-E message.
-129

425B8
The number of arguments specified in the arguments list exceeds the permitted maximum value.
For details, refer to the KFPA11129-E message.
-129

425B9
The number of table names specified in the LOCK statement exceeds the permitted maximum value.
For details, refer to the KFPA11129-E message.
-129

425BB
The number of column names specified in the derived columns list exceeds the permitted maximum value.
For details, refer to the KFPA11129-E message.
-129

425BC
The number of list names exceeds the permitted maximum value.
For details, refer to the KFPA11773-E message.
-773

425C0
Refer to the KFPA11602-E message.
-602

425C1
The number of columns in the view columns list specified in the view definition exceeds the permitted maximum value.
For details, refer to the KFPA11129-E message.
-129

425C2
The number of foreign keys specified in the table definition or the number of foreign keys resulting from the addition made by altering the table definition exceeds the permitted maximum value.
For details, refer to the KFPA11129-E message.
-129

425C3
The number of predicates specified in a check constraint exceeds the permitted maximum value.
For details, refer to the KFPA11129-E message.
-129

425C6
The number of columns specified in the index definition exceeds the permitted maximum value.
For details, refer to the KFPA11617-E message.
-617

425C7
The number of tables specified in the index definition exceeds the permitted maximum value.
For details, refer to the KFPA11617-E message.
-617

425C8
The number of exception values specified in the index definition exceeds the permitted maximum value.
For details, refer to the KFPA11617-E message.
-617

425C9
The number of exception key values specified in the index definition exceeds the permitted maximum value.
For details, refer to the KFPA11129-E message.
-129

425CA
Refer to the KFPA11570-E message.
-570

425CB
Refer to the KFPA11585-E message.
-585

425CC
The number of columns for the primary key in CREATE TABLE exceeds the permitted maximum value.
For details, refer to the KFPA11674-E message.
-674

425CD
The number of columns specified for multicolumn hash partitioning in CREATE TABLE exceeds the permitted maximum value.
For details, refer to the KFPA11674-E message.
-674

425CE
The number of columns for the cluster key in CREATE TABLE exceeds the permitted maximum value.
For details, refer to the KFPA11674-E message.
-674

425D0
Refer to the KFPA11678-E message.
-678

425D3
There is one of the following syntax errors in ALTER TABLE:

The maximum number of elements or the number of elements is specified twice in the column definition.
For details, refer to the KFPA11189-E message.

The specification for the column to be added or changed in ALTER TABLE is invalid.
For details, refer to the KFPA11676-E message.

-189
-676

425D4
Refer to the KFPA11673-E message.
-673

425D5
There is an error in the specified table options or index options.
For details, refer to the KFPA11705-E message.
-705

425D7
Refer to the KFPA11572-E message.
-572

425DP
Refer to the KFPA11136-E message.
-136

425E0
Refer to the KFPA11633-E message.
-633

425L0
Refer to the KFPA11778-E message.
-778

425L1
Refer to the KFPA11781-E message.
-781

425L2
Refer to the KFPA11782-E message.
-782

425L5
Refer to the KFPA11191-E message.
-191

42601
There is an excess character string at the end of the SQL statement, or the first keyword is invalid in the SQL statement.
For details, refer to the KFPA11104-E message.
-104

42602
Refer to the KFPA11105-E message.
-105

42603
Refer to the KFPA11106-E message.
-106

42604
Refer to the KFPA11116-E message.
-116

42605
Refer to the KFPA11138-E message.
-138

42606
Refer to the KFPA11173-E message.
-173

42607
Refer to the KFPA11175-E message.
-175

42608
Refer to the KFPA11289-E message.
-289

42609
Refer to the KFPA11292-E message.
-292

42610
Refer to the KFPA11355-E message.
-355

42611
Refer to the KFPA11461-E message.
-461

42613
Refer to the KFPA11508-E message.
-508

42614
Refer to the KFPA11638-E message.
-638

42615
Refer to the KFPA11641-E message.
-641

42618
Refer to the KFPA19323-E message.
-1323

42619
Refer to the KFPA19407-E message.
-1407

42620
Refer to the KFPA19408-E message.
-1408

42621
A column that is not the last column of the table was specified as a reserved column.
For details, refer to the KFPA19106-E message.
-1106

42701
The number of literals exceeds the permitted maximum value.
For details, refer to the KFPA11102-E and KFPA11141-E messages.
-102
-141

42702
Refer to the KFPA11161-E message.
-161

42703
The value specified for a numeric literal falls beyond the permitted value range (this is an integer literal specified for a labeled duration).
For details, refer to the KFPA11405-E message.
-405

42704
Refer to the KFPA11128-E message.
-128

42710
Refer to the KFPA11112-E message.
-112

42711
Refer to the KFPA11113-E message.
-113

42712
Refer to the KFPA11402-E message.
-402

42713
Refer to the KFPA11403-E message.
-403

42714
Refer to the KFPA11120-E message.
-120

42716
Refer to the KFPA11127-E message.
-127

42720
Refer to the KFPA11117-E message.
-117

42721
Refer to the KFPA11195-E message.
-195

42722
Refer to the KFPA11192-E message.
-192

42723
Refer to the KFPA11650-E message.
-650

42730
Refer to the KFPA11211-E message.
-211

42731
Refer to the KFPA11121-E message.
-121

42732
Refer to the KFPA11123-E message.
-123

42733
Refer to the KFPA11458-E message.
-458

42734
Refer to the KFPA11459-E message.
-459

42740
One of the following errors is present:

The table specification qualifying the column name is not the valid name specified in the SQL statement, or the qualification of the SQL parameter or SQL variable is not the valid name specified in the SQL statement.
For details, refer to the KFPA11201-E message.

The column name, *, or table specification qualifying ROW is not the valid name specified in the SQL statement.
For details, refer to the KFPA11241-E message.

The SQL parameter or the qualification of the SQL variable is not the valid name specified in the SQL statement, or a column specification is specified at an invalid location.
For details, refer to the KFPA11251-E message.

-201
-241
-251

42741
Refer to the KFPA11204-E message.
-204

42742
One of the following errors is present:

The specified column was not found in the SQL statement, table in the query specification, or query name; or, the SQL variable or SQL parameter is not declared in the routine.
For details, refer to the KFPA11202-E message.

The specified column was not found in the specified table, or in the correlation name for a derived table in the FROM clause, or in the query name in the query in the WITH clause.
For details, refer to the KFPA11205-E message.

The column name specified in the ON condition is not in the table to be joined by the join table that contains the ON condition or is not in the table that allows external references.
For details, refer to the KFPA11227-E message.

The specified column is neither in the SQL statement, nor in the table in the query specification, nor in the query name.
For details, refer to the KFPA11242-E message.

The specified SQL variable or SQL parameter is not declared in the routine, or a column name is specified at an invalid location.
For details, refer to the KFPA11252-E message.

The specified SQL variable was not found in the statement label or loop variable.
For details, refer to the KFPA11255-E message.

The specified SQL parameter was not found in the routine.
For details, refer to the KFPA11256-E message.

-202
-205
-227
-242
-252
-255
-256

42743
One of the following errors is present:

There is an error in the sort item specification number specified in the ORDER BY clause.
For details, refer to the KFPA11125-E message.

The column specified in the ORDER BY clause was not found in the column specification in the SELECT clause in the outermost query.
For details, refer to the KFPA11208-E message.

-125
-208

42744
One of the following errors is present:

It cannot be determined to which table or query name the specified column belongs because this column is in two or more tables' query names or tables in the query.
For details, refer to the KFPA11203-E message.

It cannot be determined to which table the ROW specification corresponds because two or more corresponding tables in the query contain ROW.
For details, refer to the KFPA11213-E message.

-203
-213

42745
One of the following errors is present:

There are multiple identical columns in the derived table in the FROM clause.
For details, refer to the KFPA11218-E message.

The table derived as a result of a query contains two or more columns specified in the ORDER BY clause.
For details, refer to the KFPA11220-E message.

-218
-220

42746
Refer to the KFPA11119-E message.
-119

42747
Refer to the KFPA11224-E message.
-224

42748
Refer to the KFPA11260-E message.
-260

42749
Refer to the KFPA11239-E message.
-239

42750
Refer to the KFPA11214-E message.
-214

42751
Refer to the KFPA11215-E message.
-215

42752
Refer to the KFPA11216-E message.
-216

42754
Refer to the KFPA11180-E message.
-180

42755
One of the following errors is present:

A repetition column with a subscript omitted is specified at an invalid location.
For details, refer to the KFPA11181-E message.

A repetition column with a subscript specified is specified at an invalid location.
For details, refer to the KFPA11182-E message.

A repetition column is specified at an invalid location.
For details, refer to the KFPA11183-E message.

-181
-182
-183

42756
Refer to the KFPA11184-E message.
-184

42757
Refer to the KFPA11185-E message.
-185

42758
Refer to the KFPA11186-E message.
-186

42759
Refer to the KFPA11187-E message.
-187

4275A
Refer to the KFPA11188-E message.
-188

42760
There is an error in the base table specification for the list to be created.
For details, refer to the KFPA11773-E message.
-773

42762
Refer to the KFPA11776-E message.
-776

42763
Refer to the KFPA11783-E message.
-783

42770
One of the following errors is present:

There is an error in the NULL, LIKE, XLIKE, BETWEEN, or Boolean predicate.
For details, refer to the KFPA11114-E message.

No value specification is permitted in the right-hand or left-hand operand of a comparison predicate, or in the left-hand operand of an IN predicate.
For details, refer to the KFPA11417-E message.

-114
-417

42771
Refer to the KFPA11419-E message.
-419

42772
Refer to the KFPA11422-E message.
-422

42773
Refer to the KFPA11428-E message.
-428

42774
Refer to the KFPA11445-E message.
-445

42780
One of the following errors is present:

A data type that is not permitted in date or time operations is specified together with an arithmetic operator, or a unary operation was performed on date data, time data, or a labeled duration.
For details, refer to the KFPA11413-E message.

A labeled duration other than an addition or subtraction operand is specified on date or time data.
For details, refer to the KFPA11414-E message.

-413
-414

42781
Refer to the KFPA11421-E message.
-421

42782
There is an error in the operands specified in a scalar function.
For details, refer to the KFPA11425-E message.
-425

42783
Refer to the KFPA11427-E message.
-427

42784
There is one of the following errors:

There is an error in the format or data type of the value expression specified in the CASE expression.
For details, refer to the KFPA11444-E message.

A value expression must be specified in at least one of the THEN operands in simple CASE expressions and searched CASE expressions, but the null value is specified in all THEN operands.
For details, refer to the KFPA11448-E message.

-444
-448

42785
There is an error in operands in the CAST specification.
For details, refer to the KFPA11453-E message.
-453

42786
Refer to the KFPA11177-E message.
-177

42787
Refer to the KFPA11475-E message.
-475

42792
One of the following errors is present:

FOR UPDATE OF and FOR READ ONLY clauses can be specified only in the cursor declaration.
For details, refer to the KFPA11155-E message.

An invalid specification was made in the query for updating or deleting using the cursor.
For details, refer to the KFPA11156-E message.

-155
-156

42793
Refer to the KFPA11118-E message.
-118

42794
Refer to the KFPA11148-E message.
-148

42795
No RDAREA can be specified for the following tables:

Read-only viewed tables

Query name tables

For details, refer to the KFPA19277-E message.
-1277

42796
The RDAREA specification contains one of the following errors:

There is a syntax error.

The same RDAREA name is specified more than once.

The specified RDAREA does not correspond to the RDAREA that stores the table.

For details, refer to the KFPA11497-E message.
-497

427A0
Refer to the KFPA11101-E message.
-101

427A1
Refer to the KFPA11196-E message.
-196

427A2
Refer to the KFPA11137-E message.
-137

427B2
Refer to the KFPA11194-E message.
-194

427B3
Refer to the KFPA11677-E message.
-677

427C1
Refer to the KFPA19290-E message.
-1290

427D0
Refer to the KFPA11169-E message.
-169

427DA
Refer to the KFPA19203-E message.
-1203

427E0
Refer to the KFPA11237-E message.
-237

427F0
Refer to the KFPA11259-E message.
-259

427FA
Refer to the KFPA11262-E message.
-262

427FB
Refer to the KFPA11263-E message.
-263

42801
One of the following errors is present:

The data type of the operands specified on both sides of a predicate is invalid for comparison or conversion.
For details, refer to the KFPA11401-E message.

An invalid data type is specified in the LIKE or XLIKE predicate.
For details, refer to the KFPA11407-E message.

-401
-407

42802
One of the following errors is present:

There is an error in the search condition specified in the IF or WHILE statement.
For details, refer to the KFPA11163-E message.

An arithmetic operation is specified for an invalid data type.
For details, refer to the KFPA11406-E message.

The data type of the operands specified on both sides of a concatenation operation is invalid for comparison or conversion.
For details, refer to the KFPA11411-E message.

The specified data type is invalid for concatenation operations.
For details, refer to the KFPA11412-E message.

The specified data type is invalid.
For details, refer to the KFPA11415-E message.

Data types are incompatible between the first value expression in a scalar function or CASE abbreviation, and the specified expression value.
For details, refer to the KFPA11426-E message.

Only BOOLEAN-type data can be specified in Boolean predicates.
For details, refer to the KFPA11465-E message.

Character type data with a length of 4,037 bytes or greater is specified at an invalid location in the XDS.
For details, refer to the KFPA11409-E message.

-163
-406
-411
-412
-415
-426
-465
-409

42803
Refer to the KFPA11408-E message.
-408

42804
Refer to the KFPA11197-E message.
-197

42806
One of the following errors is present:

Data types are incompatible between the value expression in CASE and the value expression in WHEN in the simple CASE expression.
For details, refer to the KFPA11446-E message.

Data types are incompatible between the value expression in THEN and the value expression in THEN or ELSE in the simple CASE and searched CASE expressions.
For details, refer to the KFPA11447-E message.

-446
-447

42807
There is an error in the combination of the data type and data length resulting from a value expression, and the data type and data length obtained after conversion.
For details, refer to the KFPA11453-E message.
-453

42809
Refer to the KFPA11238-E message.
-238

4280B
Refer to the KFPA11236-E message.
-236

4280C
Refer to the KFPA11440-E message.
-440

4280E
Refer to the KFPA11468-E message.
-468

42810
Refer to the KFPA11134-E message.
-134

42812
The length of a long data item falls beyond the permitted value range.
For details, refer to the KFPA11420-E message.
-420

42814
Refer to the KFPA11441-E message.
-441

4281A
Refer to the KFPA11132-E message.
-132

42820
Refer to the KFPA11548-E message.
-548

42830
Refer to the KFPA11230-E message.
-230

42850
One of the following errors is present:

Invalid information is specified in the query specification in the WITH clause, or in the view definition.
For details, refer to the KFPA11467-E message.

Invalid information is specified in the view definition.
For details, refer to the KFPA11651-E message.

-467
-651

42851
Refer to the KFPA11671-E message.
-671

42870
Refer to the KFPA11670-E message.
-670

42871
Refer to the KFPA11672-E message.
-672

428A0
Refer to the KFPA11456-E message.
-456

428A1
Refer to the KFPA11640-E message.
-640

428A2
Refer to the KFPA11642-E message.
-642

428D1
Refer to the KFPA19150-E message.
-1150

428D2
Refer to the KFPA19617-E message.
-1617

428D3
Refer to the KFPA19620-E message.
-1620

42907
Refer to the KFPA11146-E message.
-146

42908
Refer to the KFPA11162-E message.
-162

42909
Refer to the KFPA11174-E message.
-174

42910
Refer to the KFPA11231-E message.
-231

42911
Refer to the KFPA11232-E message.
-232

42912
Refer to the KFPA11234-E message.
-234

42913
Refer to the KFPA11240-E message.
-240

42914
Refer to the KFPA11158-E message.
-158

42915
Refer to the KFPA11282-E message.
-282

42916
Refer to the KFPA11283-E message.
-283

42917
Refer to the KFPA11284-E message.
-284

42918
Refer to the KFPA11285-E message.
-285

42919
Refer to the KFPA11286-E message.
-286

42920
Refer to the KFPA11287-E message.
-287

42921
Refer to the KFPA11288-E message.
-288

42922
Refer to the KFPA11291-E message.
-291

42924
Refer to the KFPA11294-E message.
-294

42925
Refer to the KFPA11295-E message.
-295

42927
Refer to the KFPA11382-E message.
-382

42928
Refer to the KFPA11442-E message.
-442

42929
Refer to the KFPA11460-E message.
-460

42930
Refer to the KFPA11565-E message.
-565

42931
Refer to the KFPA11600-E message.
-600

42932
Refer to the KFPA11724-E message.
-724

42933
Refer to the KFPA11780-E message.
-780

42934
Refer to the KFPA11824-E message.
-824

42937
Refer to the KFPA19330-E message.
-1330

42938
Refer to the KFPA19458-E message.
-1458

42939
Refer to the KFPA19633-E message.
-1633

42941
Refer to the KFPA11126-E message.
-126

42942
Refer to the KFPA11133-E message.
-133

42943
Refer to the KFPA11154-E message.
-154

42946
Refer to the KFPA11168-E message.
-168

42947
Refer to the KFPA11171-E message.
-171

42948
Refer to the KFPA11172-E message.
-172

42949
Refer to the KFPA11176-E message.
-176

42950
Refer to the KFPA11179-E message.
-179

42951
Refer to the KFPA11198-E message.
-198

42952
Refer to the KFPA11228-E message.
-228

42953
Refer to the KFPA11235-E message.
-235

42954
Refer to the KFPA11243-E message.
-243

42955
Refer to the KFPA11249-E message.
-249

42956
Refer to the KFPA11254-E message.
-254

42958
Refer to the KFPA11266-E message.
-266

42959
Refer to the KFPA11267-E message.
-267

42960
Refer to the KFPA11273-E message.
-273

42961
Refer to the KFPA11274-E message.
-274

42962
Refer to the KFPA11276-E message.
-276

42963
Refer to the KFPA11277-E message.
-277

42964
Refer to the KFPA11296-E message.
-296

42965
Refer to the KFPA11299-E message.
-299

42966
Refer to the KFPA11314-E message.
-314

42967
Refer to the KFPA11351-E message.
-351

42968
Refer to the KFPA11443-E message.
-443

42970
Refer to the KFPA11462-E message.
-462

42971
Refer to the KFPA11463-E message.
-463

42972
Refer to the KFPA11470-E message.
-470

42973
Refer to the KFPA11471-E message.
-471

42974
Refer to the KFPA11472-E message.
-472

42975
Refer to the KFPA11473-E message.
-473

42976
Refer to the KFPA11474-E message.
-474

42978
Refer to the KFPA11477-E message.
-477

42979
Refer to the KFPA11479-E message.
-479

42980
Refer to the KFPA11504-E message.
-504

42981
Refer to the KFPA11583-E message.
-583

42983
Refer to the KFPA11746-E message.
-746

42984
Refer to the KFPA11750-E message.
-750

42985
Refer to the KFPA11753-E message.
-753

42986
Refer to the KFPA11774-E message.
-774

42987
Refer to the KFPA11807-E message.
-807

42988
Refer to the KFPA11829-E message.
-829

42989
Refer to the KFPA11839-E message.
-839

429A2
Refer to the KFPA19101-E message.
-1101

429A5
Refer to the KFPA19110-E message.
-1110

429A6
Refer to the KFPA19111-E message.
-1111

429A7
Refer to the KFPA19130-E message.
-1130

429A8
Refer to the KFPA19170-E message.
-1170

429A9
Refer to the KFPA19180-E message.
-1180

429B0
Refer to the KFPA19181-E message.
-1181

429B1
Refer to the KFPA19182-E message.
-1182

429B2
Refer to the KFPA19184-E message.
-1184

429B3
Refer to the KFPA19185-E message.
-1185

429B4
Refer to the KFPA19187-E message.
-1187

429B5
Refer to the KFPA19188-E message.
-1188

429B6
Refer to the KFPA19189-E message.
-1189

429B9
Refer to the KFPA19212-E message.
-1212

429C0
Refer to the KFPA19220-E message.
-1220

429C1
Refer to the KFPA19221-E message.
-1221

429C2
Refer to the KFPA19254-E message.
-1254

429C3
Refer to the KFPA19270-E message.
-1270

429C4
Refer to the KFPA19271-E message.
-1271

429C5
Refer to the KFPA19272-E message.
-1272

429C6
Refer to the KFPA19273-E message.
-1273

429C7
Refer to the KFPA19274-E message.
-1274

429C8
Refer to the KFPA19275-E message.
-1275

429C9
Refer to the KFPA19291-E message.
-1291

429D0
Refer to the KFPA19292-E message.
-1292

429D1
Refer to the KFPA19295-E message.
-1295

429D2
Refer to the KFPA19319-E message.
-1319

429D3
Refer to the KFPA19321-E message.
-1321

429D4
Refer to the KFPA19322-E message.
-1322

429D5
Refer to the KFPA19324-E message.
-1324

429D6
Refer to the KFPA19327-E message.
-1327

429D7
Refer to the KFPA19328-E message.
-1328

429D8
Refer to the KFPA19329-E message.
-1329

429D9
Refer to the KFPA19405-E message.
-1405

429E0
Refer to the KFPA19409-E message.
-1409

429E2
Refer to the KFPA19452-E message.
-1452

429E3
Refer to the KFPA19453-E message.
-1453

429E4
Refer to the KFPA19454-E message.
-1454

429E5
Refer to the KFPA19577-E message.
-1577

429E6
The number of columns in INTO clauses specified in the SQL statement exceeds the permitted maximum value.
For details, refer to the KFPA11129-E message.
-129

429E7
The number of java.sql.ResultSet[] in EXTERNAL NAME clauses specified in the SQL statement exceeds the permitted maximum value.
For details, refer to the KFPA11129-E message.
-129

429E8
Refer to the KFPA11188-E message.
-188

429E9
Refer to the KFPA11553-E message.
-553

429F0
Refer to the KFPA11836-E message.
-836

429F1
Refer to the KFPA19105-E message.
-1105

429F2
Refer to the KFPA19140-E message.
-1140

429F3
Refer to the KFPA19171-E message.
-1171

429F4
Refer to the KFPA19186-E message.
-1186

429F5
Refer to the KFPA19406-E message.
-1406

429F6
Refer to the KFPA19603-E message.
-1603

429F8
Refer to the KFPA19318-E message.
-1318

429F9
Defined information cannot be changed for the columns of the base table specified in the concatenation operation or scalar function in the view definition.
For details, refer to the KFPA11716-E message.
-716

429FA
A function execution does not end with the RETURN statement.
For details, refer to the KFPA11986-E message.
-986

42E28
Refer to the KFPA11455-E message.
-455

42E29
Refer to the KFPA19459-E message.
-1459

42I02
Refer to the KFPA11207-E message.
-207

42I03
Refer to the KFPA11432-E message.
-432

42I08
One of the following errors is present:

PUBLIC, MASTER, HiRDB, or ALL was specified as the authorization identifier or group ID.
For details, refer to the KFPA11549-E message.

ALL was specified for the table identifier.
For details, refer to the KFPA11658-E message.

-549
-658

42I0A
Refer to the KFPA11766-E message.
-766

42I12
Refer to the KFPA11574-E message.
-574

42I13
Refer to the KFPA11601-E message.
-601

42I14
Refer to the KFPA11609-E message.
-609

42I15
Refer to the KFPA11612-E message.
-612

42I16
Refer to the KFPA11614-E message.
-614

42I17
Refer to the KFPA11615-E message.
-615

42I18
Refer to the KFPA11619-E message.
-619

42I19
Refer to the KFPA11621-E message.
-621

42I20
Refer to the KFPA11625-E message.
-625

42I23
Refer to the KFPA11628-E message.
-628

42I24
Refer to the KFPA11631-E message.
-631

42I25
Refer to the KFPA11632-E message.
-632

42I26
Refer to the KFPA11656-E message.
-656

42I27
Refer to the KFPA11659-E message.
-659

42I29
Refer to the KFPA11661-E message.
-661

42I30
Refer to the KFPA11664-E message.
-664

42I31
One of the following errors is present:

The information specified in the CHANGE clause in ALTER TABLE is the same information as before the change.
For details, refer to the KFPA11665-E message.

WITH DEFAULT has already been specified for the column.
For details, refer to the KFPA11699-E message.

-665
-699

42I32
Refer to the KFPA11667-E message.
-667

42I37
Tables cannot be defined with only reserved columns.
For details, refer to the KFPA11685-E message.
-685

42I41
Refer to the KFPA11690-E message.
-690

42I42
Refer to the KFPA11693-E message.
-693

42I43
Refer to the KFPA11694-E message.
-694

42I46
Refer to the KFPA11697-E message.
-697

42I47
Refer to the KFPA11698-E message.
-698

42I54
Refer to the KFPA11743-E message.
-743

42I55
Refer to the KFPA11744-E message.
-744

42I56
Refer to the KFPA11745-E message.
-745

42I58
Refer to the KFPA11747-E message.
-747

42I60
Refer to the KFPA11758-E message.
-758

42I65
Refer to the KFPA11764-E message.
-764

42I68
Refer to the KFPA11791-E message.
-791

42I70
Refer to the KFPA11793-E message.
-793

42I77
Refer to the KFPA19602-E message.
-1602

42I79
Refer to the KFPA11741-E message.
-741

42I80
Refer to the KFPA11775-E message.
-775

42I82
Refer to the KFPA11712-E message.
-712

42I86
Refer to the KFPA19612-E message.
-1612

42I88
Refer to the KFPA11591-E message.
-591

42I89
Refer to the KFPA11592-E message.
-592

42I90
Refer to the KFPA11165-E message.
-165

42I93
Refer to the KFPA11478-E message.
-478

42I9A
Refer to the KFPA19615-E message.
-1615

42I9B
Refer to the KFPA19616-E message.
-1616

42IA0
A sequence generator cannot be created.
For details, refer to the KFPA19624-E message.
-1624

42J02
Refer to the KFPA11584-E message.
-584

42J03
Refer to the KFPA11605-E message.
-605

42J04
Refer to the KFPA11606-E message.
-606

42J05
Refer to the KFPA11611-E message.
-611

42J06
Refer to the KFPA11620-E message.
-620

42J07
Refer to the KFPA11622-E message.
-622

42J08
Refer to the KFPA11624-E message.
-624

42J10
Refer to the KFPA11702-E message.
-702

42J11
Refer to the KFPA11704-E message.
-704

42J12
Refer to the KFPA11710-E message.
-710

42J13
Refer to the KFPA11717-E message.
-717

42J14
Refer to the KFPA11718-E message.
-718

42J15
Refer to the KFPA11721-E message.
-721

42J16
Refer to the KFPA19331-E message.
-1331

42J17
Refer to the KFPA19575-E message.
-1575

42J18
Refer to the KFPA19625-E message.
-1625

42J21
Refer to the KFPA11200-E message.
-200

42J22
Refer to the KFPA11369-E message.
-369

42J23
Refer to the KFPA11597-E message.
-597

42J24
Refer to the KFPA11754-E message.
-754

42J29
Refer to the KFPA11908-E message.
-908

42J30
Refer to the KFPA11909-E message.
-909

42J31
Refer to the KFPA11939-E message.
-939

42J33
Refer to the KFPA19200-E message.
-1200

42J34
Refer to the KFPA19581-E message.
-1581

42J35
Refer to the KFPA19681-E message.
-1681

42JA1
The ? parameter cannot be specified in an SQL statement for a trigger.
For details, refer to the KFPA19450-E message.
-1450

42JA2
A trigger cannot be defined for other schemas.
For details, refer to the KFPA19450-E message.
-1450

42JA4
Trigger can be defined only for a base table.
For details, refer to the KFPA19450-E message.
-1450

42JA5
The table for which a trigger is to be defined does not exist.
For details, refer to the KFPA19450-E message.
-1450

42JA6
OLD ROW or NEW ROW can be specified only once in the old or new values alias list, respectively.
For details, refer to the KFPA19450-E message.
-1450

42JA7
If INSERT is specified as the trigger execution timing, OLD ROW cannot be specified.
For details, refer to the KFPA19450-E message.
-1450

42JA8
If DELETE is specified as the trigger execution timing, NEW ROW cannot be specified.
For details, refer to the KFPA19450-E message.
-1450

42JA9
The same name cannot be specified in OLD ROW and NEW ROW.
For details, refer to the KFPA19450-E message.
-1450

42JAA
If FOR EACH STATEMENT is specified, NEW ROW and OLD ROW cannot be specified.
For details, refer to the KFPA19450-E message.
-1450

42JAB
More than 30,000 columns are specified in the trigger execution timing.
For details, refer to the KFPA19450-E message.
-1450

42JAC
The column name specified in the trigger execution timing is duplicated.
For details, refer to the KFPA19450-E message.
-1450

42JAD
The column specified in the trigger execution timing was not found in the table for which a trigger is to be defined.
For details, refer to the KFPA19450-E message.
-1450

42JAE
In the trigger definition in which BEFORE is specified as the trigger action time, an update SQL statement cannot be specified as the triggered SQL statement.
For details, refer to the KFPA19450-E message.
-1450

42JAF
Repetition columns and abstract data type columns cannot be referenced by the old or new values correlation name.
For details, refer to the KFPA19450-E message.
-1450

42JAH
A table for which a trigger is defined cannot be specified in the triggered SQL statement.
For details, refer to the KFPA19450-E message.
-1450

42JAJ
A reserved column cannot be specified as a trigger event column.
For details, refer to the KFPA19450-E message.
-1450

42JAL
The user cannot define another user's table.
For details, refer to the KFPA19450-E message.
-1450

42JAM
ROW cannot be specified for the old or new values correlation name.
For details, refer to the KFPA19450-E message.
-1450

42JAN
If a CURRENT_TIMESTAMP column with USING BES as its default value is specified as the target of an assignment statement, DEFAULT cannot be assigned as a value.
For details, refer to the KFPA19450-E message.
-1450

42JAO
In the trigger definition in which BEFORE is specified as the trigger action time, only the default constructor can be specified as the function call in the triggered SQL statement.
For details, refer to the KFPA19450-E message.
-1450

42JAP
Neither a Java function nor a Java procedure can be specified in a triggered SQL statement.
For details, refer to the KFPA19450-E message.
-1450

42JAQ
ROLLBACK cannot be specified in a triggered SQL statement.
For details, refer to the KFPA19450-E message.
-1450

42JAR
COMMIT cannot be specified in a triggered SQL statement.
For details, refer to the KFPA19450-E message.
-1450

42JAS
PURGE cannot be specified in a triggered SQL statement.
For details, refer to the KFPA19450-E message.
-1450

42JAT
GET_JAVA_STORED_ROUTINE_SOURCE cannot be specified in a triggered SQL statement.
For details, refer to the KFPA19450-E message.
-1450

42JD1
Refer to the KFPA19293-E message.
-1293

42K01
Refer to the KFPA11550-E message.
-550

42K02
Refer to the KFPA11551-E message.
-551

42K03
Refer to the KFPA11552-E message.
-552

42K04
Refer to the KFPA11554-E message.
-554

42K05
Refer to the KFPA11555-E message.
-555

42K06
Refer to the KFPA11556-E message.
-556

42K14
Refer to the KFPA11607-E message.
-607

42K20
Refer to the KFPA11663-E message.
-663

42K21
Refer to the KFPA11680-E message.
-680

42K22
Refer to the KFPA11823-E message.
-823

42K25
Refer to the KFPA11514-E message.
-514

42K26
Refer to the KFPA11547-E message.
-547

42K27
Refer to the KFPA19219-E message.
-1219

42K28
Refer to the KFPA11573-E message.
-573

42K29
Refer to the KFPA11590-E message.
-590

42K30
Refer to the KFPA11902-E message.
-902

42K32
Refer to the KFPA11904-E message.
-904

42K33
Refer to the KFPA11905-E message.
-905

42K34
Refer to the KFPA11906-E message.
-906

42K35
Refer to the KFPA11907-E message.
-907

42K36
Refer to the KFPA19518-E message.
-1518

42K37
Refer to the KFPA19631-E message.
-1631

42K38
Refer to the KFPA19634-E message.
-1634

42K39
Refer to the KFPA19635-E message.
-1635

42K40
Refer to the KFPA19680-E message.
-1680

42K41
Refer to the KFPA19296-E message.
-1296

42K42
Refer to the KFPA11925-E message.
-925

Table 8-25 SQLSTATE class 45

SQLSTATE | Explanation | SQLCODE
45501 | Refer to the KFPA19404-E message. | -1404

Table 8-26 SQLSTATE class 51

SQLSTATE | Explanation | SQLCODE
51001 | Refer to the KFPA11307-E message. | -307
51003 | Refer to the KFPA11769-E message. | -769
51004 | Refer to the KFPA11838-E message. | -838
51006 | Refer to the KFPA11804-E message. | -804
5100F | Refer to the KFPA11997-E message. | -997
5100H | Refer to the KFPA11359-E message. | -359

Table 8-27 SQLSTATE class 52

SQLSTATE
Explanation
SQLCODE

52002
Refer to the KFPA11787-E message.
-787

52003
Refer to the KFPA11558-E message.
-558

52004
Refer to the KFPA11727-E message.
-727

52005
Refer to the KFPA11734-E message.
-734

52006
Refer to the KFPA19456-E message.
-1456

52007
Refer to the KFPA19503-E message.
-1503

52008
Refer to the KFPA11948-E message.
-948

52009
Refer to the KFPA11569-E message.
-569

5200B
Refer to the KFPA11937-E message.
-937

52010
Refer to the KFPA11494-E message.
-494

52011
An error occurred during transaction control processing.
For details, refer to the KFPA19703-E message.
-1703

52014
Refer to the KFPA11990-E message.
-990

52206
Refer to the KFPA19802-E message.
-1802

52208
Refer to the KFPA19102-E message.
-1102

52209
Refer to the KFPA19518-E message.
-1518

52301
Refer to the KFPA11395-E message.
-395

52302
Refer to the KFPA11722-E message.
-722

52303
Refer to the KFPA11723-E message.
-723

Table 8-28 SQLSTATE class 53

SQLSTATE
Explanation
SQLCODE

53001
Refer to the KFPA11356-E message.
-356

53002
Refer to the KFPA11546-E message.
-546

53004
Refer to the KFPA11900-E message.
-900

53005
Refer to the KFPA19587-E message.
-1587

53006
Refer to the KFPA19800-E message.
-1800

53021
Refer to the KFPA11613-E message.
-613

53201
Refer to the KFPA11930-E message.
-930

53202
Refer to the KFPA11729-E message.
-729

53203
Refer to the KFPA11914-E message.
-914

53204
Refer to the KFPA11929-E message.
-929

53208
Refer to the KFPA11395-E message.
-395

53209
The SQL statement cannot be executed because the resource indicated by its resource ID is in use exclusively by another transaction.
For details, refer to the KFPA11770-I message.
-770

53210
There is not enough work area for locking.
For details, refer to the KFPA11912-E message.
-912

53212
An attempt to expand the thread stack area failed.
For details, refer to the KFPA11945-E message.
-945

53301
Refer to the KFPA11596-E message.
-596

53302
Refer to the KFPA19576-E message.
-1576

53305
Refer to the KFPA19705-E message.
-1705

53401
Refer to the KFPA11342-E message.
-342

53402
Refer to the KFPA11531-E message.
-531

53601
Refer to the KFPA19719-E message.
-1719

53602
Refer to the KFPA19724-E message.
-1724

53603
Refer to the KFPA19725-E message.
-1725

Table 8-29 SQLSTATE class 54

SQLSTATE | Explanation | SQLCODE
54001 | Refer to the KFPA11159-E message. | -159
54002 | Refer to the KFPA11315-E message. | -315
54003 | Refer to the KFPA11935-E message. | -935
54005 | Refer to the KFPA19411-E message. | -1411
54006 | Refer to the KFPA19502-E message. | -1502
54007 | Refer to the KFPA19510-E message. | -1510
54008 | Refer to the KFPA19511-E message. | -1511
54009 | Refer to the KFPA19512-E message. | -1512
54201 | Refer to the KFPA11563-E message. | -563
54202 | Refer to the KFPA11725-E message. | -725

Table 8-30 SQLSTATE class 55

SQLSTATE
Explanation
SQLCODE

55001
An error occurred on the Java Virtual Machine.
For details, refer to the KFPA11491-E message.
-491

Table 8-31 SQLSTATE class 56

SQLSTATE
Explanation
SQLCODE

56001
Refer to the KFPA11312-E message.
-312

56007
Refer to the KFPA11616-E message.
-616

56008
Refer to the KFPA11654-E message.
-654

56009
Refer to the KFPA11657-E message.
-657

5600B
Refer to the KFPA11706-E message.
-706

5600C
Refer to the KFPA11748-E message.
-748

5600E
The length of the SQL statement to be dynamically preprocessed is invalid.
For details, refer to the KFPA11821-E message.
-821

5600F
The length of the SQL statement specified in the view definition exceeds the permitted maximum value.
For details, refer to the KFPA11821-E message.
-821

5600G
The length of the SQL statement specified in the check constraint definition exceeds the permitted maximum value.
For details, refer to the KFPA11821-E message.
-821

5600H
The length of the SQL statement specified in the procedure definition exceeds the permitted maximum value.
For details, refer to the KFPA11821-E message.
-821

5600I
Refer to the KFPA19450-E message.
-1450

56010
Refer to the KFPA11662-E message.
-662

56011
Refer to the KFPA11167-E message.
-167

56012
Refer to the KFPA11250-E message.
-250

56013
Refer to the KFPA11343-E message.
-343

56014
Refer to the KFPA11634-E message.
-634

56015
Refer to the KFPA11636-E message.
-636

56016
Refer to the KFPA11637-E message.
-637

56017
Refer to the KFPA11703-E message.
-703

56018
Refer to the KFPA11714-E message.
-714

56019
Refer to the KFPA11795-E message.
-795

56020
Refer to the KFPA11805-E message.
-805

56022
Refer to the KFPA11952-E message.
-952

56026
Refer to the KFPA19513-E message.
-1513

56027
Refer to the KFPA19583-E message.
-1583

56028
Refer to the KFPA19584-E message.
-1584

56030
The result of serialization (conversion to character string) of an XML-type value is too long.
For details, refer to the KFPA19313-E message.
-1313

56031
The size of an SQL object exceeds 32 MB.
For details, refer to the KFPA11992-E message.
-992

56032
The SQL statement cannot be executed for one of the following reasons

The row length is greater than the page length.

The key length of the index exceeds the maximum value.

The number of columns exceeds the maximum value.

For details, refer to the KFPA11813-E message.
-813

Table 8-32 SQLSTATE class 57

SQLSTATE | Explanation | SQLCODE
57008 | Refer to the KFPA11528-E message. | -528
57009 | Refer to the KFPA11529-E message. | -529

Table 8-33 SQLSTATE class 58

SQLSTATE | Explanation | SQLCODE
58004 | Refer to the KFPA11610-E message. | -610
58005 | Refer to the KFPA11652-E message. | -652
58006 | Refer to the KFPA11653-E message. | -653
58008 | Refer to the KFPA11608-E message. | -608
58009 | Refer to the KFPA19704-E message. | -1704
58011 | Refer to the KFPA11513-E message. | -513
58012 | Refer to the KFPA11599-E message. | -599
58013 | Refer to the KFPA11707-E message. | -707
58014 | Refer to the KFPA11708-E message. | -708
58015 | Refer to the KFPA11709-E message. | -709
58018 | Refer to the KFPA11771-E message. | -771
58019 | Refer to the KFPA11796-E message. | -796
58021 | Refer to the KFPA11844-E message. | -844
58022 | Refer to the KFPA11845-E message. | -845
58023 | Refer to the KFPA11848-E message. | -848

Table 8-34 SQLSTATE class 59

SQLSTATE | Explanation | SQLCODE
59001 | Refer to the KFPA11280-E message. | -280
59002 | Refer to the KFPA11281-E message. | -281
59003 | Refer to the KFPA11761-E message. | -761
59004 | Refer to the KFPA11890-E message. | -890
59005 | Refer to the KFPA11895-E message. | -895
59006 | Refer to the KFPA11896-E message. | -896

Table 8-35 SQLSTATE class 5A

SQLSTATE | Explanation | SQLCODE
5A001 | Refer to the KFPA11329-E message. | -329
5A003 | Refer to the KFPA11785-E message. | -785

Table 8-36 SQLSTATE class 5B

SQLSTATE
Explanation
SQLCODE

5B001
Refer to the KFPA11735-E message.
-735

5B002
The SIGNAL or RESIGNAL statement resulted in an error.
For details, refer to the KFPA19400-E message.
-1400

Table 8-37 SQLSTATE class 5C

SQLSTATE | Explanation | SQLCODE
5C006 | Refer to the KFPA11431-E message. | -431
5C007 | Refer to the KFPA11476-E message. | -476
5C008 | Refer to the KFPA11484-E message. | -484
5C009 | Refer to the KFPA11485-E message. | -485
5C010 | Refer to the KFPA11553-E message. | -553
5C011 | Refer to the KFPA11720-E message. | -720
5C012 | Refer to the KFPA11728-E message. | -728
5C013 | Refer to the KFPA11731-E message. | -731
5C014 | Refer to the KFPA11732-E message. | -732
5C015 | Refer to the KFPA11733-E message. | -733
5C016 | Refer to the KFPA11736-E message. | -736
5C021 | Refer to the KFPA11941-E message. | -941
5C024 | Refer to the KFPA11984-E message. | -984
5C025 | Refer to the KFPA11987-E message. | -987
5C026 | Refer to the KFPA19332-E message. | -1332
5C027 | Refer to the KFPA19333-E message. | -1333
5C030 | Refer to the KFPA19700-E message. | -1700
5C031 | Refer to the KFPA19517-E message. | -1517
5C032 | Refer to the KFPA19520-E message. | -1520

Table 8-38 SQLSTATE class 5E

SQLSTATE | Explanation | SQLCODE
5E101 | Refer to the KFPA19222-E message. | -1222

Table 8-39 SQLSTATE class IZ

SQLSTATE
Explanation
SQLCODE

IZ003
An attempt was made to execute index batch creation for an index that had already been created.
For details, refer to the KFPA11875-E message.
-875

Table 8-40 SQLSTATE class R2

SQLSTATE
Explanation
SQLCODE

R2000
During a list search, a row that existed at the time of list creation was not returned.
For details, refer to the KFPA12110-I message.
110

8.1.2 When the PDSTANDARDSQLSTATE client environment variable is set to NO or the pd_standard_sqlstate system common definition is set to N

Table 8-41 Classes of SQLSTATE returned by HiRDB and their explanations

Class | Explanation | Reference
00 | Terminated normally. | Table 8-42
01 | A warning was issued. | Table 8-43
02 | There is no data. | Table 8-44
40 | The transaction rolled back. | Table 8-45
R0 | Terminated abnormally. | Table 8-46
R2 | There is no data. | Table 8-47

Table 8-42 SQLSTATE class 00

SQLSTATE | Explanation | SQLCODE | SQLWARN
00000 | Terminated normally. | 0 | None

Table 8-43 SQLSTATE class 01

SQLSTATE | Explanation | SQLCODE | SQLWARN
01000 | Terminated normally with a warning. | 0 | SQLWARN0='W'
0100C | A dynamic result set was returned. | 120 | SQLWARN0='W'
0100D | Another result set wass returned. | 121 | SQLWARN0='W'
0100E | An attempt was made to return too many result sets. | 120 | SQLWARN0='W'
01R00 | Terminated normally with a warning. | Positive number other than 100 or 110 | SQLWARN0=space-character or 'W'

Table 8-44 SQLSTATE class 02

SQLSTATE | Explanation | SQLCODE | SQLWARN
02000 | There is no data. | 100 | None
02001 | There is no other result set to be returned. | 100 | None

Table 8-45 SQLSTATE class 40

SQLSTATE
Explanation
SQLCODE
SQLWARN

40000
The SQL statement terminated with an error because the transaction rolled back.
For details, refer to the error message corresponding to the SQLCODE.
-1 to -999
SQLWARN0='W'
SQLWARN6='W'

Table 8-46 SQLSTATE class R0

SQLSTATE | Explanation | SQLCODE | SQLWARN
R0000 | Terminated abnormally. | SQLCODE<0 | SQLWARN6=' '

Table 8-47 SQLSTATE class R2

SQLSTATE | Explanation | SQLCODE | SQLWARN
R2000 | During a list search, a row that existed at the time of list creation was not returned. | 110 | None

Index

[A][C][D][E][F][G][K][L][M][Q][R][S][T][V]

(A)

ABORT code

EhiXXXXX

EhmXXXXX

EhxXXXXX

PaXXXXX

PbXXXXX

PdXXXXX

PeXXXXX

PhXXXXX

PiXXXXX

PkXXXXX

PoXXXXX

PrXXXXX

PsXXXXX

PtXXXXX

PuXXXXX

PxXXXXX

PyXXXXX

(C)

conventions

fonts and symbols

KB, MB, GB, and TB

version numbers

(D)

descriptive notation

detail codes

for RPC-related errors

for RPC-related errors

for system-related errors

(E)

end code types

end code types

error codes

output by HiRDB file system

returned from HiRDB file system access requests

error detail codes

(F)

font conventions

(G)

GB meaning

(K)

KB meaning

(L)

lock control errors

resource types, resource names, and resource information for

resource types, resource names, and resource information for

(M)

MB meaning

message output

format of

to event log (syslogfile in UNIX)

to standard error output or standard output

to standard output by pdcat command

messages

overview of

related to sort processing

related to sort processing (UNIX edition)

related to sort processing (Windows edition)

(Q)

query number

(R)

RPC-related errors

detail codes for

detail codes for

frequently occurring causes and required action for

(S)

shmget system call, corrective action when error occurs in (in Windows)

SQLCODE

SQLSTATE

symbol conventions

system call return codes

frequently occurring causes and required action for

system-related errors, detail codes for

(T)

TB meaning

(V)

version number conventions

Trademarks

ActiveX is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.
AIX is a trademark of International Business Machines Corporation in the United States, other countries, or both.
AIX 5L is a trademark of International Business Machines Corporation in the United States, other countries, or both.
AMD, AMD Opteron, and combinations thereof, are trademarks of Advanced Micro Devices, Inc.
CORBA is a registered trademark of Object Management Group, Inc. in the United States.
DataStage, MetaBroker, MetaStage and QualityStage are trademarks of International Business Machines Corporation in the United States, other countries, or both.
DB2 is a trademark of International Business Machines Corporation in the United States, other countries, or both.
HACMP is a trademark of International Business Machines Corporation in the United States, other countries, or both.
HP-UX is a product name of Hewlett-Packard Development Company, L.P. in the U.S. and other countries.
IBM is a trademark of International Business Machines Corporation in the United States, other countries, or both.
Itanium is a trademark of Intel Corporation in the United States and other countries.
Linux(R) is the registered trademark of Linus Torvalds in the U.S. and other countries.
Microsoft and Visual Studio are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
Microsoft Access is a registered trademark of Microsoft Corporation in the U.S. and other countries.
Microsoft Office and Excel are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
Motif is a registered trademark of the Open Software Foundation, Inc.
Microsoft and MS-DOS are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
ODBC is Microsoft's strategic interface for accessing databases.
OLE is the name of a software product developed by Microsoft Corporation and the acronym for Object Linking and Embedding.
Oracle and Java are registered trademarks of Oracle and/or its affiliates.
OS/390 is a trademark of International Business Machines Corporation in the United States, other countries, or both.
PowerHA is a trademark of International Business Machines Corporation in the United States, other countries, or both.
Red Hat is a trademark or a registered trademark of Red Hat Inc. in the United States and other countries.
UNIFY2000 is a product name of Unify Corp.
UNIX is a registered trademark of The Open Group in the United States and other countries.
VERITAS is a trademark or registered trademark of Symantec Corporation in the U.S. and other countries.
Visual Basic is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.
Visual C++ is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.
Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.
Windows NT is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.
Windows Server is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.
Windows Vista is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.
X/Open is a registered trademark of The Open Group in the U.K. and other countries.
X Window System is a trademark of X Consortium, Inc.
Other product and company names mentioned in this document may be the trademarks of their respective owners. Throughout this document Hitachi has attempted to distinguish trademarks from descriptive terms by writing the name with the capitalization used by the manufacturer, or by writing the name with initial capital letters. Hitachi cannot attest to the accuracy of this information. Use of a trademark in this document should not be regarded as affecting the validity of the trademark.