Table SDE_LOGFILE_DATA

[GundarsStarks]

Hi!

Table SDE_LOGFILE_DATA has grown very large ~451 776 205 rows. And as it seems it slows down database performance, because of a number of running DELETE FROM [].SDE_logfile_data processes.
Is it possible and safe to clean the SDE_LOGFILE_DATA table(truncate or delete?) ?
Configuration: linux, Oracle10g, ArcSDE 9.2, using Shared log files.

Thanks,

Gundars

[VinceAngelo · Accepted solution]

You can often safely TRUNCATE the SDE_LOGFILES/SDE_LOGFILE_DATA pair if
you don't have any active applications dependent on the contents (no sessions
active for the user) *and* you haven't made any permanent logfiles you won't
mind losing in the process.  Make sure you TRUCATE or DROP  both together.

- V

[yockee]

If I do TRUNCATE on both tables, do I have to stop the map/feature service first ? Which one should be truncated first ? I have similar issues where the table is in production.

If I have so many log tables, should I truncate all of them ? 

[George_Thompson]

It looks like those tables / files are used by users on the Enterprise Geodatabase. I am not sure I would truncate those table, unless all connections are not active and closed.