The restore process obtains data from a source (one or more archive files) and copies that data to a destination (one or more tables in a database).
To restore archived data, you must create a restore request. Using the Restore request, you can select data from one or more archive files and restore it to the original or a different database. Because the object definitions are included in the archive file, you can also clone the original database if desired. You can process the restore request immediately or use it as a template for application-generated jobs run from the command line, using overrides as appropriate. A restore request can also be scheduled, if circumstances warrant.
Use the Restore Request Editor to define parameters in a restore request. These parameters include the name or names of source archive files, criteria for the data to be restored, the type of process (load or insert) used to restore the data, and insert or load requests that can be used to restore the data.
Considerations that apply when deciding the method used to restore archived data include: the volume of data, the number of rows to be restored, the need for user access during a restore process, and the need to replace rows and insert rows in one step.
Use the Insert Request Editor to define parameters in an insert request or use the Load Request Editor to define parameters in a load request. Among other parameters, an insert or a load request includes:
A control file records information about the success or failure of insert or load processing for each selected row in the archive file. You must specify the name of a control file when you create the insert or load request. Diagnostics identify why any discarded rows were not processed.
A table map matches tables in the restored archive file to tables in the destination database. Individual tables can be excluded and tables with different names can be mapped. You can use an existing table map or define the table map as part of the insert or load request specifications.