E1: DB: Case Study on Deadlocks in EnterpriseOne Applications (Doc ID 1228683.1)

Last updated on MAY 30, 2017

Applies to:

JD Edwards EnterpriseOne Tools - Version SP23 and Prior and later
Information in this document applies to any platform.
*** check for relevance 9-APR-2012 ***


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:

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

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms