Progress
Database Administration
Guide and Reference


Dumping Table Contents With PROUTIL

Use the following PROUTIL command to perform a binary dump:

proutil db-name -C dump [owner-name.]table-name directory [-index num] 

db-name

Specifies the database from which you want to dump. You must completely define the 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 an 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.

You can use the PROUTIL IDXANALYS utility to help determine what the index number is. For the complete syntax of the PROUTIL IDXANALYS utility, see Database Administration Utilities."

Results Of a Binary Dump With PROUTIL

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, and customer.bd3, each of which is approximately 2GB, and customer.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.

Format Of a Binary Dump File

Each binary dump file contains a header and a description for each record in the table. The dump file appears in the following format:

Header
Record length
Table number
Binary record
Record CRC

The file header contains information that appears in this order:

  1. Version number
  2. Date and time the file was created
  3. Name of the table being dumped
  4. Number of the table being dumped
  5. CRC of the table being dumped
  6. Number of fields in the table
  7. Name of the database where the table resides
  8. Section number
  9. Number of the first record
  10. Table owner

Section numbers that appear in the file header correspond to a binary dump file created by PROUTIL DUMP when the table was larger than the UNIX 2GB file size limitation. (See the "Results Of a Binary Dump With PROUTIL" section.) For example, Section 1 corresponds to the binary dump file named customer.bd, Section 2 corresponds to customer.bd2, Section 3 corresponds to customer.bd3, and Section 4 corresponds to the customer.bd4 binary dump file.

NOTE: To support the dump and load of binary large objects (BLOBS), PROUTIL DUMP adds more items to the header of the binary dump file.


Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095