nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Finde mehr Beiträge mit dem Tag

Accepted answers

VinceAngelo

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

All comments

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.

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 ?

VinceAngelo

Nimm an der Unterhaltung teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.