Datapump Import without creating tablespaces
I have a huge datapump export that I am copying from production to development. In it are 120 schemas that i need to transpose into multiple copies, ie fromuser a touser a1,a2,etc.
The new users can be created prior to running the import, but I have this additional problem: The production copy has 120 different tablespaces, one for each user, that the schemas' data is populated in.
How can i skip over the tablespace creates in impdp? in 9i, imp would dump the objects into the user's default tablespace if the specified tablespace didn't exist. is it the same behavior in 11g?
Also can I specify multiple targets in the fromuser/touser replacement, remap_schema?
ie remap_schema=usera:usera1,
The new users can be created prior to running the import, but I have this additional problem: The production copy has 120 different tablespaces, one for each user, that the schemas' data is populated in.
How can i skip over the tablespace creates in impdp? in 9i, imp would dump the objects into the user's default tablespace if the specified tablespace didn't exist. is it the same behavior in 11g?
Also can I specify multiple targets in the fromuser/touser replacement, remap_schema?
ie remap_schema=usera:usera1,
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
no, sorry, I'm afraid there is no wildcarding for the remap operation.
You could generate the remapping though from either db by selecting from dba_tablespaces to maybe save some typing and put them all in your parfile.
You could generate the remapping though from either db by selecting from dba_tablespaces to maybe save some typing and put them all in your parfile.
ASKER
Can i dump all the remaps into a parfile? typing them all out netted 15k characters, well above the buffer for a single bash command.
yes
ASKER