Get rid of orphaned db locks

[LancasterGIS]

When I check the locks on the database there are several that are state types with shared locks  and one with an exclusive lock. There are not users/owners associated with these locks. I can only assume that this is why, after a compress, hundreds of adds and deletes tables still have data - some have large amounts of data 3+GB. How do I get rid of these locks? Disconnect user fails. If this is not the problem with the compress not reconciling all the adds/deletes tables, if anyone has other ideas that would be great.

The db has no versions or replicas except the default version. All users were out of the system when the compress was done.

[LancasterGIS]

I have reached out to support. True about large tables in the database not being an issue for the database, but there are in the adds tables, not the parent table, which does not seem right.

[dgiersz_cuyahoga]

What did support say? We are experiencing the same thing. Wondering if we can just trucate the lock tables in the database.