Release 10.1A: OpenEdge Data Management:
Database Administration

> ## Loading table contents in binary format with PROUTIL

> Use the following syntax to perform a binary load:

>      proutil db-name -C load [ filename | -dumplist dumpfile ]

> In the syntax, `db-name` specifies the database where you want to load the data. To load one file, specify `filename`; to load multiple binary dump files, specify -dumplist `dumpfile` where `dumpfile` contains a list of binary dump files. You can chose to build indexes on your data as it loads with the `build indexes` parameter. For complete syntax details, see the "PROUTIL LOAD qualifier" section.

> When specifying multiple files to load, you can use a dump file created with a multi-threaded binary dump, or create your own. A dump file contains a list of fully qualified file names of binary dump files. This example shows the contents of the file `order.dmp_lst`:

>     /usr1/docsample/101A/bindump/order.bd
>     /usr1/docsample/101A/bindump/order.bd2
>     /usr1/docsample/101A/bindump/order.bd3
>     /usr1/docsample/101A/bindump/order.bd4
>     /usr1/docsample/101A/bindump/order.bd5
>     /usr1/docsample/101A/bindump/order.bd6

> To load all the files listed in `order.dmp_lst` into a database named `newdb`, issue the following command:

>     proutil newdb -C load -dumplist order.dmp_lst

> Using the `-dumplist` parameter is the equivalent of issuing 6 individual load commands:

>      proutil newdb -C load /usr1/docsample/101A/bindump/order.bd
>      proutil newdb -C load /usr1/docsample/101A/bindump/order.bd2
>      proutil newdb -C load /usr1/docsample/101A/bindump/order.bd3
>      proutil newdb -C load /usr1/docsample/101A/bindump/order.bd4
>      proutil newdb -C load /usr1/docsample/101A/bindump/order.bd5
>      proutil newdb -C load /usr1/docsample/101A/bindump/order.bd6

> When the load procedure finishes, it reports the number of records that were loaded.

> ##### Recovering from an aborted binary load

> The procedure to recover from an aborted binary load depends on how much the binary load completed before the abort. If the binary load got all the rows loaded and aborted during the sort phase, then recovery entails running the index rebuild utility on the affected table. If the binary load aborted during the load of the rows into the database, there is a separate procedure for recovery.

> | To recover from a binary load that aborted during the loading of rows:

> 1. Truncate the storage area.

> 2. Restart the load operation.

> You can find out what phase the binary load completed by examining the database log (`.lg`) file. In this file, you will see messages identifying the major phases of the load operation, such as:

> - Binary load session started.

> - Record load phase started.

> - Record load phase completed.

> - Starting index build phase.

> - Index build phase completed.

> - Binary load session ended.

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