350K extents on a table !!
I had left an import running overnight. Looks like I made a mistake in setting up next extent too small for the table (16K). Now, the import that normally completes in 4hrs is running for @ 16hrs and isn't even 30% done. The table has grown to @ 350,000 extents.
I stopped the import. And, now want to truncate/drop the table. Its obviously taking its own sweet time. Is there any way to speed the truncate/drop ?
Its a 9204 db on HP.
why arent you using LMT's? and no, you cannot speed up the truncate
I had the same problem last year.
A table has grown up to 30,000 extents on a LMT. I tried to truncate / drop the table, but it did not work. Finally, I changed the LMT To DMT, and ran the truncate command. It took only 2 min.
1 Always set maxextents to a reasonable size (example 5000 or 6000) at the tablespace level and object level.
2 Precreate the table before import starts and check the storage parameters.
I don't really have a good answer for that question !!
The tablespace holds quite a few tables that differ in sizes. So, its very difficult to decide the extent size of the tablespace.
auto allocate :-) or have new tablespaces where you correctl size your segments - but anyway hope your drop finishes soon :-)
Click Here to Expand Forum to Full Width