even better, you should take STATSPACK snapshots during insert, to exactly
know what is happening....
"Burt Peltier" <burttemp1REMOVE_THIS_at_bellsouth.net> a écrit dans le message
de news:SoTAa.16403$iD2.2012_at_fe08.atl2.webusenet.com...
> I think you will need to provide more info before anyone can really help..
> just a few quick questions I can think of :
>
> Look for machine bottlenecks like CPU's pegged out, memory maxed out,
disk's
> I/O real high , or unsual network activity. Some of these assume you have
> looked at this in the past and have a vague idea of what's normal looking
> (especially network activity and disk I/O).
>
> Are there other users logged in, other databases on same machine?, or any
> other things going on on the same machine?
>
> What does your init.ora look like?
>
> What does your temporary tablespace and rollback setup/usage look like?
>
> When you update, are you increasing the size of the rows a lot? Seems you
> could be having a lot of row-chaining.
>
> Are you updating indexed values?
>
> Etc...
>
> --
>
> "Mike Harris" <badshah2000_at_hotmail.com> wrote in message
> news:a3e27c56.0305271521.1c481750_at_posting.google.com...
> > Hi, I am running Oracle 8.1.7 on W2K Professional (SP/3). Athlon
> > 1400MHz, 768MB RAM.
> >
> > note: redo logs are DISABLED for faster updates (it's a staging
> > machine)
> > I start a transaction
> > I do an insert in a table (it's not an overly wide table, about 30
> > fields wide) which results in about 12000 new rows.
> > I then start a process (within the same transaction) which updates
> > each new row doing some more DB processing.
> > As the number of rows being updated hits about 7000 mark, database
> > starts to slow down. I am sure that it's gradually slowing down, but
> > that's when I start noticing it. When it has updated about 8000, it's
> > realy slow. And when it's close to 8500 mark, it's realy slooooww.
> > Then it goes so slow that I haven't seen it finish all 12000 rows (my
> > patience neven seems to side with me).
> >
> > What gives? In every single case, I ended up killing the session. And
> > that started oracle in a looooong clean up cycle. It is pure hell. Can
> > you please recommend a faster way to deal with this transaction hell?
> > Yes, all of it has to be inside a transaction. Any parameters I can
> > play with? More RAM? ???
> >
> > thanks a lot!
> > Mark.
>
>
>
Received on Tue May 27 2003 - 20:49:35 CDT
