E-PRCS: Recurrence Set To 'Prior Recurrence Has Completed' Prevents The Master Scheduler From Initiating Scheduled Jobsets
(Doc ID 1285534.1)
Last updated on APRIL 04, 2025
Applies to:
PeopleSoft Enterprise PT PeopleTools - Version 8.50 to 8.51 [Release 8.4]Information in this document applies to any platform.
Symptoms
After upgrading to PeopleTools 8.50, certain Scheduled Jobsets are not initiated by the Master Scheduler. In the Master Scheduler log, mstrschdlr_ddmm.log, it shows this error message:
PSMSTPRC.5272 (0) [12/06/10 00:00:26 USER@MACHINENAME](1) =================================Error===============================
PSMSTPRC.5272 (0) [12/06/10 00:00:26 USER@MACHINENAME](1) Database error encountered
PSMSTPRC.5272 (0) [12/06/10 00:00:26 USER@MACHINENAME](2) Info:
PSMSTPRC.5272 (0) [12/06/10 00:00:26 USER@MACHINENAME](2) Section:
PSMSTPRC.5272 (0) [12/06/10 00:00:26 USER@MACHINENAME](2) Info:
PSMSTPRC.5272 (0) [12/06/10 00:00:26 USER@MACHINENAME](2) SQL Stmt: SELECT RUNSTATUS FROM PSPRCSQUE WHERE PRCSINSTANCE = :1
PSMSTPRC.5272 (0) [12/06/10 00:00:26 USER@MACHINENAME](2) =====================================================================
PSMSTPRC.5272 (0) [12/06/10 00:00:26 USER@MACHINENAME](1) =================================Error===============================
PSMSTPRC.5272 (0) [12/06/10 00:00:26 USER@MACHINENAME](1) Database error encountered
PSMSTPRC.5272 (0) [12/06/10 00:00:26 USER@MACHINENAME](2) Info:
PSMSTPRC.5272 (0) [12/06/10 00:00:26 USER@MACHINENAME](2) Section:
PSMSTPRC.5272 (0) [12/06/10 00:00:26 USER@MACHINENAME](2) Info:
PSMSTPRC.5272 (0) [12/06/10 00:00:26 USER@MACHINENAME](2) SQL Stmt: SELECT I.SCHEDULENAME,I.JOBNAMESRC,ÚteTimeOut(I.NEXTSTARTDTTM),ÚteTimeOut(I.RECURDTTM),I.CURRENTJOBINSTANCE FROM PS_SCHDLDEFNINFO I, PS_SCHDLDEFN S WHERE I.NEXTSTARTDTTM <= %CURRENTDATETIMEIN AND S.SCHEDULESTATUS = '1' AND I.SCHEDULENAME = S.SCHEDULENAME AND I.JOBNAMESRC = S.JOBNAMESRC
PSMSTPRC.5272 (0) [12/06/10 00:00:26 USER@MACHINENAME](2) =====================================================================
Further inspection revealed this behavior only happened if the previous Jobset's process instance number was removed from the PSPRCSRQST & PSPRCSQUE tables.
Changes
This behavior started after upgrading to PeopleTools 8.50.
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 |