Re: Tablespace reorg with Import/Export

From: John Blackburn <jb2_at_qdot.qld.gov.au>
Date: 1995/10/30
Message-ID: <471gd7$1e1_at_camelot.qdot.qld.gov.au>#1/1


Angelo Melendez () wrote:
: In message <46gpq4$a8t_at_ixnews7.ix.netcom.com>, hank_at_legacytech.com (Hank Eskin)
: writes:
 

: >
: >
: > Simple question:
: >
: > When an Import/Export operation is done on a database,
: > does the import:
: >
: > (1) re-set all the existing table extents to what is specified
: > in the Table definition (FIRST, NEXT EXTENT), or
: > (2) to what is specified in the Tablespace default definition, or
: > (3) does it leave the existing Extents for the existing
: > tables alone, and just defrags the unused space??
: >
: > Plesae post and/or email to hank_at_legacytech.com!
: >
: > Thanks in advance.
: >
: > - hank
: >
: >===sgs r wst f bndwdth===
: >
 

: Hank,
 

: Your tables will be imported using the tablespace's storage parameters unless
: you create the table(s) first and specify the storage parameters. Use IGNORE=Y
: on your import command line to permit import to use the new storage parameters.

If you say COMPRESS=Y when you export the data, oracle will combine all of the current extents in to one extent in the export file.

If you want to reclaim additional extents which have been allocated to a table, you could issue the ORACLE 7 command:

TRUNCATE TABLE tablename;

WARNING: this also removes _ALL_ the rows in the table.

John.

--
 
John Blackburn                           Phone: +61 7 32534634
jb2_at_qdot.qld.gov.au                      Fax:   +61 7 38541194

"Please enclose a stamped, self-addressed ethernet packet with
 all correspondence..."

#include <std_disclaimer.h>
Received on Mon Oct 30 1995 - 00:00:00 CET

Original text of this message