Progress
Database Administration
Guide and Reference
PROUTIL LOAD Qualifier
Performs a binary load of database contents.
SYNTAX
Operating System Syntax UNIXWindows proutil db-name -C load filename [build indexes
[-TB
blocksize] [-TM
n] [-T
dir-name] | [-SS
sort-file-directory-specification]]
db-name
Specifies the database where you want to load the data. You must completely define the path.
filename
Specifies the binary dump file that you want to load. You must completely define the path.
build indexes
Indicates that PROUITL LOAD will simultaneously build the indexes and perform the load.
-TB
nSpecifies that the index rebuild will be performed using Speed Sort. n indicates the allocated block size, in kilobytes. For more information on the Speed Sort (
-TB
) parameter, see the Progress Startup Command and Parameter Reference .
-TM
nSpecifies the merge number. n indicates the number of blocks or streams to be merged during the sort process. For more information on the Merge Number (
-TM
) parameter, see the Progress Startup Command and Parameter Reference .
-
T
dir-nameSpecifies the name of the directory in which the temporary files are stored. If you do not use this parameter, PROUTIL places temporary files in the current working directory. For more information about the Temporary Directory (
-T
) parameter, see the Progress Startup Command and Parameter Reference .
-SS
sort-file-directory-specificationIdentifies the location of a multi-volume sort file specification. If you use the Sort Directory Specification (
-SS
) parameter, PROUTIL does not use the Temporary Directory (-T
) parameter.NOTES
- See "Dumping and Loading," for more information about the LOAD qualifier.
- The PROUTIL DUMP and LOAD utilities use cyclic redundancy check (CRC) values to establish the criteria for loading.
The Progress database provides a flexible storage architecture and the ability to relocate objects, such as tables and indexes, while the database remains online. As a result, when you perform a binary load operation, the table numbers in a binary dump file might not match the table numbers in the target database. Therefore, when you perform a binary load operation, the criteria for loading tables is based solely on cyclic redundancy check (CRC) values, and not table numbers.
For example, when you dump a table, the PROUTIL utility calculates a CRC value for the table and stores it in the header of the binary dump file. When you load the table, PROUTIL matches the CRC value stored in the header with the CRC value of the target table. The values must match or the load is rejected.
You can load a binary dump file created with a previous version of the PROUTIL DUMP utility, because the current version of PROUTIL LOAD uses the CRC value established when the file was originally dumped. Consequently, the Progress database maintains backwards compatibility.
However, you cannot use a previous version (Version 8.3 or earlier) of the PROUTIL LOAD utility to load a binary dump file created using the current version (Version 9.0 or later) of the PROUTIL DUMP utility. The previous versions of PROUTIL DUMP and LOAD did not use CRC values to establish the criteria for loading, but instead used other mechanisms, such as:
- Looking up table RecIDs in a target database using the table number stored in the header of the binary dump file.
- Matching table numbers in the header of the binary dump file with table numbers in a target database.
- Comparing the number of fields in the binary dump file with the number of fields in the target database.
- On UNIX systems that have a 2GB file size limitation (Alpha OSF does not), PROUTIL DUMP creates multiple files when you dump a table larger than 2GB. For example, when you dump data from a table with the name “customer” that is 6.4GB, PROUTIL DUMP creates four binary dump files:
customer.bd
,customer.bd2
, andcustomer.bd3
, each of which is approximately 2GB, andcustomer.bd4
, which is approximately 0.4GB. The PROUTIL DUMP procedure adds header blocks to the binary dump files. As a result, the total size of the binary dump files is slightly larger than the table itself.On Windows NT and Alpha OSF, however, there is no 2GB file size limitation. On Windows NT and Alpha OSF, PROUTIL DUMP creates only one binary dump file regardless of the size of the table.
To load multiple binary dump files into the target database, specify each file individually. For example:
- PROUTIL LOAD supports loading binary large objects (BLOBS).
- When using PROUTIL LOAD with the BUILD INDEXES qualifier, PROUTIL marks the existing indexes as inactive. Once PROUTIL successfully creates the indexes, it marks the indexes 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.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |