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-72-1955425.1
Update Date:2016-09-20
Keywords:

Solution Type  Problem Resolution Sure

Solution  1955425.1 :   UMTS IuCS and IuPS Interprotocol Correlation Within ProTrace MOP Guide  


Related Items
  • Oracle Communications Performance Intelligence Center (PIC) Software
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec PIC
  •  


ProTrace limitations with builders generating several xDRs with same Transaction Id for a single "transaction".

In this Document
Symptoms
Cause
Solution


Created from <SR 3-9822242331>

Applies to:

Oracle Communications Performance Intelligence Center (PIC) Software - Version 7.5 to 9.0.4 [Release 7.0 to 9.0]
Tekelec

Symptoms

Tracing does not take into account all xDRs generated by the builder. A simple query shows several xDRs involved in an operation, where the tracing feature shows only one.

Cause

The discard feature in ProTrace is used to avoid displaying several time the same xDR in a trace. But the mechanism is partly based on "Transaction Id." field and it has the same value for all xDRs involved in the same "transaction".

Because of this, the trace is not complete and it generally happens that only 1 xDR is displayed. 

Solution

Moreover than just configure the system for tracing (like Sessions View creation, enabling NAS PDU option for Iu-C TDR / Iu-P TDR and couplets creation), upgrading into PIC 10 offers the possibility to manage complete traces.

In PIC 10, the mechanism to identify and discard duplicated xDRs in the trace was changed and traces are complete, even if all xDRs have the same Transaction Id.


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