Kbase 20623: Building Indexes with Binary Load
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/26/2001 |
|
SUMMARY:
This solution discusses the database enhancement to Progress Version 9.1B that allows building indexes with binary load.
EXPLANATION:
Earlier Progress versions required that, upon completion of a binary load, you use the PROUTIL utility with the idxbuild qualifier to rebuild the indexes in the database.
The PROUTIL utility for Version 9.1B can now build indexes during a binary load.
SOLUTION:
Use the following PROUTIL command to perform a binary load (include
the build indexes qualifier to simultaneously build indexes):
proutil db-name -C load file-name [build indexes [ -TB blocksize]
[ -TM n] [ -T dir-name] | [ -SS sort-file-directory-specification]]
Consider the following points when you use the build indexes
qualifier:
- To improve performance, use the Merge Number (-TM) and
Speed Sort (-TB) parameters.
See the section on the PROUTIL utility in the Progress
Database Administration Guide and Reference for additional
information on these parameters.
- If you specify the Sort Directory Specification (-SS)
parameter, PROUTIL does not use the Temporary Directory (-T)
parameter.
PROUTIL uses the (-SS) parameter to identify the location of
a multi-volume sort file specification. This file gives the
directions and the amount of space available in those
directories to create temporary files for sorting.
For example, if a directory has 1,000,000 blocks of free
space available and you are going to run two parallel binary
loads, each binary load should be given a sort file that
specifies the availability of 500,000 blocks in that
directory.
The syntax for a multi volume sort file specification is the
same as that for an index build. See the section on
rebuilding indexes in the Progress Database Administration
Guide and Reference for guidelines regarding the usage of a
multi-volume sort file because they also apply to the binary
load.
- When creating indexes for the table that PROUTIL is loading,
all of the existing indexes are marked as inactive.
Once PROUTIL successfully creates the indexes, they are
marked active. This means that if the binary load is aborted
for any reason, PROUTIL leaves the table with no active
indexes.
- Tables loaded with the build indexes qualifier must be empty.
Reference to Written Documentation:
Progress Database Administration Guide.
Progress Database Administration Reference.