I just want to clarify a concept to which SCunningham99 alluded 4 replies ago: "...when you import it back in with compress option it will be only using one segment."
When you do a exp "COMPRESS=Y", this directs the utility to evaluate the entire size of a table (perhaps 100MB, spread across dozens of extents) and create a storage parameter for table that reads, "STORAGE (INITIAL 100M...)" so that when IMP processes the table, it attempts to place the entire table into one EXTENT (Notice, "EXTENT" not "SEGMENT" as Sy suggested; a SEGEMENT is, for example, a table or an index; an EXTENT is a contiguous allocation of blocks within a SEGMENT.) And when EXP/IMP follow the COMPRESS=Y directive, it is a misnomer...there is no "compression" taking place at all; only "consolidation". Oracle would have been much more accurate to specify the EXP parameter as "CONSOLIDATE=Y", but Oracle's software developers have never been known for their literary skills anyway.
Cheers,
Dave
Sandy, Utah, USA @ 17:12 GMT, 10:12 Mountain Time