Schema Import failed :IMP-00008: unrecognized statement in the export file:

Question

Hi ,
I was running a database schema import from a database DMP file.
I encountered the following error in the log file that was getting generated :
IMP-00008: unrecognized statement in the export file:
All the tables got copied except for one. Now what I have thought of is to import that one table again after taking an export from the prod schema.
But what about the functions,triggers,procedures ?? How do i bring all of them in the schema ?
If reimporting the schema again the only option ?
Thanks
Kk

Answer 1

Hello,
In this order:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14215/exp_imp.htm#i1023988
Table Objects: Order of Import
Table objects are imported as they are read from the export file. The export file contains objects in the following order:
1. Type definitions
2. Table definitions
3.Table data
4.Table indexes
5. Integrity constraints, views, procedures, and triggers
6. Bitmap, function-based, and domain indexes
The order of import is as follows: new tables are created, data is imported and indexes are built, triggers are imported, integrity constraints are enabled on the new tables, and any bitmap, function-based, and/or domain indexes are built. This sequence prevents data from being rejected due to the order in which tables are imported. This sequence also prevents redundant triggers from firing twice on the same data (once when it is originally inserted and again during the import).
For example, if the emp table has a referential integrity constraint on the dept table and the emp table is imported first, all emp rows that reference departments that have not yet been imported into dept would be rejected if the constraints were enabled.
When data is imported into existing tables, however, the order of import can still produce referential integrity failures. In the situation just given, if the emp table already existed and referential integrity constraints were in force, many rows could be rejected.
A similar situation occurs when a referential integrity constraint on a table references itself. For example, if scott's manager in the emp table is drake, and drake's row has not yet been loaded, scott's row will fail, even though it would be valid at the end of the import.