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

I believe that both COMMIT and ROLLBACK
are implemented as SQL commands and as
calls to the database kernel. This is probably why you can have an autocommit without being able to see any sign of a commit in the sql area.

The only visibility is through v$sesstat under the 'user commits' and 'user rollbacks' statistics.

--
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
____USA_(CA, TX)_August


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





Hans de Git wrote in message
<72383d4a.0301060151.4ede21a9_at_posting.google.com>...


>Thanks to all. For the record: I am totally against Autocommit. The

>application we use is written for multiple databases: MS SQL server,

>MySQL and Oracle. I think that's why the vendor doesn't care about

>Oracle's superior transaction management, which is not very clever.

>

>However, if the application issues a sort of 'low level commit', can

I


>still any evidence of this in the v$ views, or perhaps in some x$

>view?