Re: Export/Import to tape?
Date: Sun, 24 Jan 1993 05:20:05 GMT
Message-ID: <1993Jan24.052005.18747_at_atlastele.com>
In article <bogreen.726774727_at_unixg.ubc.ca> bogreen_at_unixg.ubc.ca (Bo Green) writes:
>
> 1) I need to change the tablespace allocation of a large database I am
> working with, so I thought the best way would be to Export, create
> new tablespaces, and then Import the tables. Unfortunately, I don't
> have enough disk space to Export to disk. I figure out how I can Export
> to exabyte tape in a reasonably efficient way. Any ideas?
You can export to a named pipe and compress the output (assuming 'nix). I would identify all user objects in the tablespace first and export each table by itself.
After all user objects have been exported drop the tables. (Don't bother
to export the indexes). After all user tables are dropped you can then do
a full export (talking system tables at this point). You now have seperate
images of each table and the system. Drop the tablespace at this point.
Recreate the tablespace(s) and execute your schema generation scripts.
Be sure and adjust the storage clauses so that the entire table will fit
in a single extent. I keep my index creation scripts seperate from my
table creation scripts this will allow me to import the data and not create
indexes during import (can slow things down a great deal). After the import
you can run your index creation scripts, once again adjust the storage
clauses so that all index extents will compress into one.
>
> 2) If I use "COMMIT=Y" on an Import, will that solve the problem of a
> lack of enough rollback space for a large table?
Most definately.
Feel free to call me at (503)228-1400 ext 650 if you need more help.
Received on Sun Jan 24 1993 - 06:20:05 CET