Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: switching to 'direct path read' should help prevent thrashing buffer cache ?

Re: switching to 'direct path read' should help prevent thrashing buffer cache ?

From: joel garry <joel-garry_at_home.com>
Date: 20 Dec 2006 17:08:01 -0800
Message-ID: <1166663281.653612.287310@73g2000cwn.googlegroups.com>

bdbafh wrote:
> On Dec 20, 5:21 pm, p.santos..._at_gmail.com wrote:
> > Folks,
> > Our environment is neither an OLTP nor a DSS system. We have
> > transactions that cross boundaries.
> >
> > Particularly we have these one of jobs that many of our customers run
> > at any time during the
> > day in which they chose to clear a table column.
> > Most clients clear anywhere from 1 million rows to 11 million rows
> > per job.
> >
> > The pseudo-code and SQL looks like this:
> >
> > while SQL%ROWCOUNT < 500,000
> > do
> > UPDATE DEMO_<CLIENT_ID>
> > set col1= null,
> > col2= null,
> > col3= null
> > WHERE ( col1 is not null OR
> > col2 is not null OR
> > col3 is not null ) AND ROWNUM <= 500,000;
> > commit;
> > done.
> >

>

> Had an oracle version been posted, someone might be able to post a note
> about the use of array processing, such as BULK COLLECT.
> But as no oracle version information was posted no one will likely do
> so.

But you could be a good bdbafh and note the commit inside the loop.

jg

--
@home.com is bogus.
http://crave.cnet.co.uk/0,39029477,49286226,00.htm
Received on Wed Dec 20 2006 - 19:08:01 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US