E1: DB: Case Study on Deadlocks in EnterpriseOne Applications
(Doc ID 1228683.1)
Last updated on JUNE 16, 2023
Applies to:
JD Edwards EnterpriseOne Tools - Version SP23 and Prior and laterInformation in this document applies to any platform.
Goal
Through this case study, an actual implementation is discussed to minimize potential deadlocks in EnterpriseOne Distribution, Manufacturing and Financial Modules.
Below are two common tables that can be used to isolate certain transactions:
- F0011 (Batch Header Control Records) Batch header is to be written, when a certain transaction affects General Ledger; to set boundary of transaction
- F00095 (Business Object Reservation) Maintain higher integrity by preventing other users/processes from accessing a certain table simultaneously by recording data into the F00095 - Business Object Reservation table.
Note: Custom Table Triggers and/or Stored Procedures and Functions cause deadlocks. Ensure that any external program does not affect daily transactions. Refer to <Document 1301427.1> E1: DB: Custom Stored Procedure Causes Deadlock in the Database
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| References |