Skip to Main Content
  • Questions

  • FRM-40501 (ORA-03114) ORACLE error: unable to reserve record for update or delete

Breadcrumb

Question and Answer

Chris Saxon

Thanks for the question, Piyush.

Asked: March 19, 2021 - 11:08 am UTC

Last updated: March 30, 2021 - 12:17 pm UTC

Version: Oracle Forms (12c)

Viewed 10K+ times! This question is

You Asked

We have an Oracle Forms (12c) application that uses a data model where every table has been replaced by an editioning view. Every existing table has been renamed (to the original name "_CVW" character has been added) and the editioning view has the original table name. When we try to input any data in this application using an Oracle Form then we get the following error "FRM-40501 (ORA-00933) ORACLE error: unable to reserve record for update or delete" once this error appears there is an another error ORA - 03114 and all connections will be lost , This error does NOT occur when we login as the database user that owns the tables and editioning views but for every other database user we get this error , this error is only happening to some selected view and all others views are working fine.

We have done below checking and found no issues in it


1) Tried to update view from backend and it works fine.

2) There is no blocking session and lock in environment.

3) All Synonyms , Privileges ,roles, indexes and table space looks fine.

4) I suspected it maybe be because of Key-Mode properties in form and tried by changing to both Unique and automatic and still it is throwing same error.

5) Generated FMX using other user and still same error prompt.

Please let me know if you face similar issue or have any suggestions regarding this.





and Chris said...

I have minimal experience with Forms, so don't know what's the issue is. Here's some things to check though:

* As this works for the view owner, ensure all other users have the appropriate grants on the editioning view

* Ensure users are connecting to the correct edition

* Ensure the users have the USE permission on the edition

If these don't work, contact support for further help

Rating

  (1 rating)

Is this answer out of date? If it is, please let us know via a Comment

Comments

Forms locking mode

Dojrdje, March 30, 2021 - 11:18 am UTC

It's problem with multi-session work with Forms, when multiple users change records in database Forms block of the same table/view. It's not a problem with views or tables when you do not lock records.

One solution is not to use default database blocks in Forms.
Second solution is to set Forms isolation mode to serializable and block locking mode to delayed. And hope that it will work.
Chris Saxon
March 30, 2021 - 12:17 pm UTC

Thanks for sharing
more

Connor and Chris don't just spend all day on AskTOM. You can also catch regular content via Connor's blog and Chris's blog. Or if video is more your thing, check out Connor's channel and Chris's channel from their Youtube channels. And of course, keep up to date with AskTOM via the official twitter account.

More to Explore

Design

New to good database design? Check out Chris Saxon's full fundamentals class.