Xref: alice comp.databases.oracle.server:43379
Path: alice!news-feed.fnsi.net!news.idt.net!newshub.northeast.verio.net!worldfeed.news.gte.net!intgwlon.nntp.telstra.net!vic.nntp.telstra.net!news.mira.net.au!newsreader.mira.net.au!dingo.mira.net!not-for-mail
From: schong <schong@werple.mira.net.au>
Newsgroups: comp.databases.oracle.server
Subject: Re: Question about Record Locks
Date: Wed, 17 Mar 1999 05:08:14 -0800
Organization: Internet News services provided by Mira Networking, Australia
Lines: 47
Message-ID: <36EFA93E.1DA3@werple.mira.net.au>
References: <36ef4c25$0$209@nntp1.ba.best.com> <36EF6C8F.3FF1@bhp.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.04Gold (Win16; I)

Todd,

   I think you can still issue select for update in PL/SQL with Select 
   privilege although you won't be able to update it. However select 
   for update will put a RX lock on the row and a Row Share lock 
   on the table.

   Clement


Connor McDonald wrote:
> 
> Todd Matson wrote:
> >
> > If I have SELECT privileges only, is there anything I can do that will
> > create a record lock?
> >
> > Here's my situation: I have written a reporting tool which has SELECT
> > privileges on a database. On rare instances, another application fails when
> > it tries to make updates to the database. Now the DBA is asking me if my
> > reporting application does anything which might cause the updates to fail
> > (for instance, creating exclusive record locks). It is my understanding that
> > I simply cannot do anything to interfere, even if I want to, as long as I
> > have SELECT privileges only. Am I wrong about that?
> >
> > I should mention that I am not running any stored procedures and I'm
> > executing my queries through ODBC.
> >
> > -Todd Matson
> 
> Theoretically no...
> 
> You may wish to confirm exactly what calls your reporting tool is doing
> by issuing either "alter session set sql_trace = true" or
> "dbms_session.set_sql_trace(true)" at the start of the report run and
> use tkprof to see whether it was "sneaking" any update calls in...
> 
> HTH
> 
> 
> --
> ==============================================
> Connor McDonald
> BHP Information Technology
> Perth, Western Australia
> "Never wrestle a pig - you both get dirty and the pig likes it..."

