First
step is you have to create an OS level directory and database level directory
for the export import activity. You can ignore this step if you have the
directories available already.You can verify the directory details in
dba_directories data dictionary view.

If
you have same kind of file system available on the target system you can
proceed with following steps. If you have different files systems available on
the target system, you have to create the tablespaces before importing the
dump.

Step 1.

Create a
general purpose database using the dbca.

Step 2.

Import the full database dump using table_exists_action=skip option. This
parameter will skip all the objects already exist in the database. So,
whichever schema is available as new in the export dump will get import to the
database.

If
you know the important/required application schemas in the source database,
then you can use the schemas parameter during import instead of going for the
full import. This method will not try to import the default system schemas like
sys, system etc. Like in method 1, If
you have different files systems available on the target system, you have to
create the tablespaces before importing the dump.