Hi, You could get additional information on sorting by setting event 10032 at level 1. Nevertheless, your user's temporary tablespace should point to a nologging LMT temporary tablespace anyway. If sorting and delayed block cleanout is ruled out (if executing the same query generates redo again and again, while there is no other transactions on the table), then maybe the redo is generated by fine grained auditing? Check from dba_audit_policies... Tanel. ----- Original Message ----- From: "Alexander Gorbachev" <gorbyx@xxxxxxxxx> To: <hamcdc@xxxxxxxxxxx> Cc: "oracle-l" <oracle-l@xxxxxxxxxxxxx> Sent: Saturday, February 26, 2005 3:49 PM Subject: Re: Rego generation while executing select statement >I thought that it might be the case, but the output shows that sorts > are in memory. >> > 3 sorts (memory) >> > 0 sorts (disk) > Maybe SQL plus doesn't repors disk sorts correctly. > > Regards, > Alex > > On Sat, 26 Feb 2005 02:27:23 +0000 (GMT), Connor McDonald > <hamcdc@xxxxxxxxxxx> wrote: >> You have a "traditional" temporary tablespace (ie datafile not tempfile)? >> >> If so, the sorting could generating redo >> >> hth >> connor > -- > //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l