Better send the PL/SQL code and what error message exactly you get
Reza
"The BMA man" <bma_at_NOSPAM.geocities.com> wrote in message
news:39915c0f.27719065_at_news.tele.dk...
> 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.)
>
>
>
Received on Wed Aug 09 2000 - 00:00:00 CDT
