My Oracle Support Banner

Oracle Deadlocks From Event Notification EOEN_MSG Updating Direct Reports Tables (Doc ID 2737382.1)

Last updated on DECEMBER 16, 2020

Applies to:

PeopleSoft Enterprise HCM Human Resources - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms


When the Direct Reports Build runs, the below Transaction Deadlock message is seen at the Oracle database level.

 

ERROR MESSAGE:

The following deadlock is not an ORACLE error. It is a
deadlock due to user error in the design of an application
or from issuing incorrect ad-hoc SQL. The following
information may aid in determining the deadlock:
 
Session 433:
  sid: 433 ser: 32425 audsid: 11274374 user: 270/SYSADM
  flags: (0x100045) USR/- flags2: (0x40009) -/-/INC
  flags_idl: (0x1) status: BSY/-/-/- kill: -/-/-/-
  pid: 141 O/S info: user: oracle, term: UNKNOWN, ospid: 55851
  image: oracle@lx9402
  client details:
  O/S info: user: prhrps01, term: pts/0, ospid: 30297
  machine: lx9359 program: PSSUBHND@lx9359 (TNS V1-V3)
  application name: EOEN_MSG, hash value=851681253
  action name: OnNotify, hash value=3190168843



The issue can be reproduced at will with the following steps:


1. Go to Enterprise Manager and see deadlocks in database which occur at the same time as the Direct Reports Build.


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
Symptoms
Cause
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.