IMP-00092: Java object “string”.”string” already exists, cannot be created
Cause: Import failed to create the Java source, class or resource object because it already exists.
Action: Drop the object type from the target system and retry the operation.
IMP-00091: Above error occurred on the following function and object: string. Remaining PL/SQL blocks for this object will be skipped
Cause: An error occurred while executing a PL/SQL block that implements the DDL for the named function and procedural object. A procedural object is one whose DDL is implemented as stored procedures rather than as standard SQL statements.
Action: Contact Oracle Worldwide Support so they may determine the development group responsible for the package that failed.
IMP-00090: Unexpected DbmsJava error number at step number while creating string
Cause: The error was returned from a call to a DbmsJava procedure.
Action: Record the accompanying messages and report this as an Import internal error to customer support.
IMP-00089: Fine grain policy “string” not recreated on table/view “string”
Cause: Import user fails to recreate fine grained policies of the table/view being imported. To recreate the policy, the user doing the import needs execute privilege on the package DBMS_RLS for access policies or DBMS_FGA for audit policies.
Action: Ask the database administrator to perform the export/import of this table/view.
IMP-00088: Problem importing metadata for index string. Index creation will be skipped
Cause: Domain indexes import private metadata via anonymous PL/SQL blocks prior to the CREATE INDEX statement. The execution of one of these PL/SQL blocks failed. Because the metadata is considered an integral part of the index, the subsequent CREATE INDEX statement was skipped.
Action: Contact the developer of the index’s implementation type. If this is an Oracle-supplied index (perhaps via a data cartridge), contact Oracle Worldwide Support.
IMP-00087: Problem with internal hash table of schema/table names
Cause: Most likely a problem with allocating memory for the hash table entries.
Action: Contact Oracle Worldwide Support
IMP-00086: TOID “string” not found in export file
Cause: Import did not find the type identification specified in the TOID_NOVALIDATE parameter. The specified type identification does not exist in export file.
Action: Correct or omit the TOID_NOVALIDATE parameter.
IMP-00085: multiple input files specified for unbounded export file
Cause: You specified multiple file names for the FILE parameter when doing an import, but the header in the export file indicates that that the export operation could create only one file. Specifying multiple file names is valid for an import operation only if the export files were created by an export operation in which the user specified a non-zero value for the FILESIZE parameter.
Action: If you believe the export contains multiple files, verify that you have specified the correct files. If you believe the export should be in only one file then try the import operation again, but specify only one value for the FILE parameter.
IMP-00084: attempt to mix incremental import with user or table import
Cause: An incremental import was requested along with the FROMUSER, TOUSER, or TABLE qualifier. An incremental import cannot be done if any of these other qualifiers are also specified.
Action: Determine whether you want to do an incremental import, full import, user import or table import and reissue the import command with the appropriate qualifiers.
IMP-00083: dump file does not contain an incremental export
Cause: An incremental import was requested and the dump file specified for the import command is either a user or table export.
Action: Reissue the command import command but specify the name of a dump file containing an incremental export.