RelationalDBDesign RelationalDBDesign


Database Backup   «Prev 

Using Oracle Import

The (imp) import utility reads files generated by the export utility and loads the objects and data into the database. After the tables are created, their data is loaded, and the indexes are built. Following these objects, triggers are imported, constraints are enabled, and bitmap indexes are created. This sequence is important for several of reasons.
  1. Rows are inserted before triggers are enabled to prevent the firing of the triggers for each new row.
  2. Constraints are loaded last because of referential integrity relationships and dependencies among tables.
  3. If each EMPLOYEE row required a valid SECTION row and no rows were in the SECTION table, errors would occur.
  4. If both of these tables are present, the constraints should be disabled during the import and enabled after import.

The following commands listed below are deprecated and were used with Oracle 8

  1. imp80 system/manager inctype=SYSTEM full=y file=exp0712.dmp
  2. imp80 system/manager inctype=RESTORE full=y file=exp0701.dmp
  3. imp80 system/manager inctype=RESTORE full=y file=exp0706.dmp
  4. imp80 system/manager inctype=RESTORE full=y file=exp0710.dmp
  5. imp80 system/manager inctype=RESTORE full=y file=exp0711.dmp
  6. imp80 system/manager inctype=RESTORE full=y file=exp0712.dmp