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

Last updated on MARCH 16, 2020

Applies to:

Symptoms

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

Changes are as follows:

• Created/called stored procedures to handle Sales Order Header transactions which update table  F4201 (Sales Order Header) at 9:00 in the morning
• Coincidentally you have set EnterpriseOne scheduled job at 9:00 to call R42950 - Sales Order Batch Price/Cost Update which updates the Price and Cost based on F4201/F4211 - Sales Order Header/Detail File

Cause

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