Re: Table-locks

bma_at_NOSPAM.geocities.com (The BMA man) wrote:
>On Wed, 09 Aug 2000 20:18:06 +0200, Stefan Roesch
><Stefan.Roesch_at_t-online.de> wrote:
>
>>>
>>
>>Run the script catblock and afterwards utlblockt. You will get
 an lock
>>graph which will help in what kind of locks are held.
>
>Tried to do so.
>Am I supposed to run both of these under the system-account?
>Anyway - it didn't give me any output - not usefull output that
 is.
>
>So please if you could help me some more.
>
>(I will include the original posting in this mesage, for you to
 see my
>ideas of the problem).
>
>Regards
>
>Brian Madsen
>
>>
>>Hope this helps
>>Stefan
>>
>>> Hello group.
>>>
>>> I have a little problem - hope someone can help :-))
>>>
>>> My system is Oracle 7.3 running on Win NT 4.0
>>>
>>> As far as I know, normally Oracle doen't lock on table-
 level, but
>>> locks on a record-level.
>>> And - as far as I know - a select, even into a cursor, does
 NOT lock
>>> anything, only if it's a select for update.
>>>
>>> Am I on level so far?
>>>
>>> My problem now is I have a program (c++/pro*c/sql-net) that
 does a lot
>>> of creating data from external sources.
>>> Recently someone made som PL/SQL which among other things
 opens a
>>> cursor (NOT select for update, only select) on a table, my
 program
>>> inserts data into.
>>>
>>> Now it seems that when the PL/SQL runs it locks the entire
 table????
>>> Anyway my program fails to do a simple insert into if the
 PL/SQL
>>> program is running.
>>>
>>> Can someone tell me if there is different rules for locking
>>> tables/record when it is PL/SQL than otherwise? Or can you
 tell me
>>> what the problem could be beside som locks?
>>>
>>> Finally I will like to excuse my bad english - I'm from
 Denmark :-)
>>>
>>> Regards - and hope to hear from you in this group
>>>
>>> Brian Madsen
>>> Senior software construktor.
>>>
>>> (IF you reply by e-mail please do remove "NOSPAM." from my
 address.)
>>

All Oracle provided database $ORACLE_HOME/rdbms/admin/cat* scripts should only be ran as sys or internal. If you ran catblock as system, delete the objects and rerun as sys.

You should be able to run utllockt.sql as any id with create table privilege and select any table privilege.

• Mark D. Powell -- The only advice that counts is the advice that you follow so follow your own advice. --

  ---

Got questions? Get answers over the phone at Keen.com. Up to 100 minutes free!
http://www.keen.com Received on Mon Aug 14 2000 - 08:29:21 CDT