Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: locks

Re: locks

From: Sybrand Bakker <postbus_at_sybrandb.demon.nl>
Date: Thu, 10 Aug 2006 19:37:09 +0200
Message-ID: <fhrmd2h2nua98g08tt6chhd1mpmnu661vi@4ax.com>


On 10 Aug 2006 10:08:11 -0700, mike7411_at_gmail.com wrote:

>I was reading this online:
>
>------------------------------------------------------------------------------
>Many users, and some programmers, don't understand that terminating a
>process does not always release locks. Switching off your workstation
>before you go home does not always release locks. Locks are released
>only when changes are committed or rolled back.
>------------------------------------------------------------------------------
>
>Isn't it true though that if you end your database connection, the lock
>will go away? If not, how would you send the final commit or rollback?

exiting *normally* will end the database connection and will issue a commit.
What is described above is people just pull the plug from their workstation.
No commit is being issued. How can the backend know the session has ended?
So sqlnet.expire_time was invented. But that doesn't work on many editions of Winblows, as Winblows only allows 16 timers per process.

--
Sybrand Bakker, Senior Oracle DBA
Received on Thu Aug 10 2006 - 12:37:09 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US