Timeline for Importing schema to new or different tablespace
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 8, 2019 at 16:10 | comment | added | Nicolas de Fontenay | I'm working on something similar but it's a whole DB migration using expdp/impdp because I want our QA env to match production. If I use remap_tablespace it would remap every schema into another single tablespace, however I think I can run the impdp command once per schema and using remap_tablespace. This should achieve the job. | |
| Oct 12, 2012 at 16:58 | vote | accept | Roy | ||
| Oct 12, 2012 at 14:10 | comment | added | Roy | Thank you very much, Phil. I was wondering: If the user being imported to exclusively has a quota on the default tablespace, will that force imp to place all imported objects in that default tablespace regardless of the layout on the source of the data? | |
| Oct 12, 2012 at 14:06 | history | answered | Philᵀᴹ | CC BY-SA 3.0 |