Re: IMP, suggestion for extents ..(Need!!!)???

jkyf0131_at_hotmail.com (JK Yao) wrote in message news:<93f65984.0108302247.4d0d849_at_posting.google.com>...
> dear all,
>
> I had exported our database from Oracle7.3.4 with compress=Y and
> imported to 8.1.6.
>
> Some big tables, the extents are kind of huge. For example, one of my
> table have EXTENT INITIAL 200M and NEXT 200M, is that ok? What should
> I set my next and initial. Small and big INITIAL or NEXT have any
> effect?
>
> Thanks a lot
> regards,
> JK

The compress=y option tells Oracle on import to allocate the initial extent set equal to the size the table was taking before export. This setting is a hold over from the days when it was thought that objects needed to be in one extent as multiple extents were thought to be bad for performance (which we should all know by now is not true). The table could be 90% empty, but it is holding the space for 100% of the data.

Since you have version 8.1.6 you should consider adopting the uniform extent feature and organizing your objects into tablespaces based on expected total size and hence a particular extent size per tablespace.

Just my opinion.

• Mark D Powell --