E1: UBE: Slow UBE Processing and Delay in Transition from 'S' to 'P' Status In WSJ With Errors "[SQL_EXCEPTION_OCCURRED] An SQL exception occurred: ORA-04020: deadlock detected while trying to lock object SYS.X$KZSRO" in E1root.log (Doc ID 2956475.1)

Last updated on JUNE 23, 2023

Applies to:

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

Symptoms

The Universal Batch Engines (UBEs) are processing slow and stuck in 'S' (Submitted) status before moving to 'P' (Processing) in WSJ - Work with Submitted Jobs ( P986110B ).
Due to the extended processing time of the UBEs, a large backlog of jobs has accumulated in the WSJ in 'W' status.

The PORTTEST is successful, and no errors are found in the kernel logs.

The e1root.log shows the following error:

Changes

Patched the Oracle Database to Oracle DB version 19.18

Cause

	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.

E1: UBE: Slow UBE Processing and Delay in Transition from 'S' to 'P' Status In WSJ With Errors "[SQL_EXCEPTION_OCCURRED] An SQL exception occurred: ORA-04020: deadlock detected while trying to lock object SYS.X$KZSRO" in E1root.log (Doc ID 2956475.1)

Applies to:

Symptoms

Changes

Cause

To view full details, sign in with your My Oracle Support account.

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