Re: truncate has execessive row cache wait

From: ~Jeff~ <jifjif_at_gmail.com>
Date: Mon, 22 Sep 2008 15:49:31 +1200
Message-ID: <363634910809212049s3af95475lb360a220b4a854bc@mail.gmail.com>

if this is DMT, there can be performance issues with large numbers of extents. Very slow recursive lookups hitting sys.uet$ and fet$.

I once had to truncate a table gradually over 24 hrs (..reuse storage..) because it had >30,000 extents, ugh :P