Relinker MD5 .msg Files: How Do They Get Purged? Why Is Space Not Freed Up?
(Doc ID 1466857.1)
Last updated on OCTOBER 31, 2019
Applies to:Oracle Communications Messaging Server - Version 7.0.0 and later
Information in this document applies to any platform.
I ran the Messaging Server relinker and have a couple of questions about how it works - also see Reducing Message Store Size Due to Duplicate Storage.
1. From the following excerpt in the above link:
If the relinker command line mode is used exclusively, and not the run-time option, it is necessary to purge the digest repository (=md5), otherwise messages purged in the store (=user) will not become available disk space since they still have a link in the digest repository (they become orphaned). If you are just performing a one-time optimization of the store—for example after a migration—you can run relinker once, then delete the entire repository with relinker -d. For repeated purging during migration, it is sufficient to just run the relinker command repeatedly, since each time it runs it also purges the expired or orphaned messages from the repository.
What happens to the .msg files in the =md5 directory? Do they get purged?
2. Below is the output from running the relinker:
From the above output, why hasn't the "Space used" or the "Space savings from single-copy" changed to reflect a gain in space?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|What happens to the .msg files in the =md5 directory? Do they get purged?|
|Background about how this works|
|Why hasn't the "Space used" or the "Space savings from single-copy" changed to reflect a gain in space?|