MAR file_hash.db size exceeds max db size set in MAR policy
We are seeing instances of the file_hash.db file growing well past the limit of 60 MB set in the MAR File Hashing policy. In one case the size of the file was 123 GB. Has anybody run into this? How do we clean up the database so it doesn't take up so much disk space?
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.