There are two basic ways you can load data online into partitions of a table:

  • Using the Database Administration Console
  • Using binary load

If you can use binary load, you can load new data into multiple partitions in parallel.

Load new data using Database Administration Console

If the data for a partitioned table resides in a .d file that has the same name as the table, you can use the Database Administration Console to load the data online. Whether the data must be loaded into one or multiple partitions, OpenEdge automatically examines and loads the data into the appropriate partitions.

Follow these steps to load new data using the Database Administration Console:
  1. From the Data Administration section, click Load table contents (.d file).
  2. In the Load root directory field, specify the directory where the .d file resides.
  3. To import LOB data, select the Include LOB check box. If not, clear the check box.
  4. If you select the Include LOB check box, specify a LOB subfolder. By default, lobs is specified.
  5. In the Acceptable error percentage field, specify an error percentage. The default value is 0.
  6. Select the Skip secured tables check box if you do not want to load secured tables; that is, tables that are encrypted with OpenEdge Transparent Data Encryption (TDE).
  7. Select the Skip missing directories check box if you do not want to validate missing sub-directories under the root directory.
  8. In the Tables field, click All or Selected.
    • If you click All, skip to Step 11.
    • If you click Selected, the Selected Tables section appears, letting you search for tables by table name or by storage area.
  9. Specify your search criteria and click Apply Filter.
  10. Select or clear the tables as required.
  11. Click Load.

    The Confirm task for table data load dialog box appears.

  12. Click Commit & Monitor to perform and monitor the load.

    The Database Connection Details page displays three sections: Load Table Data Summary, File System Status, and Monitor Database Table Load.

  13. Look at the Load Table Data Summary and Monitor Database Table Load sections.

    The Load Table Data Summary section should show complete progress, and the Monitor Database Table Load section should show the number of rows loaded into each table.

  14. If there are errors, you will see one or more media/image22.png (information) icons and a message such as Errors/Warnings listed in .e files placed into same directory as .d files. Open the .e files, review the error messages, and troubleshoot the problem. When you finish, delete the .e files.

Load new data using binary load

You use the PROUTIL LOAD utility to binary-load data from a .bd file into a partition. Whether the .bd file contains data for one or multiple partitions, the utility examines and loads relevant data into the intended target partition. Remember that you will also have to build the local indexes associated with the partition.

To achieve the benefit of parallel loading, you can binary-load data into multiple partitions of the same table at the same time.

The command to binary-load data online into a specific partition is:

proutil db-name -C load file-name [partition partition-name] [build indexes]
Note:
  • If you use the partition parameter, the utility loads all records that belong to a partition into that partition. All other records are skipped and their number reported at the end. Use this method to load data into a specific partition.
  • If you do not use the partition parameter, the utility loads records into all relevant partitions. All other records are skipped and their number reported at the end. Use this method to migrate data from a non-partitioned table to a partitioned table or to load data to all partitions from a .bd file that was dumped from all partitions of a partitioned table.
  • If you use both the partition and build indexes parameters, all local indexes associated with the partition are rebuilt. Note that the partition must be empty prior to the build.
  • If you do not use the partition parameter but use the build indexes parameter, all global indexes and local index partitions are rebuilt.

Suppose the Order table has 12 partitions including Order-1, Order-2, and Order-3, and all the partitions are empty. And suppose we have a .bd file, order.bd, that contains data for all the partitions.

Here is an example of three PROUTIL LOAD commands to binary-load data into the three partitions and to build indexes online in parallel. To run them in parallel, we have to execute each command in a separate Proenv window. Note that the data for the other partitions will be skipped.

proutil sportsco -C load order.bd partition order-1 build indexes
proutil sportsco -C load order.bd partition order-2 build indexes
proutil sportsco -C load order.bd partition order-3 build indexes