-
Change the prop table cleaner default properties in
alfresco-global.properties:
-
Enable the new prop cleaner
algorithm:
system.prop_table_cleaner.algorithm=V2
-
Set the prop cleaner to read
only:
system.delete_not_exists.read_only=true
-
Set the prop cleaner
timeout:
# This will stop the next batch from being processed if the elapsed time from the job start is greater than 1 hour system.delete_not_exists.timeout_seconds=3600
-
Enable the new prop cleaner
algorithm:
- Restart the application server.
-
Open a web browser.
- Go to <alfresco_ip>/alfresco/s/enterprise/admin/admin-log-settings.
-
Enable debug logging to see the amount of data that would be deleted by
the algorithm. Change the log setting to DEBUG for
package
name:
org.alfresco.repo.domain.schema.script.DeleteNotExistsExecutor
- Go to <alfresco_ip>/alfresco/s/enterprise/admin/admin-scheduledjobs in a web browser, and execute the propTablesCleanupJobDetail job.
-
Check the logs to see which values would be deleted from each
table:
alf_prop_root alf_prop_value alf_prop_string_value alf_prop_serializable_value alf_prop_double_value
You should see something like:
[org.alfresco.repo.domain.schema.script.DeleteNotExistsExecutor] [DefaultScheduler_Worker-10] Script would have deleted a total of X items from table alf_prop_root.