Load Process

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 specified, 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.

A Load Request contains the 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 in the Load Request to transform data before loading. For details, see the Common Elements Manual.

Data to be loaded must be contained in an Archive or Extract File. You can use the Archive or Extract Process to create the corresponding file, or use an existing Archive or Extract File. See Extract Process, or see the Archive User Manual.

Load versus Insert

Optim™ can move data into a database in two ways — using a Load Process or an Insert Process. Consider the following when deciding which method to use:

Process File Names

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

Note: If your file server does not allow long file names of greater than 8 characters and the Archive or Extract File has a long name, the Load Process will fail. The best solution is to avoid using long file names for Archive or Extract Files. If needed, you can copy and rename a file before you use it for a Load Process.

Run or Schedule

You can process a Load Request immediately by clicking File > Run, or you can save and schedule the request for processing at a later time by clicking File > Schedule. You must save the request before it is scheduled, but it is not necessary to save the request before it is run.

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.

Note: You cannot start the database load utility from within Optim using a previously created set of SQL statements.

Naming Conventions

The fully qualified name of a Load Request consists of: 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.

Chapter Contents

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

Note: For details on using a particular DBMS loader, refer to the documentation provided with your DBMS.