Re: ISOLATION LEVEL

I thought the isolation level was 'committed read' not 'read committed'. And that it requires that what you are select has been committed to the database. Since you are attempting to read everything in the table and you are requesting that all the rows be committed, you get an error. One thing that may help would be to use 'set lock mode to wait' in session 2 and when the transaction in session 1 is committed, session 2 will continue. Hope this helps, John RL wrote: > Hi! > > I have a problem with the ISOLATION LEVEL. > > Session 1 > ======== > begin work; > set transaction isolation level read committed; > update table1 > set... > where cle = 1 > ... > ... > > Session 2 > ======== > begin work; > set transaction isolation level read committed; > select * from table1> ... > ... > .. > > In the Session 2 I not be able to read the table "table1" > Error message : record locked > > And I specified "read committed" !!!! > > Could you help me ?