What evidence do you have that this is a locking problem? It sounds toQuote:>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
>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 18.104.22.168.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'
>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.
me as the server is busy.
Have you looked at either System stats (CPU usage, IO rates) or database
stats while this is going on?
How long does the update statement take? How many records are there in
the table altogether and is the expirationdate indexed? If the update is
taking a long time, then you should look into tuning it.
I don't understand your comment about the immediate commit. AUTOCOMMIT
executes a commit after each statement and should have no effect on
performance of either the current session or anybody elses.