The “DeletePercentage” setting defaults to “10” which selects 10% of the rows that are not protected by the “KeepInterval” setting. The “DeletePercentage”, “DeleteAllThreshold” and “MaxRowsToDelete” settings are related to each other. When this setting is set to “1” then all the records are deleted apart from those protected by the “KeepInterval” setting above. The day the Background Jobs are being ran is also kept from being deleted. It is the number of days that will not be deleted before the day the Background Jobs are being ran. The “KeepInterval” setting defaults to “5d”. They have five settings, and is more complicated than the REFRDEL_CLEANUP task. Both of these jobs have the same set of control parameters, which are different to the REFRDEL cleanup task from the last article. The CLEANUP_PRMQUEUE task removes completed EPS and project security tasks, which were nowhere near the same number of records, but was still configured such that it doesn’t remove all the unwanted records every week. This removes records from the USESSAUD table and was standing at over 32 million records for our client. The CLEANUP_USESSAUD task removes old audit records for user sessions. Fixing CLEANUP_USESSAUD and CLEANUP_PRMQUEUE These are configured to delete just 1 day’s worth and we’ll show how to change them. In this article we’ll discuss the set of parameters that are used by other tasks in the Background Jobs. That used one set of parameters for removing the records. One of our customers had over 70 million records in their REFRDEL table. The first article showed how to change the settings for the REFRDEL table to remove the unwanted records. The Background Jobs come along once a week and are supposed to delete all these records.ĭespite there being 7 days in a week, the Primavera P6 EPPM Background Jobs are configured to delete just 1 day per week, leaving 6 days of deleted data inside the database. Primavera P6 doesn’t actually delete these records, choosing to mark them as deleted instead. These are the records of deleted items such as Activities. In the first article on this subject that you can read here, we introduced the role of the Primavera P6 EPPM Background Jobs which included the removal of records from the database that were no longer required.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |