Re: truncate has execessive row cache wait

Use exchange partition instead of truncate will be the solution,

Sent via BlackBerry by AT&T

-----Original Message-----
From: "Mark W. Farnham" <mwf_at_rsiz.com>

Date: Fri, 19 Sep 2008 03:46:22
To: <oracledbaquestions_at_gmail.com>; <oracle-l_at_freelists.org> Subject: RE: truncate has execessive row cache wait

?table part of a cluster

?local or dictionary tablespace management

?Oracle version

?ASM

?ASSM or freelists (aka manual to make it sound like you have to do work,
previously not called anything because that was all there was)

?checked for locks (or repeat on a test system with no possible contention)
 

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Dba DBA
Sent: Thursday, September 18, 2008 10:33 PM To: oracle-l_at_freelists.org
Subject: truncate has execessive row cache wait  

well it was a truncate table drop storage.

is that a known result of running a truncate with the "drop storage" option
?

took 15 minutes to do a simple truncate on a 2.4 GB table. 1 mb extent sizes. not alot going on.
was waiting on row cache wait ?

--
http://www.freelists.org/webpage/oracle-l