Results 1 to 3 of 3
  1. #1
    Join Date
    Nov 2010
    Posts
    2

    Unanswered: impdp not importing anything

    I have copied across datapump files which were created on our test system last night (RHEL 5.5, 10.2.0.4), and am wanting to import some tables in, however, when I run the import command, I just get the Datapump banner.

    The parfile used to run the backup is as follows:

    dumpfile=full_101115_0500_datapump_yesrows.dmp_%U. dmp
    full=Y
    content=all
    directory=data_pump_dir
    parallel=4
    job_name=datapump_yesrows_101115_0500
    logfile=data_pump_working_dir:full_101115_0500_dat apump_yesrows.dmp.log

    The datapump files produced are:
    -rw-r----- 1 oracle oinstall 563429376 Nov 15 14:01 full_101115_0500_datapump_yesrows.dmp_01.dmp
    -rw-r----- 1 oracle oinstall 1664196608 Nov 15 14:02 full_101115_0500_datapump_yesrows.dmp_02.dmp
    -rw-r----- 1 oracle oinstall 1366802432 Nov 15 14:02 full_101115_0500_datapump_yesrows.dmp_03.dmp
    -rw-r----- 1 oracle oinstall 27308032 Nov 15 14:02 full_101115_0500_datapump_yesrows.dmp_04.dmp

    I created a new database on my PC this morning (RHEL 5.5 10.2.0.4) using dbca and have scott schema installed. The Test db is 32 bit, but my PC is running 64 bit Oracle. (I don't think this matters).

    I have created a directory and given read/write privs to myself. Have also granted create session, dba, imp_full_database and exp_full_database to my import user account.

    Running the import just gives me this:

    [oracle@s DR]$ impdp stu999 directory=my_datapump_dir tables=general.patient remap_schema=general:scott remap_tablespace=general:users dumpfile=full_101115_0500_datapump_yesrows.dmp_01. dmp, full_101115_0500_datapump_yesrows.dmp_02.dmp, full_101115_0500_datapump_yesrows.dmp_03.dmp, full_101115_0500_datapump_yesrows.dmp_04.dmp

    Import: Release 10.2.0.4.0 - 64bit Production on Monday, 15 November, 2010 15:37:25

    Copyright (c) 2003, 2007, Oracle. All rights reserved.
    Password:

    Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options


    nothing.. just the impdp banner. Now try importing a schema...

    [oracle@s DR]$ impdp stu999 directory=my_datapump_dir schemas=biskit remap_schema=general:scott remap_tablespace=general:users dumpfile=full_101115_0500_datapump_yesrows.dmp_01. dmp, full_101115_0500_datapump_yesrows.dmp_02.dmp, full_101115_0500_datapump_yesrows.dmp_03.dmp, full_101115_0500_datapump_yesrows.dmp_04.dmp

    Import: Release 10.2.0.4.0 - 64bit Production on Monday, 15 November, 2010 15:37:49

    Copyright (c) 2003, 2007, Oracle. All rights reserved.
    Password:

    Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options

    Again,... nothing, just the banner. The logfile also just has the banner, and nothing appears in my dba_datapump_jobs.

    Am I missing something obvious? The table and schema definitely exist.

  2. #2
    Join Date
    Aug 2003
    Location
    Where the Surf Meets the Turf @Del Mar, CA
    Posts
    7,776
    Provided Answers: 1
    >The table and schema definitely exist.
    post proof

    one approach that sometime is worth considering is as follows:
    first make it work, then make it fancy.
    Can you get ANYTHING into the new DB without any "rename"?
    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.

  3. #3
    Join Date
    Nov 2010
    Posts
    2
    ah,... just figured it out.

    When I tried to run the import as full=Y, I got a fatal error, and in the error stack was the following:
    ORA-25153: Temporary Tablespace is Empty

    I checked dba_temp_files, and there was no temp file.

    I had earlier created my datafiles in the wrong location, and moved them (including the temp file). I did a 'alter database rename file '...' to '...'; but never got an error for the tempfile.

    Have created a new temp tablespace, set it as the new database default and dropped the old temp tablespace. Works fine now when I run the same import commands.

Posting Permissions

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