Be glad to tell that to the vendor. You could trace the session , that
would probably tell you. Seems like the vendor is incompetent and I would
be glad to tell them. What vendor?
Jim
"Hans de Git" <hansdegit_at_hotmail.com> wrote in message
news:72383d4a.0212260216.2f629dca_at_posting.google.com...
> Thanks, great suggestion. Try telling that to the vendor...
> I totally agree with you that autocommit sucks and pretty much makes
> Oracle's transaction management useless. However, I still want to see
> those commit statements in v$sqlarea. Any suggestions?
>
> "Jim Kennedy" <kennedy-down_with_spammers_at_attbi.com> wrote in message
news:<bDiO9.107387$qF3.8882_at_sccrnsc04>...
> > Try not using auto commit. The waits will probably go away if you do.
> > Autocommit is not a good idea.
> > Jim
> > "Hans de Git" <hansdegit_at_hotmail.com> wrote in message
> > news: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
Received on Thu Dec 26 2002 - 09:22:12 CST
