The RMU Load command accepts the following five types of data
files, all of which, except the security audit journal, have the
file extension .unl:
o Text data file
o Delimited text data file
o Binary data file
o Specially structured file
o OpenVMS security audit journal file
With the exception of the specially structured file and the
security audit journal file, you must provide a record definition
file (.rrd) on the RMU Load command line to load these data
files. The record definition file provides Oracle RMU with a
description of (metadata for) the data you are loading.
The following list describes the additional requirements for
loading each of these types of files:
o Text data file
To load a text data file (.unl), you must specify the Record_
Definition qualifier with the Format=Text option.
The following command loads text data (employees.unl) into
the EMPLOYEES table of the mf_personnel database. The
employees.rrd file provides the record definition for the
data in employees.unl
$ RMU/LOAD/RECORD_DEFINITION=(FILE=employees.rrd, FORMAT=TEXT) -
_$ mf_personnel EMPLOYEES employees.unl
You can generate an appropriate .rrd file for the preceding
example by issuing the following command:
$ RMU/UNLOAD/RECORD_DEFINITION=(FILE=employees.rrd, FORMAT=TEXT) -
_$ mf_personnel EMPLOYEES unload.unl
o Delimited text data files
To load delimited text data files (.unl) you must
specify the Record_Definition qualifier with the with the
Format=Delimited_Text option.
The following command loads delimited text data
(employees.unl) into the EMPLOYEES table of the mf_personnel
database. The employees.rrd file describes the format of
employees.unl
$ RMU/LOAD/RECORD_DEFINITION=(FILE=employees.rrd, -
_$ FORMAT=DELIMITED_TEXT, TERMINATOR="#") -
_$ mf_personnel EMPLOYEES employees.unl
You can generate an appropriate .rrd file for the preceding
example by issuing the following command:
$ RMU/UNLOAD/RECORD_DEFINITION=(FILE=employees.rrd, -
_$ FORMAT=DELIMITED_TEXT) mf_personnel EMPLOYEES unload.unl
o Binary data files
To load binary data files, you must ensure that the records
you load match the record definition in both size and data
type. The records must all have the same length and the data
in each record must fill the entire record. If the last field
is character data and the information is shorter than the
field length, the remainder of the field must be filled with
spaces. You cannot load a field that contains data stored in
packed decimal format.
The following command loads binary data (employees.unl)
into the EMPLOYEES table of the mf_personnel database. The
employees.rrd file describes the format of employees.unl.
$ RMU/LOAD/RECORD_DEFINITION=(FILE=employees.rrd) mf_personnel -
_$ EMPLOYEES employees.unl
You can generate an appropriate .rrd file for the preceding
example by issuing the following command:
$ RMU/UNLOAD/RECORD_DEFINITION=(FILE=employees.rrd) mf_personnel -
_$ EMPLOYEES unload.unl
o Specially structured binary files that include both data and
metadata.
To load the specially structured binary files (created by the
RMU Unload command without the Record_Definition qualifier)
you must specify the file (.unl) created by the RMU Unload
command.
The following command loads the binary data contained in
the employees.unl file into the EMPLOYEES table of the mf_
personnel database. The record definition information is
contained within the binary .unl file.
$ RMU/LOAD MF_PERSONNEL EMPLOYEES employees.unl
This specially structured employees.unl file is created with
the following RMU Unload command:
$ RMU/UNLOAD MF_PERSONNEL EMPLOYEES employees.unl
o Security audit journal files
To load the records from a security audit journal file
maintained by the OpenVMS operating system, you must decide
whether to load records into the same database for which
security audit journal records are being recorded or to load
them into a separate database. In either case you do not
need to specify a record definition file; use of the Audit
qualifier indicates to Oracle RMU that the record definition
is that of the security audit journal file.
The following command loads the records from the security
audit journal file (with a logical name of SECURITY_AUDIT) for
the mf_personnel database into the AUDIT_TABLE table of the
mf_personnel database:
$ RMU/LOAD/AUDIT MF_PERSONNEL.RDB AUDIT_TABLE -
_$ SECURITY_AUDIT
This example loads the records from the security audit journal
file (with a logical name of SECURITY_AUDIT) for the mf_
personnel database into the AUDIT_TABLE table of the audit
database:
$ RMU/LOAD/AUDIT=DATABASE_FILE=MF_PERSONNEL.RDB AUDIT.RDB -
_$ AUDIT_TABLE SECURITY_AUDIT
See the Usage Notes for more detailed information on loading
security audit journal records and the file name of the
security audit journal.
In all cases where you specify a record definition file (.rrd),
the record definition file and the database definition of the
table being loaded must match in the number of specified fields
and the data type of each field. If the data you want to load
has more fields than the database table definition specifies,
you can still load the data, but you must use the FILLER keyword
with the field definition in your .rrd file to represent the
additional field. See Example 15 in the Examples help entry under
this command.
By default, the table specified in the RMU Load command is
reserved for PROTECTED WRITE.
Data Type Conversions Performed by Oracle Rdb shows the data type
conversions that can occur while you are performing a load or
unload operation.
Table 11 Data Type Conversions Performed by Oracle Rdb
Original Data
Type New Data Type
TINYINT INTEGER, QUADWORD, SMALLINT, FLOAT, DOUBLE
PRECISION, VARCHAR, CHAR
SMALLINT INTEGER, QUADWORD, FLOAT, DOUBLE PRECISION,
VARCHAR, CHAR
INTEGER SMALLINT, QUADWORD, FLOAT, DOUBLE PRECISION,
VARCHAR, CHAR
QUADWORD SMALLINT, INTEGER, FLOAT, DOUBLE PRECISION,
VARCHAR, CHAR
FLOAT DOUBLE PRECISION, CHAR, and VARCHAR
DOUBLE FLOAT, CHAR, and VARCHAR
PRECISION
DATE CHAR or VARCHAR
TIME CHAR or VARCHAR
TIMESTAMP CHAR or VARCHAR
INTERVAL CHAR or VARCHAR
CHAR FLOAT, DOUBLE PRECISION, DATE, TIME, TIMESTAMP,
INTERVAL, VARCHAR, SMALLINT, INTEGER, or QUADWORD
See the Oracle Rdb SQL Reference Manual for a description of
these data types.