Preface

This manual is intended for system administrators and system designers who use HiRDB Dataextractor to link data. The manual assumes that the reader has a basic understanding of the following:

• Operating system under which HiRDB Dataextractor is running
• HiRDB
• XDM E2 (only if you will link data with XDM)
• XDM/XT (only if you will link data with a database on a mainframe using XDM/XT)

This manual is organized as follows:

1. Overview of HiRDB Dataextractor

Chapter 1 describes the features and functions of HiRDB Dataextractor.

2. HiRDB Dataextractor Environment Setup

Chapter 2 describes the software configuration of HiRDB Dataextractor and its environment setup procedure.

3. Extracting and Importing Data and Creating Files

Chapter 3 explains the procedures for extracting and importing data and for creating files.

4. Extracting Data from HiRDB and Importing It into HiRDB

Chapter 4 explains the procedures for extracting data from a HiRDB database and importing it into a HiRDB table or specifying information for file creation.

5. Extracting Data from ORACLE and Importing It into HiRDB

Chapter 5 explains the procedures for extracting data from an ORACLE database and importing it into a HiRDB table or specifying information for file creation.

6. Operation

Chapter 6 explains the procedures for starting and terminating HiRDB Dataextractor.

7. Error Handling Procedures

Chapter 7 explains the error handling procedures.

8. Messages

Chapter 8 explains the messages that are issued by HiRDB Dataextractor.

A. Memory and File Requirements

Appendix A explains the memory and file size requirements for HiRDB Dataextractor.

B. Functional Differences with Windows

Appendix B explains the functional differences when the Windows operating system is used.

C. Functional Differences with Solaris

Appendix C explains the functional differences when the Solaris operating system is used.

D. Functional Differences with Linux

Appendix D explains the functional differences when the Linux operating system is used.

E. Functional Differences with AIX

Appendix E explains the functional differences when the AIX operating system is used.

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

HiRDB (for Windows)

• For Windows Systems HiRDB Version 8 Description (3020-6-351(E))
• For Windows Systems HiRDB Version 8 Installation and Design Guide (3020-6-352(E))
• For Windows Systems HiRDB Version 8 System Definition (3020-6-353(E))
• For Windows Systems HiRDB Version 8 System Operation Guide (3020-6-354(E))
• For Windows Systems HiRDB Version 8 Command Reference (3020-6-355(E))

HiRDB (for UNIX)

• For UNIX Systems HiRDB Version 8 Description (3000-6-351(E))
• For UNIX Systems HiRDB Version 8 Installation and Design Guide (3000-6-352(E))
• For UNIX Systems HiRDB Version 8 System Definition (3000-6-353(E))
• For UNIX Systems HiRDB Version 8 System Operation Guide (3000-6-354(E))
• For UNIX Systems HiRDB Version 8 Command Reference (3000-6-355(E))
• HiRDB Staticizer Option Version 7 Description and User's Guide (3000-6-282(E))
• For UNIX Systems HiRDB Version 8 Disaster Recovery System Configuration and Operation Guide (3000-6-364)^*

HiRDB (for both Windows and UNIX)

• HiRDB Version 8 UAP Development Guide (3020-6-356(E))
• HiRDB Version 8 SQL Reference (3020-6-357(E))
• HiRDB Version 8 Messages (3020-6-358(E))
• HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide (3020-6-360(E))
• HiRDB Dataextractor Version 8 Description, User's Guide and Operator's Guide (3020-6-362(E))

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

You must use the UNIX or the Windows manuals, as appropriate to the platform you are using.

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.

This manual uses the following abbreviations for product names:

