Use
This section describes the preparations necessary for an
export and import with SAPDBA for Oracle.Prerequisites
You have chosen an
export type.Procedure
The file systems or tapes to which the export dump files are written must have sufficient storage space to hold the objects for export. SAPDBA checks whether the contents of the objects to be exported fit in the directories or onto the tapes, and issues a warning if they are too large.
If the export is running in parallel – that is, if the value of
exp_imp_degree is greater than 1 and you have specified multiple dump destinations (disk directories or tapes) – SAPDBA tries to distribute the exported objects equally across the specified directories or tapes.Before you import tables, you must make sure that the tablespaces to which the tables and the indexes belong exist.
The import script contains all commands for creating tables and the indexes, and for importing data, but not the commands for recreating any tablespaces.
Oracle indexes in the SAP System are generally held in tablespaces – on separate disks – other than those of the tables to which they refer.
The tablespaces must have enough free storage space to hold the table and the indexes. In contrast to reorganization, SAPDBA does not check whether the import into the database will run successfully.
Result
You can now start the export and import.