Oracle import type Object Error ORA-02304

Type is the database object structure that we often use. In practice, we can define type types individually and then use them in PL/SQL code or data tables.

In an accidental opportunity to let the author discover The trouble of using type types in data exp/imp . when we use Exp/imp tool to the same DB instance (Instance ) different Schema if the Schema is copied between data has type in type, a problem error occurs.

As follows:

imp-00003: ORACLE Error encountered2304ORA-02304: Invalid object identifier literal imp-00017: Due to ORACLE error2304, the following statement failed:"CREATE TYPE"T_rec_table"TIMESTAMP ' 2010-12-21:18:17:33 ' OID ' d9afd3fae0a5" "4964b1684ca28c69ceed ' as Table of t_rec_test;" "" ""IMP-00003: ORACLE Error encountered2304ORA-02304: Invalid object identifier literal imp-00017: Due to ORACLE error2304, the following statement failed:"CREATE TYPE"T_typ"TIMESTAMP ' 2012-03-07:10:47:03 ' OID ' 8e294ab7cc28493a94" "ff82791a376379 ' As Object (ID number);" "" ""

For Create type failure, add transform=oid:n to the end of the import command

You can refer to the instructions below.

This means that if the transform parameter is set to Oid=n, the newly created table or the type will be given a new OID, rather than the value of the OID contained in the DMP file, at the time of the Imp. However, the default value of this parameter is oid=y, so when the IMP is made, the newly created table or type will give the same OID, if it is a different schema on the same database, it will cause the OID conflict problem, so it is very simple to solve this problem, Only need to be in IMPDP when the display setting transform parameter is oid=n. As shown below,

(cmd> impdp test/test directory=dump_dir dumpfile=dump.dmp logfile=dump.log remap_schema= Frank:test transform=oid:n)

Reference Address: http://www.shangxueba.com/jingyan/View.aspx?id=52990

http://blog.itpub.net/17203031/viewspace-732089/

Thank

Oracle import type Object Error ORA-02304