All HiRDB utilities use files as I/O files unless otherwise specified; the file mode is single-file, single-volume (utilities cannot handle any file larger than 263 bytes). Files on a network drive cannot be used as I/O files for utilities. Use files on local drives.
Some utilities can handle file modes other than single-file, single-volume. The table below lists the utilities that can handle I/O files other than single-file, single-volume files.
Table 1-3 Utilities that can handle I/O files other than single-file, single-volume files
Utility | File type | Single-file, multi-volume regular files | Tape device | HiRDB files |
---|---|---|---|---|
Database load utility (pdload) | Input data files, LOB input files, LOB input files by column | C | V# | N |
Database reorganization utility (pdrorg) | Unload data files, LOB data unload files | C# | C -f hirdb | |
Database copy utility (pdcopy) | Backup files | C -k i | ||
Database recovery utility (pdrstr) | ||||
Dictionary import/export utility (pdexp) | Export files | N | N |
The table below lists the tape devices supported by the utilities.
Table 1-4 Tape devices supported by the utilities
Device name | Direct input/output by the utilities |
---|---|
CMT | N |
DAT | Y |
OMT | N |
CGMT | N |
8mm | N |
DLT | Y |
LTO | Y |
When the utilities access the tape device for direct input/output, they assume a single volume and access the device as a single tape drive. They do not provide Autoloader or Tape Library control.
We recommend that you use the tape device in the variable-length blocked mode.
You can reduce the number of input/output operations in the variable-length blocked mode, in which the utilities input/output data in units of 32 kilobytes while they input/output data in units of 512 bytes in the fixed-length blocked mode. When using the fixed-length blocked mode, make sure that the block size is 512 bytes.
For details about each tape device, see the applicable OS manual.
If you use a tape device with pdrorg, pdload, or pdrstr, do not specify the device driver's minor number in such a manner that the tape will not be rewound during close processing. If you execute the utility without rewinding the tape, you must rewind the tape using a command such as mt (magnetic tape manipulation program) after the utility has terminated.
To save multiple backups on the same medium, use the utility to output the backups to files and then copy them onto the desired medium.
To use a HiRDB file as an I/O file, a HiRDB file system must first be created with the pdfmkfs command in which -k UTL is specified, and the appropriate option shown in Table 1-3 must be specified when the HiRDB utility is executed.
HiRDB utilities use HiRDB files in the following modes:
For details about HiRDB files, see the HiRDB Version 9 Installation and Design Guide.