Name of product or other entity	Representation
HiRDB/Single Server Version 8	HiRDB/Single Server	HiRDB or HiRDB Server
HiRDB/Single Server Version 8 (64)
HiRDB/Parallel Server Version 8	HiRDB/Parallel Server
HiRDB/Parallel Server Version 8 (64)
HiRDB/Developer's Kit Version 8	HiRDB/Developer's Kit	HiRDB Client
HiRDB/Developer's Kit Version 8 (64)
HiRDB/Run Time Version 8	HiRDB/Run Time
HiRDB/Run Time Version 8 (64)
HiRDB Datareplicator Version 8	HiRDB Datareplicator
HiRDB Datareplicator Version 8 (64)
HiRDB Dataextractor Version 8	HiRDB Dataextractor
HiRDB Dataextractor Version 8 (64)
XDM/RD E2 XDM/RD	XDM/RD
AIX 5L	AIX
HP-UX 11i V2 (PA-RISC)	HP-UX
HP-UX 11i V2 (IPF)	HP-UX or HP-UX (IPF)
Red Hat Linux	Linux
Red Hat Enterprise Linux
Red Hat Enterprise Linux AS 3 (IPF)	Linux (IPF)	Linux
Red Hat Enterprise Linux AS 4 (IPF)
Red Hat Enterprise Linux AS 3 (AMD64 & Intel EM64T)	Linux (EM64T)
Red Hat Enterprise Linux AS 4 (AMD64 & Intel EM64T)
Red Hat Enterprise Linux ES 3 (AMD64 & Intel EM64T)
Red Hat Enterprise Linux ES 4 (AMD64 & Intel EM64T)
Microsoft(R) Windows(R) 2000 Professional Operating System	Windows 2000
Microsoft(R) Windows(R) 2000 Server Operating System
Microsoft(R) Windows(R) 2000 Advanced Server Operating System
Microsoft(R) Windows(R) 2000 Datacenter Server Operating System
Microsoft(R) Windows(R) XP Professional Operating System	Windows XP Professional	Windows XP
Microsoft(R) Windows(R) XP Professional x64 Edition	Windows XP x64 Edition
Microsoft(R) Windows ServerTM 2003, Standard Edition	Windows Server 2003
Microsoft(R) Windows ServerTM 2003, Enterprise Edition
Microsoft(R) Windows ServerTM 2003, Standard x64 Edition	Windows Server 2003 x64 Editions	Windows Server 2003
Microsoft(R) Windows ServerTM 2003, Enterprise x64 Edition
64 bit Version Microsoft(R) Windows ServerTM 2003, Enterprise Edition (IPF)	Windows Server 2003 (IPF)
Microsoft(R) Windows ServerTM 2003 R2, Standard Edition	Windows Server 2003 R2
Microsoft(R) Windows ServerTM 2003 R2, Enterprise Edition
Microsoft(R) Windows ServerTM 2003 R2, Standard x64 Edition	Windows Server 2003 R2 or Windows Server 2003 R2 x64 Editions
Microsoft(R) Windows ServerTM 2003 R2, Enterprise x64 Edition

• Windows 2000, Windows XP, and Windows Server 2003 may be referred to collectively as Windows. In explanations about HiRDB clients, such references may include Windows Me. Note, however, that any of the above operating systems may be referred to explicitly if required for reasons of clarity.
• The xtrepO command is referred to as the xtrep command, unless noted otherwise.
• The following ORACLE attributes are represented as BLOB, unless noted otherwise: LONG, LONG RAW, BLOB, CLOB, NCLOB, and BFILE.

This manual uses the following conventions in diagrams:

Font and symbol conventions are classified as:

• General font conventions
• Conventions in syntax explanations

These conventions are described below.

General font conventions

The following table lists the general font conventions:

Font	Convention
Bold	Bold type indicates text on a window, other than the window title. Such text includes menus, menu options, buttons, radio box options, or explanatory labels. For example, bold is used in sentences such as the following: From the File menu, choose Open. Click the Cancel button. In the Enter name entry box, type your name.
Italics	Italics are used to indicate a placeholder for some actual text provided by the user or system. Italics are also used for emphasis. For example: Write the command as follows: copy source-file target-file Do not delete the configuration file.
Code font	A code font indicates text that the user enters without change, or text (such as messages) output by the system. For example: At the prompt, enter dir. Use the send command to send mail. The following message is displayed: The password is incorrect.

