What Did Rehostuser Mean By "Source mailbox reset successfully."?
(Doc ID 2592589.1)
Last updated on MAY 10, 2021
Applies to:Oracle Communications Messaging Server - Version 8.0.2 and later
Information in this document applies to any platform.
On : Oracle Communications Messaging Server 188.8.131.52.20190826 version, Message Store
We had an LDAP replication delay cause a problem with a rehostuser -e.
The first "half" took 3 hours.
The seconds "half" took about 3 minutes (thanks to the -e option).
We have tracked thru the LDAP access and audit logs and there is clearly a replication delay. The replication of the change of the mailUserStatus from defer to active and the mailhost change did not arrive at the LDAP replica used by the source mailstore until about 30 seconds AFTER rehostuser stopped checking.
But our question is...
The second half of the rehostuser operation ended with:
Qn1: What does "Source mailbox reset successfully" mean?
The message seems to indicate that it is setting the user back to the original mailhost, but we do not see any trace in the LDAP logs of any attempt to change anything at that point.
What is rehostuser supposed to be doing in a case like this?
Qn2: Does rehostuser also check, wait, check again when changing the user to defer at the beginning?
Qn3: When it is initially setting the user to defer, and is there any retry?
Or does it make the change, check, and if it hasn't changed then fail immediately without any retry?
Or does it not check?
We are pursuing this because in the same incident, after the rehostuser completed, we found more mail on the source system than on the target system.
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