Originally posted by tamilselvan
Do a simple test to check the oracle release is bug free with the LMT.
I found a bug in LMT in 9i.

Create a LMT with initial and next size 16K.
Create a table on this new tablespace.
Insert rows using a PL/SQL block so that number of extents can reach around 30000. Then truncate the table. Wait and watch how much time Oracle needs to truncate the table.
If the table is truncated within 5 to 10 minutes, then you are safe and you can use LMT. If not, do not use LMT.
With all due respect, this is one of the most silly tests I've ever heard of.

First, I don't see what bug you haver found with LMT in 9i. At least not from the above description. Can you be more specific about that bug of yours?

Second, with LMT you don't specify INITIAL and NEXT at all, you either specify UNIFORM extent size or AUTOALlOCATE.

Third, no one in his right mind will have segments of 30.000 extents, neither in LMT nor in DMT. So what is the point of that test?

Fourth, just out of curriosity, have you tried to truncate a table of 30.0000 extents in dictionary managed tablespace? What was the timing? What is the whole big deal with those magic facts/numbers (LMT + 30.000 extents + TRUNCATE + 5-10 minutes)?

Fifth, even if the above test proves there is/there is not a specific bug (that I can't see) with LMT, it does not proove that "then you are safe and you can use LMT" at all - there could be tens of bugs related with LMT that this test doesn't even touch! But this is not a point - there could be tens of bugs related to DMT that noone of us is avare of too! So Sricky, don't waste your time, switch to LMT wherever possible and whenever you are sure that known LMT bugs are not applicable to your specific situation/bussiness rules.

[Edited by jmodic on 08-27-2002 at 05:00 PM]