ETL9.2: Deadlock on timesheet submission causes error in CallAppEngine: TL_CALL_VAL (2,653) FUNCLIB_TL_WEEK.APPLY_RULES.FieldFormula Name:RunValidation
(Doc ID 2450401.1)
Last updated on FEBRUARY 06, 2019
Applies to:PeopleSoft Enterprise HCM Time and Labor - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
On : 9.2 version, Time Reporting
Deadlocks causing users to see "SQL Error" messages.
Employees get message "A SQL error occurred. Please consult you system log for details." when submitted time on the timesheet
Users occasionally experience an error message when submitting a transaction on their timesheets: "A SQL error occurred. Please consult you system log for details."
Looking at the App Server log, I found instances of deadlocks related to the statement: UPDATE PS_TL_VALID_DATA3 SET PROJECT_ID=' ' WHERE TEAM_MEMBER_IND='N'
The table TL_VALID_DATA# is part of the delivered Time Admin process. But the Update statement isn't referencing any of the table keys, which might be causing the deadlock (doing a full-table lock).
2018-09-14T10:17:55.712 FEUERBT@172.31.20.240 (IE 11.0; WIN10) ICPanel] pgRAS1wgIOWwBA 6924440758941935617 FEUERBT (3) File: e:\pt85605d-retail\peopletools\src\psappeng\aedebug.hSQL error. Stmt #: 1725 Error Position: 0 Return: 8603 - [Microsoft][SQL Server Native Client 11.0][SQL Server]Transaction (Process ID 78) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. (SQLSTATE 40001) 1205
Failed SQL stmt: UPDATE PS_TL_VALID_DATA1 SET PROJECT_ID=' ' WHERE TEAM_MEMBER_IND='N'
PSAPPSRV.21580 (5239) [2018-09-14T10:17:55.746 FEUERBT@172.##.##.### (IE 11.0; WIN10) ICPanel] pgRAS1wgIOWwBA 6924440758941935617 FEUERBT (0) CallAppEngine: Application TL_CALL_VAL: AppEngine error. (2,653) FUNCLIB_TL_WEEK.APPLY_RULES.FieldFormula Name:RunValidation PCPC:7311 Statement:69
The issue can be reproduced at will with the following steps:
Submit timesheet while real time rules are on in the installation table
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