Examples of coding and messages appear as follows (although there may be some exceptions, such as when coding is included in a diagram):

MakeDatabase
...
StoreDatabase temp DB32

In examples of coding, an ellipsis (...) indicates that one or more lines of coding are not shown for purposes of brevity.

Conventions in syntax explanations

Syntax definitions appear as follows:

StoreDatabase [temp|perm] (database-name ...)

The following table lists the conventions used in syntax explanations:

Example font or symbol	Convention
StoreDatabase	Code-font characters must be entered exactly as shown.
database-name	This font style marks a placeholder that indicates where appropriate characters are to be entered in an actual command.
SD	Bold code-font characters indicate the abbreviation for a command.
perm	Underlined characters indicate the default value.
[ ]	Square brackets enclose an item or set of items whose specification is optional.
{ }	One of the items enclosed in brackets must be specified.
|	Only one of the options separated by a vertical bar can be specified at the same time.
...	An ellipsis (...) indicates that the item or items enclosed in ( ) or [ ] immediately preceding the ellipsis may be specified as many times as necessary.
()	Parentheses indicate the range of items to which the vertical bar (|) or ellipsis (...) is applicable.
~	The user-specified value preceding the swung dash must be specified in accordance with the attributes following the swung dash.
< >	Angle brackets enclose the syntax element notation for a user-specified value.
<< >>	Double angle brackets enclose the default value assumed by the system when the specification is omitted.
(( ))	Double parentheses enclose the permitted range of values that can be specified.

Syntax element notations

Syntax element notations explain the types of user-specified values.

Syntax element notation	Explanation
alphabetic	Alphabetic characters (A-Z, a-z) and _ (underscore)
alphabetic symbol	Alphabetic characters (A-Z, a-z), #, @, \
alphanumeric	Alphabetic characters and numeric characters (0-9)
alphanumeric symbol	Alphabetic symbols and numeric characters (0-9)
unsigned integer	Numeric characters (0-9)
hexadecimal	Numeric characters (0-9)and A-F (or a-f)
identifier	Alphanumeric character (A-Z, a-z) string beginning with an alphabetic character
symbolic name	Alphanumeric symbol string beginning with an alphabetic symbol
character string	String consisting of any characters
pathname	String consisting of one or more symbolic names, forward slashes (/), periods (.), or backslashes (\)
filename	Character string consisting of alphabetic characters (A-Z, a-z), numeric characters (0-9), a period (.), underscore (_), and the at mark (@) (maximum 30 characters)

Note

Use single-byte characters only. Alphabetic characters are case-sensitive (i.e., lowercase alphabetic characters are distinguished from uppercase alphabetic characters). Path names are also dependent on the operating system being used.

Notations used in calculation formulas

The following notations are used in formulas:

Notation	Explanation
	The resulting value is to be rounded up. Example The result of 34 3 is 12.
	The resulting value is to be rounded off. Example The result of 34 3 is 11.
(nnnn)16	Indicates a hexadecimal number. Example (12AB)16 indicates the hexadecimal value 12AB.

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.

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.

In the Windows version of HiRDB:

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.

3. 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 the UNIX version of HiRDB:

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 5L	/var/adm/ras/syslog
Linux	/var/log/messages

In this manual, the term directory includes both of the Windows terms directory and folder, and path names are delimited by forward slashes (/). If you are using the Windows version of Datareplicator, you must replace instances of the forward slash with the back slash (\).

The HiRDB relational database language described in this manual was developed by adding Hitachi's unique interpretations and specifications to the following standards. Hitachi expresses its appreciation to the developers and acknowledges the sources of these specifications.

HiRDB relational database

JIS	X3005-1997	Database Language SQL
IS	ISO9075-1992	Information processing systems - Database Language SQL
ANS	X3.135-1986	Information system - Database Language SQL