Re: log file sync

From: Tony Hunt <tonster_at_bigpond.net.au>
Date: Wed, 03 Oct 2001 10:30:03 GMT
Message-ID: <LMBu7.116614$bY5.580330@news-server.bigpond.net.au>

The commits force LGWR writes...

I missed the previous post, but why do you need to INSERT, COMMIT, DELETE, COMMIT Can't you use PL/SQL ROLLBACK/SAVEPOINTS or variables to test the values before inserting them to the table? Why do you need to add the value and then delete it again?

If it's temporarily needed while another transaction takes place, can't you store it in a smaller table somewhere?

"Ethan Post" <Blah_at_Blah.com> wrote in message news:OAuu7.19310$Xk4.1337160_at_news1.rdc1.sdca.home.com...
> I always thought log file sync waits primary cause was commiting too
often.
> We have a few jobs that run during the day and this is the primary wait
> event. However during some of my testing regarding potential transaction
> rates for our server (see recent post) I wrote a script that inserts a
> record, commit's, deletes the record, commits for a large table. I am
> getting 140 MB of redo per minute and over 50,000 commits per minute but
no
> log file sync's. Scratching my head on this one. The file layout is
> optimal. - E
>
>
Received on Wed Oct 03 2001 - 05:30:03 CDT