Progress
Database Administration
Guide and Reference
PROUTIL DUMP Qualifier
Performs a binary dump of a database table to a file. PROUTIL DUMP writes data from a table to a dump file. When the procedure finishes, it reports the number of records written to the dump file.
SYNTAX
Operating System Syntax UNIXWindows proutil db-name -C dump [ owner-name.]table-name directory[ -index num ]
db-name
Specifies the database where the dump will occur. If the database is not within the current working directory, you need to define the complete path.
owner-name
Specifies the owner of the table containing the data you want to dump. You must specify an owner name unless the table’s name is unique within the database, or the table is owned by “PUB.” By default, Progress 4GL tables are owned by PUB.
table-name
Specifies the name of the table containing the data you want to dump.
directory
Specifies the name of the target directory where the data will be dumped.
-index num
Specifies the index to use to dump the table’s contents. If you choose not to use this option, the command uses the primary index to dump the table.
NOTES
- See "Dumping and Loading," for more information about the DUMP 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.
- PROUTIL DUMP writes data from a table to a dump file. The name of the resulting dump file depends on the owner of the table. By default, Progress 4GL tables are owned by “PUB.” When tables owned by PUB are dumped to a file, the filename is the table name with
.bd
appended. For example, tablename.bd
.However, when tables owned by anyone other than PUB are dumped to a file, the resulting filename contains the owner name and table name. For example, ownername_tablename
.bd
- 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.
- PROUTIL DUMP supports dumping binary large objects (BLOBS).
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |