Troubleshooting PeopleSoft Process Scheduler Contents 2 Generic troubleshooting 2.

1 PSDSTSRV Dumps - Oracle reference ID: 200966614

Reports stuck in posting status Look for the following in Distribution agent log ( PSDSTSRV_MMDD.LOG ) PSDSTSRV.29517 (43) [11/19/10 12:16:51 PostReport](1) (JNIUTIL): Java exception thrown: java.io.IOException: Error reading from server PSDSTSRV.29517 (43) [11/19/10 12:16:51 PostReport](3) HTTP transfer error. PSDSTSRV.29517 (43) [11/19/10 12:16:51 PostReport](3) Post Report Elapsed Time: 388.8700 SOLUTION: Shutdown process scheduler on cccune46 Shutdown web server on cccune109 Shutdown app server on cccune109 Startup app server on cccune109 Startup web server on cccune109 Startup process scheduler on cccune46 Generic troubleshooting PSDSTSRV Dumps - Oracle reference ID: 200966614 To ident ify or isolate process that would force the Distribution Agent to dump, NOT the reason for the crash. ISSUE: If your process schedulers distribution agent all of a sudden starts crashing an d repeated attempts to restart the server results in continuing PSDSTSRV dump fi les, one quick method to resolve a crashing PSDSTSRV.exe would be to isolate the process that is forcing the distribution agent down. SOLUTION: The distribution agent scans a database table called PS_CDM_LIST, entries in thi s table contain information about report output scheduled to be transfer by the PSDSTSRV.exe to the report repository on the web server. This table can grow qui te large so to further isolate which report could be forcing the distribution ag ent down run the following query: SELECT * from PS_CDM_TRANSFER PS_CDM_TRANSFER is a staging table used by the Distribution Agent that identifie s which reports the agent is currently attempting to transfer, when the report i s transferred each record entry in this table will be deleted so ideally this ta ble should contain no records if nothing is being posted. If PS_CDM_TRANSFER contains a number of records (which are most likely a backlog of reports ready for transfer), identify the lowest TRANSFERINSTANCE value in t his table. From there issue another SQL query on PS_CDM_LIST using that transfer instance number: SELECT * FROM PS_CDM_LIST where TRANSFERINSTANCE = '####' This query will give you the process instance number of the report; goto Process Monitor and confirm that this process is still in a posting status. The quick a

nd easy method of stopping a PSDSTSRV crash would be to run the following SQL an d set the runstatus and/or distribution status to NOT POSTED. 1)DELETE from PS_CDM_TRANSFER where TRANSFERINSTANCE ='###' (All Tools releases) 2)UPDATE PS_CDM_LIST SET DISTSTATUS = '4' where TRANSFERINSTANCE = '###' (All To ols releases) 3)UPDATE PSPRCSRQST SET DISTSTATUS ='4' where PRCSINSTANCE = '###' (Tools 8.44 a nd above) UPDATE PSPRCSRQST SET RUNSTATUS = '12'where PRCSINSTANCE = '###' (Tools 8.1x, 8. 2x, 8.4x -8.43) 4)UPDATE PSPRCSQUE SET DISTSTATUS = '4' where PRCSINSTANCE = '###' (Tools 8.44 a nd above) UPDATE PSPRCSQUE SET RUNSTATUS = '12' where PRCSINSTANCE = '###' (Tools 8.1x, 8. 2x, 8.4x - 8.43) Restart the scheduler and immediately monitor the PSDSTSRV status thru PSADMIN, also, continue to run the SQL Query SELECT COUNT(*) from PS_CDM_TRANSFER The number of records in this table should begin to decrease as the backlog of r eports are transferred and rows are deleted, if the number of rows does not star t decreasing after some time and the PSDSTSRV.exe is no longer running thru PSAD MIN, then repeat this cycle of events until such time as the offending process i nstance is identified and the PSDSTSRV.exe remains up.