Gene,
First of all, the out of space failure may be perfectly normal. Even if you
do a 200M table import there are several other recursive statements that
generate a lot of undo information, including but not limited to segment
expansion, extent creation, partition operation process, etc. Some
Gene,
Are you using Automatic (System Managed) UNDO? or the traditional
Rollback segment method?
If you are using Automatic UNDO, you should have more than 2
segments in the UNDO tablespace. The number of segments initially created is
the function of processes and the minimum I
Is the table a pre-existing empty table, or is it being
created on the fly by the import ? In the latter case,
does your table have a primary key, or other index -
as this could explain why you are seeing two large
rollback segments. (Although 200M of table plus an
index shouldn't take anything
