My Oracle Support Banner

The relinker =md5 Directory is NOT a Central Repository for the Message Store (Doc ID 1956355.1)

Last updated on SEPTEMBER 21, 2018

Applies to:

Oracle Communications Messaging Server - Version 6.0.0 and later
Information in this document applies to any platform.

Goal

A few customers seem to have come to the misunderstanding that the =md5 directory is the central repository for the message store.

For example, see the discussion about Disabling Hard Linking (Single Message Strategy) in the Messaging Server OTN forum.

This article explains the purpose of the =md5 directory in each partition, when you should use the relinker feature, when you should stop using it, and don't forget to clean up.

Solution

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
Goal
Solution
 The relinker documentation
 Not intended to be a central repository
 The single-copy nature of the store and how hardlinks work
 To see the single-copy feature in action
 The difference between hard and soft links
 The du command will show twice the space used
 The space is freed when the final link is removed
 The relinker =md5 directory is just another link
 The relinker feature exists to repair a situation which should never exist
 Enable relinker when you know you will being doing something that will cause the problem
 Or use command line relinker to fix it after the fact
 Disable relinker and clean up when you are done
 Isn't it stored which does single-copy?
 The short answer is: No.
 stored does not do the relinking either
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.