[Logs Management] After cleaning, records count is updated (to 0) but occupied space is not

[Logs Management] After cleaning, records count is updated (to 0) but occupied space is not

  
Forge Component
(6)
Published on 12 Feb by Carlos Alfaro
6 votes
Published on 12 Feb by Carlos Alfaro

Hi!

Environment: Enterprise Cloud.

After cleaning up a big amount of logs, the record count is updated to 0 but space occupied is not also 0. See screenshot.

Is there any other process that needs to run for the occupied space to be updated, since this is a cloud environment?

This is my current view on the extension logs:

total record count: 96

space occupied (kb): 397,288!!

Thanks for any additional info that you can provide.

Tiago Bernardo

Hello Tiago,

One question, the database is SQL or Oracle?

The occupied DB space is read directly from the system tables, there is no background process to update these numbers.

Thank you.

CA

Generally, database maintenance tasks should clear that out within a week