| Asset ID: |
1-71-1929772.1 |
| Update Date: | 2017-04-24 |
| Keywords: | |
Solution Type
Technical Instruction Sure
Solution
1929772.1
:
How to Restart Dsapi Process to Solve PDU Load Issues in ProTrace and Which Log to Gather?
| Related Items |
- Oracle Communications Performance Intelligence Center (PIC) Software
|
| Related Categories |
- PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec PIC
|
In this Document
Created from <SR 3-9647981641>
Applies to:
Oracle Communications Performance Intelligence Center (PIC) Software - Version 10.0.0 and later
Information in this document applies to any platform.
Goal
Restart dsapi and gather logs for Oracle Support analyses.
Solution
- Stop dsapi as cfguser:
pm.set off dsapi
- Wait for process to stop
- Start dsapi
pm.set on dsapi
- Wait for process to start before retrying to display PDU in ProTrace
It is important to gather dsapi logs on IXP server which hosts IxpStore process of the session to analyze them and find root cause.
List of log files to gather before and after dsapi process restart:
- In /var/TKLC/log/ixp:
- DsapiContext.log
- DsapiCplusplusServer.log
- DsapiError.log
- DsapiJavaServer.log
- In $PROC:
- In /var/tmp:
- Client.log
- EtherDecoder.log
- Server.log
- stderr.txt
- WiresharkServer.log
Attachments
This solution has no attachment
