5 Replies Latest reply: Oct 11, 2013 8:21 AM by DK2010 RSS

    having problem with import via dblink

    983554

      this is the import command:

      impdp schemas=g2log network_link=HS5 directory=DATA_PUMP_DIR logfile=g2loggblink.log CONTENT=data_only

       

      here are the error messages that I am getting:

      Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production

      With the Partitioning, OLAP and Data Mining options

      Starting "SYS"."SYS_IMPORT_SCHEMA_06":  /******** AS SYSDBA schemas=g2log network_link=HS5 directory=DATA_PUMP_DIR logfile=g2loggblink.log CONTENT=data_only

      Estimate in progress using BLOCKS method...

      Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA

      ORA-39125: Worker unexpected fatal error in KUPW$WORKER.GET_TABLE_DATA_OBJECTS while calling DBMS_LOB.CREATETEMPORARY []

      ORA-01157: cannot identify/lock data file 1504 - see DBWR trace file

      ORA-01110: data file 1504: '/data/oracle/oradata/hs4/temp02_01.dbf'

       

      ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95

      ORA-06512: at "SYS.KUPW$WORKER", line 6228

       

      ----- PL/SQL Call Stack -----

        object      line  object

        handle    number  name

      43045e5d0     14916  package body SYS.KUPW$WORKER

      43045e5d0      6293  package body SYS.KUPW$WORKER

      43045e5d0      9108  package body SYS.KUPW$WORKER

      43045e5d0      3870  package body SYS.KUPW$WORKER

      43045e5d0      6910  package body SYS.KUPW$WORKER

      43045e5d0      1259  package body SYS.KUPW$WORKER

      4303272b0         2  anonymous block

       

      Job "SYS"."SYS_IMPORT_SCHEMA_06" stopped due to fatal error at 14:34:40

       

       

      can someone please help me with this thanks

        • 1. Re: having problem with import via dblink
          davidp 2

          You should do your export / import as a user, without SYSDBA - logging on as SYSDBA changes many things and could be causing this. SYSTEM or some other user with DBA is able to do anything impdp /expdp can do.

          The error could be due to running as SYSDBA.

          I've never seen that particular error before. If running as SYSTEM doesn't fix it, it sounds like a problem with the TEMP tablespace and you should have a look at the DBWR trace file in the database trace directory.

          I'd also suggest exporting the source to a file, just to isolate whether the problem is with the export or the import, but try running it without SYSDBA first.

          • 2. Re: having problem with import via dblink
            saurabh

            This error might be due to temporary datafile not present

             

            check the output of below cmd

             

            select name from v$tempfile.

            and depending on the output check if the file specified is present or not.

            • 3. Re: having problem with import via dblink
              DK2010

              Hi,

               

              ORA-39125: Worker unexpected fatal error in KUPW$WORKER.GET_TABLE_DATA_OBJECTS while calling DBMS_LOB.CREATETEMPORARY []

              ORA-01157: cannot identify/lock data file 1504 - see DBWR trace file

              ORA-01110: data file 1504: '/data/oracle/oradata/hs4/temp02_01.dbf'

               

              because of temp file missing. Add the File in Temp TS like

              ALTER TABLESPACE TEMP ADD TEMPFILE  '<Location>' SIZE ....;

               

              HTH

              • 4. Re: having problem with import via dblink
                983554

                I have tried with the g2log user I still get the same error

                I also added 30gb to the temp tablespace as well

                 

                impdp g2log/****** schemas=g2log network_link=HS5 directory=DATA_PUMP_DIR logfile=g2loggblink.log CONTENT=data_only

                Import: Release 10.2.0.3.0 - 64bit Production on Friday, 11 October, 2013 6:50:12

                Copyright (c) 2003, 2005, Oracle.  All rights reserved.

                Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
                With the Partitioning, OLAP and Data Mining options
                Starting "G2LOG"."SYS_IMPORT_SCHEMA_02":  g2log/******** schemas=g2log network_link=HS5 directory=DATA_PUMP_DIR logfile=g2loggblink.log CONTENT=data_only
                Estimate in progress using BLOCKS method...
                Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
                ORA-39125: Worker unexpected fatal error in KUPW$WORKER.GET_TABLE_DATA_OBJECTS while calling DBMS_LOB.CREATETEMPORARY []
                ORA-01157: cannot identify/lock data file 1513 - see DBWR trace file
                ORA-01110: data file 1513: '/data/oracle/oradata/hs4/temp02_10.dbf'

                ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
                ORA-06512: at "SYS.KUPW$WORKER", line 6228

                ----- PL/SQL Call Stack -----
                  object      line  object
                  handle    number  name
                43045e5d0     14916  package body SYS.KUPW$WORKER
                43045e5d0      6293  package body SYS.KUPW$WORKER
                43045e5d0      9108  package body SYS.KUPW$WORKER
                43045e5d0      3870  package body SYS.KUPW$WORKER
                43045e5d0      6910  package body SYS.KUPW$WORKER
                43045e5d0      1259  package body SYS.KUPW$WORKER
                429e4fd80         2  anonymous block

                Job "G2LOG"."SYS_IMPORT_SCHEMA_02" stopped due to fatal error at 06:50:16

                • 5. Re: having problem with import via dblink
                  DK2010

                  Hi,

                   

                  there is nothing to do with the user, this is Error for Temporary tablespace, this is at Db level

                  share the result for

                   

                  select file_name,autoextensible,bytes/(1024*1024)from dba_temp_files;