If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

You might want to consider creating the tables ahead of time with dynamic sql and importing into them with ignore=y. This will ensure that the LMT extent sizes are used. If you import data from a database using DMT's than Oracle will allocate enough uniform extents to make it original initial extent. Still this doesn't explain a 300K extent size. But I would create the tables ahead of time with no storage clause and import into them.

Re: goofy LMT extent allocation

Originally posted by newbie5 Why is the initial extents are 300K/4MB rather than the uniform size 500K?

Well, the actual size of extents for those tables in the database are not 300K/4M, they are just what they were supposed to be - 500K. What you are looking is the report from DBA/USER_SEGMENTS view. The column INITIAL_EXTENT in that view does not represent the actual size of the extents created, they realy represent the size of the extents as it is requested in their creation DDL statements. Now in case of LMT the size of the extent you requested in your CREATE statement is something totaly different from what actually gets allocated from the tablespace. If you realy want to see the actual size of the extents, you better query DBA/USER_EXTENTS, not DBA/USER_SEGMENTS.

In your case the tables that were exported were created with 300K/4M initial extents and in the dump file this is recorded in their CREATE DDLs. When you import those tables into a LMT, they were created with 500K extents, although the size of the original requested size of the initial extents during the creation is recorded in DBA/USER_SEGMENTS view.

Last edited by jmodic; 02-07-2003 at 05:49 PM.

Jurij ModicASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?