Re: autocommit ON but no commits visible in v$sqlarea

With autocommit, the front-end is probably sending a low-level commit call to the database, rather than an explicit execution of a "commit;" statement.

The autocommit is probably the cause of your 'log file sync' problem. Every time you commit, your session has to post LGWR to pad the (perhaps very small) amount of redo buffer that you have generated and write it to disc - and the session will suspend until posted back by LGWR that the write is complete.

Your process will be waiting on "log file sync" and whilst LGWR is doing its thing, any other process that also issues a commit has to wait in the same state until LGWR returns, notices that they have a pending commit, and clears the outstanding log buffer to disc.

--
Regards

Jonathan Lewis
http://www.jlcomp.demon.co.uk

Coming soon a new one-day tutorial:
Cost Based Optimisation
(see http://www.jlcomp.demon.co.uk/tutorial.html )

Next Seminar dates:
(see http://www.jlcomp.demon.co.uk/seminar.html )

____England______January 21/23


The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html





Hans de Git wrote in message
<72383d4a.0212250316.bdf8945_at_posting.google.com>...


>Hi,

>

>We use an OCI application which connects to our database using the

>autocommit setting ON. When I emulate such a session using SQL+ (set

>autocommit on) I cannot see any COMMIT statements in v$sqlarea. How

is


>that possible? I always believed that ALL changes to the database

were


>visible in the v$ views....

>

>I would like to have some kind of control over those sessions,

because


>we are experiencing a lot of waits on the 'log file sync' event,

which


>pretty much prevents us from allowing more users to use this

>application concurrently (the wait would grow to unacceptable

>proportions).

>

>Any suggestions would me much appreciated.

>

>HTH,

>

>Hans de Git