Impact of ICX:Session Timeout Profile Setting to Avoid HR_7165_OBJECT_LOCKED Error During Annual Benefits Enrollment in Self-Service
(Doc ID 753888.1)
Last updated on SEPTEMBER 14, 2022
Applies to:
Oracle Advanced Benefits - Version 11.5.10.2 and laterInformation in this document applies to any platform.
Goal
During annual Open enrollment, the following message is received by several employees a day:
ORA-20001: HR_7165_OBJECT_LOCKED: N, TABLE_NAME, ben_prtt_enrt_rslt_f
Cause: An unexpected Oracle error has occurred.
Action: please refer to your system administrator
Cause: An unexpected Oracle error has occurred.
Action: please refer to your system administrator
To avoid this, the "ICX: Limit time" profile was increased to 8 and "ICX:Session Timeout" profile to 180.
If someone goes through benefit enrollment and closes out their session by closing their browser instead of following the close applications in self-service, would it hold the database session open, thus keeping the record locked because of the timeout setting is so long?
Solution
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
Goal |
Solution |
References |