Specifies the database where you want to load the data. You must completely define the path.
filename
Specifies a single binary dump file that you want to load. You must completely define the path.
tenant tenant-name
Specifies that the LOAD operation is to be performed only on the table partitions of tenant-name. If tenant-name is not a valid tenant, LOAD exits with an error. Specifying tenant is only allowed on databases enabled for multi-tenancy.
group group-name
Specifies that the LOAD operation is to be performed only on the table partitions of group-name. If group-name is not a valid group, LOAD exits with an error. Specifying group is only allowed on databases enabled for multi-tenancy.
partition partition-name
Specifies that the LOAD operation is to be performed only for the table partition partition-name. If partition-name is not valid, LOAD exits with an error. Specifying partition is only allowed on databases enabled for table partitioning.
composite initial
Specifies that the LOAD operation is to be performed into the composite initial partition of a database enabled for table partitioning.
build indexes
Indicates that PROUTIL LOAD will simultaneously build the indexes and perform the load, if the table or partition (for a multi-tenant or partitioned table) is empty prior to the start of the load.
If tenant, group, partition, or composite initial is specified, build indexes only builds the index for the specified partition. For partition and composite initial global indexes are not deactivated during the load.
For a partitioned database when partition or composite initial is not specified, global indexes are deactivated and rebuilt during the load.
refresh n
Specifies the frequency in seconds to update the display of clients that are blocking the build of an index. The default refresh rate is 60 seconds.You can set it as high as 300 seconds. Connected clients with a schema timestamp earlier than the index's schema timestamp will prevent LOAD from building the index until they are disconnected, unless Database Client Notification is enabled (see notes).
-dumplist dumpfile
Specifies a file containing a list of fully qualified binary dump files to load. Use the file created by PROUTIL DUMP, or create one. For more information on dump files, see Loading table contents in binary format with PROUTIL.
-TB blocksize
Specifies that the index rebuild will be performed using Speed Sort. blocksize indicates the allocated block size, in kilobytes.
-TM n
Specifies the merge number. n indicates the number of blocks or streams to be merged during the sort process.
-T dir-name
Specifies 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.
-SS sort-file-directory-specification
Identifies 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.
-Cipher 6
For an Enterprise database enabled for Transparent Data Encryption, specify -Cipher 6 to indicate that the contents of the dump file being loaded is encrypted. You are prompted to enter the passphrase that was specified when the dump file was created.
The PROUTIL DUMP and LOAD utilities use cyclic redundancy check (CRC) values to establish the criteria for loading.
The OpenEdge 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 binary dump files 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 OpenEdge database maintains backwards compatibility.
However, you cannot use PROUTIL LOAD from Version 8.3 or earlier to load a binary dump file created using the Version 9.0 or later of the PROUTIL DUMP utility. The earlier 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 LOAD supports loading binary large objects (BLOBS).
When using PROUTIL LOAD with the Build Indexes option, 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 option must be empty.
When using PROUTIL LOAD with the Build Indexes option, if clients with an earlier schema timestamp than the index are connected to the database, there are two possible outcomes:
For OpenEdge Release 11.7 and later, if you have enabled Database Client Notification (-usernotifytime), PROUTIL LOAD waits until all connected clients respond to the notification, and then proceeds.
For releases prior to Release 11.7, or if you have not enabled Database Client Notification (-usernotifytime 0), you may wait for those clients to disconnect, or SQL clients to start a new transaction, or forcibly disconnect them with PROSHUT. PROUTIL LOAD can not complete and build and activate the index until the clients with an earlier schema timestamp are disconnected from the database.
You cannot use LOAD to load protected audit data. For more information on auditing and utility security and restrictions, see Auditing impact on database utilities
If the contents of the binary dump file was encrypted with -Cipher 6 when created, you must specify -Cipher 6 for PROUTIL LOAD to indicate that the file is encrypted. You are prompted to enter the passphrase entered when the file was created. You cannot load the contents without the passphrase.
When loading the contents of an encrypted binary dump file, the loaded records are not encrypted unless there is an active encryption policy on the table before the load begins. See PROUTILEPOLICY MANAGE qualifier or Transparent Data Encryptionfor more information on creating an encryption policy.
The keywords tenant, group, partition and composite initial are mutually exclusive.
You cannot specify the composite initial partition with the partition qualifier.
If a table partition is specified, and the LOAD operation encounters records that do not belong to the partition, they are skipped. The number of skipped records is reported at the end of the load. Index keys are added to the global indexes if build indexes is not specified.
If the LOAD operation is loading a partitioned table, records are loaded into the proper partitions according to the partition definition. Index keys are added to the global indexes if build indexes is not specified. If build indexes is specified, both local partition indexes and the global indexes are rebuilt.
If db-name is a UTF-8 database, you must specify -cpinternal UTF-8 on the command line. If not specified, an error message is generated and LOAD exits.
See Dumping andLoading for more information about the LOAD qualifier.