Imsrestore Fails When Mailuserstatus Is Set to Inactive
(Doc ID 2660894.1)
Last updated on APRIL 22, 2020
Applies to:Oracle Communications Messaging Server - Version 8.0.2 and later
Information in this document applies to any platform.
When a store backup taken from the host running Messaging Server version 188.8.131.52.20180629 is being restored on a host running Messaging Server version 184.108.40.206.20190730, imsrestore fails with following error:
Performing reconstruct of mailboxes makes no difference in behavior.
It seems that imsrestore is completely bailing out after searching LDAP for the entry on the target side and finding it, but with mailuserstatus: inactive. So now it seems that if mailuserstatus is set to inactive in the target LDAP entry, imsrestore gives up and rehostuser fails. When this issue was first noticed, imsrestore was just logging an error
This process worked without issue for years until 8.0.2! In 8.0.2, when rehostuser calls imsrestore on the target store, imsrestore performs an ldapsearch against the UG ldap for that partition to validate that the account is present in LDAP before restoring, but because the mailuserstatus attribute is set to inactive, it doesn't find the entry and logs an error about the missing LDAP entry - even though the LDAP access logs show that an entry was returned for the search. Their (customer's) customized 'mailmove' code sees that error log and aborts the move, thinking it's failed, even though rehostuser would go on to re-create the LDAP entry and complete the move.
Prior to 8.0.2, the behavior was exactly the same, except that the inactive status of the LDAP entry on the target side didn't prevent imsrestore from seeing that the entry was present and it didn't log an error about it being missing. It just went on and performed the restore. However, with 220.127.116.11.0, imsrestore does not complete.
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