Numerous Deadlock Errors On OTL Code After Applying HRMS RUP 14
(Doc ID 2755721.1)
Last updated on DECEMBER 09, 2022
Applies to:
Oracle Time and Labor - Version 12.2.9 and laterInformation in this document applies to any platform.
Symptoms
On : 12.2.9 HRMS RUP 13 version,
ACTUAL BEHAVIOR
---------------
After applying HRMS RUP 14 Patches as per note 2656548.1 Applying the R12.HR_PF.C.Delta.14 Release Update Pack (Doc ID 2656548.1) (30096069,30793908), it is observed that many deadlocks are being created related to OTL pl/sql code. This results in trace files being created and they are so numerous they are consuming all of the disk space reserved for trace files on the database server.
The statement having an issue seems to be:
----- Current SQL Statement for this session (sql_id=08pfumd9shm53) -----
DELETE FROM HXT_DET_HOURS_RPT_TEMP WHERE RESOURCE_ID = :B3 AND TC_START_TIME = :B2 AND TC_STOP_TIME = :B1
The EBS code being called during the issue seems to be:
0x1265898db8 5235 package body APPS.HXT_HXC_RETRIEVAL_PROCESS
EXPECTED BEHAVIOR
-----------------------
It is expected not to have so many OTL deadlocks after the application of HRMS RUP 14
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Apply patches for HRMS RUP 14 as per Applying the R12.HR_PF.C.Delta.14 Release Update Pack (Doc ID 2656548.1)
2. Observe deadlock issues coming from OTL code
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, trace files are being created and they are so numerous they are consuming all of the disk space reserved for trace files on the database server.
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 |