Load

Use the Load Process to transform the contents of an Archive or Extract File into a format that is appropriate for a particular DBMS loader and then, if desired, start the corresponding database load utility.

The Load Process generates a data file in the correct format for each table in the Archive or Extract File and an SQL file or a BAT file (Batch Execution), depending on the DBMS, that contains the syntax necessary to start the database loader.

Specifications for the Load Process are embodied in a Load Request, which may be named and saved in the Optim™ Directory, so that it is available for a variety of users and uses. A Load Request may also be embedded in a Restore Request, in which case it is not named and is not accessible except by editing or using the Restore Request. The Load Request provides parameters used to prepare data for a DBMS loader and the instructions required to process the load. Specify a Table Map in the Load Request to map the destination for the data to load. Use optional Column Maps to transform data before loading. For more details, refer to the Common Elements Manual .

Load versus Insert

Archive can move data into a database using a Load Process or an Insert Process. For details on using a particular DBMS loader, please refer to the documentation provided with your database management system and consider the following when deciding the best method:

Process File Names

The Load Process generates several types of files to support the database utility load process:

Note: If your file server does not allow for file names greater than 8 characters, the Load Process will fail to process a Source File with a long name. Avoid using long file names for Archive or Extract Files or copy and rename a file before you use it for a Load Process.

Run Online or Automate

You can process a Load Request immediately (by clicking File > Run). You can also run a Load Request from the command line, whether manually, in batch, or from an external application. When running a process from the command line, you can supply overrides for various Load Request parameters and settings to tailor the process to circumstances as they exist at runtime. (See Command Line Interface — Processing Utilities for more information.) Named Load Requests can also be scheduled for automated processing by clicking File > Schedule.

Note: You must have authority from the SYSADM or DBA to run or schedule the Load Process.

You can also direct the Load Process to generate the necessary files immediately, but defer running the database load utility. If you choose not to start the database load utility as part of the Load Request, the loader must be started manually.

A Load Request can also be run as part of a Restore Request. See Restore.

Naming Conventions

The fully qualified name of a Load Request is in the form identifier.name.

identifier
Identifier that serves as the prefix for the request name (1 to 8 characters).
name
Name assigned to the request (1 to 12 characters).

When you create Load Requests, it is helpful to use a logical set of naming conventions to identify the use for each and to organize them for easy access.

Section Contents

This section explains how to create and maintain a Load Request, including how to: