Jump to content

- - - - -

Oracle record locking

2 replies to this topic

#1 Ralph Gadsby

Ralph Gadsby


  • Members
  • PipPipPipPip
  • 154 posts
  • Gender:Male
  • Location:United Kingdom

Posted 02 September 1999 - 11:22 AM

I am getting a record lock in an update function which updates loads of files. In order to try to determine which file is being locked I thought I would add lock logics to all the files to write a record with the file name to an error logging file. However the function just sits there staring at me, not going into the lock logic.

Any ideas as to either how to get the lock logic working or how to track down the file being locked?

#2 Guest_bob neville_*

Guest_bob neville_*
  • Guests

Posted 02 September 1999 - 11:43 AM

Not much use to you, but we get the same problem !!
Since the later versions of 4.5 and now 4.6, locking problems with Oracle have got worse. I have raised it with PRO IV but am still awaiting an answer (after 2 months !!).
We have tried UMSG's to see what is going on but have had
no success.

#3 Dan Shannon

Dan Shannon

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 374 posts
  • Gender:Male
  • Location:Australia

Posted 02 September 1999 - 04:01 PM

According to the docs I've read, it's IMPOSSIBLE for PRO-IV to detect a row-level lock in Oracle. This means that the lock state is simply PRO-IV waiting and waiting for Oracle response - it never gets a lock and therefore will never run lock logic.

There *are* ways to analyse who has what locks in Oracle itself - ask your DBA!

Dan Shannon

Reply to this topic


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users