Re: OPEN fails when active set includes a locked row

In <bpayneD795tz.CLy@netcom.com> bpayne@netcom.com (Bob Payne) writes: >We ran an experiment here on both versions 5 and 7 online engines. >Locked a row with one process and tried to update several rows with >another process. We never even got to the update because the OPEN of the >cursor failed when the engine realized that *one* of the rows was locked. >Our ISOLATION LEVEL is set to COMMITTED READ so I'd expect the process >to fail when we FETCHed the locked row, but the failure on an OPEN >really threw me. >Is this normal? Have you run across such a thing? Should it matter >whether we are doing page level locking or row level locking? If the table is set for page-level locking, then locking a row will result in locking all rows that reside in the same page. The problem you are experiencing is quite likely to happen during a "committed read". In general, these settings should be appropriate to your environment in order to achieve the right balance of concurrency and integrity. Edwin Babadaglian edwinb@panix.com