Oracle Error 2304 Encountered Import
Contents |
January 10, 2008 - 5:31 pm UTC Category: Database � Version: oracle 8.1.7 Whilst you are here, check out some content from the AskTom team: On Sorts, Selecting, and Selectivity Latest Followup You Asked i have installed oracle 8.1.7. and
Ora 02304 Invalid Object Identifier Literal During Import
i have exported a table having object data type and i am tring to transform=oid:n import it in different schema but it is giving me error -> "IMP - 00017:following statement failed with oracle error 2304:
Imp-00017: Following Statement Failed With Oracle Error 2304:
"CREATE TYPE TEMP_TYPE TIMESTEMP '2001-01-24:12:54:38' OID 'C07F6E6CF1E' "511D488B80050BA897E09" AS OBJECT (TP1 VARCHAR2(30),TP2 VARCHAR2(30))" IMP 00003:ORACLE ERROR 2304 ENCOUNTERED ORA-02304:INVALID OBJECT IDENTIFIER LITERAL IMP 00063:WARNING: SKIPPING TABLE "TEMPUSER"."FIRST_TABLE" BECAUSE OBJECT TYPE "TEMPUSER"."TEMP_TYPE" CAN NOT BE CREATED ora-39083: object type type failed to create with error: OR HAS DIFFERENT IDENTIFIER and we said... That will not work -- the OID already exists in that database. In order to import that data, we need to use the SAME exact type -- not a "similar" type, the same type. You should not install the same type more then once in a database for this and OTHER reasons. It would be a good practice to create a schema, say called ora-02304 invalid object identifier literal create type TYPES, and install all types into that schema. This ensures a type is installed ONCE per database instance -- never once per schema. In this fashion, all schemas will use the same consistent type. They will be able to do things like: insert into myobjectTable select * from someone_elses.objectTable; if we used "similar" types -- each in our own schema -- that would not be possible. Think about what would happen if everyone had their own "NUMBER" type -- it would be a mess. The same thing is true for user defined types. If you had a user TYPES with the type in it and you had a user "A" with a table "T" of that type and a user "B" with a table (or not -- the table doesn't have to exist) you will be able to: 1) exp owner=a 2) imp fromuser=a touser=b ignore=y that'll create (or not) the table based on the common type and fill it up. the same would be true of CROSS DATABASE issues. You would install the types into 1 database and then export them and import them into the other databases. In this fashion, they all get created with the same OID and you can import/export back and forth between t
time i faced an error ORA-02304 while Importing one database schema to another user (Actually i was copying the scheme for some reasons and i had already 1 copy of the same schema in my database). Problem: The complete error
Impdp Transform
was IMP-00003: ORACLE error 2304 encountered ORA-02304: invalid object identifier literal IMP-00063: Warning: Skipping table imp-00003 "DEV_SCHEMA"."SUPPLIER_PAYMENT" because object type "DEV_SCHEMA"."SUP_PAYMENT_TYPE" cannot be created or has different identifier Reason: Whenever you create Oracle object types with command for example create type mytype as object (ids number, names varchar2(60)); Oracle assigns Object ID internally for all objects while i was imported the same Type with Same Object ID was already exists in my database. like https://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:1323002416801 One column in my table SUPPLIER_PAYMENT contains Nested Table type column and in my database i had already one copy of my schema and NESTED TABLE TYPE with same Object ID (Internally) named SUP_PAYMENT_TYPE. Solution: Whenever you create objects with TYPES its a good practice to create all objects types in separate schema so you can share your objects in different schema's objects. I removed the duplicate schema from the database and re-imported my http://www.baigzeeshan.com/2010/02/how-to-avoid-ora-02304-invalid-object.html tables and everything went smoothly. So, Keep in mind If u going to work with objects in Oracle its better to create them in separate schema. Have a nice day, Baig Posted by Zeeshan Baig at 3:07:00 AM Labels: DBA, Developer, Errors, General, ORA-02304, Oracle Reactions: 2 comments: LAcikeAugust 6, 2010 at 9:21 AMor just use impdb parameter "TRANSFORM=oid:n"ReplyDeleteBaigAugust 6, 2010 at 9:28 AMHi, Thanks for comments in which DB version this parameter added ?My solution is similar to Oracle support one and for 10g database.I guess 11g got this TRANSFORM parameter.ReplyDeleteAdd commentLoad more... Newer Post Older Post Home Subscribe to: Post Comments (Atom) Contact Form Name Email * Message * Search This Blog Loading... Subscribe by email About Me Zeeshan Baig Oracle ACE, Solution architect specialized in Middleware, Database, Cloud and Web technologies View my complete profile Google+ Followers Support my Music Follow me on Twitter Tweets by @baigsorcl Popular Posts How to Change JDK used by Weblogic Server Open File Dailog box example using Webutil CLIENT_GET_FILE_NAME Forms 10g How to find out which weblogic server version installed on the machine Calling PL/SQL Procedure and Function in Oracle ADF application Solution to fix Exception java.lang.NoClassDefFoundError While running weblogic commands from console How to Create ADF LOV with Filter or View Criteria How to
Problem If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you http://www.dbasupport.com/forums/showthread.php?18443-Import-Problem can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Page 1 of 2 12 Last Jump to page: Results 1 to 10 of 13 Thread: Import Problem Tweet Thread Tools Show Printable Version Email this Page… Subscribe to this Thread… Display Linear Mode Switch to oracle error Hybrid Mode Switch to Threaded Mode 11-30-2001,01:54 AM #1 venudba View Profile View Forum Posts Junior Member Join Date Aug 2001 Location Hyderabad, India Posts 29 I am running Oracle 8.1.7 I took the export of one of the user having 40 objects having data. When I am importing to the other user or same user, there is a problem.I am oracle error 2304 able to import the objects those doesnot contains object types. Those tables contains object types, the import is ignoring. Venkateshwarlu.K Reply With Quote 11-30-2001,04:57 AM #2 padmam View Profile View Forum Posts Join Date Mar 2000 Location Chennai.Tamilnadu.India. Posts 658 Solution Hi, 30th Nov 2001 15:23 hrs Mumbai The Problem is OID should be unique in the DB. Since already if the same Object identifier for the type is existing you will have problem. Even if you try to import to the other user you cannot. Cheers Padmam Attitude:Attack every problem with enthusiasam ...as if your survival depends upon it Reply With Quote 11-30-2001,06:25 AM #3 venudba View Profile View Forum Posts Junior Member Join Date Aug 2001 Location Hyderabad, India Posts 29 Import - Invalid object identifier literal I know that there is a problem with OID. I have the Export dump file of Application Schema along with bunch of Data. I want to Import all the Schema along with Data in to the New User. I am able to Import all the tables except those tables does not contain