![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||
Solution Type Technical Instruction Sure Solution 1933173.1 : IxpBuild or IxpOperate Logs Message Same Data Timestamp Amount Too High
In this Document
Created from <SR 3-9571893941> Applies to:Oracle Communications Performance Intelligence Center (PIC) Software - Version 9.0.0 and laterTekelec GoalWhy are we getting below message in IxpBuild logs for some sessions : 0905:084403.236 DTS2 Stream 'B_MAP' same data timestamp amount too high: 09/05/2014 8:43:56.0 [13281/DtsProducerBuffer.cpp:241]
0905:084403.336 DTS2 Stream 'B_MAP' data with same time: 09/05/2014 8:43:56.0 dropped [13281/DtsProducerBuffer.cpp:228] 0905:084403.339 IXP3 Send alarm: xDR Loss (major event) Stream = B_MAP [13281/DmAlarm.cpp:214] 0905:084403.913 DTS2 Stream 'B_MAP' same data timestamp total amount dropped: 4782240(Bytes) [13281/DtsProducerBuffer.cpp:250] 0905:084403.942 IXP3 Send alarm: xDR Loss clear (clear event) Stream = B_MAP [13281/DmAlarm.cpp:214] Or in IxpOperate: 0420:114625.837 OPR2 pOutStream->StoreData failed -> data lost [41895/OpPluginsSequence.cpp:1117]
0420:114625.837 DTS2 Stream 'O_outpu' same data timestamp total amount dropped: 157935(Bytes) [41895/DtsProducerBuffer.cpp:250] SolutionIf session have lots of timer xDR in the session, this article will explain how to reduce the risk of having this issue. Following points are usually enough in most cases:
Finetune DTS parameters No|DtsMaxDataTimeSDrop|25|
No|DtsMaxDataTimeSWarn|20| The values for these 2 parameters are the default ones so they need to be adjusted depending on the situation. No|DtsMaxDataTimeSDrop|50|
No|DtsMaxDataTimeSWarn|40| All IxpBuild processes of the IXP subsystem must be restarted to have the changes applied. Attachments This solution has no attachment |
||||||||||||||
|