Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-2215554.1
Update Date:2017-06-20
Keywords:

Solution Type  Technical Instruction Sure

Solution  2215554.1 :   We Are Observing Abrupt Values In Almost All PCRF Reports.  


Related Items
  • Oracle Communications Policy Management
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Broadband Network Solutions>SN-SND: Tekelec Policy
  •  




In this Document
Goal
Solution
References


Created from <SR 3-13052179731>

Applies to:

Oracle Communications Policy Management - Version POLICY 11.5.0 and later
Information in this document applies to any platform.

Goal

On : POLICY 11.5.0 version, Wireless (Production)
Abrupt values are being shown in almost all PCRF reports.

Solution

Below is the RCA for this issue.

ISSUE:
Customer is observing abrupt values in almost all PCRF reports. Customer has shared DiameterEventTriggerstats.xlsx to highlight the problem. This file has negative values for triggers which does not look right.These negative values are associated with timestamps which have 1sec difference,
when compared to data collected at other times throughout the day.

ROOT CAUSE:

MPEs insert stats into comcol tables and these stats are merged into CMP comcol tables. Sometimes performance issues cause this insertion ti write the end-timestamp with additional seconds (1 second or more is possible)
and the same gets copied to CMP tables.So, when the OSSI query has the end time stamp with accurate time like 14:15:00Z, the stats from some MPEs with additional seconds end
time cannot be extracted from the OSSI query as the time stamp has the additional 1+ second. (Our code mechanism for OSSI response is that returning
the stats exactly between the start time and end time in OSSI query, so if the end time of stats for some MPEs has additional seconds in comcol, these
stats will not be returned in OSSI response although these stats belong to the same interval.).

.
WORKAROUND
The only workaround is for the customer to modify their OSSI query with end time like 2016-xx-xxTyy:yy:59Z so the query can retrieve as many as possible
stats from CMP in case the thread mentioned above added additional seconds to the timestamp.

FIX:
This issue is fixed in 12.2

References

<BUG:24324549> - STATS FILE GENERATED HAVE RANDOM 1SEC TIME DIFFERENCE

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback