Results 1 to 9 of 9

Thread: Import Issues

  1. #1
    Join Date
    Oct 2005
    Posts
    61

    Unanswered: Import Issues

    Hi,

    I am exporting form 9.2.0.7 to 10.2.0.2.

    I did a full export of 9.2.0.7 database and I am performing a fromuser touser import in 10.2.0.2.

    Some tables have rowid column, now I get a the following displayed -

    Note: table contains ROWID column, values may be obsolete

    I understand this column is there for searching my rowid, now how do I get the values to not be obsolete?


    Does anyone know what the following error could be corrected?

    IMP-00017: following statement failed with ORACLE error 6550:
    "BEGIN TATUS := DBMS_JAVA.START_IMPORT('META-INF/MANIFEST.MF', 0, 30, "
    "0, 3, 95, 0); END;"
    IMP-00003: ORACLE error 6550 encountered
    ORA-06550: line 1, column 22:
    PLS-00201: identifier 'DBMS_JAVA.START_IMPORT' must be declared
    ORA-06550: line 1, column 11:
    PL/SQL: Statement ignored
    IMP-00017: following statement failed with ORACLE error 6550:
    "BEGIN TATUS := DBMS_JAVA.START_IMPORT('oracle/wh/runtime/xml/ElementH"
    "andler', 0, 29, 0, 3, 1171, 1); END;"
    IMP-00003: ORACLE error 6550 encountered
    ORA-06550: line 1, column 22:
    PLS-00201: identifier 'DBMS_JAVA.START_IMPORT' must be declared
    ORA-06550: line 1, column 11:
    PL/SQL: Statement ignored

    I got this error many times.

    Thanks,
    Srinivas

  2. #2
    Join Date
    Jun 2004
    Location
    Liverpool, NY USA
    Posts
    2,509
    First NEVER, NEVER, NEVER make permenent tables that contain rowid's (except for temporary tables used for reports). The rowid's stored will be meaningless. They refer to the storage location in your 9.2.0.7 database.
    Bill
    You do not need a parachute to skydive. You only need a parachute to skydive twice.

  3. #3
    Join Date
    May 2004
    Location
    Dominican Republic
    Posts
    721
    As for your error, install Oracle JVM on the 10.2.0.2 db.

  4. #4
    Join Date
    Oct 2005
    Posts
    61
    Oh...is there any way of correcting the rowid?

    Any way by which we can make Oracle store the rowid assigned in 10.2.0.2?

    Now if I go ahead with the import would it only slow down when search is made using the rowid or does it have any other implications?

    How do I determine if JVM is installed or not, I don't have the cd mounted to use the OUI, any other way?

    And if I am not using the java procedures in my database, can I ignore the error and go ahead?

    Thanks for your responses?

    -Srinivas

  5. #5
    Join Date
    Jun 2004
    Location
    Liverpool, NY USA
    Posts
    2,509
    There is no way to alter the rowid's to be correct. You will have to alter your tables in the original database to use a real key instead of a rowid. A rowid is the worst selection for a perm row identifier that you could possibly choose. Even if you had to rebuild or copy a table in the same database, it would invalidate the rowid's. Repair your application and tables and then you can move them to the new database. As for the java, you will have to install the JVM into the database.
    Bill
    You do not need a parachute to skydive. You only need a parachute to skydive twice.

  6. #6
    Join Date
    Oct 2005
    Posts
    61
    Yes, that's correct. I may have to correct this (the rowid usage) at some time.

    And I understand that I need to install JVM, but before installing I just want to verify if it has been already installed or not. Is there any way other than OUI to determine that?

    Incase I want to use Java/JVM later and not now, can I go ahead with the import ignoring the java related errors and install the java/jvm when needed later?

    Also, do you have any idea about why we are getting those java related errors as we are not using java now?

    Thanks,
    Srinivas

  7. #7
    Join Date
    Aug 2003
    Location
    Where the Surf Meets the Turf @Del Mar, CA
    Posts
    7,776
    Provided Answers: 1
    select count(*) from dba_objects where object_name like '%JAVA%';
    A small count mean no Java installed.
    A large count means Java is installed.
    where "large" > "small"
    You can lead some folks to knowledge, but you can not make them think.
    The average person thinks he's above average!
    For most folks, they don't know, what they don't know.
    Good judgement comes from experience. Experience comes from bad judgement.

  8. #8
    Join Date
    Oct 2005
    Posts
    61
    Thanks much!

  9. #9
    Join Date
    May 2004
    Location
    Dominican Republic
    Posts
    721
    Just do a desc dbms_java and you should see whether it is installed or not.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •