E1: DB: How to Tune JD Edwards EnterpriseOne (E1) UBE Performance with an SQL Database Due to Excessive "Query timeout expired" Before NOLOCK? (Doc ID 2821736.1)

Last updated on MARCH 02, 2022

Applies to:

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

Goal

After upgrading JD Edwards EnterpriseOne (E1) and/or the SQL Database (DB) jobs are now taking longer to process, logs reflecting "Query timeout expired" messages in the UBE Debug log multiple times.

Where can you make tuning changes in JD Edwards E1 to shorten the amount of Query Timeout Retries?

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

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

E1: DB: How to Tune JD Edwards EnterpriseOne (E1) UBE Performance with an SQL Database Due to Excessive "Query timeout expired" Before NOLOCK? (Doc ID 2821736.1)

Applies to:

Goal

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!