(a) server-name

<identifier> ((1-8))

Specifies the name of the server used to create the LOB data unload file.

HiRDB/Single Server

Do not specify this option for a HiRDB/Single Server.

HiRDB/Parallel Server

When reorganizing multiple LOB columns of a row-partitioned table, specify the name of the server used to create the LOB data unload file. When reorganizing a row-partitioned table in units of RDAREAs or reorganizing a non-partitioned table, there is no need to specify this option.

When unloading to a single LOB data unload file specifying the -g option, specify the name of the server used to create the LOB data unload file.

(b) LOB-data-unload-filename

<pathname>

Specifies the absolute path name of the LOB data unload file.

If you have specified a HiRDB file as the type of LOB data unload file in the -f option, specify the LOB data unload file name as follows:

Rules applicable when the LOB data unload file is a HiRDB file:

• Express the name of the LOB data unload file as 1 to 167 characters.
• To use a HiRDB file, the HiRDB file system area must have already been created by the pdfmkfs command. In this case, specify UTL as the usage purpose in the -k option of the pdfmkfs command.
• An error results if the HiRDB file specified is in the HiRDB file system area that was created by the pdfmkfs command specifying a value other than UTL in the -k option.
• If the HiRDB specified file name is not found in the HiRDB file system area, pdrorg creates a new HiRDB file. If you specify the name of an existing HiRDB file, the utility overwrites the file.

You can also use the tape device access facility for LOB data unload files. For details about the tape device access facility, see 1.4.3 Tape device access facility.

Note about LOB data unload files

1. If there is too much table data to fit in one LOB data unload file, you can specify multiple files.

(c) HiRDB-file-information

 
[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 LOB data unload 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.

init={initial-allocation-size| (initial-allocation-size[,initial-allocation-size]...)} <unsigned integer> ((1-1048574)) <<100>>

Specify in MB the size of the area to be allocated to write to the HiRDB file.

Estimation formula:

For details about determining the initial allocation size, see the section in the HiRDB Version 8 Installation and Design Guide that describes the file size during execution of the database reorganization utility (pdrorg). Obtain the size of the LOB data unload file in bytes, then use the following formula:

Initial allocation size = (size of LOB data unload file in bytes + 1024) (1024 1024) (MB)

Rules

1. The initial allocation size must be smaller than the value specified in the -n option when the HiRDB file system area was created with the pdfmkfs command (because the system requires an area for management purposes).
2. Be sure to specify a nonzero value in the -e option of the pdfmkfs command. Otherwise, the secondary allocation is not possible.
3. Use the pdfstatfs command to determine the permitted of initial allocation size.
4. Specify as many allocation sizes as there are files specified in the lobunld statement. The system resolves a mismatch between the number of initial allocation sizes and the number of file names as follows:
   

   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:

• Attempt to expand the corresponding HiRDB file system area will exceed the specified number of extensions.
• Attempt to expand the corresponding HiRDB file will exceed the maximum number of extensions for individual HiRDB files (23 times).

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-18 shows limitations to the secondary allocation size. Specify the value of n so that the above two attempts are avoided.

Figure 8-18 Limitations to the secondary allocation size (lobunld 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.