My Oracle Support Banner

E1: DB: Custom Stored Procedure Causes Deadlocks (Doc ID 1301427.1)

Last updated on MARCH 16, 2020

Applies to:

JD Edwards EnterpriseOne Tools - Version SP23 and Prior and later
Information in this document applies to any platform.


This document is not intended to guide customers on how to write/put stored procedures in the database.

This document deals with possible locking (Deadlocks) or application failure which is caused by the implementation of stored procedures in the relational database system.

In general, it is hard to determine the root cause of the issue when additional routine is written outside JDE, so it is important to inform Oracle Support of any changes made at the database level (which may include: function, stored procedures, table triggers and view).

Symptoms appear in EnterpriseOne that return multiple errors/problems. One example of these issues are:


Changes are as follows:


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.