Re: Export Tablespaces

FlameDance wrote (answering to myself):

> exp system/password_at_instance file=mydump full=y
>
> works (after giving the EXP_FULL_DATABASE role to system) but I've been
> warned that a full import will attempt to overwrite the production
> database instead of creating the test database.

I'm working further on this approach.

imp system/password_at_instance file=mydump full=y destroy=n

leads to many errors of this kind:
IMP-00015: following statement failed because the object already exists:

We've had the same problem with importing tables only and worked around it by dynamically creating a script which dropped all tables.

Questions:
1. Is there an option which allows to overwrite objects while importing? I haven't found one. IGNORE affects error handling but in either case existing objects are skipped. DESTROY=Y would kill the production database. COMMIT affects committing of rows but not overwriting of objects.

[Quoted] 2. How would a script look that dynamically drops all objects in the test database (like we so far drop tables), so they can be newly created while importing?

Yours,
Stephan

PS: I guess, probably it would be easier to buy another machine and recreate the test database there in the same setting (paths, SID, etc). But that's not wanted. Received on Wed Nov 26 2003 - 14:47:22 CET