Export/import to clone database -- please advise

Question

Hi All,
Need help especially from exports that are strong in export/import.
can someone advise me how to use export/import to clone a database?
I know how to clone database using cold backup and hot backup.
But wish to know the full steps in using export/import to do cloning.
I'm going to do a full export on my "TEST" database, drop the database, create a database and import using the full export.
After doing a full database export, full=y. What are the steps to follow. Have a few doubts about it.
1) export the database (full=y)
2) drop the database
3) re-create the database, will be using the same name "TEST".
4) create the users (IDs created by DBA, eg: schemas), tablespace and datafiles. --> import doesn't do it right?
5) do a full import (full=y). In this step, will i encounter any problems? As in understand that all the oracle-owned objects (example SYSTEM, SYS, AUX) are already in the newly created database, will import full=y cause any problems?
6) do i have to re-create the roles, SYNONYMS and grant role,sys,obj privileges to IDs not created by oracle. (example schema owner)
in short i would like to know what EXPORT will export and not export
what IMPORT will import and not import.
Please advise.

Answer 1

Hi zetabouy,
thanks for ur input, definately helpful for me.
just to confirm. am i right to say that only a full database level (full=y) export/import will export/import out roles as well as public synonyms? because i have tried also exporting a user from the database, and imported that user into a different database, but public synonyms and roles were not imported.
one more question:
For example we are going to do port data from production to uat database using export and import for only the schema.
After exporting from production with such syntax (owner=OWNER01),
is is better to drop all objects beloging to the schema owner in UAT before importing it (touser=OWNER01, ignore=y) using the production dumpfile?
I'm asking this question as I'm afraid that if we did not drop all the pl/sql objects in UAT database, the updated procedures/fuctions/triggers exported from the production database will not get imported to the UAT database as UAT database have the same procedures/fuctions/triggers names (but not updated code) .
will profiles be exported and imported too duing full database level exp/imp?
please kindly advise.
thanks
Message was edited by:
chew