Process Scheduler Issues

Issue 1: Generating Integration Broker .trc file with messages like (PublicationManager::Publish()), eventhough IB services are down Resolution: I find this as a bug with Peoplesoft. This wont do any harm ,but will result in unnecesssary generation of trace files. To avoid this change the parameter LogFence=0 in psprcs,cfg file and reboot the process scheduler . Issue2: Peoplesoft Process scheduler-Processes getting queued. Resolution There are three tables in Peoplesoft which should be in sync always PSPRCSRQST, PSPRCSQUE and PSPRCSPARMS Execute the below query to check the tables are in synch . select count(*) from PSPRCSRQSTunion allselect count(*) from PSPRCSQUEunion allselect count(*) from PSPRCSPARMS; If the counts are different execute the delete queries to synch them and restart the scheduler. This will resolve the issue DELETE FROM PSPRCSQUE QUE WHERE NOT EXISTS (SELECT 'X' FROM PSPRCSRQST RQST WHERE RQST.PRCSINSTANCE = QUE.PRCSINSTANCE); DELETE FROM PSPRCSPARMS PARMS WHERE NOT EXISTS (SELECT 'X' FROM PSPRCSQUE QUE WHERE QUE.PRCSINSTANCE = PARMS.PRCSINSTANCE); You can also check when the process is scheduled to run if it remains queued after doing the above synch up. Also check whether there is any timezone difference between your DB,App and PRcs server machines. This can also cause the processes to get queued. Issue:3 Database error encountered: SELECT DAYSBEFOREPURGE FROM PS_PRCSPURGELIST WHERE RUNSTATUS = '9'. When starting the Process Scheduler, this error message appears in the SCHDLR_mmdd.log. This is preventing the purge process from running Resolution This is a potential issue for customers upgrading to 8.4 or new customers. The applications upgrade path or installation instructions should include a step to run the prcspurgelist.dms. Some products like CRM and EPM don't include it.

Most customers reporting this issue are using CRM or EPM. The prcspurgelist.dms populates the PS_PRCSPURGELIST with the information seen in the System Settings System Purge Options. The PS_PRCSPURGELIST table must contain this information before the purge process can run. Issue4 The Process Scheduler purge process is not running. The following messages were found in the scheduler log file, schdlr_mmdd.log. "PSMSTPRC.1278194 (0) [03/31/05 01:00:29 PSAPP@machinename](0) Purging expiredrequest(s)...PSMSTPRC.1278194 (0) [03/31/05 01:00:30 PSAPP@machinename](-1) Debuggingdisabled. Comm unication failure during connect(): 79. (143,9)PSMSTPRC.1278194 (0) [03/31/05 01:00:30 PSAPP@machinename](1) Debugging has beenforcibly disabled do to a Configuration or Communication problem.PSMSTPRC.1278194 [03/31/05 01:00:32 PSAPP@machinename](1) (Handler):PSMSTPRC.1278194 (0) [03/31/05 01:00:32 PSAPP@machinename](3) Unable toinitiate purge due to unsuccessful schedule ofthe request using PT_PRCS Application Class" Resolution The PTPT1200 and PTPT1000 permission lists are required for the Process Scheduler user. These can be made available to the user by adding the roles PeopleTools and PeopleSoft User.For additional information on the security needed for the purge, Issue5 AE programs stays in initiated state If you check PSAESRV log you see an error message like'RunAeAsync1 parameter data validation failed' Resolution: Check the trace settings associated with the program setting trace options on an application engine process but using override instead of append in the parameter list can be the issue .