ORACLE record locking acting like page locking

ORACLE record level locking? When I try to update an EXPIRATIONDATE field in approximately 23,0000 records with SQL*Plus, my DLL, which uses the Oracle Objects for OLE (OO402 Class Library) has to wait a long time (normally less than 3 seconds becomes about 1.5 minutes) to create a dynaset.

The dynaset is just a simple SELECT statement (no update) with flags ODYNASET_READONLY | ODYNASET_NOCACHE. It's as if Oracle is doing page or block level locking. From what I've read, I know this is not the case, so I wonder what's going on.

I am running Oracle Workgroup Server 7.3.2.1.1 on Windows NT. We have a simple database for our Website that just verifies a username/password/access rights/expiration dates.

My SQL*PLUS statments are:
SET AUTOCOMMIT ON;
UPDATE UDBA SET EXPIRATIONDATE='19970331235959' WHERE EXPIRATIONDATETIME='19970228235959'; Since the SQL commit is immediate I would expect the performance of my DLL dynaset creation to change very little. Instead it can take a user 1.5 minutes to log in!

Your thoughts and comments would be greatly appreciated.

-------------------==== Posted via Deja News ====-----------------------
      http://www.dejanews.com/     Search, Read, Post to Usenet