imp-00093:inconsistency between dumpfile constraint definition for table account with columns ("Acctid", "CurrencyID")
First look at the error file, basically there is no meaningful hint.
imp-00093 inconsistency between dumpfile constraint definition for table string with columns (string)
Cause:import failed to locate a base table for a constraint that is defined in the dump file and statistics were not imp Orted.
Action:check to the If the table and constraint exist. If the table and constraint exist, then the to Oracle Support Services as a import internal error.
Again check Metalink, sure enough, again a bug.
Bug 2834541-imp-93 on import when using the Touser parameter
Bug No. 2834541
The bug was fixed in 9.2.0.6 and 10.1.0.3, and the cause was to import system-generated constraints in the import process, similar to sys_c0027639, but Metalink only mentioned this reason, but many times before, IMP should have the system-generated constraint name , and did not report missed, so there should be another factor mixed with it, such as the generation of statistical information. No further study.
Workaround: Use Indexes=no or Statistics=none parameters in imp, of course the latter is better.
The problem is solved, not too much to say, when designing schemas, it's a good practice to manually specify the names of all constraints.