Use an Insert Process to insert data from an Archive File or Extract File into a destination database.
If the file contains data from tables that do not exist at the destination, the Insert Process uses object definitions in the file to create the tables. Specifications for the Insert Process are embodied in an Insert Request, which may be named and saved in the Optim™ Directory, so that it is available for a variety of users and uses. An Insert 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. (See Restore.) Based on your specifications, you can:
You must use a Table Map to identify the destination tables for data in the Archive or Extract File. You may also use Column Maps to control or transform the data inserted in destination columns.
Archive can move data into a database by using an Insert Process or a Load Process. Consider the following when deciding the best method:
You can process an Insert Request immediately (by clicking ). You can also run an Insert 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 Insert 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 Insert Requests can also be scheduled for automated processing by clicking .
The fully qualified name of an Insert Request is in the form: identifier.name.
When you create Insert 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.
This section explains how to create, maintain, and process Insert Requests, including how to: