2 Replies Latest reply on Apr 16, 2020 1:05 PM by Dean Gagne-Oracle

    IMPDP error

    manooty

      Issue during import.

       

      The export was taken from 12.2 database and trying to do import in 19c PBD. We never had issues piror to this. We tried to validate the dump file using sqlfile parameter in impdp command line and we ended up in the same error. But if we try using the some other dump file it works fine. Seems like the issue is only with this dump file. Please help with a workaround to fix this issue.

       

      Attached the log file of the export for reference.

       

       

      [oracle@ORACDBD003 EXPORT]$ impdp directory=EXPORT_HOME dumpfile=CONVTST_extract_Apr2020_version12.dmp

       

      Import: Release 19.0.0.0.0 - Production on Wed Apr 15 07:52:40 2020

      Version 19.3.0.0.0

       

      Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved.

       

      Username: sys @c2mcnvd as sysdba

      Password:

       

      Connected to: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production

      ORA-39002: invalid operation

      ORA-31694: master table "SYS"."SYS_IMPORT_FULL_01" failed to load/unload

      ORA-02354: error in exporting/importing data

      ORA-02373: Error parsing insert statement for table "SYS"."SYS_IMPORT_FULL_01".

      ORA-00904: : invalid identifier

       

       

      Export log:

      Export: Release 12.2.0.1.0 - Production on Wed Apr 15 09:03:21 2020

       

       

      Copyright (c) 1982, 2017, Oracle and/or its affiliates.  All rights reserved.

      ;;;

      Connected to: Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production

      ;;; **************************************************************************

      ;;; Parfile values:

      ;;;  parfile:  logfile=CONVTST_extract_Apr2020_version12.log

      ;;;  parfile:  dumpfile=CONVTST_extract_Apr2020_version12.dmp

      ;;;  parfile:  tables=CNVSTG1.CI_PER

      ;;;  parfile:  version=12.2

      ;;;  parfile:  directory=EXPORT_DIR

      ;;; **************************************************************************

      Starting "SYS"."SYS_EXPORT_TABLE_01":  /******** AS SYSDBA parfile=CONVTST_extract_Apr2020_version12.par

      Processing object type TABLE_EXPORT/TABLE/TABLE_DATA

      Processing object type TABLE_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS

      Processing object type TABLE_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS

      Processing object type TABLE_EXPORT/TABLE/STATISTICS/MARKER

      Processing object type TABLE_EXPORT/TABLE/TABLE

      Processing object type TABLE_EXPORT/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT

      Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINT

      . . exported "CNVSTG1"."CI_PER"                          34.88 MB  284865 rows

      Master table "SYS"."SYS_EXPORT_TABLE_01" successfully loaded/unloaded

      ******************************************************************************

      Dump file set for SYS.SYS_EXPORT_TABLE_01 is:

        /u01/EXPORT/CONVTST_extract_Apr2020_version12.dmp

      Job "SYS"."SYS_EXPORT_TABLE_01" successfully completed at Wed Apr 15 09:04:04 2020 elapsed 0 00:00:37

       

        • 1. Re: IMPDP error
          dohdatabase-Oracle

          Hi,

           

          I am not aware of any known issues on 19 but somethings to try out:

          1) Have you applied the latest Release Update to the 19 Oracle Home?

          2) Have you tried to import using a less privileged user than SYS?

          3) Can you re-export the data and see if the error is also present with a new dump file?

           

          Regards,

          Daniel

          • 2. Re: IMPDP error
            Dean Gagne-Oracle

            Oracle says NOT to export or import as SYS.   I'm not saying that is the problem, but there are issues when doing that.

             

            Have you run sqlfile on the source database?   I just wonder if that dumpfile got corrupted some how.   The last thing to write out during export is the master table and that is the first thing that is read in during import.   Have you tried to copy the dumpfile again?

             

            This just sounds like your dumpfile got corrupted some how.

             

            Dean