SCRTY_OPRCLS Process Fails When It Runs At The Same Time With TL_TIMEADMIN In HCM
(Doc ID 2315870.1)
Last updated on FEBRUARY 05, 2019
Applies to:PeopleSoft Enterprise HCM Human Resources - Version 9.2 and later
Information in this document applies to any platform.
SCRTY_OPRCLS process fails when it runs at the same time with TL_TIMEADMIN in HCM. All users in the system lose access to the data. This happens approximately once a month. Processes were scheduled to run at the same time.
The process fails on the final step with the following error:
"File: /vob/peopletools/src/psappeng/aedebug.hSQL error. Stmt #: 1723 Error Position: 0 Return: 805 - ORA-00001: unique constraint (SYSADM.PS_SJT_OPR_CLS) violated
Failed SQL stmt: INSERT INTO PS_SJT_OPR_CLS (OPRID , CLASSID , SEC_RSC_FLG) SELECT OPRID , CLASSID , SEC_RSC_FLG FROM PS_SJT_OPR_CLS_TMP
Process 368997 ABENDED at Step SCRTY_OPRCLS.UpdAll.Step06 (SQL) -- RC = 805 (108,524)
Process %s ABENDED at Step %s.%s.%s (Action %s) -- RC = %s
PSAESRV completed service request at 09.00.31 2017-09-29"
When the process is rerun manually, it runs to success.
Is there any way the process could be set up to roll back its changes in case it runs into another issue like this in the future?
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