Tuesday 23 June 2015

Process Scheduler is running fine, still processes are in a queued state



Process Scheduler is running fine, still processes are in a queued state.

Things to check :-

1.MAX API Aware setting <-----------Are all active slots filled?

2.MAX Concurrent setting <-------- Are all active slots filled for problem process type?

This setting controls the amount of processes assigned to the corresponding process category that the Process Scheduler can handle at any time. For example, if the Process Category is defined as 5, then a total of 5 processes assigned to that Process Category can be run concurrently. This is limited by the value defined in the Max Api Aware. Once the maximum value has been reached, the Process Scheduler cannot start processing new requests  
3. Is the Process Scheduler successfully updating it's timestamp and heartbeat?
Shutdown the process scheduler, delete it's CACHE directory to clear any possibly corrupt cache,
set TraceSQL=31and LogFence=5 in psprcs.cfg, reconfigure the process scheduler server via the psadmin
utility and then boot up the process scheduler. Gather all log files from the process scheduler LOGS

4.Check the system Time Zone settings. For UNIX, this may be in different places, for example AIX, the /etc/environment file. Make sure the parameter is correctly stated, e.g. PST8PDT, EST5EDT. The middle figure is the UTC offset. Consult UNIX man pages for details on the particular OS

The purge process did not run because the Oprid configured to start the Process Scheduler did not have the required permissions to run the purge process.

  Purge process - Required permissions The PeopleSoft Oprid used to start the Process Scheduler, as defined in the Scheduler's psprcs.cf...