Scalable Database Server, HiRDB Version 8 Command Reference
The unload statement specifies information about an unload data file.
unload {[server-name:]
unload-data-file-name[,unload-data-file-name]...
|(uoc)}
[HiRDB-file-information]
[uoc-information]
|
<identifier> ((1-8))
Specifies the name of the server used to create the unload data file.
<pathname>
Specifies the absolute path name of the unload data file.
If you have specified a HiRDB file as the unload data file type in the -f option, specify the unload data file name as follows:
You can also use the tape device access facility for unload data files. For details about the tape device access facility, see 1.4.3 Tape device access facility.
Specify this option when you use a UOC to reorganize the database or to create a UOC data file (when the unload data file is not output by pdrorg).
(uoc) is applicable only to -k unld.
[init={initial-allocation-size
|(initial-allocation-size[,initial-allocation-size]...)}]
[,incr=secondary-allocation-size
|(secondary-allocation-size[,secondary-allocation-size]...)}
|
Specify this operand if the unload data file is a HiRDB file. Be sure to specify the HiRDB file information on a single line.
If you omit init, do not specify a comma (,) before incr.
| Condition | Resolution |
|---|---|
| Number of files < number of initial allocation specifications | As many initial allocation specifications are valid as there are files, and subsequent initial allocation specifications are ignored. |
| Number of files = number of initial allocation specifications | Specification for each file is valid. |
| Number of files > number of initial allocation specifications | The last initial allocation specification is assigned to all the remaining files. |
incr=secondary-allocation-size| (secondary-allocation-size[,secondary-allocation-size]...)} <unsigned integer> ((1-1048574)) <<10>>
Specifies the size of the extension area when the initial allocation size is not sufficient during a write operation on the HiRDB file.
The utility does not expand the HiRDB file in the following cases:
If the actual size exceeds the estimated size, specify the secondary allocation size in such a manner that neither of the previous attempts is made. Figure 8-17 shows limitations to the secondary allocation size. Specify the value of n so that the above two attempts are avoided.
Figure 8-17 Limitations to the secondary allocation size (unload statement)
When creating a new HiRDB file system area, you can specify the number of secondary allocations in the -e option of the pdfmkfs command. For an existing HiRDB file system area, check the value of available expand count in the pdfstatfs command output result.
[uoc_lib=library-name[param='user-parameters']
Specify UOC information when you use a UOC to reorganize the database. When specifying the unlduoc statement, make sure that UOC information is also specified (if it is omitted, an error results).
All Rights Reserved. Copyright (C) 2007, Hitachi, Ltd.