1. Get rid of all advertisements and get unlimited access to documents by upgrading to Premium Membership. Upgrade to Premium Now and also get a Premium Badge!

ORA-01466: unable to read data - table definition has changed

Discussion in 'SQL PL/SQL' started by jesthr@gmail.com, Apr 13, 2012.

  1. jesthr@gmail.com

    jesthr@gmail.com Active Member

    Messages:
    23
    Likes Received:
    0
    Trophy Points:
    80
    Dear!

    I have Oracle v11g 11.2.0.3!

    After completion of the procedure to upgrade Oracle from 10g on 11g 11.2.0.3 I have a problem with
    implementation of the export process

    ORA-31693: Table data object "APL_VIRI"."TIS_STN1" failed to load/unload and is being skipped due to error:
    ORA-02354: error in exporting/importing data
    ORA-01466: unable to read data - table definition has changed

    ORA-31693: Table data object "APL_VIRI"."PFI_OBI_NBP_DRZ_MV" failed to load/unload and is being skipped due to error:
    ORA-02354: error in exporting/importing data
    ORA-01466: unable to read data - table definition has changed

    ORA-31693: Table data object "APL_VIRI"."PFI_OBI_NBP_AGREGATI_S_MV" failed to load/unload and is being skipped due to
    error:
    ORA-02354: error in exporting/importing data
    ORA-01466: unable to read data - table definition has changed

    Procedure:

    . . .
    EXP_DUMPFILE="expdp_$1_full_%U.dmp"
    EXP_DUMPLOG="expdp_$1_full.log"
    EXP_DIRECTORY="bsexpdp_dir"
    EXP_FILESIZE="4000M"
    V_EXPDP_COMPR="METADATA_ONLY"

    # exporting
    expdp / dumpfile=$EXP_DUMPFILE logfile=$EXP_DUMPLOG \
    parallel=4 directory=$EXP_DIRECTORY full=Y COMPRESSION=$V_EXPDP_COMPR \
    flashback_time=\"to_timestamp\(to_char\(systimestamp,\'DD/MM/YYYY HH24:MI:SS.FF\'\),\'DD/MM/YYYY HH24:MI:SS.FF\'\)\" \
    filesize=$EXP_FILESIZE
    . . .


    Please help to resolve the error!

    Regards!

    Hine Rosulnik
     
  2. zargon

    zargon Community Moderator Forum Guru

    Messages:
    2,348
    Likes Received:
    348
    Trophy Points:
    1,430
    Location:
    Aurora, CO
    This is an issue with flashback query; either the object is too new to flashback or the table definition has actually changed. If you wait a day or so and try this again can you perform the export? Also, is the flashback date/time reasonable for this particular table?
     
  3. docora

    docora Active Member

    Messages:
    12
    Likes Received:
    0
    Trophy Points:
    80
    Hi,

    Try to expand UNDO retention time and execute again datapump command. It is due to either your flashback time is not sufficient or undo retention time is not sufficient.

    Thanks and regards,
    Rajiv
     
  4. zargon

    zargon Community Moderator Forum Guru

    Messages:
    2,348
    Likes Received:
    348
    Trophy Points:
    1,430
    Location:
    Aurora, CO
    That won't fix the problem; it's an issue of the table being newly created, the flashback just being activated or the table definition being changed. UNDO retention has nothing to do with this problem.