Use a load request in an Optim™ interoperability service that will load data. You can also export the request to an Optim directory.
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.
The load process generates the following types of files to support the database utility load process:
Additionally, a format file is generated for each data file. A format file has the same name as the corresponding data file, except that the file name extension is different. If there are less than 500 tables to load, the format file name extension is 500 greater numerically than the data file name extension. (For example, if there are three data files named demo.001, demo.002, and demo.003, the corresponding format files are named demo.501, demo.502 and demo.503, respectively.) If there are more than five hundred tables, a more complex file extension generation algorithm is employed.