Re: tuning a massive delete

2003-09-18 Thread Binley Lim
In this example, yes, looks like you need a union. - Original Message - To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]> Sent: Thursday, September 18, 2003 12:44 PM > Perhaps this small example can make it clear? > I have two tables, orders and order_to_delete. > I want to

RE: tuning a massive delete

2003-09-17 Thread Jacques Kilchoer
Perhaps this small example can make it clear? I have two tables, orders and order_to_delete. I want to find orders to KEEP - i.e. the order_id is not in table order_to_delete, or it's in table order_to_delete with a status 'N'. If I'm using outer joins, I think I need a a union, nicht wahr? drop

Re: tuning a massive delete

2003-09-17 Thread Binley Lim
On a general note, this older outer join syntax to simulate a not-in requires ALL the "b" columns to include the (+) sign, including the "nvl...", except the "b.cusip is null", which is the not-in itself. If you miss one, the logic is completely changed. 9i's new syntax does outer-joins by doing t

Re: tuning a massive delete

2003-09-17 Thread Stephane Faroult
[EMAIL PROTECTED] wrote: > > create table ani_prx_faster parallel (degree 5) nologging > as > select b.* > from bo_owner_master.ani_prx b, > bo_owner_stage.ani_prx a > where a.cusip = b.cusip (+) >and a.fund_no = b.fund_no (+) >and a.add_cymd = b.add_c

RE: RE: tuning a massive delete

2003-09-17 Thread rgaffuri
ECTED]> > Date: 2003/09/17 Wed PM 02:19:40 EDT > To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]> > Subject: RE: RE: tuning a massive delete > > Well, large sort area size would certainly help, as well as the parallel > hints. > As for the bitmap index

RE: RE: tuning a massive delete

2003-09-17 Thread Govindan K
:39:49 AMTo: [EMAIL PROTECTED]Subject: RE: RE: tuning a massive delete Ryan - One solution that is often suggested would be to copy the rows you wish to retain to another table, then truncate the table. Oracle is relatively slow at deletes compared to inserts. Would this method work for you? Dennis Wi

RE: RE: tuning a massive delete

2003-09-17 Thread Mladen Gogala
IL PROTECTED] On > Behalf Of [EMAIL PROTECTED] > Sent: Wednesday, September 17, 2003 1:25 PM > To: Multiple recipients of list ORACLE-L > Subject: Re: RE: tuning a massive delete > > > i tested the minus in the explain plan and the estimate was > very large. dont i need a lar

Re: RE: tuning a massive delete

2003-09-17 Thread rgaffuri
t ORACLE-L <[EMAIL PROTECTED]> > Subject: RE: tuning a massive delete > > How abuout: > create table ani_prx_new parallel (degree 5) nologging > as > ( select * from ani_prx > minus > select * from from bo_owner.ani_prx > where ba_recode='V') >

Re: RE: tuning a massive delete

2003-09-17 Thread rgaffuri
recipients of list ORACLE-L <[EMAIL PROTECTED]> > Subject: RE: tuning a massive delete > > How abuout: > create table ani_prx_new parallel (degree 5) nologging > as > ( select * from ani_prx > minus > select * from from bo_owner.ani_prx > where

RE: Re: RE: tuning a massive delete

2003-09-17 Thread Stephane Faroult
gt; > >ill try it, but i think exists is faster. we dont >want to do an index scan here and my hash_area_size >isnt real big. >> >> From: "Richard Ji" <[EMAIL PROTECTED]> >> Date: 2003/09/17 Wed PM 12:04:56 EDT >> To: Multiple recipients of

RE: tuning a massive delete

2003-09-17 Thread Mladen Gogala
How abuout: create table ani_prx_new parallel (degree 5) nologging as ( select * from ani_prx minus select * from from bo_owner.ani_prx where ba_recode='V') / I assume that the description of the bo_owner.ani_prx is identical to the description of the ani_prx. Furthermore, a bitmap index on

RE: RE: tuning a massive delete

2003-09-17 Thread Kevin Toepke
hard Ji" <[EMAIL PROTECTED]> > Date: 2003/09/17 Wed PM 12:04:56 EDT > To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]> > Subject: RE: tuning a massive delete > > Try anti hash join. > > -Original Message- > Sent: Wednesday, September 17,

RE: RE: tuning a massive delete

2003-09-17 Thread DENNIS WILLIAMS
lt;[EMAIL PROTECTED]> > Subject: RE: tuning a massive delete > > Try anti hash join. > > -Original Message- > Sent: Wednesday, September 17, 2003 11:45 AM > To: Multiple recipients of list ORACLE-L > > > i have a table with 27 million records that is about

Re: RE: tuning a massive delete

2003-09-17 Thread rgaffuri
hash_area_size isnt real big. > > From: "Richard Ji" <[EMAIL PROTECTED]> > Date: 2003/09/17 Wed PM 12:04:56 EDT > To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]> > Subject: RE: tuning a massive delete > > Try anti hash join. >

RE: tuning a massive delete

2003-09-17 Thread Richard Ji
Try anti hash join. -Original Message- Sent: Wednesday, September 17, 2003 11:45 AM To: Multiple recipients of list ORACLE-L i have a table with 27 million records that is about 1.2 GB in size. I have a 'staging table' with 18 million records. 16 million records have a 'delete' flag. I