Xref: alice comp.databases.oracle.server:46489
Path: alice!news-feed.fnsi.net!news.idt.net!news-peer.gip.net!news.gsl.net!gip.net!den-news-01.qwest.net!news-feeds.jump.net!nntp2.dejanews.com!nnrp1.dejanews.com!not-for-mail
From: dgriffiths@my-dejanews.com
Newsgroups: comp.databases.oracle.server
Subject: Locking Tables Via SQL*Plus, ODBC
Date: Tue, 20 Apr 1999 19:57:19 GMT
Organization: Deja News - The Leader in Internet Discussion
Lines: 23
Message-ID: <7fim6t$b8o$1@nnrp1.dejanews.com>
X-Article-Creation-Date: Tue Apr 20 19:57:19 1999 GMT
X-Http-User-Agent: Mozilla/4.0 (compatible; MSIE 4.01; Windows NT)
X-Http-Proxy: 1.1 x14.dejanews.com:80 (Squid/1.1.22) for client 206.87.129.196

We're having a strange problem with locking tables in back-end applications.

We have to instances of the application that "share" the data for processing.
In order to guarantee consistancy, one instance will lock the table, process
the data, and then unlock the table.

It didn't seem to be working in ODBC if the applications log onto the database
with the same userid and password. If instance A locks the table, and then
instance B locks the table (while instance A still has it locked, and without
the NOWAIT option), it gets locked by B as well. Basically, B can update the
table while A has it locked.

SQL*Plus doesn't allow this to happen. If A has it locked, B will block until
A releases the lock.

Anyone have any ideas?

Thanks,
David
GTE Enterprise Solutions

-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/       Search, Read, Discuss, or Start Your Own