Sequence on MsgNo Doesn't Match with that of Internal-Date
(Doc ID 2205234.1)
Last updated on NOVEMBER 06, 2019
Applies to:Oracle Communications Messaging Server - Version 7.0.5 and later
Information in this document applies to any platform.
From the imcheck output (as illustrated in the extract below), it can be observed that messages do not appear in the correct order of 'MsgNo'.
For instance, in the extract below, it is seen that while MsgNo. 2936 corresponds to Internal-Date '20070606183444', messages with a lower MsgNo (such as 2890), corresponds to Internal-Date '20160914212022'.
What is it that causes such disorder in the Internal-Date / MsgNo sequence? Is it an expected behavior?
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