I think there is an init.ora parameter to change the default transaction
level. I have never used it,and I think the docs recommend against doing
so.
Jim
"Niall Litchfield" <n-litchfield_at_audit-commission.gov.uk> wrote in message
news:3ddcb924$0$1290$ed9e5944_at_reading.news.pipex.net...
> "Michael Howitz" <mhowitz_at_firemail.de> wrote in message
> news:3DDC9B9F.6030800_at_firemail.de...
> > sorry, but i do not get it. (after searching half an our using google)
> > so i will discribe my problem a bit more precise:
> > we have some oracle-installations in our company with different oracle
> > versions from 8.1.5 to 9.2. all seem to behave equal but one has
> > problems with transactions. it seems to have another (i.e. higher)
> > transaction isolation level by default. (it is version 9.2.0.1.0)
>
> the default level in all versions (including 9.2) is read committed. This
> can only be changed on a per transaction or per session basis. What
problems
> are you having that you attribute to a difference in isolation level?
>
> > is this possible? is there a way to find which transaction isolation
> > lever is currently set?
>
> I am not aware of one.
>
>
> --
> Niall Litchfield
> Oracle DBA
> Audit Commission UK
> *****************************************
> Please include version and platform
> and SQL where applicable
> It makes life easier and increases the
> likelihood of a good answer
>
> ******************************************
>
>
Received on Thu Nov 21 2002 - 05:33:22 CST
