[DBA notes] IMP-00093 Error Resolution

Error | Address Today field staff report in imp a DMP file times exceeds the maximum number of cursors for errors, ora-01000:maximum open cursors exceeded.
Asked about the basic situation, on the Metalink check, IMP did not mention any of the ORA-01000 error, this is a little puzzled. At this time, through the mail received DMP file, their own simulation test, found that the cause of the mistake is not ORA-01000, but IMP-00093, just because too many IMP-00093 mistakes consumed a lot of cursor, The number of cursor in one session is more than 300 of the definition, so the ORA-01000 error is reported at the end.

imp-00093:inconsistency between dumpfile constraint definition for table account with columns ("Acctid", "CurrencyID")

First look at the error document, 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, is a bug.

Bug 2834541-imp-93 on import when using the Touser parameter

Bug No. 2834541

This bug was fixed in 9.2.0.6 and 10.1.0.3, and it was caused by importing 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. Did not report miss, 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, but to say a little more, it's a good habit to manually specify all the constraints ' names when designing schemas.