PROUTIL DUMP writes data from a table to a dump file or files. The name of the resulting dump files depends on the owner of the table. When tables owned by PUB are dumped to a single 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 systems that have a 2GB file size limitation, a single-threaded 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 systems without file size limitation, a single-threaded PROUTIL DUMP creates only one binary dump file regardless of the size of the table.

Multi-threaded PROUTIL DUMP creates a file for each thread created. The first thread creates the file, tablename.bd; the second thread creates the file tablename.bd2; each additional thread creates a file with an incremental number, tablename.bdn. Use the -dumpfile option to generate a list of the files created by the threaded dump. The file specified by the -dumpfile option contains a list of fully qualified file names, and can be used as input to PROUTIL LOAD. If the file specified by the -dumpfile option exists, PROUTIL DUMP will overwrite the existing file.