Note: Data Pump Import (invoked with the impdp command) is a new utility as of Oracle Database 10 g.
Although its functionality and its parameters are similar to those of the original Import utility ( imp ), they are completely separate utilities and their files are not compatible.
See Chapter 19, “Original Export and Import” for a description of the original Import utility.
Much time has elapsed since you entered this.
Seems like datapump has perhaps added more features.
I see an example in metalink of using the remap_tablespace option, impdp username/password dumpfile=example schema=example remap_tablespace =tablespace_source:tablespace_target # Patrick Bacon Apr 12 ’16 at 20:01, RMAN Using Data Pump Import Utility (impdp).
As the name suggests, import (impdp) is the reverse of export and is used to move the data back into the Oracle database from the dump file.
import needs a mandatory dump file to be passed to it.
17/09/2009 I have a routine expdp/ imp where i remap about > a dozen prod tablespaces into a single test tablespace.
> > > On Sep 17, 2009, at 1:45 PM, chet justice wrote: > > Database: 10.
3 > DP : 10.
1 > > I’ve received a datapump export of our production database (objects only) > so that I can test my migration script.
> > On first go, none of the.
Data Pump Import Interfaces.
You can interact with Data Pump Import by using a command line, a parameter file, or an interactive-command mode.
Command-Line Interface: Enables you to specify the Import parameters directly on the command line.
For a complete description of the parameters available in the command-line interface, see Parameters Available in Import’s Command-Line Mode.
RMAN Using remap_tablespace to Import Objects to a Different Tablespace.
Being a DBA, there are plenty of times when you have to move the objects around the tablespaces to get them reorganized.
This can be done in many ways; for example, using the alter #, Dear TOM, We are using impdp Release 11.
0 – Production to exchange data between two databases, both in version 11.
0 – 64bit Production.
Import : imp user2/[email protected] —> again on server2 With above two commands I transferred data from one server to another server by logging on just one server and without using FTP.
If same thing I have to do using new IMP and EXP, I have to create directory on server-1, give access permission to user of Oracle -1.
And then do export.
imp scott/[email protected] file=.
dmp fromuser= touser= to import from one user to another.
Be prepared for a long haul though if it is a complicated schema as you will need to precreate all referenced schema users, and tablespaces to make the imp work correctly.
Update: The reason I still use the original exp and imp utilities is because my company still have that legacy data on previous version Oracle database.
If that is the case, I would import the objects in the same tablespace and later on I would migrate to another tablespace using ALTER INDEX REBUILD TABLESPACE command.