Oracle Deadlocks From Event Notification EOEN_MSG Updating Direct Reports Tables
(Doc ID 2737382.1)
Last updated on NOVEMBER 26, 2021
Applies to:PeopleSoft Enterprise HCM Human Resources - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
When the Direct Reports Build runs, the below Transaction Deadlock message is seen at the Oracle database level.
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:
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
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.
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