Nonstop Database, HiRDB Version 9 Installation and Design Guide

[Contents][Index][Back][Next]

19.1.1 File sizes required for the execution of the database load utility (pdload)

The following table shows the formulas for determining the file sizes required for the execution of the database load utility (pdload):

File type Formula (bytes)
Input data file h [Figure] b
Index information file

B-tree index:
(d + y) [Figure] (b + e) + 512

Plug-in index:
(12 + q) [Figure] p + 1,024
These formulas are for the size of one index. If there are multiple indexes, determine the size of each index.
Error information file k [Figure] f + s [Figure] 200
Temporary file for creating error information file In the following conditions, the work file output directory will need number of key duplication errors [Figure] 8 + number of errors detected by plug in function [Figure] 200 of space for each server that has a table storage RDAREA. For details about work file output destination directories, see 2.3.2 Creating a work file output directory.
  • For a HiRDB single server configuration, a utility special unit contains the input files.
  • For a HiRDB parallel server configuration, the server that contains the input files is different from the server containing the table storage RDAREAs.
LOB input file

EasyMT used to create the LOB input file:
a
[Figure] (LOB data length + 400)
i=1

LOB input file by column:
b
[Figure] (LOB data length + 4)i
i=1
LOB middle file B
[Figure]{
i=1
c
[Figure] (LOB file name length-ij + 36) + 24} + 1,024 + c [Figure] 84
j = 1
Error data file MIN(f, g) [Figure] h
Process results file 1,500 + number of servers storing table [Figure] 500
Work file# [4 + 2 [Figure] R + 2 [Figure] r + 4 [Figure] I [Figure] R + {b [Figure] (value of past message output interval specified by the -m option)}] [Figure] 200
Work file for sorting

Condition 1:
Size of index information file + 4 [Figure] (b + e)

Condition 2:
{Size of index information file + 4 [Figure] (b + e)} [Figure] 2
  • Condition 1
    When 1,024 (KB) [Figure] E
  • Condition 2
    When 1,024 (KB) < E

E: Buffer size
The buffer size obtained according to 19.1.12 Buffer size used to determine the size of the work file for sorting.

a: Number of input rows [Figure] number of LOB columns

b: Number of input rows (for a repetition column, number of input rows [Figure] number of elements)

c: Number of LOB columns

d: Index key length
See Table 16-5 List of index key lengths. For variable-length data, treat a single column as multicolumn and use the largest defined length.

e: Number of existing rows (for a repetition column, number of existing rows [Figure] number of elements)

f: Number of error data items

g: Number of output rows specified in the errdata operand of the source statement

h: Average source record length

k: If there is a column with an abstract data type, the value is 300; otherwise, it is 120.

m: For a DAT-format file or a binary format file output by pdrorg, the value is 0.
For any other file, the value is (record length of one row in the input file [Figure] 4).

p: If index storage RDAREAs are initialized, the value is (b + e); otherwise, the value is b.

q: Value as follows
  • 27 for the abstract data type stored in the LOB RDAREA
  • Key length + 2 for the abstract data type of a maximum of 255 bytes of definition length
  • 2 for the abstract data type of 256 bytes or more of definition length
Typical abstract data type values are as follows.
  • 27 for the SGMLTEXT type
  • 2 for the FREEWORD, GEOMETRY, and XML types

r: Number of RDAREAs for LOB storage

s: Number of servers

y: If all key component columns are fixed length, the value is 10; if they include a variable length, the value is 12.

I: Number of indexes

R: Number of partitioned index or table RDAREAs

Note
When calculating the size of index information files and sort work files, if the index configuration columns are repetition columns, b and e do not refer to the number of rows but to (number of rows [Figure] number of elements).

#
Output if lvl2 is specified as the information message output suppression level in the -m option.