[DB Cleaner on Steroids] Inconsistency on Module_PublicElement (OSSYS_MODULE_PUBLICELEMENT)
db-cleaner-on-steroids
Web icon
Forge component by Miguel 'Kelter' Antunes
Application Type
Traditional Web
Service Studio Version
11.53.20 (Build 61431)
Platform Version
11.13.0 (Build 31107)

Hi!

I have created a post recently where we are discussing the clean-up of old version modules using DBCleanerOnSteroids and the High Records on Module_PublicElement Database Entity from Service Center (OSSYS_MODULE_PUBLICELEMENT) 

Module_PublicElement Increasing Database (OSSYS_MODULE_PUBLICELEMENT)

As part of a further investigation and my last comments there, it is related to this Forge Asset

And as stated on my last Comment
or I'm missing any step on using DBCleanerOnSteroids 
or DBCleanerOnSteroids doesn't take this Database Entity in consideration

Too even more details this is what contains the Database Entity in question, where I believe that "Producer_SS_KEY" Entity Attribute is the Foreign Key to the Espace Module Version Database Entity


Greetings,
Pedro Vieira

Solution

Hi!

As part of the platform server release notes I discovered that this table is also clean-up by Service Center it self

The Timer UnusedElements_Cleanup should clean up the records from the OSSYS_MODULE_PUBLICELEMENT table, but it was failing with a timeout. This could impact publishing from Service Studio. (RPM-2241) 

This timer is executed automatically at day 1 of each Month

Our database shines now!

Thanks for the amazing component!

Greetings,
Pedro Vieira

Hi, 

With a bit more investigation using SQL Sandbox:

Before Deleting the Module and his Versions:


After Deleting the Module and his Versions:


OutSystems uses a Week Reference between "{Espace_Version_Producer}" and "{Module_PublicElement}"
So, when deleting modules versions, the entries on {Module_PublicElement} (OSSYS_MODULE_PUBLICELEMENT) are not being deleted from the database when using the DBCleanerOnSteroids

Greetings,
Pedro Vieira

Hey Pedro!

Nice finding! We're using the internal DBCleaner_API, probably there's the bug. But I'll take a look into your findings and see what can be done in the component. Thanks for all this info!

Solution

Hi!

As part of the platform server release notes I discovered that this table is also clean-up by Service Center it self

The Timer UnusedElements_Cleanup should clean up the records from the OSSYS_MODULE_PUBLICELEMENT table, but it was failing with a timeout. This could impact publishing from Service Studio. (RPM-2241) 

This timer is executed automatically at day 1 of each Month

Our database shines now!

Thanks for the amazing component!

Greetings,
Pedro Vieira

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.