You could also specify parallel hints in your sql, and try creating a
loopback database link and run your selects over that.
if you are inserting in a loop don't forget to commit every 5 records,
within the loop. You could also set SORT_AREA_SIZE really small and then do
loads of big sorts.
--
Niall Litchfield
Oracle DBA
Audit Commission UK
*****************************************
Please include version and platform
and SQL where applicable
It makes life easier and increases the
likelihood of a good answer
******************************************
"Billy Verreynne" <vslabs_at_onwe.co.za> wrote in message
news:amec6h$37i$2_at_ctb-nnrp2.saix.net...
> steve wrote:
>
> > I need to "hammer" on the database, causing tremendous amounts of I/O.
> > I have one program that I submit about 30 processes of to a batch queue,
> > and it does 50K inserts to the table (per process), but the machine is
> > still loafing.
>
> Try using full table scans (not using any indexes). This can be done via a
> hint in your SQL SELECT statement, e.g.
> SELECT /*+ FULL(tablename) */ * FROM tablename
>
> Use cartesian joins, e.g.
> SELECT * FROM table1, table2, table3
>
> Combine these with a CREATE TABLE AS SELECT.
>
> In fact, being a newbie you have all the qualifications you need or
> hammering Oracle. :-)
>
> --
> Billy
Received on Fri Sep 20 2002 - 09:36:01 CDT
