My Oracle Support Banner

ETL9.2 - Reported Time Submission Throwing Deadlock Error On EOAW_SUMM_DTL with MSSQL 2016 Database (Doc ID 2445371.1)

Last updated on JANUARY 31, 2019

Applies to:

PeopleSoft Enterprise HCM Time and Labor - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

On : 9.2 version, Time Reporting

Time and Labor Time timesheet entry is throwing an optimistic lock exception when using Reported Time Approvals and MSSQL Server database. Appserver log is showing deadlocking on the AWE tables.

ERROR
-----------------------
Error seen in PIA by user:

Optimistic Lock exception at %1. Please refresh the page try the same operation again. (18081, 1009) EOAW_CORE.Utils.OnExecute
Name: ThrowOptimisticLockException PCPC:26436 Statement:619
Called from: EOAW_CORE.ENGINE.Thread.OnExecute Name:UpdateTimestamp Statement:655


Errors seen in Appserver log:

Return: 8601 - [Microsoft][SQL Server Native Client 11.0][SQL Server]Transaction (Process ID 57) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. (SQLSTATE 40001) 1205

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Submit Time on classic Timesheet.

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!


In this Document
Symptoms
Changes
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.