IMP-00402: Invalid parameter “string” with data_only mode
Posted by ODBAV on 2011/01/07
0 comments
In this article you will be presented a suitable solution for IMP-00402 in Oracle 11g Release 2 (11.2).
Tag Archives: IMP
IMP-00401: dump file “string” may be an Data Pump export dump file
Posted by ODBAV on 2011/01/07
0 comments
This is a brief information taken from Oracle documentation, where you can find a proposed solution for Oracle error: IMP-00401. This solution is suitable for Oracle 11g Release 2 (11.2). If you are interested please come in.
IMP-00400: Warning: Object type “string”.”string” already exists with a different typeid
Posted by ODBAV on 2011/01/07
0 comments
This is the solution for the following problem:An object type could not be created because it already existed on the target system, but with a different typeid
IMP-00099: Warning: The typeid in the dump file for object type “string”.”string” is invalid
Posted by ODBAV on 2011/01/07
0 comments
In htis article you will fine a solution for error: The character string representing the object type’s identifier could not be converted.. This solution is suitable for Oracle 11g Release 2 (11.2).
IMP-00098: INTERNAL ERROR: string
Posted by ODBAV on 2011/01/07
0 comments
This is the solution for the following problem:An INTERNAL error occurred.
IMP-00097: STREAMS_CONFIGURATION=Y ignored, only valid with FULL=Y
Posted by ODBAV on 2011/01/07
0 comments
This is the solution for the following problem:STREAMS_CONFIGURATION=Y can only be used when FULL=Y is present on the command line
IMP-00096: Warning: Skipping table “string”.”string” because type synonym “string”.”string” cannot be created
Posted by ODBAV on 2011/01/07
0 comments
If the following problem occurs in your application read this article: An error occurred creating a synonym for a type that is used by the table.
IMP-00095: Resumable parameters ignored — current session not resumable
Posted by ODBAV on 2011/01/07
0 comments
This is a quick solution for Oracle error IMP-00095. This solution is suitable for Oracle 11g Release 2 (11.2). If you are interested please come in.
IMP-00094: Warning: The identifier on the dump file for object type “string”.”string” is invalid
Posted by ODBAV on 2011/01/07
0 comments
This is the solution for the following problem:The character string representing the object type’s identifier could not be converted.
IMP-00093: Inconsistency between dumpfile constraint definition for table string with columns (string)
Posted by ODBAV on 2011/01/07
0 comments
In this short article you will be presented a quick solution for error IMP-00093.
IMP-00092: Java object “string”.”string” already exists, cannot be created
Posted by ODBAV on 2011/01/07
1 comment
This is a brief information taken from Oracle documentation, where you can find a proposed solution for Oracle error: IMP-00092. This solution is suitable for Oracle 11g Release 2 (11.2). If you are interested please come in.
IMP-00091: Above error occurred on the following function and object: string. Remaining PL/SQL blocks for this object will be skipped.
Posted by ODBAV on 2011/01/07
0 comments
If the following problem occurs in your application read this article: 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.
IMP-00090: Unexpected DbmsJava error number at step number while creating string
Posted by ODBAV on 2011/01/07
0 comments
In this short article you will be presented a quick solution for error IMP-00090.
IMP-00089: Fine grain policy “string” not recreated on table/view “string”
Posted by ODBAV on 2011/01/07
0 comments
This is a short information taken from Oracle documentation where you can find a proposed solution for Oracle error: IMP-00089. This solution is suitable for Oracle 11g Release 2 (11.2). If you are interested please come in.
IMP-00088: Problem importing metadata for index string. Index creation will be skipped
Posted by ODBAV on 2011/01/07
0 comments
This is the solution for the following problem: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.