E-PRCS: PRCSYSPURGE Process Taking a Few Hours To Run And Generating Large STDOUT file
(Doc ID 2496429.1)
Last updated on OCTOBER 30, 2019
Applies to:PeopleSoft Enterprise PT PeopleTools - Version 8.56 and later
Information in this document applies to any platform.
On : PeopleTools 8.56 version, Process Scheduler
Purge process,PRCSYSPURGE, is taking a few hours to run and generates a large log file every time it is run.
Total number of reports to be removed from Report Repository XCOPY: 1897962 (65,301)
Deleting Report Repo. Dir.: FSPROD/20081206/1328788.
Deleting Report Repo. Dir.: FSPROD/20081206/1328789.
Deleting Report Repo. Dir.: FSPROD/20081206/1328790.
Deleting Report Repo. Dir.: FS92MIDR/20190110/4886153.
Deleting Report Repo. Dir.: FS92MIDR/20190110/4886154.
Deleting Report Repo. Dir.: FS92MIDR/20190110/4886155.
File: E:\pt85606b-retail\peopletools\src\pspsm\psmrptmgrarchive.cppSQL error. Stmt #: 1826 Error Position: 0 Return: 805 - [Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot insert duplicate key row in object 'dbo.PS_CDM_LIST_PURGE' with unique index 'PS_CDM_LIST_PURGE'. The duplicate key value is (1682332, 3232559).
Failed SQL stmt: INSERT INTO PS_CDM_LIST_PURGE (PRCSINSTANCE,CONTENTID,SERVERNAMERUN,DISTNODENAME,OUTPUTDIR) SELECT A.PRCSINSTANCE,A.CONTENTID,' ',A.DISTNODENAME,A.OUTPUTDIR FROM PS_CDM_LIST A WHERE (EXPIRATION_DATE <= :1 OR A.DISTSTATUS = '6') AND A.DISTNODENAME <> :2
Step 'ArchRptM' of section 'ReptMgr' in program 'PRCSYSPURGE' completed normally (65,310)
There is a "Cannot insert duplicate key row" error occurring which indicates a data contention issue for the "PS_CDM_LIST_PURGE" record used to store temporary report purge data in the affected environment. It can also be seen that the purge process is attempting to purge around 1.9 million reports going all the way back to the year 2008 based off the date-based folder names being used. The sheer volume of reports to purge would explain the amount of time it is taking to run the process and the accompanying error could explain why it continues to occur whenever the purge is run.
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