Oracle Communications Performance Intelligence Center (PIC) Software
 
Oracle Communications Performance Intelligence Center (PIC) Software
 

PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec PIC
 

When there are Enriched dictionary in a Sessions View, the trace contains only the xDR used to launch the trace and do not find the other related xDRs

In this Document

Symptoms

Cause

Solution

References

Created from <SR 3-11478403781>

Applies to:

Symptoms

The trace feature does not provide a complete result despite the fact that couplet exists (this point must be verified prior to continue investigation). Indeed, instead of showing all xDRs related to the first xDR, only one xDR is displayed: the one used to launch the trace.

EPIs are also well defined.

Cause

The enriched dictionaries are not well managed for trace feature.

When the Protrace.log file is activated to log information related to ProTrace activities, following suspicious lines can be found that point out:

1. A time tolerance issue:
   (BuilderMetadata.()) Could not load Trace Builder for classId=229699. Using default values. Cause is:
   (BuilderMetadata.loadTimeTolerance()) Could not load time tolerance for protocolId=null. Using default values. Cause is:
   (BuilderMetadata.()) Could not load Trace Builder for classId=245282. Using default values. Cause is:
   (BuilderMetadata.loadTimeTolerance()) Could not load time tolerance for protocolId=null. Using default values. Cause is:
   The protocolId=null makes impossible to get time tolerance values and the system does not query the sessions with time boundaries allowed.
2. Or a bad EPI management for enriched dictionaries:
   2015-11-17 16:53:28,998 - INFO - tekelec@127.0.0.1:7003 - (TraceEngine.startTrace()) START startTrace() - XDR-based
   2015-11-17 16:53:28,998 - INFO - tekelec@127.0.0.1:7003 - (TraceEngine.generateInitialXDR()) DictionaryManager generated initial XDR
   2015-11-17 16:53:29,191 - DEBUG - tekelec@127.0.0.1:7003 - (QueryUtils.createInitialFilter()) LTE DIAMETER S6 TDR_ENR_1.2.1 initial filter created
   2015-11-17 16:53:29,191 - INFO - tekelec@127.0.0.1:7003 - (TraceEngine.generateInitialQuery()) 0 EPI filters created from initial filter
   2015-11-17 16:53:29,191 - INFO - tekelec@127.0.0.1:7003 - (QueryUtils.mergeFilters()) Merging filters. 0 filters on the input.

Both problems make that queries to look for related xDRs are not generated and only the xDR used to launch the trace is found.

Solution

Issue comes from identified <Bug:21945722>.

For PIC 10.1.5, a patch is available.

The solution to fix is to download and deploy the patch to get full traces results. More information in <Document:2058722.1>

References

This solution has no attachment