Certain times, we find
distribution status for a huge number of processes is Not Posted, which could
happen for many reasons. In this case, resending the content from PIA process
monitor page for each single process is not efficient and is very time
consuming.
Solution:
We can update few tables
playing role in sending the output reports to report repository .Run the below
update statements on the database :
UPDATE PSPRCSRQST SET DISTSTATUS=7 where DISTSTATUS=4;
UPDATE PSPRCSQUE SET DISTSTATUS=7 where DISTSTATUS=4;
UPDATE PS_CDM_LIST SET DISTSTATUS = '8',TRANSFERINSTANCE = 0 WHERE DISTSTATUS=4;
After updating the
distribution status in respective tables, distribution agent takes up the
request and posts the files to report repository.UPDATE PSPRCSQUE SET DISTSTATUS=7 where DISTSTATUS=4;
UPDATE PS_CDM_LIST SET DISTSTATUS = '8',TRANSFERINSTANCE = 0 WHERE DISTSTATUS=4;
It is confusing why diststatus=8 in PS_CDM_LIST table not 7.
ReplyDeleteHi Venkat,
DeleteThats how PeopleSoft works internally , the numeric codes shown to users are not always the same taken while internal processing. psdstsrv picks the content and posts only when diststatus is 8 in PS_CDM_LIST . the codes shown in psprcsrqst or psprcsque vary for few values. Try this:
Make a process go in not posted.
fix the issue, put a frontend trace and resend the content. You will see there it fires the exactly same 3 queries and updates the diststatus as 8 in ps_cdm_list table.
Try this out and post your comments !!!