Re: Backup and restore just one DBF or one user

Having your database schema owners (not exactly the same as users) separated each into their own tablespaces and datafiles works well for a lot of people.

If you really want to use export to backup each schema separately then you can use "exp owner=schema1 etc", "exp owner=schema2 etc".

> I am exploring the cold backup option right now and having problem
> restoring. It is not quite right yet and i am still struggling with
> it.

Now you have me a little worried, there's nothing much simpler than a cold backup. You shutdown the database (best advice don't do an abort and get a clean consistent shutdown), and copy everything to somewhere else.

>
> I am less familiar with exp and imp that my last attempt at restoring
> caused
> double entry in most of my tables. Besides, it took too much time to
> import mainly due to my lack of experience in dealing with imp.

Usually if one wants to recover on a schema level from an export you drop the schema owner with cascade, re-create the schema owner and define database privileges for the schema owner, then do the import with a fromuser= and touser= clauses.

Remember though that a recovery using import ONLY has exactly the information that was present in the schema when the export was done. NO FORWARD RECOVERY OF any info updated/changed in the schema after the export which means potentially loss of data.

This is a severe enough penalty for most people and/or organizations to stop them immediately from thinking about using export/import as a primary backup strategy.

Export/import is fine as a supplementary backup strategy though.

>
> I am not familiar at all with RMAN, so i am not considering it.

RMAN is something you should definitely consider. You sound as if you are just starting up the hill on your learning curve with oracle backups. If you are having problems with export and import and cold backups, open your thinking and consider using RMAN. Received on Tue Dec 28 2004 - 07:02:50 CST