
Restarting an Export or Import
Use
You can restart an export or import with SAPDBA for Oracle:
- If the export or import failed due to a problem in the export or import phase, but not if the failure was in the preparatory phase (that is, when scripts are created). You can restart from the point of failure.
- If you stopped the export or import after the preparatory phase because you wanted to restart it later
You can use SAPDBA for Oracle to restart any of the following procedures:
Exporting Tables and Indexes Including Data
Exporting Structures of Tables and Indexes
Exporting Constraints, Synonyms, Sequences, Views, and Grants
Importing Tables and Indexes Including Data
Importing Structures
Prerequisites
You have configured and started SAPDBA. Refer to
Getting Started with SAPDBA.
You have completed the
Preparations for Export and Import.
If you are exporting or importing tables and indexes including data, you have
shut down the Oracle database and then
started it in restricted session mode.
SAPDBA logs the import in the
<timestamp>.imd
file. For more information, see
SAPDBA Log Files and Their Contents.
You have identified the:
- Log written by SAPDBA during the export or import
You can use SAPDBA to do this as described in "Procedure" below or find it yourself on disk as follows (these are default locations):
<SAPDATA_HOME>/sapreorg/<timestamp>.<extension>
Windows:
<SAPDATA_HOME>\sapreorg\<timestamp>.<extension>
See the example below. To find the name of the extension, refer to the documentation for the procedure that you want to restart. You can also find this information in
SAPDBA Scripts and Files.
Restart file for export or import in the
sapreorg
subdirectory
<timestamp>
, which also contains the SQL scripts for the restart

The log
0011281141.exd
refers to an export of tables and indexes including data on 28
th November 2000 at 11:41. In this example on a UNIX system, you can find the restart file
restart.exd
and scripts in the directory
<SAPDATA_HOME>/sapreorg/012281141
.
Always make sure you have found the correct log and restart file before restarting an export or import.
Procedure
If the export or import failed, identify and fix the error, using the log described above in "Prerequisites". To do this with SAPDBA:
- Choose Show/Cleanup
®
Show log files/profiles
®
SAPDBA log files.
Select the log
<timestamp>.<extension>
written during the operation that failed, and examine it to find the cause of the error.
If required, find the restart file
restart.<extension>
.
For more information about the log and the restart file, see "Prerequisites" above.
- Choose Export/Import
®
Restart.
SAPDBA displays the:
This is the working directory for the import. The default is
<SAPDATA_HOME>/sapreorg
or
<SAPREORG>
, based on the environment variable
SAPREORG
. Logs and scripts are saved in this directory. For more information on
<SAPREORG>
, see
Environment Variables (UNIX) and
Environment Variables (Windows NT).
This is the subdirectory
<timestamp>
that contains the restart scripts. This information is based on the last export or import performed. Compare this information with that in the appropriate log
<timestamp>.exd
,
<timestamp>.imd
,
<timestamp>.exs
,
<timestamp>.ims
,
<timestamp>.exg
.
This shows the type of restart to be performed, based on the type of the most recent import or export.
- If required, change the Working directory or Restart subdirectory
.
Choose Show import plan or Show restart plan to check the plan before you start.
Choose Restart to restart the import or export, or Restart in batch to execute it in the background.
SAPDBA restarts the import or export.
Result
On successful completion, SAPDBA displays a confirmation message