Restart File for Export or Import
Definition
The restart file contains the scripts that are processed during an export or an import with the Oracle database. The scripts can include the following:
alt<TSP>.sql, exp<TSP>.sh, exc<TSP>.sh, tab<TSP>.sql, imp<TSP>.sh, imc<TSP>.sh, ind<TSP>.sql, con<TSP>.sql, grants.sql, cssvg<DBSID>.sql, imx<TSP>.sh.
Structure
Restart files are named as follows:
<SAPDATA_HOME>/sapreorg/<timestamp>/restart.<ext>
.The extension
<ext> shows the SAPDBA function that the scripts in this file were written for.Restart File Extensions for an Export or an Import
Extension |
Meaning |
exd |
Export/import of tables with indexes and data |
exs |
Export/import of tables and index definitions (structure export) |
exg |
Export/import of constraints, synonyms, sequences, views and grants (structure export) |
These extensions are identical with those of the corresponding export log:
<SAPDATA_HOME>/sapreorg/<timestamp>.<ext>
.Logs with the following extensions are also created during the import:
Log File Extensions for an Import
Extension |
Meaning |
imd |
Log for importing tables with indexes and data |
ims |
Log for structure import (table and index definitions, constraints, synonyms, sequences, views and grants) |
For more information on the scripts used by SAPDBA, see
SAPDBA Scripts and Files.Use
Script Indicators
When you start the respective operation (that is, an export or import), the scripts in the restart file are processed one by one. The flag by each script tells you whether the script was processed successfully or not. The following flags for the scripts in the restart file are possible:
Script Indicators in the Restart Files for Export or Import
Script |
Meaning |
Y |
Script processed successfully |
N |
Script not yet processed or incorrectly processed. Before the export is started, all scripts either have this indicator or the indicator I. |
I |
Script is only processed for the import, not during the export. When the import is started for the very first time, these scripts are automatically marked with N by SAPDBA so that they can be included in the process (this only applies to a data import, and not to a structure import). |
S |
The data import was already started, but could not be correctly terminated due to an external error (such as a power failure, or termination by a kill command). Scripts marked with S are automatically processed again when there is a restart. |
Scripts marked with N are always processed during an export/import and are assigned the indicator Y after the process has been finished successfully. The import shell scripts are assigned the indicator S during the import.
All tables belonging to the script indicated with S are deleted before a restart of the Oracle import.
During an export, all necessary import scripts are created and included in the corresponding restart file (file extension
exd , exs , or exg ). However, the respective import scripts are marked with I and are, therefore, not processed during the export. The indicator is not changed to N until the import process is started, so that SAPDBA includes these scripts in the process.
Do not change the sequence of the scripts in the restart file. This defines the flow of the corresponding export or import operations.
In contrast to a reorganization, the command
This means that indicator Y has to be reset to N manually in the restart file for scripts
tab<TSP>.sql before a data import is restarted.It is no longer necessary to manually delete the incompletely imported tables as in earlier SAPDBA versions (up to and including 3.0C).