Discussions
Categories
- 196.7K All Categories
- 2.2K Data
- 235 Big Data Appliance
- 1.9K Data Science
- 449.8K Databases
- 221.5K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 549 MySQL Community Space
- 477 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 532 SQLcl
- 4K SQL Developer Data Modeler
- 186.8K SQL & PL/SQL
- 21.2K SQL Developer
- 295.3K Development
- 17 Developer Projects
- 138 Programming Languages
- 292K Development Tools
- 104 DevOps
- 3.1K QA/Testing
- 645.9K Java
- 27 Java Learning Subscription
- 37K Database Connectivity
- 153 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 17 Java Essentials
- 158 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 203 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 390 LiveLabs
- 37 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.6K Other Languages
- 2.3K Chinese
- 170 Deutsche Oracle Community
- 1K Español
- 1.9K Japanese
- 230 Portuguese
How Can I Avoid Table Locks that normally shows data in query mode.

I am using Database 12c with Oracle Forms 12.2.1.3.0 (Production)
I have one module that loads or shows twelve month history of Student and end use can update the any record as per required.
But I have noticed that, before posting of committing, The underlying table becomes under lock and at the same time if there any insert in the same table, entire the process stucks.
I am trying to use View but form is not allowing to update the view in case I want to use Instead of triggers.
Please guide me, how can I hold the update at once without facing any locks because this table is used for updates and insert from other modules too.
Thanks.
Best Answer
-
I failed to understand the problem:
1. The program locks the database rows, even though the user did not change Forms rows?!
2. The program locks the database rows as soon as the user changes the Forms rows, even though the user did not give Save (= COMMIT_FORM)?
The second problem can be easily solved - change the block property Locking Mode from Automatic (= Immediate) to Delayed.
Regards,
Zlatko
Answers
-
I failed to understand the problem:
1. The program locks the database rows, even though the user did not change Forms rows?!
2. The program locks the database rows as soon as the user changes the Forms rows, even though the user did not give Save (= COMMIT_FORM)?
The second problem can be easily solved - change the block property Locking Mode from Automatic (= Immediate) to Delayed.
Regards,
Zlatko
-
It's perfect.
"change the block property Locking Mode from Automatic (= Immediate) to Delayed."
I changed it and now there is no locking.
Thanks