Message-Id: <10614.116592@fatcity.com> From: "Michael Kline" Date: Sat, 9 Sep 2000 21:57:45 -0400 Subject: ROW Level Locking solved This is a multi-part message in MIME format. ------=_NextPart_000_0009_01C01AA8.FC4FF3E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Thanks to Steve Adams, and a few others, we found the PCTFREE was only 10%... We recreated the table with 40%... We got less rows(from 37 to 18), of course, but in testing we were able to lock each and every row separately from 18 separate sessions... One of those "strange" things since I normally use 60% used, 40% free when I create tables, and this one was basically built with TOAD from what I was told. Wasn't something I was looking for... Now the customer will have several databases to be rebuilt, but they can concentrate on the tables that will actually get changes. Funny how it's those little things that "gotcha"... but that's where we come in.. :-) Michael Kline ThinkSpark Richmond, VA 804-744-1545 ------=_NextPart_000_0009_01C01AA8.FC4FF3E0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Thanks = to Steve=20 Adams, and a few others, we found the PCTFREE was only 10%... We = recreated the=20 table with 40%... We got less rows(from 37 to 18), of course, but in = testing we=20 were able to lock each and every row separately from 18 separate = sessions... One=20 of those "strange" things since I normally use 60% used, 40% free when I = create=20 tables, and this one was basically built with TOAD from what I was told. = Wasn't=20 something I was looking for...

Now = the customer=20 will have several databases to be rebuilt, but they can concentrate on = the=20 tables that will actually get changes. Funny how it's those little = things that=20 "gotcha"... but that's where we come in.. :-)

Michael = Kline
ThinkSpark
Richmond,=20 VA
804-744-1545