Does the target database need to have the same structure of the source database before to use IMPDP

backupdatapumpexpdpimpdporacle

When I do a import from another database have I need the same estruture of the source database in the target database?

For example, if my source database use ASM and my target database no, what have I to do before to make the import?

In the last time I received an error during the import. The error was about the creation of a tablespace and the datafiles. The erro said that the path of the datafile does not exist. For this problem I used the remap_datafile. But I wonder if is there another way to do it without this parameters. Mainly if there are several datafiles

In the last time I didn't use ASM, it was file system on different machines

My scenery is a full export and import

Best Answer

The new database can have a different directory structure and even storage system, but you'd need some preparation before running the import. Especially, you'd need to create the tablespaces in advance with the correct (new) storage parameters (and of course the required size). Then impdp would not have to create them (an error might still be shown, but import should proceed).

Make sure to give the tablespaces the same names (or use the corresponding REMAP parameters on import). No need to apply quotas etc, that the import should take care of then (when creating the users).

Related Solutions

How to Create Tablespace in Oracle 11g

The answer to your question can be found in the SQL Language Reference (excerpt follows).

Creating Basic Tablespaces: Examples

This statement creates a tablespace named tbs_01 with one data file:

CREATE TABLESPACE tbs_01 DATAFILE 'tbs_f2.dbf' SIZE 40M ONLINE;

It sound like you are new to Oracle databases. Oracle provides a wealth of documentation at http://docs.oracle.com/en/database. Specifically, I recommend reading their excellent introduction to the database called the Concepts Guide.

Oracle IMPDP job ORA-30036 unable to extend segment by 8 in undo tablespace ‘UNDOTBS1’

Ensure that the default undo tablespace has enough capacity.

Based on your output, I see 3 tablespaces with 2GB of size. Perhaps one of them is the default assigned UNDO and auto extend is off.

Another prediction is that the default undo could be another tablespace with a different name, the query executed does not indicate the default undo but rather checks the tablespaces named with 'UNDO'.

You can check the default undo tablespace using the below query

select value from v$parameter where name like 'undo_tablespace';

Best Answer

Related Solutions

How to Create Tablespace in Oracle 11g

Oracle IMPDP job ORA-30036 unable to extend segment by 8 in undo tablespace ‘UNDOTBS1’

Related Question