I am not sure of the RDBMS being used, but going to guess for Oracle.
Did the user do any of the bottom two below:
- You (or a tool or other process you run) create a selection set of a specific size—more than 100 records in ArcMap; more than 1,000 records in ArcGIS Pro; more than 1,000 records when Object IDs are requested from a feature service.
- You reconcile or post to a versioned geodatabase.
- A client application checks out data for disconnected editing.
The log file table should be cleaned out when the user / application disconnects from the geodatabase. I am not sure the # of records in the table is an issue, as long as performance decreases are not experienced.
Yes, we are on Oracle ( sorry I should have led with that). And we are on ArcMap 10.6.1.
The user does often select more than 100 features. The user also reconciles and posts to a versioned geodatabase often. We don't do disconnected editing.
It looks like this users log files are not getting deleted when the user disconnects. I now show him with 2,000 more rows in this table and no active connections to the database. I checked the connections with ArcCatalog and on the Oracle backend. The other heavy users have no row in the log data table, so the problem appears to limited in scope at this time.
Any other bright idea's? I am thinking it might be time for an Esri case.
I would agree that contacting technical support would be best.