Re: Performing Backups via the GUI

A dump is not a backup.(or at least not a good strategy for doing one)

I am guessing several problems with what you are trying to do. 1. The import does not delete the rows that are aleardy in the db so you probably get a ton of errors.
2. Your table might reside on different paths on server B than server A so that you end up not being able to create them. (if they are already there this is probably not a problem.)
3. If you read the Oracle utilities documentation (eg with your install or at otn.oracle.com, free to join up) you might not have set the ignore parameter to not error out on object creation if the object exists.

What version, what OS?

You might consider a standby database depending upon what your needs are. But a dump file is not really a good backup strategy.

Jim

"Richard" <rich251076_at_hotmail.com> wrote in message news:aa97aa34.0209130714.5068ac57_at_posting.google.com...
> I have set up my database on one server to export nightly and store
> it's *.dmp file on another server.
>
> This other server then imports the file and recreates the database.
>
> My problem is that I have found I just can't export a whole database
> and then do a full import it on this new machine - everything messes
> up?
>
> I have only had success when I exported the tables alone, ran a script
> to create the appropriate users on the new server and then imported
> those tables.
>
> Why can't I just do a full import? :-(
>
> Your help would be much appreciated thank you...
>
> Rich
Received on Fri Sep 13 2002 - 22:04:07 CDT